Editorial workflow for human-led content

What this playbook is for

Use this workflow for a guide, landing page, comparison, report, or other substantive page that makes factual claims or helps a reader make a decision. It creates a reviewable path from the reader’s need to the published page while keeping responsibility with named people.

Adapt the stages to the risk and complexity of the work. A short product explanation may need one writer and one approver. Medical, legal, financial, safety, or security guidance may require a qualified specialist, a formal approval policy, and more evidence. The workflow is complete when each required decision has an owner, not when a large number of people have touched the draft.

Assign the roles before work begins

One person may fill several roles, but do not leave a role implied.

The editorial owner must be a person with authority to approve, return, pause, correct, or retire the page. A tool can assist any stage, but it cannot hold this accountability.

Use explicit working states

Move the page through a small set of states so its condition is visible:

Proposed → Scoped → Evidence ready → Drafting → Fact-check → Editorial review → Specialist review, if required → Approved → Published → Monitoring

Return the page to an earlier state when a material claim lacks support or a reviewer changes the scope. Do not relabel an unresolved draft as approved to meet a publishing date.

1. Open an editorial brief

The editorial owner records:

• the reader’s question, decision, or task;
• the direct answer the page is expected to explain;
• evidence that the audience need is real;
• what the page will and will not cover;
• the page type, intended destination, and any required related resources;
• the named owner, contributors, reviewers, and approver;
• material risks, including privacy, rights, regulated advice, or likely harm from an error;
• the events or dates that should reopen the page after publication.

Resolve an unclear audience or contradictory objective before commissioning a draft. If the intended answer changes as evidence is gathered, update the brief so reviewers are not judging against an obsolete premise.

Scope gate: The owner can state who the page serves, what the reader should be able to do, where the answer stops, and who can approve it.

2. Plan the evidence and expert input

List the claims the page will probably need to establish. Identify the best available evidence for each one before writing polished prose. Prefer original documentation, standards, research, public records, product data, or direct evidence when each source fits the claim. Add independent reporting or analysis when it provides necessary context or scrutiny.

Create a Claim-and-Source Record at this stage. Record source dates, versions, markets, populations, methods, and other limits that affect what the evidence can support.

Give the subject-matter expert a focused request rather than a topic alone. Ask:

1. What does the reader need to understand or decide?
2. Which distinctions are commonly lost in a general summary?
3. What fails in practice, and under which conditions?
4. Which claims require direct evidence or careful qualification?
5. What would make the proposed guidance wrong, unsafe, or obsolete?

Preserve the expert’s reviewed notes, demonstration, or interview record. Mark statements that still require documentary support. Expertise can explain a mechanism or direct the research, but it does not turn every recollection into a verified fact.

Evidence gate: Each central claim has a plausible source or documented original-evidence plan, and the expert has identified important conditions and failure cases.

3. Draft from the brief and evidence

Use Writing web content for readers and AI answers for the drafting method and complete examples. This workflow owns the review gates; the writing guide explains how to build the page and preserve the meaning of its important passages.

Lead with the practical answer, including any condition that changes it materially. Then explain the mechanism, consequence, and next action. Use descriptive headings that let a reader understand the page’s shape before reading every paragraph.

Keep these bases distinct in the prose and working record:

• Source-backed fact: a claim supported by an inspectable source.
• Original observation or test: what was observed under recorded conditions.
• Analysis: an interpretation derived from stated evidence.
• Editorial recommendation: a reasoned course of action proposed by the publication.
• Hypothetical example: an invented situation used only to clarify a decision or process.

AI may help organize notes, propose an outline, transform approved material, or suggest edits. Treat its research leads, summaries, citations, calculations, examples, and wording as unverified until a responsible person checks them. Do not use an AI system’s confidence or self-review as evidence.

Draft gate: The draft answers the brief, represents the evidence without overstating it, labels examples and judgment, and does not contain placeholders disguised as finished claims.

4. Fact-check the material claims

The fact-checker works claim by claim from the record, not from a general impression of the page.

1. Read the exact draft wording and identify every assertion it contains.
2. Open the cited source rather than relying on a search snippet, prior summary, or citation supplied by a tool.
3. Locate the passage, table, data, or record that supports the assertion.
4. Compare the claim’s subject, measure, timeframe, version, market, population, and level of certainty with the evidence.
5. Check names, dates, figures, units, quotations, availability, attribution, and causal language.
6. Record verified, revise, replace source, remove, or unresolved, with a reason.
7. Recheck revised wording. Approval of an earlier sentence does not automatically carry over to the new one.

A source can be credible and still fail to support a particular claim. One source may establish that an organization announced a feature but not that the feature is generally available or effective. Preserve that boundary in the wording.

For original testing, confirm the setup, variables, sample, date, result, and limitations. Separate the observed result from a proposed explanation, especially when more than one factor could have produced it.

Fact-check gate: Every material factual claim is supported as written, narrowed to match the evidence, clearly identified as unresolved, or removed.

5. Run editorial and required specialist review

The editor reviews the complete page after factual issues are visible. Check whether:

