Emails, Minutes & Client Updates

Most of a practice's writing is not proposals and reports; it is the steady stream of shorter pieces that keep everyone informed and aligned. Three kinds recur, and Claude handles each well when you direct it properly.

Client and consultant emails. The routine ones - confirming a decision, chasing a drawing, answering a query - Claude drafts in seconds. The valuable case is the hard email: the one where you have to deliver bad news, decline a request, or push back on a late change without souring the relationship. Here Claude earns its keep not by knowing what to say but by giving you options: ask for three versions - one firm, one warm, one neutral - and you will often find the right line faster than staring at a blank message, because reacting to a draft is easier than starting one.

Meeting minutes. You come out of a site meeting with two pages of shorthand: half-sentences, arrows, who said what, three things someone must do. Claude will turn that into structured minutes - attendees, discussion, decisions, and crucially an actions table with owners and due dates - in one pass. This alone can save an hour a week and, more importantly, actually get written instead of forgotten.

Progress updates. Weekly or monthly, to a client or your own team. Give Claude your bullets on what moved, what is stuck and what is next, and it produces a readable, consistent update in your chosen format. Consistency matters here: a client who gets the same clear shape every Friday trusts the project more than one who gets a wall of text when something goes wrong and silence when it does not. The rhythm itself is reassurance: it tells the client the project is being held, whether the week's news is good or dull, and that steadiness is worth as much as any single update in it.

There is a fourth category worth naming: replies you draft into an existing thread. Paste the message you are answering and Claude will pitch its reply to that context - picking up the sender's questions, mirroring their level of formality, and not repeating what has already been said. This is one of the fastest wins of all, because the hardest part of a reply is usually holding the whole thread in your head, and Claude reads it in a second. As always, you decide what to concede and what to commit to; Claude just gets a good first draft onto the page far faster than the blank reply box ever will.

Minutes deserve their own warning, because they are the piece of correspondence with the longest memory and the sharpest teeth. Months later, when there is a dispute about what was agreed, the minutes are the record everyone reaches for. That makes them a high-stakes document dressed as an administrative chore.

Here is the hard limit, stated plainly: Claude cannot know what happened in your meeting - it only knows what you wrote down. If your notes are thin, Claude will fill the gaps with plausible-sounding decisions that were never made, plausible owners for actions no one accepted, and plausible dates no one agreed. It is not inventing maliciously; it is doing what a plausibility engine does - completing the pattern of what minutes usually contain. A minute that records a decision that never happened, or assigns an action to someone who never took it, is not a tidy document; it is a liability with your name on it.

So the discipline is twofold. First, feed it real, specific notes - the more you capture in the room, the less Claude has to guess. A directing prompt helps:

Turn these raw meeting notes into minutes. Use ONLY what is in the
notes - do not add decisions, owners or dates that are not there.
Where something is unclear or missing, list it under "To confirm"
rather than guessing. Format: attendees, discussion by topic,
decisions, and an actions table (action / owner / due date).

Second, read the output against your memory of the room before it goes out, paying closest attention to the decisions and the actions table - the exact places a plausible-but-wrong line does the most damage. Circulating minutes with a short "corrections within 48 hours" line is good practice anyway; it also catches anything you and Claude between you got wrong. The habit to internalise is that structure is Claude's to give and substance is yours to guarantee: a beautifully formatted set of minutes is worthless, even harmful, if a single decision in it never happened. Speed on the formatting, never on the truth.

The second trap in correspondence is subtler than a wrong fact but just as corrosive: tone. A client who has exchanged fifty emails with you knows how you write. When one arrives that is suddenly smoother, longer, and studded with phrases you would never use - I hope this email finds you well, please do not hesitate to reach out - it reads, correctly, as not-quite-you, and a small trust erodes. The fix is not to avoid Claude but to teach it your voice.

The most reliable method is by example, not description. Rather than telling Claude "write in a friendly professional tone" - which produces the average of a million emails - paste two or three of your own real messages and say: match this voice - the length, the level of formality, the way I open and sign off. Claude mimics a concrete sample far better than it invents a register from an adjective. The tone dial in the figure is worth keeping in mind: most client mail sits in the cordial-to-businesslike middle, a friendly note swings warm, and a formal notice or a dispute swings the other way. Name where on that dial you want to be, each time.

There is also a length discipline. Left alone, Claude tends to over-write - three sentences where one will do, a paragraph of context nobody asked for. For everyday email that is a fault, not a feature; busy clients skim. Tell it the length you want ("under 120 words", "three short paragraphs") and cut ruthlessly. The best test is the read-aloud: if a sentence sounds like a brochure or a form letter when you say it out loud, it is not yours yet. Fix it, and over time you will build - in a Project, as Lesson 5.4 shows - a saved sense of your voice that every draft starts from.

Everyday correspondence feels low-stakes, and most of it is - but the cost of a mistake is not always small. An email that concedes a point you did not mean to, a set of minutes that misrecords a decision, an update that over-promises next week's drawings: each is a plausible draft that slipped through because it looked fine. A light, fast, habitual check keeps the speed and removes the risk.

For emails, before you send, ask three quick questions. Does it say what I actually mean, including the things I am declining or qualifying? Does it commit me to anything - a date, a deliverable, a concession - that I did not intend? And does it sound like me? For anything with commercial or contractual weight, apply the proposal-grade caution from the last lesson: the same rule that a plausible number is a promise applies to a plausible sentence in an email.

For minutes and updates, the check is against reality: does every decision and action match what truly happened and what you truly plan? Never let Claude's version become the record without your eyes on it.

The pay-off is real and daily. Practices that use Claude well for correspondence do not send more email; they send it faster, more consistently, and with less dread - and they get the hour back that used to disappear into inbox friction. Used carelessly, though, it becomes a machine for generating plausible, off-key, occasionally wrong messages at speed. The difference, as always, is the human who directs the draft and reads it before it goes. Build the send-safe check into muscle memory now, while the stakes of any single email feel small, and it will be there automatically on the day one message really matters.