Flawless Documents & Reports

The blank page no longer exists

Professional writing suffers from a paradox: it's almost never the hardest part of the job, but it's often the one that takes the most time. Marc knows exactly what to tell his client — it's in his head within three seconds. Putting it into proper shape, finding the first sentence, structuring the paragraphs: that's what costs him twenty minutes per document, several times a day.

With a digital coworker, the balance of power flips: putting things into words becomes instant, and your work shifts to what really has value — deciding on the substance, validating the tone, checking the facts. You never start from a blank page again: you start from a complete first draft that you correct. And correcting is ten times faster than creating, and far less tiring.

This chapter covers the four writing situations that come up most in a typical week: turning notes into minutes, adapting content for several audiences, writing delicate emails, and building templates that standardize the whole team's output.

From notes to minutes

Paste your raw meeting notes and ask for structured minutes: decisions, actions (with owners and deadlines), open points. Claude brings order to the chaos. Your notes can be telegraphic, full of abbreviations, out of chronological order: it doesn't matter — that restructuring is exactly the work you're delegating.

The "decisions / actions / open points" structure isn't decorative: it's what makes the minutes actionable. A decision without an owner or a deadline is wishful thinking; an unlisted fuzzy point will be forgotten until the next crisis. Always demand the "who does what, by when" — if your notes don't specify it, the minutes will show the empty slot, and that's valuable information: you'll know what to clarify with your team.

Here are my raw meeting notes: <paste>.
Turn them into minutes:
1. Decisions made
2. Actions (who does what, by when)
3. Points to settle next time
Stay factual, no fluff. If an action has no owner or deadline in my notes, write "TO CLARIFY" rather than inventing one.

One content, three audiences

The same substance can serve several audiences. Ask for the adapted versions from a single source: you keep consistency and save a huge amount of time. It's one of the most spectacular gains in practice: where you used to write three documents in an hour and a half, you validate three adaptations in ten minutes.

The classic trap of manual adaptation is drift: through repeated rewriting, the client version ends up saying something different from the internal version, and one day a client confronts two conflicting messages. By starting from a single source and asking for the adaptations, the substance stays rigorously identical — only the angle, the tone and the level of detail change.

Here are the internal minutes of our meeting about switching invoicing software: <paste>.
Adapt them into two versions:
1. Email to clients (10 lines max): what changes for them, what they need to do, reassuring tone, zero technical jargon.
2. Memo for the team (1 page): migration schedule, who does what, points of caution.
The substance must stay strictly identical across versions: same dates, same decisions.

Delicate emails: the right tone on the first try

Some emails cost ten times their length in mental energy: announcing a price increase, refusing a request, chasing an unpaid invoice without damaging the relationship, replying to an unhappy client. These are precisely the ones where assistance changes the game — not because the AI "knows better", but because it instantly offers you several angles and you're no longer writing in the heat of emotion.

The method: describe the situation with its relationship stakes, not just the facts. "Announce an 8% increase" will yield an administrative email. "Announce an 8% increase to a client loyal for ten years, who has already told us they find our fees high, and whom I absolutely don't want to lose" will yield an email that anticipates the objection, values the relationship and offers a gesture. The relationship stake is working data, just like an amount.

Context: accounting firm. The client Boulangerie Petit has been loyal for 10 years but has already told us they find our fees high. Our costs have risen and I must announce an 8% increase effective January 1st. I don't want to lose them.
Task: write this announcement email. Anticipate their objection on price, soberly recall the value delivered this year (e-invoicing compliance, 2 audits passed without adjustment), and offer a phone call.
Format: 180 words max, warm and direct tone, email subject line included.
Give me 2 variants: one more factual, one more relationship-focused.

Create your templates: YOUR firm's formatting

Provide 2 examples of your existing documents so Claude can mirror your usual formatting. This is the technique known as the template by example: rather than abstractly describing your style ("fairly formal but accessible..."), you show two documents you're proud of and ask for the template to be extracted — structure, tone, opening and closing phrases, typical length.

Once the template is made explicit, file it in your library and attach it to every writing request: "write this memo following this template". Result: every document from the firm comes out with the same stylistic signature, whether Marc or his colleague produces it. For a client, this consistency is a silent signal of professionalism.

Here are two client memos I'm happy with: <paste memo 1> <paste memo 2>.
Analyze them and extract a reusable template: typical structure, tone, length, opening and closing phrases, formatting.
Present this template as an instruction I can give you back for any future writing.

Proofreading and quality control

Writing assistance works both ways: producing, but also reviewing. Before sending an important document, ask for a targeted review pass: spelling and grammar of course, but above all clarity ("what could a rushed reader misunderstand?"), consistency ("are there internal contradictions?") and completeness ("what obvious question will the recipient ask that this document doesn't address?").

That last question is formidably useful. Marc applies it to every business proposal: "what objections could this prospect have that this document doesn't anticipate?". Half the time, the answer leads him to add a paragraph that would otherwise have caused a week-long email exchange. Critical review by the AI doesn't replace your judgment: it holds up a mirror before the client does.

Consistency as an asset

When several documents start from the same base, your firm speaks with one voice. That's a credibility gain as much as a time gain. Put the bricks of this chapter end to end: minutes always structured the same way, adaptations faithful to the substance, shared templates, systematic review — you get the document output of a firm much bigger than yours, without hiring.

And the benefit compounds over time: every template created, every phrasing saved enriches your capital. After three months, Marc hardly "writes" anymore in the sense he used to: he briefs, he validates, he adjusts. His relationship to professional writing has changed in nature — and the twenty minutes per document have become four.