• the opening answers the reader’s actual question;
• the explanation connects mechanisms to consequences and actions;
• headings, paragraphs, lists, links, and examples form a coherent path;
• qualifications appear beside the claims they constrain;
• facts, observations, analysis, and recommendations remain distinguishable;
• attribution is clear and quotations or media have an appropriate basis for use;
• the language is understandable to the intended reader without being misleadingly simple;
• meaningful headings, descriptive links, text alternatives, captions, and transcripts are present where needed;
• the page avoids repetition, unsupported padding, and promises of rankings, citations, or AI-answer inclusion.

Route high-consequence material to the qualified reviewer required by the organization’s policy. Give that reviewer the brief, full draft, claim record, and unresolved questions. A vague request to “take a look” does not establish what was reviewed.

Send changes that introduce or materially alter factual claims back through fact-checking. Keep approval separate from contribution: supplying a quote or reviewing one paragraph does not imply approval of the whole page.

Review gate: Required reviewers have recorded approval or specific exceptions, and all blocking issues have an owner and resolution.

6. Approve and publish the page

Freeze the approved copy or identify the exact version being released. The editorial owner confirms the final decision, and the publisher checks the implemented page rather than assuming the content-management preview matches production.

Before release, verify:

1. The title, summary, headings, body, captions, and calls to action match the approved version.
2. Citations point to the specific supporting pages or documents and appear near the relevant claims.
3. Authorship, review, sponsorship, and substantial automation disclosures are accurate where readers need them.
4. Links, media, structured data, canonical information, and indexability behave as intended.
5. Private notes, credentials, confidential records, tracked changes, and unlicensed assets are absent.
6. The claim record identifies the published version and the owner of the next review.

Publication gate: The production page matches the approved content, passes the required technical checks, and has a named maintenance owner.

7. Maintain the published record

Monitor the review triggers defined in the brief. Reopen the page when a relevant policy, product, standard, price, role, source, or body of evidence changes. Also reopen it when a correction, credible challenge, failed test, or related-page update calls a claim into question.

For a substantive correction, preserve what changed, why it changed, who approved it, and whether related pages, structured data, feeds, or internal records repeat the same claim. Do not describe a requested or drafted change as published until the live page has been checked.

Retire or redirect a page when its purpose no longer exists and revision would mislead readers about the continuity of the subject. Preserve records needed to explain consequential past decisions under the organization’s retention policy.

Maintenance gate: The live page remains within its approved scope, its material claims still match their evidence, and its next review trigger has an owner.

A workable small-team track

Small teams do not need to simulate a large editorial department. One person can be the owner, writer, fact-checker, and publisher when the subject is low consequence, provided the record makes that overlap visible and the person performs each check deliberately. A second person can provide editorial challenge or approval when available. Do not call that a specialist review unless the person has the relevant qualification and remit.

Use this minimum track for a routine, evidence-backed explainer:

1. The owner writes a brief with the reader question, direct answer, boundary, review trigger, and material-risk assessment.
2. The writer creates a claim-and-source record for the material factual claims and marks any original observation or recommendation.
3. The same person fact-checks each claim against the opened source, then revises the draft where the evidence is narrower.
4. A second reviewer, if available, checks whether the answer is understandable and the limits are visible. Route high-consequence material to the required qualified reviewer regardless of team size.
5. The owner freezes the approved version, checks the implemented page, and records the maintenance trigger.

The number of people is not the test. The page needs an accountable owner, evidence checked as written, and the review appropriate to its consequence.

Completed hypothetical example

This fictional example shows the record of a small editorial decision. It does not describe a real publication, reviewer, or result.

Page: “How to compare a product-page price with a merchant feed”

• Reader question: “The price in a feed and on a product page differs. What should I check before changing either value?”
• Direct answer: “Confirm which system has the current effective price, then correct the supplying record before changing downstream displays.”
• Scope: Covers one product price discrepancy. It does not explain feed-platform policy or guarantee that a downstream listing will update.
• Evidence plan: The product database establishes the current approved price; the page and feed export show the observed values; internal system documentation identifies the feed’s source field.
• Draft change after fact-check: “Update every listing” becomes “Correct the supplying record, then recheck the affected displays.” The broader wording was removed because the evidence did not establish control over every listing.
• Review decision: No specialist review is required for this low-consequence operational page. A second editor checks that the procedure distinguishes the current approved value from an observed display.
• Publication check: The owner confirms the live links, visible steps, and related template route. The page reopens when the product-data workflow changes or a correction reveals a new source path.

The example works because it records the question, boundary, evidence, changed wording, owner decision, and trigger. A list of named gates without those decisions would not show whether the page is ready.

A compact release checklist

- [ ] The reader, answer, scope, owner, and approver are recorded.
- [ ] Appropriate subject-matter expertise informed the work.
- [ ] Material claims appear in the claim-and-source record.
- [ ] The draft distinguishes fact, observation, analysis, recommendation, and example.
- [ ] A person opened each supporting source and checked the claim as written.
- [ ] Required editorial, accessibility, rights, and specialist reviews are complete.
- [ ] Material revisions were returned to fact-checking.
- [ ] The production page matches the approved version and its links work.
- [ ] Review triggers, correction handling, and maintenance ownership are recorded.

References

• Google Search Central: Creating helpful, reliable, people-first content
• W3C Web Accessibility Initiative: Page structure tutorial