Outcome
By the end of this article, you'll be able to turn a messy pile of bullet points into a real first draft in minutes, pull the three things that actually matter out of a 12-page report before a meeting, and stop re-explaining your formatting preferences every single time you ask for help. You'll still be the one who signs off on the document — but you won't be the one starting from a blank page anymore.
This is the third free module in the Work track, after automating your inbox and your meetings. Documents are next because they're where a lot of your best hours quietly disappear: drafting the update nobody reads twice, skimming the report you were handed an hour before the meeting, reformatting the same proposal for the fifth time this quarter.
Concept
Every document task at work is really one of three jobs:
- Writing — turning scattered notes into something structured.
- Reading — pulling the relevant signal out of something long.
- Formatting — keeping tone and style consistent across everything you produce.
AI is genuinely good at all three, but only if you remember the delegation loop from earlier modules: context, guardrails, review. You give it what it needs to know, you tell it what not to do, and you check its work before it goes anywhere near a colleague or a client.
Documents raise the stakes a little higher than an email or a meeting recap. A wrong number in a meeting summary is awkward. A wrong number in a report that goes to a client or your boss's boss is a problem. So the review step isn't optional here — it's the whole reason this workflow is safe to use.
Build
1. Rough notes → structured first draft
You don't need polished thoughts to get a polished-looking draft. You need the actual content — even in fragments — plus a clear shape for the AI to pour it into.
I need a first draft of a project status update for my manager.
Context: this is for the Q3 website redesign project. Audience is my
manager, who wants the headline first, not the process.
Here are my rough notes:
- design phase done, dev started last week
- one delay: waiting on stock photo licensing, pushes launch ~5 days
- budget still on track
- need manager to approve the new launch date
Structure it as: Headline status, Key updates, Risks/blockers, What I need
from you. Keep it under 200 words. Don't invent any numbers or dates I
didn't give you.
Notice what's doing the work: real notes (even messy ones), a named audience, a requested structure, a length limit, and an explicit guardrail against inventing details. That last line matters more here than almost anywhere else in this course — more on why in a moment.
What you get back is a draft, not a finished document. It'll need your voice, your judgment on what to emphasize, and a final read. But you've skipped the hardest part: turning a blank page into a structured page.
2. Long document → what matters for your purpose
Generic summaries are a trap. "Summarize this" gives you a summary of everything, weighted toward whatever the AI thinks is important — which isn't the same as what's important to you.
Instead, tell it the job the summary needs to do:
I have a 14-page vendor proposal attached. I'm reading this to decide
whether to recommend we switch vendors in our Thursday leadership meeting.
Pull out only:
1. Pricing changes vs. our current vendor
2. Anything that affects our current contract or renewal timeline
3. Red flags or unusual terms I should ask about
Skip the vendor's marketing language and background sections entirely.
Same document, completely different — and far more useful — output than a generic "summarize this" would give you. The purpose you state (a decision, a meeting, a deadline skim) is what tells the AI what to keep and what to throw away.
3. A reusable house style, instead of repeating yourself
If you've ever caught yourself typing "make it more concise, use headers, no corporate jargon, sign-off with my name" for the fifth time this month — save it once instead.
Keep a short "house style" note somewhere you can paste from (a notes app, a doc, a saved snippet) and drop it into any drafting prompt:
House style: Plain, direct language. Short paragraphs, no more than 3
sentences each. Use headers and bullet points over dense prose. No
corporate jargon ("synergy," "leverage," "circle back"). Sign off as
"Best, Alex."
Paste that at the top of any drafting request, and you get a consistent voice across every report, update, and proposal — without re-teaching your preferences every time. This is the same instinct as the guardrails you set up in B1 and B2: define it once, reuse it everywhere.
Run
Two habits make this sustainable instead of risky:
Fact-check anything with numbers, quotes, or claims — every time. AI is excellent at structure and language. It is not a source of truth for facts it wasn't explicitly given. If a draft includes a statistic, a date, a quote, or a claim you didn't hand it directly, treat it as unverified until you check it. This is the single most important guardrail in this entire module — documents carry more weight than a quick email, and a confident, wrong number in a client-facing report is exactly the kind of mistake this habit prevents.
Review before it leaves your hands. A first draft is a starting point, not a send-ready file. Read it once for accuracy (the facts you fed it are right, and it didn't invent any new ones), and once for voice (does this still sound like you, or like a house style you'd never actually approve).
Once these two habits are automatic, the writing and reading grind gets dramatically lighter — you're editing and deciding, not starting from nothing and not drowning in fourteen pages you don't have time to read.
Ready to build the full workflow — inbox, meetings, and documents together?