Editorial Review and Quality Assurance
Editor-Writer Handoff Note
Transfer editorial rationale, accepted changes, preserved strengths, unresolved decisions, source questions, priorities, owners, and next actions without ambiguity.
Free editable Markdown · Editors, writers, and content managers ·
Accessible HTML preview
Blank template
The downloaded file contains the same fields in editable Markdown.
Handoff identity
- Project and draft
- [Title]
- Reviewed version
- [File, URL, or commit]
- Brief
- [Link]
- Review stage
- [Structure / Line / Copy / Final]
- Editor
- [Name]
- Writer
- [Name]
- Handoff date
- [YYYY-MM-DD]
- Return deadline
- [YYYY-MM-DD]
Editorial summary
- Reader task
- [What the draft must enable]
- Overall status
- [On track / Substantial revision / Blocked]
- Priority 1
- [Issue, reason, and locations]
- Priority 2
- [Issue, reason, and locations]
- Priority 3
- [Issue, reason, and locations]
- Strength to preserve
- [Specific evidence, example, structure, or voice]
- Structural change made
- [What moved and why]
Open action
- Action ID
- [Identifier]
- Status type
- [Required / Writer decision / Source query / Specialist / Optional]
- Location
- [Heading or comment]
- Decision needed
- [Specific question or change]
- Reason
- [Reader, fact, brief, or policy]
- Owner
- [Person or role]
- Due date
- [YYYY-MM-DD]
- Acceptance evidence
- [How resolved]
- Superseded comments are marked closed.
- Meaning-changing edits are visible to the writer.
Return and signoff
- Writer returns
- [File, query responses, source list, or another]
- Next pass
- [Reviewer and scope]
- Outside scope
- [Checks still required]
- Disagreement path
- [Decision owner]
- Writer response
- [Accepted, questioned, or completed]
- New version
- [Identifier]
- Handoff closed by
- [Name and date]
How to use this template
- Record the exact version, brief, review stage, editor, writer, and deadline.
- Summarize the outcome, top priorities, rationale, and strengths that must survive revision.
- Group accepted changes, writer decisions, factual queries, specialist issues, and optional suggestions separately.
- Assign owners, dates, dependencies, and acceptance evidence for every open action.
- Agree on the return format, resolve disputes, and update the note when the next version changes hands.
Orient the writer quickly
Begin with the reader task, current stage, overall editorial judgment, and two or three priorities. Name strengths to preserve, especially examples, evidence, or voice that broad revision might erase. Explain the main change through its reader effect rather than the editor’s taste. Link the brief, source file, tracked draft, and applicable guidance. A writer returning after several days should understand what changed and why without reconstructing a comment thread.
Separate decisions by status
Group accepted editorial changes, writer decisions, source queries, specialist referrals, and optional improvements. For each open item, provide location, question, consequence, owner, and due date. Do not label a required factual correction as a suggestion or a preference as mandatory. If structure changed, explain what moved and which local comments are obsolete. Record deliberate non-changes so reviewers do not reopen settled issues. Surface dependencies, because line work completed before a factual decision may need to be repeated.
Close the feedback loop
Define what the writer should return: revised file, query responses, updated sources, or a short change summary. Name the next review pass and acceptance evidence. Allow the writer to challenge an edit that changes meaning or first-hand perspective. Resolve disagreement through the stated decision owner, not silent undoing. When the draft changes hands again, update version and status instead of appending ambiguous messages. A concise maintained handoff is more reliable than scattered chat history and makes delay visible to the content manager.
See the fields in context
Fictional example: orchard volunteer article
Maple Row Orchard and the draft team are invented.
- Status: On track after structural edit.
- Priority: Move fictional safety prerequisites before equipment steps; the editor made the move.
- Writer decision: Confirm whether the first-hand opening accurately reflects the invented coordinator’s experience.
- Source query: Replace an undated harvest figure or provide its current record.
- Strength: Preserve the concrete tool-label example through line editing.
Frequently asked questions
Should every tracked edit be listed?
No. Link the tracked file and summarize patterns, consequential changes, and decisions. Listing every punctuation edit makes the handoff harder to use and duplicates the source.
What belongs under required?
Corrections and changes mandated by the brief, evidence, policy, accessibility, or authorized editorial decision. Explain the authority; do not elevate a preference merely by labeling it required.
Can the writer reject an edit?
They should question any change that alters meaning, evidence, experience, or voice. The agreed decision owner resolves material disagreement and records the result.
When is a handoff complete?
When the receiver acknowledges the version and actions, blockers have owners, and the return and next-review path are clear. Update status when revised work changes hands.