Post status explained in one line each: Draft means the post is saved but not public. Pending (called Needs Review or Pending Review on some platforms) means the writer considers it finished and someone else has to approve it. Scheduled means it is approved and will go live by itself at a set time. Private means it is published but hidden from the public. Published means anyone can read it.
Most small teams use two of those, Draft and Published, and treat the rest as clutter. That works until a freelancer’s finished piece sits in Draft for a week because nobody knew it was done, or a scheduled post goes out with a typo at 6am while everyone is asleep. The statuses are small, but each one is a promise about who acts next. This guide covers what each status means, what it is called on five common platforms, and the part the help pages rarely spell out: what each status does not do.
Platform labels below were checked against each vendor’s own documentation on September 23, 2026. Labels and behavior change between releases, so confirm them against your platform before building a process around them.
The four statuses in plain terms
A status is a label the CMS attaches to a post that decides two things: who can see it, and what the software will do with it next. The table below is the platform-neutral version, with Published included as the baseline.
| Status | What it tells the team | Who can see it | What happens next |
|---|---|---|---|
| Draft | “Not finished. Still mine.” | The writer and anyone with editing rights | Nothing, until a person changes it |
| Pending / Needs Review | “Finished. Your turn.” | Editors and admins | An editor approves, schedules, or sends it back |
| Scheduled | “Approved. Going out at a set time.” | Editors and admins, until it goes live | The platform publishes it automatically |
| Private | “Live, but not for the public.” | Admin-level users (varies by platform) | Nothing; it stays hidden until changed |
| Published | “Live.” | Everyone | Nothing, until someone edits or unpublishes it |
The key column is the last one. Only one status, Scheduled, makes the software act without a person. Every other status waits for somebody. That is the whole reason scheduled posts deserve more care than any other state, and it comes up again below.
Post status names on WordPress, Ghost, Squarespace, Wix and Webflow
The concepts are shared across platforms. The names are not, and some platforms leave a status out entirely. Here is how the same ideas map, as each vendor documents them.
| Idea | WordPress | Ghost | Squarespace | Wix Blog | Webflow CMS |
|---|---|---|---|---|---|
| Not finished | Draft | Draft | Draft | Draft | Draft |
| Ready for approval | Pending | No built-in status | Needs Review | Pending Review | No built-in status |
| Set to go live later | Scheduled (stored as “future”) | Scheduled | Scheduled | Scheduled | Scheduled |
| Live but restricted | Private | Post access setting, not a status | Not listed as a post status | Not listed as a post status | Not listed as an item status |
| Live | Published | Published | Published | Published | Published |
| Platform extras | Trash, plus custom statuses added with code | Sent (email-only newsletter) | None beyond the four | Rejected posts revert to Draft | Changes in draft, Queued to publish, Archived |
A few details worth knowing from that table:
- WordPress lists eight built-in statuses in the WordPress.org Post Status documentation (read September 23, 2026), including two you will rarely see in the admin: auto-draft and inherit. A scheduled post is stored internally as “future.” Adding your own statuses is possible but requires code or a plugin.
- Ghost keeps unpublished work in draft. Its Admin API documentation describes a scheduled post changing to published at its set time, or to “sent” if it was delivered only as an email newsletter. Who can read a post is handled by a separate post access setting (public, members only, paid-members only, or specific tiers), not by status.
- Squarespace lists four blog post statuses in its help center: Draft, Needs Review, Scheduled and Published. It describes Needs Review as useful when a senior editor reviews several authors’ work.
- Wix Blog puts submitted posts on a Pending Review tab. Its help center says Editors and Owners get an email when a writer submits a post, and a rejected post goes back to draft with an email to the writer.
- Webflow CMS items carry more states than most platforms, including “Changes in draft” and “Queued to publish,” which trips up writers coming from a blog-first CMS.
If your platform has no review status at all, that is not a flaw you can fix with discipline alone. It is a gap you track somewhere else, which is covered below.
What each status does not do
This is the part platform documentation mostly leaves out, because each help page explains its own button, not the assumptions a team brings to it.
Draft does not always mean offline
On a post that has never been published, Draft means nobody outside the team can see it. On a post that is already live, it depends on the platform. On WordPress, moving a published post back to Draft takes it off the public site. On Webflow, the opposite is true for live items: the Webflow developer documentation on CMS publishing (read September 23, 2026) says that when a live item is set to draft, “it remains published on your site,” so you can edit safely without changing what visitors see. Webflow shows this as “Changes in draft,” and unpublishing is a separate action.
A writer who learned “Draft means hidden” on one platform can leave a post live on another while believing it is down. If your team works across more than one CMS, write down which one does what.
Pending does not notify anyone unless the platform says so
Pending is a label, not a message. Wix documents an email to Editors and Owners on submission. The WordPress.org post status page describes pending as awaiting a user with publishing rights and says nothing about notifying that user. Squarespace’s description of Needs Review does not mention a notification either. Unless you have confirmed your platform or a plugin sends one, assume a pending post is invisible to the editor until they go looking.
The practical fix is dull and effective: the writer moves the post to Pending, then tells the editor in whatever channel the team already uses. The status records the state. The message moves the work.
Scheduled does not wait for anyone
A scheduled post publishes at its set time whether or not anyone is watching, and whether or not something inside it is still wrong. On Ghost, the Admin API documentation states that at the scheduled time the post is published, email newsletters are sent where applicable, and the status changes to published. That means a scheduled Ghost post can reach subscribers’ inboxes, where a later fix to the web version will not follow it.
Two more things catch teams out. The time is read from the site’s configured time zone, which Ghost documents under Settings, General, not from the writer’s laptop. And a scheduled post has passed the last point where a human was guaranteed to look at it. Treat Scheduled as the end of review, not a parking spot.
Private is not a security feature
Private hides a post from the public, but it is still a published post inside your CMS. The WordPress.org documentation describes private posts as viewable only to users at Administrator level. Ghost’s closest equivalent, members-only or paid-members-only access, is built to restrict reading to subscribers, not to keep content secret from people you have invited.
Private is fine for an internal reference page or a post you want to pull from public view while you decide what to do with it. It is the wrong place for anything confidential, such as a client’s unreleased announcement, because anyone with the right role can open it.
Draft vs Pending: the distinction most small teams skip
If a team uses only two statuses, the one it drops is usually Pending, and that is the one that carries the most information. Draft says “still mine.” Pending says “done, your turn.” Without Pending, a finished draft and a half-written one look identical in the post list, and the editor has to open each one or ask.
This matters most with freelancers. A freelancer who cannot publish has no way to signal “finished” inside the CMS except through a review status. On WordPress, a user who can edit but not publish sees a “Submit for Review” button instead of “Publish,” and pressing it sets the post to pending. That is the platform doing half your handoff for you, if you let it.
Pending also only works when it points at one person. A review status that any of three editors might pick up tends to be picked up by none of them. The case for naming a single final approver is made in the one-final-approver rule that fixes most broken workflows, and it applies directly here: whoever owns approval owns the Pending queue.
How post statuses map to your workflow stages
A CMS usually offers four or five statuses. A real editorial process has more stages than that: assigned, drafting, editing, fact-check, approved, scheduled, published. Statuses and stages are not the same thing, and trying to force one into the other is where confusion starts. If you have not named your stages yet, start with the stages every publishing process has, named or not, then map them onto statuses like this:
| Workflow stage | CMS status to use | Who moves it |
|---|---|---|
| Assigned, drafting | Draft | Writer |
| Writer finished | Pending / Needs Review | Writer |
| Editing, fact-check | Pending, or Draft if sent back | Editor |
| Approved | Scheduled or Published | Final approver only |
| Live, then pulled | Draft (or Private, where available) | Final approver only |
Three conventions keep this map working on a team of two to five:
- Write down what each status means for your team, in one sentence each. “Pending means finished and waiting for the editor” is a rule. “Pending means sort of done” is not.
- Only the final approver moves anything to Scheduled or Published. Writers stop at Pending. This is the single rule that most reduces surprises.
- Check the Scheduled list on a fixed day each week. It is the only list where the software acts on its own, so it is the one worth reviewing on purpose.
A fuller version of this setup, including who does what on a very small team, is in the editorial workflow for a team of two to five.
When your platform has fewer statuses than you need
Ghost and Webflow have no built-in review status. That does not make them unusable for teams with editors. It means the review stage has to live outside the CMS, in a shared document or tracker, while the CMS status stays at Draft until approval.
That split is workable, but it has one weak point: the tracker and the CMS can disagree. A post marked “approved” in the tracker may still be Draft in the CMS, or the reverse. Pick one source of truth for “is this live,” and it should be the CMS, because that is what readers see.
If a review status is a hard requirement for your team, test for it before you commit to a platform rather than after. It belongs on the list of questions in choosing a CMS for a content team, next to whether your writers can publish without help.
Frequently asked questions
What is the difference between draft and pending?
Draft means the writer is still working on the post. Pending, called Needs Review on Squarespace and Pending Review on Wix, means the writer considers it finished and is waiting for someone with publishing rights to approve it. Neither is visible to the public.
Does a scheduled post publish automatically?
Yes. That is the defining feature of Scheduled: at the set date and time, the platform publishes the post without anyone clicking anything. On Ghost, any attached newsletter is sent at the same moment. Check the site’s time zone setting, since the schedule follows it.
Can anyone see a private post?
Not the public. On WordPress, the official documentation describes private posts as viewable only to administrator-level users. Private is a visibility setting, not encryption, so do not use it for confidential material.
How do I unpublish a post without deleting it?
On most platforms, change its status back to Draft. Webflow is the main exception covered here: setting a live item to draft keeps it published, so use the platform’s separate unpublish action instead. Confirm on your own platform before relying on either behavior.
Can I add my own post statuses?
On WordPress, yes, with code or a plugin; the core documentation describes custom statuses as something you register yourself. Squarespace and Wix document a fixed set of blog post statuses. If you need more stages than your CMS provides, track them outside it and keep the CMS status as the record of what is live.
