Last updated: October 12, 2026
Key Takeaways
- Draft is usually best while the post is still being written.
- Save an unpublished post as a draft with Save Draft or Draft status before exiting.
- Pending Review sends a finished post to an editor for approval before publication.
- Schedule a post by setting a future publish date, then clicking Schedule.
If you need to keep a post private for now, WordPress gives you three clean states: draft, pending review, and scheduled. This guide to how to publish to WordPress as draft, pending review, or scheduled post shows which one to use, how each status behaves, and where people trip up when a post looks “saved” but is not actually ready to publish.
Publishing status is not a cosmetic choice. It controls who can see the post, who can edit it, and when it goes live. I write about WordPress publishing workflows because the small details here create the biggest headaches later: lost edits, surprise live posts, and approval bottlenecks. WordPress.com documentation and WordPress.org support notes both describe these status controls as part of the publishing workflow. For teams, that can matter on the same day a post is due.
What each post status actually does
Draft is often the safest choice when the post is still being written. Pending review is usually the right choice when someone else needs to approve it before publication. Scheduled is the right choice when the post is finished and you want WordPress to publish it at a specific future time.
Those three states are not interchangeable, and the difference matters most in teams. A draft can usually be edited by the person who created it and by admins or editors. A pending post is a signal to reviewers that the post is ready for eyes other than the author’s. A scheduled post is locked into a publish time, which helps you plan around launches, newsletters, and social posts.
The simple rule is this: use draft for unfinished work, pending review for finished work that needs approval, and scheduled when you already know the go-live moment. If you pick the wrong one, the failure mode is predictable. Drafts never reach a reviewer. Pending posts can sit unnoticed if nobody watches the queue. Scheduled posts can go live before the final check if you set the wrong date or timezone.
A useful detail many generic guides skip: in WordPress, the button you see can vary by editor and user role. In the block editor, the post status sits in the right sidebar under the summary or status panel. In the classic editor, it usually sits near the Publish box. The workflow is the same, but the path is not.
How do I save a WordPress post as a draft?
You save it as a draft by leaving the post unpublished and choosing Save Draft or Draft status before you exit. That keeps the post private and out of the public site until you publish it manually.
In the block editor, open the post, start writing, and look at the top-right controls. If the post is new, WordPress commonly starts it as a draft until you publish it; if you are unsure how your setup behaves, check the editor status and confirm with WordPress support or your site administrator. If it is already published or scheduled and you want to return it to an unpublished state, you can change the status back to Draft from the Post settings panel.
The point of a draft is speed. You do not need a finished headline, final image, or polished excerpt to save one. This is the right state for messy work: research notes, first passes, placeholder links, and sections you still need to fact-check. If you are working alone, draft is usually the default I would choose until the post is complete.
The downside is coordination. Drafts are easy to forget because they are invisible to readers and easy to lose in a long list of content. If your site has dozens of unpublished posts, a draft can sit for weeks with no one noticing. That makes it a poor choice for work that depends on approval or a deadline.
I would not use draft for posts that are already approved and waiting on timing. That creates one more manual step later and invites delay. If the post is ready and the date matters, schedule it instead.
How do I set a post to pending review in WordPress?
You set a post to pending review by changing its status to Pending Review before publishing, then saving or submitting it so an editor can approve it.
This status exists for multi-author sites, editorial teams, classrooms, and agencies with approval workflows. It tells the next person in the chain that the draft is ready for review, but not ready for public release. In the block editor, the status is usually in the right-hand settings panel. In the classic editor, the status appears in the Publish box near Visibility and Publish options.
Pending review is a strong choice when the author should not be the final gatekeeper. That is the main strength. It creates a clean handoff and reduces the “I thought you checked it” problem. It also keeps the post out of the public site while still surfacing it for editors and admins who have permission to review it.
The trade-off is that pending is only as good as your process. If nobody checks the queue, it becomes a parking lot. If your team is tiny and one person handles both writing and publishing, pending review adds friction without adding safety. In that case, draft is simpler.
I would not choose pending review for solo sites with no editor or for sites where the person writing is also the person approving. It adds a status without adding control. I would choose it when at least two people touch the content and the final decision needs to be visible.
How do I schedule a WordPress post for later?
You schedule a post by choosing a future publish date and clicking Schedule instead of Publish. WordPress then holds the post until that date and time arrives.
This is the most useful option when you want timing to do real work for you. Launch day posts, newsletter tie-ins, time-sensitive announcements, and consistent publishing cadence all benefit from scheduling. The post can be finished today and published on a Tuesday at 9:00 a.m. without anyone logging in at that hour.
The thing people miss is timezone control. WordPress uses the site’s timezone setting, not necessarily your local clock. If your site timezone is wrong, a “9:00 a.m.” post may go live at the wrong moment. That is a small setting with a big consequence, especially for campaigns or coordinated releases. WordPress.org documents this in its scheduling guidance, and the same issue shows up in support threads from site owners who missed the published hour.
Scheduled posts are strong for discipline and weak for last-minute change. If the copy still needs review, do not schedule it yet. If the date matters but the content is not final, you risk publishing something that looked ready only because the calendar was. I would schedule only after the final proofread, image check, and link check are done.
One more caution: scheduled does not mean hands-off forever. If the subject is news-sensitive or tied to an event that may change, the post should be reviewed again shortly before the publish time. A scheduled post can still become wrong while it waits.
Draft vs pending review vs scheduled post
Draft wins for unfinished work, pending review wins for editorial control, and scheduled wins for timed publication. That is the cleanest way to think about the three statuses.
| Criteria | Draft | Pending review | Winner for [condition] |
|---|---|---|---|
| Best use case | Work in progress | Ready for approval | Draft for unfinished content |
| Public visibility | Hidden from readers | Hidden from readers | Tie for privacy |
| Who should act next | The author | An editor or approver | Pending review for team workflows |
| Risk of forgotten content | High in large sites | High if the queue is unmanaged | Draft for solo work, pending for teams |
| Timing control | None | None | Scheduled for release timing |
| Approval control | Weak | Strong | Pending review for editorial sign-off |
| Best for teams of 2+ | Sometimes | Usually yes | Pending review for multi-author sites |
| Best for solo creators | Yes | Usually no | Draft for single-author sites |
| Best for launch-day posts | No | No | Scheduled for fixed publish dates |
The table only looks simple because the choice is simple once you name the real goal. If you want safety while writing, choose draft. If you want someone else to approve it, choose pending review. If you want the post to appear later without babysitting it, choose scheduled.
A generic article often misses this: the wrong status is not just inconvenient, it changes the workflow. A draft does not alert an editor. A pending post does not publish itself. A scheduled post does not invite more editing unless you reopen it before the deadline.
The honest strengths and weaknesses of each option
Draft is the most forgiving status, but it is also the easiest to ignore. I would pick it for solo writers, rough outlines, and posts that are nowhere near final. Its strength is flexibility. Its weakness is that it offers no built-in push toward publication. That is a real cost when a site has a lot of abandoned content.
Pending review is the right answer for editorial gates, but it is only useful if someone actually watches the queue. I would pick it for sites with editors, agencies, client approvals, or student submissions. Its strength is accountability. Its weakness is delay. If the reviewer is out for 3 days, the post sits there.
Scheduled is the cleanest option for timing, but it demands accuracy. I would pick it for product launches, recurring features, holiday posts, and anything tied to a publish window. Its strength is precision. Its weakness is that it can publish the wrong version if the final pass is sloppy. A scheduled post is not a substitute for a final review.
My rule is simple: do not use scheduled as a way to avoid finishing the post. Do not use pending review when no one is responsible for reviewing it. Do not leave everything as draft just because it feels safe. Each status works best when it has a job.
Exception cases that change the choice
Draft is not always the safest choice, and scheduled is not always the smartest one. There are a few cases where I would change the recommendation.
If you are publishing on behalf of a client, pending review usually beats draft because it creates a visible approval step. A draft can disappear into email threads, but a pending post is harder to miss. This matters even on small sites with only 1 editor and 1 writer.
If the content is tied to a hard launch time — a webinar at 10:00 a.m., a product reveal, a press mention — scheduled is the only status that protects the timing. Manual publishing at the right moment is too easy to miss, especially across timezones.
If the post is being edited by several people at once, draft can become a bottleneck because everyone assumes someone else will finalize it. In that case, pending review creates a cleaner handoff, even if the post still needs small changes.
If your site is news-heavy or fast-moving, I would hesitate to schedule too far in advance. A post that is accurate on Monday can be wrong by Thursday. For that kind of site, draft plus a same-day final check is safer than a long schedule.
Choose the status that matches the next action
Choose draft if the post is still being written or revised by the same person. Choose pending review if the next step is approval by someone else. Choose scheduled if the post is finished and the publish time matters. Neither if the content is so unsettled that you cannot trust a future publish date yet.
That is the clean decision tree. The right choice is not about which status sounds more professional. It is about what should happen next, and who is responsible for making it happen.
If you are solo, draft and scheduled cover most needs. If you are on a team, pending review becomes important fast. If you run a site with editorial deadlines, all three statuses matter, but each one needs a clear rule so posts do not vanish into the backend.
What setting should I check before scheduling a post?
I would check the site timezone first, then the post date, then the final preview. The timezone is the one setting that can make a correct post publish at the wrong hour.
This is especially worth checking on sites that serve readers in more than one region. A site set to UTC, for example, will not behave the same way as one set to a local city timezone. The exact label depends on the WordPress settings page, but the issue is always the same: the scheduled time follows the site, not your laptop clock.
Also check the preview in the editor, especially if the post includes embedded media, custom blocks, or a long list of links. A scheduled post that looks fine in draft can still break after publication if the final formatting is off.
FAQ
Can I change a draft to pending review later?
Yes. You can switch a post from draft to pending review once it is ready for editorial approval.
Can a scheduled post be edited before it goes live?
Yes. You can reopen it, make changes, and reschedule it as long as it has not published yet.
Does pending review publish automatically?
No. Pending review waits for a person with the right permissions to approve it.
Why did my scheduled post publish at the wrong time?
The site timezone is the first thing to check. The scheduled time follows the WordPress settings, not necessarily your local clock.
Should a solo blogger use pending review?
Usually no. If there is no editor in the process, draft is simpler and less confusing.
Drafted with AI; not yet reviewed by a person.
