WordPress Development

Building an Editorial Workflow in WordPress: Statuses, Reviews and Approvals

Building an Editorial Workflow in WordPress: Statuses, Reviews and Approvals

WordPress’s publishing model was built for bloggers. You write a post, maybe save it as a draft, then publish it. There’s a “Pending Review” status for contributors who can’t publish themselves, but that’s about as far as the built-in workflow goes. A clear WordPress editorial workflow fixes this.

For a single author, that’s plenty. For a business with writers, an editor, a subject matter expert who checks facts, a legal reviewer for some topics and a manager who approves anything about pricing, it quickly gets messy. Drafts sit in limbo. Nobody knows who’s supposed to look at what next. Articles are published before the legal check, or held for weeks because nobody realised they were waiting on them.

A good editorial workflow fixes this by making the stages of content production visible and clear. This article covers how to design one and how to build it in WordPress.

Design the workflow before building it

The mistake most teams make is starting with a plugin. Plugins are useful, but they can’t decide your process for you. Start by writing down how content actually moves through your team.

Ask:

  • Who comes up with ideas, and who approves them?
  • Who writes, and who edits?
  • Which content needs specialist review: legal, medical, technical, brand?
  • Who has the final say before publishing?
  • Who actually presses publish?
  • What happens if a reviewer rejects something?

Draw it out. A typical workflow for a small marketing team might be:

  1. Idea proposed by anyone
  2. Assigned to a writer by the editor
  3. In progress while the writer drafts
  4. Ready for edit when the writer is done
  5. In edit while the editor revises
  6. Expert review for technical or regulated topics
  7. Approved and ready to schedule
  8. Scheduled for a publish date
  9. Published

Then simplify. Every stage adds friction. If expert review only applies to a few topics, make it conditional. If the editor always edits immediately, combine “ready for edit” and “in edit”.

Roles and capabilities

WordPress’s default roles map reasonably to a workflow:

  • Contributors can write and submit for review but can’t publish or upload media.
  • Authors can publish their own posts.
  • Editors can publish and edit anyone’s content.
  • Administrators can do everything.

For most editorial teams, writers should be Contributors, or Authors without publish rights, so nothing goes live without review. Editors handle publishing.

If the default roles don’t fit, you can create custom ones. A “Reviewer” role might be able to read and comment on all drafts but not edit or publish. Role management plugins make this easy without code, but you can also do it programmatically:

Run add_role once, on plugin activation, rather than on every page load, because roles are stored in the database.

Custom post statuses

The default statuses are draft, pending, private, future (scheduled) and publish. Custom statuses like “In edit” or “Expert review” make the workflow visible in the posts list.

WordPress has a register_post_status function, but its support in the admin interface is incomplete. Registered statuses don’t appear in the block editor’s status selector without extra work. That’s why most teams use a plugin for custom statuses.

Plugins such as PublishPress Statuses and similar tools add:

  • Custom statuses with names and colours
  • Status selection in the block editor
  • Filters in the posts list by status
  • Restrictions on which roles can move content into which status

When choosing statuses, keep the list short. Five to seven statuses is usually enough. Long lists become confusing, and people stop updating them.

Editorial comments and handoffs

Moving content between people needs communication: “Can you check the figures in paragraph three?” “Legal says we can’t use this claim.” Email and chat scatter that conversation away from the content.

The block editor now has built-in notes and comments on blocks, which lets reviewers leave feedback directly on paragraphs. For older setups or more structured needs, editorial comment plugins add a comment thread to each draft, visible only to the team.

Keeping feedback attached to the content means anyone picking it up can see the history.

Checklists before publishing

A pre-publish checklist catches common mistakes: missing featured image, no meta description, no category, broken links, missing alt text. The block editor has a pre-publish panel, and plugins can add custom required checks.

Useful checks for most teams:

  • Featured image set, with alt text
  • Category and tags assigned
  • SEO title and meta description written
  • At least one internal link
  • Excerpt written, if your theme uses it
  • Word count within a target range
  • Expert review completed, for topics that need it

Some checks can be enforced, blocking publication until they pass. Others can be warnings. Be careful about enforcing too much. A checklist that blocks publishing for minor issues gets bypassed by giving people more privileges, which defeats the purpose.

Notifications

People need to know when something is waiting for them. Notifications can be sent when a post changes status or is assigned to someone. Options include:

  • Email notifications, built into many workflow plugins
  • Slack or Teams messages through integrations
  • A dashboard widget showing each person’s queue

Be selective. Notify the person who needs to act, not the whole team. “The draft you were assigned is ready for your edit” is useful. “Someone saved a draft” is noise.

The editorial calendar

A calendar view of scheduled and planned content helps editors balance topics, spot gaps and avoid publishing three articles on the same day. Several plugins add a drag-and-drop calendar to the admin.

Some teams prefer to plan in external tools like Trello, Notion or a spreadsheet and use WordPress only for drafting and publishing. That’s fine, as long as status is kept in sync somewhere people actually look.

Scheduling and embargoes

Scheduled publishing is built in: set a future date and WordPress publishes it automatically. A few things to watch:

  • Make sure the site’s timezone is correct in Settings, General.
  • WP-Cron triggers scheduled posts, and on low-traffic sites it might run late. A real server cron job running every few minutes makes scheduling reliable.
  • For embargoed content, such as announcements that mustn’t appear before a specific time, check that previews and drafts aren’t accessible publicly, and that the post won’t appear in feeds or sitemaps early.

Revisions and accountability

Revisions record who changed what, which is invaluable when something goes wrong. Make sure revisions are enabled, and consider limiting their number on very large sites to keep the database tidy:

An activity log adds records of status changes and approvals, which helps for regulated content where you may need to show who approved a page and when.

Keep it light

The best workflow is the lightest one that prevents real problems. Every status, required check and approval step costs time. Review the workflow every few months with the team. Which stages cause delays? Which checks catch real mistakes? Which approvals are rubber stamps?

Remove what doesn’t help. A workflow people actually follow is worth far more than a perfect one they work around.

Workflow for regulated content

Some industries need stricter workflows. Healthcare, finance and legal services often require that certain content is reviewed by a qualified person before publication, and that the review is recorded. In those cases, the workflow becomes part of compliance, not just convenience.

Practical measures include a required “Reviewed by” field with the reviewer’s name and date, shown on the published page where appropriate; a status that only the reviewer role can set; and an activity log that records who approved what and when. Keep the record even after content is updated, because you may need to show what was published on a particular date.

Start small

If your team currently has no workflow at all, don’t jump straight to eight statuses and four approval steps. Start with roles that prevent accidental publishing and a single “Ready for review” status. Add more only when you see a specific problem it would solve.

Handling rejections gracefully

When a reviewer sends content back, say why in a comment and move it to a clear status such as “Needs changes”, not back to plain draft. Otherwise the writer may not notice, and the post quietly stalls for weeks. A WordPress editorial workflow should make publishing easier, not harder. If it doesn’t, simplify it.

Frequently asked questions

Can I build a workflow without plugins?

Partly. Roles, the pending status and scheduled publishing are built in. For custom statuses visible in the block editor, editorial comments and calendars, plugins are the practical option.

How do I stop writers publishing by accident?

Give them the Contributor role, or a custom role without the publish_posts capability. They’ll see “Submit for review” instead of “Publish”.

Can different content types have different workflows?

Yes. Many workflow plugins let you assign statuses and rules per post type, so blog posts and product pages can follow different paths.

What about content written outside WordPress?

Many teams draft in Google Docs and paste into WordPress at the final stage. That’s fine, but make sure the review process covers the final WordPress version, because formatting and links can change during transfer.