A publishing workflow audit you can run in an afternoon

Why an afternoon is enough

Workflow audits get postponed because they sound like a project. They are not. If you can answer fourteen questions honestly, you will know within a few hours where your drafts get stuck and which steps are worth automating.

Do this with the two or three people who actually move work through the pipeline, not with the whole department. You want accurate answers, not diplomatic ones.

The fourteen questions

Intake

1. Where does a new page idea get recorded, and who can add one?
2. What has to be true before an idea becomes scheduled work?
3. Who decides priority when two ideas compete for the same slot?

Briefing

4. Does every page start from a written brief, or only the important ones?
5. How long does a brief take to produce, and who produces it?
6. What is in the brief that a writer actually uses?

Drafting and review

7. How many days does a draft sit before someone reviews it?
8. What does the reviewer check first, and is it structure or substance?
9. How often does a draft go back for a second round, and why?
10. Who approves publication, and what happens when they are away?

Publishing and after

11. How does an approved draft become a live page, step by step?
12. Who adds metadata, images and internal links, and when?
13. What is recorded at publication that you will need in six months?
14. When does anyone look at the page again?

Reading the answers

Three patterns show up in almost every audit.

The waiting room. Drafts sit for days between stages, not because anyone is slow but because nobody is told the work has arrived. Fix with assignment and notification, not with pressure.

The structural rewrite. Reviewers spend their first pass fixing headings and formatting, so substance gets a tired second look. Fix by running structural checks before review.

The orphan page. Nobody looks at a page again after publication. Fix with a review date set at publish time and a refresh queue that surfaces decay.

Most stalls are handover problems disguised as capacity problems. Adding a writer to a pipeline with a two-day notification gap just adds drafts to the same waiting room.

Three fixes that pay for themselves

• Assign an owner at intake. Not at drafting. The moment an idea becomes scheduled work, it gets a name.
• Move checks before review. Structure, metadata and link checks belong to the machine. Reviewers should arrive at a draft that already passes them.
• Schedule the review date at publication. It costs ten seconds and turns decay from an emergency into planned work.

What to do with the result

Write the answers down and share them. The document itself becomes your first process record, and the gaps in it are your roadmap. Re-run the same fourteen questions in six months: if the answers have not changed, either the process is genuinely stable or nobody is looking at it. The difference will be obvious from your publishing dates.