Content workflows: drafts, reviews and publishing approvals

Someone hits Publish on a page that still has placeholder text in the middle of it. Or a price gets updated on the live site, wrongly, and nobody can remember what it said before. Both are symptoms of the same gap: there is no agreed content workflow, so every edit goes straight from one person's screen to the public website.

A workflow does not have to be bureaucratic. For most small teams it means three states, two named people and a habit of scheduling. This article shows how to set that up and keep it light enough that people follow it.

The three states almost every team needs

Keep the basic path short, because each extra stage adds delay and gives people a reason to bypass the system entirely.

• Draft: the writer is still working. Nobody else needs to look at it, and it must never be reachable by the public or by search engines.
• In review: the writer has finished and handed it to a named reviewer. The content is complete, not perfect.
• Approved or scheduled: the reviewer has signed off and the item is either live or waiting for its publish time.

Add a fourth state only when there is a real second check, such as legal or pricing sign-off on certain pages. If everything needs two approvals, you will find that nothing gets published on Fridays.

Decide who approves what, by type of content

Blanket rules fail because a typo fix and a new pricing page carry very different risk. Split content by consequence instead.

• Low risk, self-publish: blog posts by experienced writers, event notices, minor wording fixes.
• Needs a peer review: most new pages, product descriptions, case studies.
• Needs the owner or a specialist: prices, offers and discounts, delivery and returns terms, anything with GST or invoicing implications, medical or financial claims, and legal pages such as privacy or terms.

Write this into a one-page document listing content type, who reviews it and how long they have. The time limit matters as much as the approver. "Review within one working day, otherwise it goes ahead" prevents the queue that kills most workflows.

Name individuals, not departments. A task assigned to "marketing" is assigned to nobody.

What a reviewer should actually check

Reviewers waste time when the brief is vague. Give them a short, fixed checklist so reviews take fifteen minutes rather than an hour.

1. Facts: prices, dates, phone numbers, addresses, specifications and any claim about results.
2. Links: every link opens the right page, and internal links are not pointing at a staging address.
3. Images: the right picture, correctly cropped, with alt text written, and the business has the right to use it.
4. Title and meta description: present, accurate and not duplicated from another page.
5. URL: short, readable and final, because changing it after publishing means setting up a redirect.
6. Formatting: headings in order, short paragraphs, and no leftover placeholder text.
7. Mobile view: the page read once on a phone before approval.

Comments belong inside the CMS where possible, attached to the item. Feedback scattered across WhatsApp and email is how corrections get missed.

Scheduling instead of publishing at midnight

Scheduled publishing is the most under-used feature in most content tools. Once a piece is approved, set its date and time and stop thinking about it.

Two practical points. First, check that your site's timezone is set correctly, usually Asia/Kolkata, otherwise scheduled items appear hours early or late. Second, scheduling on many self-hosted systems depends on a background task running on the server; if scheduled posts have ever silently failed to appear, ask your developer to confirm that the scheduler is running properly rather than assuming the feature is unreliable.

Use scheduling for time-sensitive content too: festival offers that must not appear early, price changes that start on the first of the month, and campaign pages tied to an advertisement going live.

Revision history is your safety net

Any system worth using keeps previous versions of a page. That single feature answers the two questions that follow a bad edit: what did this say before, and who changed it?

Check what your platform stores and for how long. Some keep unlimited revisions, some keep a fixed number, and some keep none for certain content types such as products or menus. If products and prices are not versioned, that is worth raising with your developer, since those are exactly the fields where a mistake costs money.

Encourage a short note with each significant change, describing what changed and why. When you are looking at nine versions of a page from the same week, those notes save real time.

Keeping the process light enough to survive

Workflows die from friction. A few habits keep them alive:

• Agree a maximum review time and honour it.
• Let trusted writers publish low-risk content without approval.
• Keep an emergency path for genuine urgencies, such as a wrong phone number, with the rule that it is reviewed afterwards.
• Use a shared calendar of what is planned so reviewers are not surprised.
• Review the process itself once a quarter and drop any step that has never caught a problem.

Setting this up on your own site

Start this week with the simplest version: write the one-page list of who approves what, agree the review deadline, and switch on scheduled publishing for anything time-sensitive. Add roles in your CMS so writers cannot publish directly where that matters, and check that revisions are being stored.

If your current admin has no review states, no scheduling or no version history, those gaps can usually be added. Our team can look at what your platform supports and what it would take; see our custom software and admin panel work or ask an expert about your setup.

Frequently asked questions

Do drafts on my website show up in Google search?

Properly implemented drafts are not publicly accessible, so they should not. Be careful with preview links that anyone can open, and check that staging copies of the site are blocked from indexing.

How many approval steps are too many?

If routine content needs more than one approver, the process will be bypassed. Keep second approvals for genuinely high-risk items like pricing and legal pages.

What happens if two people edit the same page at once?

Many systems lock the page or warn the second person. If yours does neither, one person's work can silently overwrite the other's, so agree who owns each page while it is being edited.

Should freelance writers be given publishing rights?

Usually not at first. Give them an account that can submit for review, and reconsider once you have seen a few pieces go through without corrections.