There’s a moment every writer knows. The draft is done. You’ve read it twice, you like it and you’re about to hit send. Then, eleven minutes after delivery, the client replies: “The link in paragraph three goes to a 404. Also, we discontinued that product. Also, is this supposed to still say [INSERT QUOTE]?”
None of those are writing problems. The writing might be excellent. They’re handoff problems, small, checkable failures that slip through because the writer was checking whether the piece was good, not whether it was ready.
Handoff QA is the short, structured pass that separates “done” from “delivered.” This article tears down how it works, what it checks and why a checklist beats a careful reread every time.
Why doesn’t rereading the draft catch these problems?
Because rereading is the wrong tool. When you reread your own draft, you read what you meant to write. Your brain fills gaps, skips familiar sentences and assumes links work because you remember adding them. Rereading is great for flow and voice. It’s poor at catching mechanical failures.
A checklist works differently. It asks specific questions, one at a time, and requires a specific answer: pass, fail or not applicable. You stop reading the piece as an author and start inspecting it as a reviewer.
What did high-stakes fields learn about checklists?
The case for checklists was made convincingly in fields where mistakes are far costlier than a broken link.
The B-17’s ancestor and the pilot’s checklist. In 1935, Boeing’s Model 299, a prototype bomber, crashed during a demonstration flight at Wright Field. The investigation pointed to pilot error: a control lock had been left engaged. The airplane was considered too complex for any one person’s memory, and test pilots responded by developing a checklist. Aviation checklists became standard practice.
The WHO Surgical Safety Checklist. In 2008, the World Health Organization introduced a short checklist for operating rooms covering steps before anesthesia, before incision and before the patient leaves the room. Its premise was that skilled teams still skip basic steps under pressure.
Mission control’s go/no-go poll. NASA flight controllers have long used a structured poll before critical events, with each position confirming “go” or “no-go” aloud. The ritual ensures that every critical system is confirmed by its owner rather than assumed by the group.
Content delivery is lower stakes. The underlying human problem is identical: experts skip basic steps because they’re experts.
What does a handoff QA check?
The Handoff QA in the Content-Brief Toolkit runs 18 checks, each scored Pass, Fail or N/A, with a fix note for anything that fails. They group into six areas.
1. Brief alignment
Does the draft match the brief’s purpose, audience and CTA? Is every planned section present, or cut deliberately with a note? Is the direct-answer or summary block there if the brief required one? This catches drift, the slow slide from what was agreed to what got written.
2. Claims and evidence
No statistics, rankings or review scores without a verified source. No invented testimonials, customer names or case-study results. Every claim marked as needing client confirmation is either resolved or clearly flagged. This is the most important group, because unsupported claims are the failures that damage trust.
3. Requirements
Are the must-include points present and the must-avoid points absent? Are required disclosure lines included where the topic calls for them? These come straight from the intake and brief, which is why a good intake makes QA fast.
4. Voice
Does the voice match the brief? The practical test is to read one paragraph aloud against the voice notes. If the brief says “plain and direct” and the paragraph says “leverage synergistic solutions,” the check fails.
5. Links, images and on-page details
Internal links use correct URLs and sensible anchors. External citations point to real, appropriate sources. Images have descriptive alt text. Title and meta direction is followed or a better alternative noted. FAQ answers appear in visible copy if FAQ schema is planned.
6. Delivery hygiene
Formatting is clean, with a sensible heading hierarchy and no leftover placeholder text. Open questions for the client are listed at the top, not buried. File naming and delivery format match what was agreed. And a final skim at phone width confirms there are no walls of text in critical sections.
Which checks catch the most problems?
In practice, three checks earn their place on almost every project:
- No leftover placeholder text. Brackets, “TK,” “INSERT LINK” and “[CLIENT TO CONFIRM]” are the most embarrassing thing a client can find. They’re also the easiest to catch with a quick search.
- Links actually work. Click every one. Don’t trust memory.
- Unconfirmed claims are flagged, not hidden. If you’re still waiting on the client to confirm a detail, say so at the top of the delivery. Clients forgive open questions. They don’t forgive surprises.
What does a QA pass look like in practice?
Picture an illustrative delivery: a 1,400-word guide for a fictional home-organizing company, due Friday. The writer opens the Handoff QA tab and works down the list.
Brief alignment passes, but one planned section on garage storage was cut for length, so the writer adds a note explaining why. Claims and evidence produce one failure: a sentence says most clutter accumulates in kitchens, with no source. The writer can’t find a credible one in five minutes, so the sentence becomes an observation from the client’s own intake notes instead. The requirements check catches a missing must-include point, the company’s free consultation, which gets a sentence and a link. Voice passes on a read-aloud. Links produce two failures: one internal link points to a staging URL, and one external source has moved. Both get fixed. Delivery hygiene finds a stray “[PHOTO?]” in the fourth section.
Twenty minutes, six findings, six fixes, one open question listed at the top for the client: “Please confirm the consultation is still free for first-time customers.” The client’s reply is about the ideas, which is exactly the point.
Which habits make QA faster over time?
Three habits compound:
- Search before you read. Search the draft for brackets, “TK” and “TBD” first. It takes seconds and catches the worst failures immediately.
- Click links in a batch. Open every link in its own tab at once, then close them one by one as they pass.
- Keep a personal failure log. After a month, you’ll know your two or three habitual mistakes, and you can check for those first.
How long should handoff QA take?
About fifteen to twenty-five minutes for a typical blog post. That’s the cost. The benefit is that the client’s first impression is the writing, not the mistakes.
It also gets faster. After a few projects, you’ll start avoiding the failures while writing, because you know the checklist is coming. That’s one of a checklist’s quieter effects: it improves the work before it’s even run.
What do you do with failures?
Fix them, and write a one-line note for each saying what you changed. Then run the failed checks again. The note matters for two reasons. It creates a record if the client asks what was revised, and it helps you spot patterns. If “external citations” fails on every project, your research step needs attention, not your QA step.
Some failures can’t be fixed by you, such as a claim only the client can confirm. Those go into the open-questions list at the top of the delivery, clearly worded, with a specific ask.
Should handoff QA happen before or after the client reviews?
Before. Always. The point is that the client never sees the failures. If you run QA after client review, you’re doing damage control, not quality assurance.
For pieces that go straight into a CMS, run QA before publishing, ideally in the CMS preview, where you can check formatting, links and mobile layout exactly as readers will see them.
How does handoff QA connect to the rest of the workflow?
It closes a loop that starts with intake. Intake defines what the piece must do. The brief turns that into a plan. Handoff QA checks that the delivered piece actually honors the plan. Each stage makes the next one easier: a thorough intake gives QA clear requirements to check, and a strict QA makes clients trust the next brief you send.
The Content-Brief Toolkit includes all three stages, with a Client Intake tab, a 15-task Research Checklist, an eight-section Content Brief, an annotated example for a fictional studio called Cedar & Kiln and the 18-check Handoff QA, plus a 13-page guide and Markdown templates.
Quick answers
Is handoff QA the same as fact-checking?
No. Fact-checking verifies claims in depth. Handoff QA confirms that claims were verified or flagged, alongside many other delivery checks. Do both.
Can a colleague run the QA?
Yes, and it often works better. A fresh reviewer doesn’t read what you meant to write.
Should you share the completed QA with the client?
For many clients, yes. A short “QA complete, three open questions below” signals professionalism and invites focused feedback.
Deliver the piece you meant to deliver
The difference between a writer clients tolerate and a writer they rehire is rarely talent. It’s reliability: drafts that arrive matching the brief, with working links, no placeholders and every open question visible. That reliability comes from a twenty-minute habit, not from heroics.
Get the Content-Brief Toolkit and run its Handoff QA before your next delivery. Eighteen checks, Pass, Fail or N/A, and a client whose first reply is about the ideas, not the broken link in paragraph three.
The Toolkit, including the 18-check Handoff QA, is on Content & SEO Workflows.
Leave a Reply