Use states that describe real work
A calendar date is not a workflow. Define a small set of states with clear entry and exit conditions: proposed, researched, drafted, reviewed, ready, published and monitoring. Name what must exist before a piece moves forward. This makes blocked work visible and prevents half-researched drafts from filling the schedule. Keep the system simple enough that contributors update it without a meeting.
Prioritise by audience consequence
Score ideas by the importance of the reader problem, evidence of demand, strategic relevance, confidence and maintenance cost. Reach can be one factor, but it should not crowd out material that prevents costly mistakes for a smaller audience. Limit work in progress. Finishing and learning from two pieces is more valuable than opening ten. Revisit rejected ideas when new evidence changes their value rather than keeping an endless backlog.
Separate drafting from verification
Draft for argument and clarity, then verify claims in a dedicated pass. Maintain a source table for consequential statements, dates, links and limitations. Check names, quantities and examples against primary material where possible. Editing cannot rescue unsupported certainty. If evidence is unavailable, narrow the claim or label the interpretation. A fact-check pass should produce visible changes, not simply a checkbox.
Edit at three levels
Structural editing asks whether the piece fulfils one coherent job. Paragraph editing checks sequence, evidence and transitions. Line editing improves precision and rhythm. Doing all three at once encourages cosmetic changes while larger problems survive. Read headings alone to test the argument, then inspect paragraphs for one clear purpose each. Remove introductions that delay the answer and conclusions that merely repeat the headline.
Publish with operational details
Before release, verify title, description, canonical, heading order, image alternatives, link behaviour and structured data. Confirm that downloadable files are accessible and that forms accurately describe where data goes. Record publication date, reviewer and sources. A piece is not complete if only the central column works; navigation, error states and mobile reading are part of editorial quality.
Maintain by risk
Not every page needs the same review interval. Prioritise pages containing regulations, prices, platform procedures, safety guidance or fast-changing statistics. Lower-risk explanatory material may need less frequent review. Add expiry triggers during research: a source update, product change or annual cycle. When a page is retired, choose whether to update, consolidate, redirect or preserve it with an archive notice based on reader value.
Worked example: a guide from question to review
A support question enters the proposed state with its source and audience consequence. An editor checks whether an existing page can answer it before approving new work. Research produces a decision statement, source table and explicit scope. Drafting follows the evidence plan; structural review happens before line editing. Readiness requires verified claims, accessible media, metadata, working links and a named review trigger. After publication, the team watches task completion and repeated questions for six weeks. The guide then moves to monitoring with an owner rather than disappearing into an archive of finished tickets.
Workflow failure modes
Too many statuses hide blocked work, while vague statuses such as ‘in progress’ conceal whether research, writing or approval is missing. Templates can also become ceremonial: contributors fill every field even when it does not affect the piece. Define the minimum evidence for each transition and allow exceptions to be explained. Avoid scheduling work before access to sources or reviewers is confirmed. If urgent publication bypasses a check, create a dated follow-up rather than pretending the normal gate passed. Track corrections as learning, not embarrassment.
Maintenance rhythm
Hold a brief monthly review of pages with upcoming expiry triggers, unresolved corrections and repeated audience questions. Assign action by risk: verify, update, consolidate, redirect or archive. Keep source tables with the page so updates do not restart research from zero. Sample published pages for heading structure, alternatives, broken links and claim freshness. Measure queue age and completed maintenance alongside new publication volume. An editorial system is healthy when it can explain what deserves attention next and why, not when every calendar square is full.
Focused workshop
Use this short working session to turn the guide into a decision-ready artefact. Keep the scope to one live example and record assumptions beside the output.
- Define seven workflow states and their exit conditions.
- Score five ideas by consequence, evidence and maintenance cost.
- Assign review triggers to one high-risk and one evergreen page.
Definition of ready: another practitioner can inspect the evidence, understand the proposed change and name the result that would stop or reverse it.
Review questions
What evidence supports the problem? Which audience and context does it describe? What is the smallest change that can test the mechanism? Which signal is close enough to the decision to be useful? What harm could a single success metric hide? Record answers before implementation, then return to them when the review window closes.