Editorial Workflow Process: Stages and Handoffs
What makes an editorial workflow process usable?
An editorial workflow process moves a piece through commissioning, drafting, editing, verification, approval, production, and publication. Each handoff needs a named owner, an identified version, a decision, and evidence that the stage’s exit condition is met. Returned work goes to the person who can resolve the stated issue; changed approved copy goes back for the affected checks. AI assistance may be permitted within a stage, but it does not become the accountable approver.
The sequence below is Margin & Method’s proposed operating model for a small publication, not a universal industry standard. Its purpose is to make handoffs inspectable. A stage name records where the work is; a handoff record explains who must do what next.
The workflow tools guide covers evaluating software against editorial requirements. This guide covers operating the process, including the return path when a draft cannot advance. It does not claim that any product implements these controls automatically.
What must pass between the seven stages?
Use the same article identifier throughout. Keep the working version separate from the latest approved version. In the table, “owner” means the person responsible for closing that stage, not everyone who might contribute.
| Stage | Owner | Evidence required before advancing |
|---|---|---|
| 1. Commission | Commissioning editor | Accepted pitch, reader need, scope, author, reviewer, deadline and publication constraints |
| 2. Draft | Author | Submitted version and source package addressing the brief |
| 3. Edit | Editor | Resolved structural and wording decisions, with outstanding questions routed |
| 4. Verify | Verification owner | Documented evidence decisions for claims and required specialist checks |
| 5. Approve | Authorized approver | Explicit approval naming the complete version and permitted next step |
| 6. Produce | Production owner | Rendered package checked against approved content, with changes reconciled |
| 7. Publish and maintain | Publication owner | Live output checked, publication record saved and future review responsibility assigned |
A small team may assign several roles to one person where its policy permits. Record the decisions separately. If the work requires independent or specialist review, combining job titles does not remove that requirement.
Commission and draft: resolve the brief before editing
Accept, decline, or return the pitch with a reason. An accepted pitch becomes a brief: audience, question, boundaries, evidence needed, protected material and intended output. Name who can decide a scope change.
The author’s submission should identify the draft and attach the necessary source notes through an approved location. “I have finished” is not a complete handoff if the editor cannot find the version or supporting material.
If the draft answers a different question from the brief, return it to commissioning for a scope decision before investing in detailed edits. Do not silently turn a changed assignment into a copyediting problem.
Edit and verify: distinguish wording decisions from evidence decisions
The editor resolves organization, clarity and house style. The verification owner resolves factual support and coordinates any required subject-matter review. These activities may interact; they still answer different questions.
Use the existing claim-ledger guide for the evidence method rather than creating a second ledger inside the workflow board. Link the relevant record and state which version it covers. A checked source does not approve every possible paraphrase of it.
If verification changes the argument, return the piece to editing. If editing subsequently changes a number, attribution, qualification or other substantive claim, reopen the affected verification work. Record the reason for the return instead of resetting the entire article to an unexplained “in progress.”
Approve, produce and publish: check the package that readers receive
Approval should identify the body and associated headline, summary, captions and other reader-facing material included in the decision. Record the approver, version, decision time and release conditions. “Approved pending an unresolved factual check” should remain blocked from release under this model.
Production prepares and inspects the rendered package. A changed caption or summary can require further review even when the body remains unchanged. After release, the publication owner checks the actual output and records where corrections or review requests should go.
The Department for Education’s quality guidance places its final second-person check in context, such as a preview or test environment, after factual review and clearance. It also requires accuracy to be checked when preparation changes the content. That is a documented departmental practice, not a claim that our seven-stage model is its prescribed workflow.
How should a handoff be accepted or returned?
A practical handoff record has six fields:
- Article identifier and submitted version.
- Requested decision and receiving owner.
- Evidence or approved files needed for that decision.
- Known open issues, including any release blocker.
- Requested response date or dependency.
- Receiver’s acceptance, return or escalation decision.
Sending a link does not establish that its recipient accepted responsibility. Agree how the receiver acknowledges the handoff and what the sender does if nobody responds. Do not infer notification behavior from a status change.
A concrete example appears in GOV.UK’s current standard-content review guidance: after submission for second-person review, the system does not automatically notify a reviewer. Rejected material returns to draft and can be submitted again after editing. Those are documented Whitehall Publisher behaviors, not tests performed here or assumptions about other systems.
For your own process, distinguish three outcomes. Returned means a named person has a specific revision to make. Blocked means the next decision depends on missing evidence, authority or another prerequisite. Declined ends the assignment under the recorded decision. Preserve the reason and current version in each case.
What does a version-scoped return look like?
The following is a fictional paper exercise. Article E-042 compares two invented book editions; all records and wording below are illustrative, not reporting about actual editions or observed team performance.
| Record | Event | Required next action |
|---|---|---|
| E-042/v1 | Author submits the agreed comparison and source notes | Editor accepts the editing handoff |
| E-042/v2 | Verification finds that the draft describes a feature as shared when the exercise’s evidence covers only one edition | Return the identified sentence to the author; verification remains open |
| E-042/v3 | Wording distinguishes the editions; verifier closes the affected evidence decision and approver approves v3 | Send that complete package to production |
| E-042/v4 | During production, a rewritten summary again describes the feature as shared | Block release and reopen the summary’s factual check |
| E-042/v5 | Summary corrected and checked; authorized approver approves v5; rendered package checked | Release v5 and check the live output |
The approval for v3 remains a true historical event. It is not evidence that v4 was approved. Likewise, v5 does not inherit approval merely because its author believes the correction restores the intended meaning.
A useful return note for v4 is: “Summary changes the edition scope checked in v3. Verification owner: review the revised summary against the evidence record. Publication remains blocked.” It identifies the location, problem, owner and consequence without reopening unrelated work by default.
Where can an AI-assisted pass fit?
Treat proposed AI work as a bounded task inside a stage, subject to the publication’s rules. A request to suggest headings or identify inconsistent terms still needs a person to inspect the output against the supplied draft. The human-owned AI editing workflow supplies the narrower editing-pass method.
AP’s July 2026 newsroom-standards announcement describes uses including suggested headlines and summaries, with AP journalists reviewing and editing output before publication. Reporting, sourcing, verification and editorial judgment remain human responsibilities in that announcement. This describes AP’s policy, not permission for another publication or a measured claim about tool performance.
Before using any service, confirm approved inputs, current data-handling terms and applicable confidentiality rules. Keep sensitive or confidential material out of unapproved systems. If authorization is unclear, stop the upload and ask the responsible owner. Record material assistance and make the disclosure decision under the rules governing the work; no universal disclosure wording is assumed.
How do you introduce the process without a migration project?
Choose one representative assignment and fill its handoff records manually. Give a reviewer the submitted version, the decision requested and the evidence location. Ask whether they can act without reconstructing the assignment from messages.
Then run the fictional return exercise above on paper. Confirm who blocks release, who repairs the issue, who checks the revision and who approves the replacement. This is a proposed rehearsal, not a validated productivity intervention or a software test.
Once published, assign a maintenance owner and a review trigger appropriate to the subject. A new source, reported error or changed underlying fact should enter a recorded correction or update decision. Publication closes the release handoff. It does not end responsibility for the article.
Sources
Primary guidance checked September 8, 2026: Department for Education quality and assurance; GOV.UK standard-content review; AP’s dated AI-standards announcement. Links accompany the specific documented practices. Stage names, handoff fields and the E-042 exercise are original editorial proposals, not source quotations or claims of operational testing.