Module 13 · Lesson 01

Document Drafting and Editing Loops

Reading time: 16 minutes Track: Claude Fluency for Teams · Knowledge worker path

The right mental model for writing with Claude

The biggest mistake in AI-assisted writing: treating Claude as a ghostwriter who produces finished content for you to use as-is. The result is generic, impersonal, and often misses important context you had but didn't convey.

The right model: Claude is an accelerator for your own thinking. You bring the ideas, the knowledge, the judgment, and the final voice. Claude handles the drafting, restructuring, and editing — the mechanical parts of writing that consume disproportionate time.

The three-phase workflow

Phase 1: Brain dump, not draft request

Instead of asking Claude to write something from scratch, give it the raw material:

I need to write a project update for the engineering team. Here's my brain dump of what happened this week:
- We shipped the new caching layer — 40% latency reduction on average
- The auth bug we had last week: root cause was a race condition in token refresh, fixed Thursday
- Deployment pipeline is now fully automated — big deal, took 3 months
- Next week: starting the database migration planning

Turn this into a clear, concise project update in 3 bullet points per area.
Format: [Context] [What changed] [What's next]

This is dramatically better than "write a project update for the engineering team" — you've given Claude the actual content; it's just structuring and polishing.

Phase 2: Structure review before prose

For longer documents, review structure before prose:

Here's an outline for the Q3 product review:
[paste outline]

Before I write any prose: does this structure make sense for a 15-minute executive presentation?
What's missing? What would you cut?

Getting structure right before writing saves significant rework.

Phase 3: Targeted editing, not full rewrites

When editing, be specific about what needs to change:

Edit paragraph 2 only. It's too hedgy — remove every "might" and "could consider" and
replace with direct statements. Preserve the substance.

This is more effective than "make it more direct" applied to the whole document.

Document type patterns

Executive summary (any length)

Here is [document/data/meeting notes]. Write a 3-paragraph executive summary.
Paragraph 1: Situation. Paragraph 2: Key findings. Paragraph 3: Recommended actions.
No jargon. Decision-maker audience with 3 minutes.

Email drafts

Draft an email to [recipient/role].
Purpose: [what you need to communicate or get]
Tone: [professional/warm/direct/formal]
Key points to cover: [list them]
Length: [approximate]

Proposal or business case

Help me write a one-page proposal for [initiative].
Problem: [describe it]
Proposed solution: [describe it]
Why now: [the urgency]
What you're asking for: [resources/approval/budget]
Audience: [who approves this]

The voice calibration technique

Claude's default writing voice is often slightly more formal and generic than your own. To get output that sounds like you:

1. Paste 2-3 paragraphs you've written yourself
2. Say: "Match this writing style for the following task: [task]"

This is one of the most useful techniques for anyone who writes regularly — it trains Claude to your voice from just a few examples.

Quality check before sending

Before any Claude-drafted external document leaves your hands:

• Read it aloud — awkward phrasing is easier to hear than see
• Check every specific claim or number against the source
• Ask yourself: does this sound like me, or like a committee?
• For important communications: does this achieve the actual goal?