Choose your default publish state and stick to it
Most sites have no default publish policy
Your CMS probably lets you save things as drafts or publish them live. Good. But if you haven't decided which state new content starts in by default, you're forcing every person who touches the CMS to make that decision independently, every single time.
That's how half-finished pages go live. That's how drafts sit untouched for months because someone thought they were already published. That's how you end up with a content calendar no one trusts.
Pick a default. Write it down. Enforce it in your CMS settings if you can, or in your documentation if you can't.
Default to draft for sites with review processes
If anyone other than the original author needs to check content before it goes live, your default state should be draft. No exceptions.
This means new pages, new posts, new product descriptions—all of them start as drafts. The person who writes them cannot publish them. They save, they notify the reviewer, and the reviewer decides when it's ready.
Your CMS may let you enforce this with roles and permissions. Use them. If your CMS doesn't support that, make it the first rule in your [editorial workflow documentation](/category/production).
Default to published for single-author sites
If one person writes and publishes everything, defaulting to draft just adds a step. You're going to publish it anyway. You're the only person who will ever see the draft. Skip the toggle.
Publish immediately, review your work in preview or on the live site, and make your edits there. You'll move faster and you won't accumulate a draft queue that haunts you.
The exception: if you write in batches and schedule publication dates, keep things as drafts until their scheduled time arrives.
Don't let contributors toggle their own default
Some CMSes let individual users set their own publish defaults. Terrible idea for any site with multiple contributors. You'll end up with three people who default to draft and two who default to published, and no one will know what state anyone else's work is in.
Set the default at the site level. If your CMS won't do that, document it clearly and audit it quarterly. Check for drafts that should have been published and published pages that should have stayed drafts.
Make the default visible before you save
Your CMS should show the current state prominently—before you hit save. Not buried in a dropdown. Not in a sidebar you have to scroll to find. Right there, next to the save button, in a way that makes it impossible to miss.
If your CMS doesn't do this, add it to your training materials. Show people where to look. Make them check it twice before they save. This is not about trusting people less; it's about designing a system that doesn't rely on perfect attention every single time.
Audit your defaults once
Open your CMS. Create a new page or post as if you were a new contributor. Don't change any settings. Just type a title and save.
What state did it save in? That's your actual default, regardless of what you think it is or what your documentation says.
If that's not the state you want, fix it now. Change the CMS settings, update the documentation, and tell everyone who publishes content on your site.
Then move on. This is a decision you make once, not a policy you revisit every month. Consistent defaults prevent mistakes. Inconsistent defaults create them.