Documents on Demand
Never start a report, proposal, or update from a blank page again — documents get assembled, not invented.
In this lesson, you'll learn to…
- 1Kill the blank-page tax: understand why recurring documents should never start from nothing
- 2Gather the three ingredients every document workflow needs: template, source material, standard
- 3Run draft → shape → check: the document version of the four-stage pattern
- 4Apply mini-recipes to the big three: the report, the proposal, and the update
- 5Turn every finished document into the template that makes the next one faster
The blank-page tax
"Every report, proposal, or update starts from a blank page."
Count what that blank page actually costs. It's not just writing time — it's the twenty minutes of staring, the 'how did I structure this last quarter?' archaeology, the re-deciding of decisions you already made last time: what sections, what order, what tone, how long. For a document you produce monthly, you are paying that decision tax twelve times a year *for the same decisions*.
Here's the observation that dissolves it: your recurring documents are repeats. The quarterly report is 'almost the same' as last quarter's — same structure, same audience, same tone, new numbers. The proposal is almost the same as the last proposal — same sections, new client, new scope. That phrase 'almost the same' should be setting off your Module 1 radar, because it means recurring documents are squarely inside what AI automates well.
One clarification before we start, so this lesson doesn't overpromise: this is about recurring documents — the ones you produce again and again in a stable shape. A genuinely novel piece of thinking — your first-ever strategy memo, a sensitive personal letter — still deserves the blank page. Novel work needs your full attention; it always did. We're here for the twelve-times-a-year documents.
Key idea: A document you've written five times is not a writing task anymore — it's an assembly task wearing a writing costume. Recurring docs get assembled. Novel thinking still gets the blank page — and your full attention.
Documents are assembled, not invented
Watch yourself write a recurring document honestly and you'll see you're not really writing — you're doing three jobs at once, badly interleaved: remembering the structure (what sections, what order), gathering the period's information (this month's numbers, this client's details), and wording it in the expected tone and format.
The blank page forces you to do all three simultaneously, which is why it feels heavy. The assembly method separates them: the structure gets remembered ONCE (that's a template), the gathering becomes a checklist (that's your source material), and the wording — the 'almost the same' transformation — goes to the AI stage with your review on top.
This is the same four-stage pattern you've now run twice in this module, pointed at documents: Input = template + this period's source material. AI = assemble the draft in the template's structure and your voice. Review ★ = facts first (every number checked), then completeness, then tone. Output = the finished document, delivered — and saved as next time's even-better template.
Maria's Friday status email from Module 2? That was this method in miniature. Today we scale it to the documents that take an hour, not five minutes.
Document assembly
The three ingredients
Every document workflow needs exactly three things on the counter before the AI stage can produce something worth reviewing. Miss one and you get the classic failure: a confident, generic document that reads like it was written by someone who's never met you — because, in the ways that matter, it was.
1 — The template
Your best past version of this document, blanks marked. Not a description of the structure — the actual document. It carries your sections, order, tone, and length in one artifact.
2 — The source material
This period's real information: the numbers, the client details, the week's updates. Gathered BEFORE drafting — a 5-line checklist per document type ends the mid-draft scavenger hunt.
3 — The standard
The output's contract: audience, length cap, tone, the anti-invention rule. 'For leadership, under one page, plain language, never invent numbers — mark gaps as ASK.'
Pro tip: The template is the highest-leverage ingredient and the one beginners skip. Thirty seconds of 'use this structure' beats three paragraphs of describing what you want — show, don't describe.
Draft → shape → check
With ingredients gathered, the writing session becomes three short passes instead of one long grind.
Draft — hand the AI all three ingredients and get a full first draft in the template's structure. Resist the urge to perfect the prompt; a decent draft to react to beats a perfect prompt you spent twenty minutes on.
Shape — react to the draft *as an editor, not a typist*: 'cut section 3 in half,' 'the risks section is missing the vendor issue — here are the details,' 'make the opening less formal.' Each instruction is seconds of your judgment steering minutes of AI rework. This conversational shaping is where the document becomes genuinely yours — and it's a skill that improves fast with use.
Check — your ★ gate, and in documents it has a strict order. *Numbers first:* verify every figure against the source material — AI can transpose, mislabel, or invent numbers, and it does so confidently; in a report, a wrong number is the one unforgivable error. *Completeness second:* did anything from the source material silently vanish? *Tone last:* does it sound like you, for this audience? Ten minutes of three-pass review on an assembled draft consistently beats sixty minutes of blank-page writing — and produces a more consistent document.
Watch out: In document review, numbers outrank everything. A slightly stiff sentence embarrasses nobody; a wrong figure in a leadership report follows you around. Check every number against the source — every time, no exceptions.
Mini-recipes: the big three
The assembly method, tuned to the three documents that dominate office life:
The recurring report (weekly / monthly / quarterly)
TEMPLATE: last period's report, numbers blanked. SOURCE: this period's data, gathered by checklist. STANDARD: same length as last time, plain language, every number sourced. The AI's extra job: 'flag anything unusual versus last period' — it drafts the what, you supply the why. REVIEW: numbers → completeness → tone.
The proposal
TEMPLATE: your best-ever accepted proposal, client details blanked. SOURCE: this client's situation, needs, scope notes from your call. STANDARD: their language (mirror the words THEY used), your proven structure, no promised deadlines or prices without your explicit input. REVIEW: heaviest of the three — every commitment is Lane A material and gets your careful read.
The status update
TEMPLATE: your standard format (you built this in Module 2). SOURCE: the tracker, plus this week's meeting notes — which your Lesson 2 archive now supplies automatically. STANDARD: short, scannable, honest about blockers. This is the lightest of the three — and notice the system compounding: one workflow's output is now another workflow's input.
Key idea: After each document ships, one last move: save it as the new template. Every cycle, your template absorbs this period's improvements — the same compounding you built into the Reply Library and the standing block.
Prompt Lab
Every prompt below is exactly what you saw in the lesson. Copy them, use them, make them yours.
The document assembler
Any recurring document, three ingredients ready. This is the 'draft' pass — shape conversationally afterward, then run your numbers-first check.
Assemble a draft of my recurring document from the three ingredients below. Follow the TEMPLATE's structure, section order, tone, and length exactly — it is my best past version with blanks marked. Fill it using only the SOURCE MATERIAL; never invent facts, numbers, names, or commitments — write ASK wherever information is missing. Flag anything in the source that seems unusual compared to what the template implies is normal. THE STANDARD: [audience · length cap · tone]. THE TEMPLATE: [paste best past version, blanks marked]. THIS PERIOD'S SOURCE MATERIAL: [paste the gathered information].
Why it works: The template shows structure and voice instead of describing them — the single biggest quality lever. Restricting the AI to the source material plus the ASK rule turns your review into a fast verification pass instead of a rewrite. The 'flag anything unusual' line makes the AI surface what deserves your judgment.
AI Workflow View
How AI fits into the real-world process — step by step.
Gather
Template + source material + standard
Draft
AI assembles in your structure and voice
Shape
You direct as editor — seconds steer minutes
Check ★
Numbers → completeness → tone
Ship + save
Delivered — and saved as the next template
The document engine: three ingredients in, three passes through, every number checked, and each finished document becomes next period's template. The blank page never returns.
Hands-on Lab: Build One Document Kit and Ship One Real Document
0/8 steps done
Pick the recurring document that costs you the most — the monthly report, the standard proposal, the weekly update — and build its permanent kit, then use it for real.
Your Turn: Do It Yourself
Now it's your turn. Follow these steps and check them off as you go.
You'll know it worked when:
One permanent document kit (template + checklist + standard) and one real document shipped in roughly a third of the usual time — with a review pass that caught anything the draft got wrong.
Going further:
Build a second kit for a different document type from the big three. The second one takes half as long to set up — and that acceleration is the feeling of owning a method rather than a trick.
Download Resources
Knowledge Check
4 questions — click the best answer for each scenario, then check your answers.
Question 1. Which document should still start from a blank page?
Question 2. Your assembled draft reads generic — correct structure, but it could have been written by anyone. Which ingredient was most likely missing or weak?
Question 3. In the document check pass, what gets verified FIRST?
Question 4. What's the last step after shipping an assembled document?
0/4 answered
Key Takeaways
- Recurring documents are 'almost the same' repeats — assembly tasks, not writing tasks; novel thinking still gets the blank page
- Three ingredients before drafting: the actual template (show, don't describe), a source checklist, and the standard
- Draft → shape → check: AI assembles, you direct as editor, then verify numbers → completeness → tone
- In documents, numbers outrank everything — check every figure against source, no exceptions
- Save every shipped document as the next template — the kit compounds like the Reply Library
Lesson Summary
The blank page was a tax on decisions you'd already made — and you've stopped paying it. Recurring documents now run through the assembly engine: three ingredients gathered, AI drafts in your proven structure, you shape as an editor, and your check verifies numbers first, always. You built a permanent kit for your most expensive document, shipped one for real, and set up the compounding loop where every finished document improves the next. Your workday system now covers email, meetings, and documents. One thief left: the admin swarm — scheduling, reminders, and status pings — and the autopilot hour that Module 3's final lesson reclaims.
BrainTrain Pro Tip
Keep a 'gathering doc' open during the period between documents: every time a number, decision, or update crosses your desk that next month's report will need, paste it there with a date. When drafting day comes, your source material is already gathered — the scavenger hunt was the real time thief all along.
Module 3: Automate Your Workday
0/4 doneYou'll know it worked when:
One permanent document kit (template + checklist + standard) and one real document shipped in roughly a third of the usual time — with a review pass that caught anything the draft got wrong.
Going further:
Build a second kit for a different document type from the big three. The second one takes half as long to set up — and that acceleration is the feeling of owning a method rather than a trick.
