The problem
What the customer needs
- Get a complete first draft in minutes, not a blank page at 9pm the night before the client call.
- Be confident every figure in the deck traces back to a real source, not to Claude's best guess.
- Have a repeatable checklist, not a one-off gut feeling, for what "reviewed" means before it goes out.
Why naive approaches fail
- Asking Claude to "write the Q3 client report" with no attachments produces a fluent draft built on plausible-sounding invented numbers.
- Treating a well-formatted, confident-toned paragraph as proof of accuracy, fluency is not a validation step.
- Skipping validation on the sections that "read fine" and only checking the sections that felt uncertain while drafting, the fluent-but-wrong sections are the dangerous ones because they don't feel uncertain.
- Every number, date, and client name in the deliverable traces to a specific source document, not to memory
- A named human reviewer signs off before send, every time, regardless of how confident the draft reads
- The validation pass is written down as a checklist, not held in one person's head
- Client-sensitive data used to draft the deliverable never left the approved Claude workspace or product tier
The system
What each part does
5 components, each owns a concept. Click any card to drill into the underlying primitive.
Source Packet
the raw material, not a summary of it
The actual workshop transcript, the actual spreadsheet, the actual prior deliverable, uploaded or pasted in full. Not a bullet-point summary someone typed from memory. This is the single biggest lever on accuracy, better source material beats a cleverer prompt every time.
Configuration
Client Project (or a single chat with everything attached): workshop transcript, current-quarter data export, last deliverable as a formatting reference. Nothing paraphrased, nothing summarized before upload.
Draft Pass
structure and tone, not final numbers
Claude produces a complete first draft, organized the way the client expects to read it, with a consistent voice. Treat this output as a strong skeleton, not a finished product. Its job is to save you the blank-page hour, not to be sign-off ready.
Configuration
Prompt gives the audience, the section structure, and the tone (formal exec summary vs working-team update), and explicitly asks Claude to flag any place it filled a gap rather than pulling from the attached source.
Validation Pass
a separate step, run by a human, against the source
Every number, date, name, and factual claim gets checked against the source packet, one by one. This is not re-reading the draft for typos, it is fact-checking against the original documents, the same way you would check a junior analyst's first draft.
Configuration
A checklist, not a vibe: highlight every number/name/date in the draft, locate it in the source, mark match or mismatch. Anything that doesn't trace to a source gets rewritten or cut before it moves forward.
Audience Pass
the deliverable's final shape
Once the facts are validated, the last pass adjusts tone, length, and format for whoever reads it first, an executive one-pager reads nothing like a working-team appendix, even if the underlying facts are identical.
Configuration
Ask Claude to reformat the validated draft for the specific reader (exec summary vs. detailed appendix) without reintroducing new claims, this pass changes presentation, not facts.
Sign-Off Record
who checked what, and when
A short, named record that the validation pass happened: who reviewed it, against which source documents, and when. This is the difference between "we probably checked it" and a defensible answer if a client questions a number six months later.
Configuration
One line per deliverable: reviewer name, date, source documents checked against, any flagged-and-resolved discrepancies. Lives with the deliverable, not in someone's inbox.
Data flow
6 steps to production
Gather the real source material first
Before opening Claude, collect the actual workshop transcript, the actual data export, and the actual prior deliverable. Resist the urge to summarize these from memory, a five-minute collection step here prevents the entire failure mode this scenario exists to catch.
↪ Concept: evaluating-output-accuracy-completenessSet up a Project (or a single well-loaded chat)
Attach every source document. State the audience and the purpose in one sentence at the top: who reads this first, and what decision or update does it support. A vague prompt with good sources still beats a precise prompt with no sources.
Ask for a draft, and ask Claude to flag its own gaps
Request the full first draft in the target structure, and explicitly instruct Claude to mark, inline, any place it had to infer or estimate rather than pull directly from an attached source. This single instruction turns silent guessing into a visible flag you can chase down.
↪ Concept: task-type-prompting-strategiesRun the validation pass against the source, not against the draft
Go line by line through every number, date, and name. For each one, find it in the original source document and confirm it matches. Anything you cannot locate in the source, including anything Claude did not flag itself, gets treated as unverified until you find it or fix it.
↪ Concept: identifying-and-validating-ai-output-errorsAdapt the validated draft for its actual reader
Once the facts are locked, ask Claude to reshape tone and length for the specific audience, executive summary, working document, or client-facing narrative. This step should never reintroduce new claims, only change how the already-validated facts are presented.
↪ Concept: adapting-outputs-for-audienceRecord the sign-off before it ships
Write down who reviewed the deliverable, against which sources, and when. A one-line record is enough. This is what lets your team answer "how do we know this is right" with a name and a date instead of a shrug.
The four decisions
| Decision | Right answer | Wrong answer | Why |
|---|---|---|---|
| Where do the numbers in the draft come from? | Only from attached source documents | From Claude's general knowledge of the client or industry | Claude has no access to your client's actual quarterly numbers unless you provide them. A fluent-sounding figure is not a real one. |
| How do you know the draft is accurate? | A separate validation pass checking claims against source | It reads well and the tone feels confident | Confident tone is a writing-quality signal, not an accuracy signal. Fluency and correctness are independent. |
| Who validates the deliverable? | A named human, every time, before send | Skip validation when the draft "looks obviously right" | The deliverables that look obviously right are exactly the ones where an unnoticed error does the most damage, no one double-checks what looks fine. |
| What happens to a claim Claude can't source? | Rewrite it as a flagged open question or cut it | Leave it in because it sounds plausible and probably fine | "Probably fine" is not a validation standard for a client deliverable. Unsourced claims get resolved or removed, never shipped on faith. |
Where it breaks
5 failure pairs. Each maps to an exam-style question - the naive move on the left, the disciplined fix on the right.
The draft reads polished and professional, so it gets forwarded to the client without a fact-check.
AP-CCAOF-D2-01Run the validation pass regardless of how polished the draft reads. Polish is a writing-quality output, not a correctness signal.
The team asks Claude to "summarize the Q3 client results" without attaching the actual Q3 data.
AP-CCAOF-D1-02Always attach the real source documents before drafting. If the source isn't available yet, the draft waits.
The reviewer double-checks the one paragraph that felt shaky and skims past the confident-sounding ones.
AP-CCAOF-D2-03Validate every number, date, and name uniformly. Confidence in the writing has no relationship to correctness in the facts.
A client questions a figure months later and no one can say who checked it or against what source.
AP-CCAOF-D2-04Log a one-line sign-off record per deliverable: reviewer, date, sources checked. Cheap now, essential later.
A detailed working document gets sent straight to a client executive, unread and unedited for the reader.
AP-CCAOF-D5-05Run a separate audience-adaptation pass after validation. The facts don't change; the shape does.
Cost & latency
A well-sourced first draft replaces the blank-page hour and most of the structural writing time, without touching validation time.
Fact-checking every number and claim against source takes real time. This is the non-negotiable cost of the time saved above.
Even after a rigorous validation pass, the workflow is faster than drafting from a blank page, as long as validation is never skipped to save the remaining time.
A single wrong number or invented client detail sent to a client costs far more in trust and rework than the 30 minutes the validation pass takes.
Ship checklist
Two passes. Build-time gates verify the code; run-time gates verify the system in production.
Build-time
- Real source documents collected and attached before drafting begins↗ evaluating-output-accuracy-completeness
- Draft prompt states audience, purpose, and structure explicitly
- Claude instructed to flag any inferred or estimated content inline↗ task-type-prompting-strategies
- Every number, date, and name checked against the source, not skimmed
- Unsourced claims rewritten as open questions or removed↗ identifying-and-validating-ai-output-errors
- Audience-adaptation pass run after validation, not before↗ adapting-outputs-for-audience
- Named reviewer and date recorded before the deliverable ships
- Client-sensitive data confined to the approved workspace and product tier
Run-time
- Source-collection step happens before any drafting starts, not after
- Draft prompts explicitly request inline flagging of inferred content
- Validation checklist exists as a written artifact, not an unwritten habit
- Named reviewer + sign-off record required before any client send
- Team knows which client data tier is approved for use in Claude
- Escalation path exists for a discrepancy the reviewer can't resolve alone