Client communication
How to Write a Useful Matter Progress Email
A progress email that buries the decision wastes everyone's time. Lead with what changed or what you need, then give just enough context to act.
Most progress emails fail in the same way: they narrate. They walk the client through everything that has happened since the last message, in order, and somewhere in the fourth paragraph is the sentence that actually needed their attention, a decision only they can make, now surrounded by so much context that they miss it or set the whole thing aside to read properly later. Later rarely comes. A useful progress email respects that the client is busy and gives them the point first. Everything else in the message is there to help them act on that point, not to prove how much work you have done.
Put the reason for writing in the first line
Open with why this email exists. Is it a decision you need? An update they should note? A document you are attaching? The first sentence should tell them, so that even a client reading on their phone between meetings knows immediately whether they must respond now or can absorb it later. "We need your decision on whether to accept the revised timeline by Thursday" is a good opening. A paragraph of preamble before that same request is not.
Ask for one clear thing
If the client has to do something, make it a single, unmistakable request. Vague endings like "let me know your thoughts" invite silence, because the client cannot tell what a complete answer looks like. Instead, spell out the choice and what each option means:
- The decision you need them to make, stated as a question.
- The options, with the practical consequence of each in one line.
- The deadline, and what happens if it passes.
One email asking for one decision gets answered. An email asking for three gets deferred until the client has time for all three, which is never.
Give context in service of the decision
Background belongs in the email only to the extent it helps the client decide. If a detail does not change their answer, it can wait for a fuller update or the file. Keep the context tight, factual, and directly connected to the request above it, so the client reads it as the reason for the decision rather than as a separate history lesson. When there genuinely is a lot to convey, a short summary in the body with the detail attached serves the reader far better than a wall of text.
Verify before you hit send
A progress email carries dates, figures, and attachments that the client will rely on, so check them against the record first. Confirm the attachment is the right version, that the dates match the file, and that any figure you quote is the current one. Ask yourself whether the client could answer without another phone call; if not, add the missing piece before sending rather than after. A moment spent checking saves the correction email that undoes the confidence the first one built.
Close the loop when the reply arrives
The email is not finished when you send it. When the client responds, record their decision against the matter, note who is now doing what, and file the exchange so the instruction is captured and not just sitting in a thread. The next person to touch the file should be able to see what was asked, what was decided, and when, without reading the whole conversation back.
A progress email is a small act of client service. Lead with the point, ask for one thing, give only the context that helps, check it, and capture the answer. Do that and your emails become the ones a client opens first, because experience has taught them that yours are short, clear, and always about something that actually needs them.