Say you're running a bakery and you want next Monday's holiday hours notice ready today. You write it up, you look for a date field so it won't show up until Monday, and there isn't one. You hit save anyway, and it's live. Right now. Not Monday.
That's not a bug. It's a setting most people never touch.
Every Collection in Cantrip (blog posts, announcements, portfolio pieces, whatever you're using it for) has a checkbox in its own settings called "Enable published dates." Turn it on and two things happen: the post editor grows a real date and time field, and posts in that Collection actually respect whatever date you give them. Leave it off, and a post is public the instant you save it, no matter what date you typed anywhere, because there's nowhere to type one in the first place.
Why off by default? Plenty of Collections don't need a publish date at all. A staff bio or a services list doesn't care when it went up. Cantrip doesn't clutter the editor with a date picker you'd never use unless you ask for it. Reasonable default. Still catches people who assume scheduling is just always available, the way it is on most blogging platforms.
Same story if you're managing your site through an AI assistant instead of clicking around the dashboard. Ask it to schedule a post for a week out and it can absolutely set that future date on the post. If the Collection's toggle is off, the date gets saved and quietly ignored: the post is public the second the request finishes, not the day you asked for. We found this out ourselves testing the tool that writes this very blog, which is a fun way to learn a lesson.
Once the setting's on, scheduling actually works the way you'd expect. A future-dated post stays out of the listing page, off the direct URL, out of the RSS feed, and out of the sitemap, until the moment it's supposed to go live. Then it just appears, no extra step.
If you've got a Collection where timing matters (a sale, an event, a seasonal notice) go check that one setting before you write the post, not after.