# How to Write an Update Email That Your Manager Will Actually Read Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-an-update-email/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-an-update-email.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer How to write an update email your reader can act on: nine rules covering the subject line, the opening status, blockers, next steps, and how long it should be. ## Key facts - Title: How to Write an Update Email That Your Manager Will Actually Read - Category: Communication - Primary skill: Communication - Related skills: Working with Your Manager, Influence - Primary keyword: how to write an update email - Source page: https://headwayskills.com/knowledge/communication/how-to-write-an-update-email/ ## What this page covers - How to write an update email your reader can act on: nine rules covering the subject line, the opening status, blockers, next steps, and how long it should be. - Practical guidance for how to write an update email - How this topic connects to Communication ## Detailed explanation The cursor sits in an empty draft while you try to work out how much of the last two weeks anyone actually wants. To write an update email, name the project and the purpose in the subject line, state where things stand in your first sentence, list what is finished and what is blocked, close with the next step and who owns it, and keep the whole thing under about 250 words. None of that is contested. Nearly every guide agrees on it. What they leave you to work out alone is the judgment underneath — what counts as worth reporting, and what to do when the honest answer is that you are behind. ## Which update email are you writing Two different messages share the name, and roughly a third of the top results for this search are about the other one. There is the update you send, which reports on something you are responsible for. And there is the update you ask for — the polite chase you send when a hiring manager, a client, or a colleague has gone quiet on something you are waiting on. Indeed keeps a separate page for that version, and the convention there is a much shorter message: 60 to 120 words, one to three short paragraphs, opening with a reference to the earlier exchange and closing with a specific question about where things stand. Everything below is about the first kind. ## How to write an update email, rule by rule The rules are settled enough to treat as a checklist. Read for the reason behind each one; that is what lets you make the call when a situation does not fit. ### 1. Decide who the To line is for before you draft Indeed's list of what an update should contain starts with the recipient and the objective, before any of the content — which is the right order, even if almost nobody writes that way. Who is on the To line determines what counts as relevant. A manager needs decisions and risks. A client needs outcomes and dates. A project team needs handoffs. Put the people who have to act or decide in To, and the people who only need to know in Cc. Reusing whatever address list the last thread happened to have is how updates end up written for nobody in particular. ### 2. Put the project and the purpose in the subject line "Update" is named across the guides as one of the worst subject lines you can send, alongside "Hello" and "Important." The argument against it is practical rather than stylistic. A generic line cannot be prioritized in a full inbox this morning, and it cannot be found by search in six months — which is exactly when someone goes back to reconstruct who knew what and when. Name the thing, then the type of message: the project plus "status update" or "weekly progress." Keep it under roughly 60 characters so it survives the preview pane on a phone. ### 3. Open with the headline status in one sentence Every top-ranking guide specifies the same thing directly under the greeting: one sentence saying where things stand. On track, slipping, blocked, finished. This is harder than it sounds. You are writing from inside the project, where the background feels necessary and the conclusion obvious — so you start with the background. Your reader has the opposite problem. They have not thought about this since the last update and need orienting before any detail means anything. Write the summary sentence first and let everything after it serve as the evidence for it. ### 4. Report outcomes, not an activity log "Writing too much" appears on every list of common mistakes, and the mechanism named is specific: long runs of tasks and context hide the decisions and concerns the reader is scanning for. The instinct is understandable, since a long list looks like proof of effort. But an update is not a timesheet. Swap what you touched for what is now finished and what changed as a result. "Drafted, revised and circulated the spec" is activity. "The spec is approved, so build starts Monday" is something the reader can act on. ### 5. Raise blockers early, and know when the update is the wrong place for them Hiding blockers is among the most consistently named failures across sources, and burying one has much the same effect as hiding it: put a risk below four paragraphs of completed work and [stakeholders](/knowledge/influence/stakeholder-management/) either miss it or read it as minor. Move it up, and attach the specific thing you need — a decision, an introduction, another two days. A blocker with no ask beside it reads as a complaint rather than a request. Fyxer adds a rule worth keeping: something genuinely urgent does not belong in the weekly update at all. Send it on its own, or say it out loud. The regularity that makes a routine update useful is what makes it the wrong container for anything that cannot wait. ### 6. Say what slipped plainly, then say what you are doing about it Sources uniformly tell you to be [honest about what did not work](/knowledge/communication/difficult-conversations-at-work/). None of them show you how, and that gap is where most drafts stall, because honesty with no remedy attached reads as either an excuse or a plea. The shape that holds up is three short parts in order: what happened, stated flatly and without adjectives; what it means for the date; what you are doing next. "The vendor missed their delivery, so testing moves to the 14th. I have asked for a firm date and will confirm on Thursday." No apology paragraph, no account of how hard you worked. Getting that right is judgment rather than formatting, which is why it stays hard even once you know the rules — and [a read on your habits](https://assessment.headwayskills.com/) tells you more about that than another checklist can. ### 7. Close with next steps that have an owner and a date Forgetting the next steps sits on the standard list of mistakes, and the cost is named plainly: ambiguity here produces a round of follow-up messages and the delay that comes with them. End with what happens next, who is doing it, and when. That includes the case where nothing is required from the reader, since "no action needed from you this week" is a real closing and it spares them working out whether that is true. An update that finishes with "let me know your thoughts" has handed the reader a decision instead of making one. ### 8. Keep it under about 250 words and let bullets carry the density The ceiling the sources agree on is roughly 250 words, and it is not a matter of taste. Updates are read in an inbox queue, between other things, so length reduces how much gets taken in — the longer version usually communicates less. Once the content gets dense enough that a reader would have to go back over it, switch to bullets: finished, in progress, blocked, next. If you cannot [get under 250 words](/knowledge/communication/to-write-a-concise-email-message/), that is usually a sign that two different updates are competing inside one email. ### 9. Send on a fixed rhythm, with the same shape every time The last rule is the one that makes the other eight cheap. Pick a day, hold it, and reuse the same section order every time. Two things follow. Your reader learns where the blockers live and can take in the fifth update in fifteen seconds rather than parsing it. And you stop facing a blank draft, because the structure is already decided and only the content changes. This is also the point where the update stops being an errand and starts doing something for you: never having to be chased for status is a specific and fairly rare [reputation](/knowledge/influence/build-good-reputation-work/) to have. ## What the rules are really describing Set the nine rules side by side and the email part looks incidental. Working out who needs to know, leading with the conclusion instead of the context, saying the uncomfortable thing early and without decoration, keeping a promise about when the next one arrives — move any of that to a stand-up or a chat channel and it still holds. **Communication** underlies nearly all of it. Put the main point first. Be brief. Be direct enough that nobody rereads a sentence hunting for the meaning. Pitch the level of detail at whoever is reading. And before any of that, decide whether this belongs in writing at all — writing suits information moving one way and anything that needs a record, while a conversation suits the sensitive, the complicated and the negotiable. A great many badly received updates are conversations that got sent instead of spoken. **Working with Your Manager** is the relationship most of these updates land in. The useful shift is away from reporting for inspection and toward delivering your side of a partnership: making your results visible in the stretches between one-on-ones, staying honest when the honest version is uncomfortable, bringing a problem with a proposed move attached rather than on its own, and making sure your manager hears it from you before they hear it from somebody else. **Influence** is the part you cannot see from inside any single email. Reputations are built out of unremarkable things done reliably, and following up on commitments until they are genuinely finished is one of them. The person whose updates arrive before anyone asks, and whose stated dates hold, ends up handed the work that matters — not through campaigning for it, but because trusting them costs nothing. The free Job Skills Test takes the same view of this that the nine rules do: adjustable behavior, not a fixed aptitude. It puts real working situations in front of you rather than asking what you know in theory, and reports across the whole set the framework uses, **twelve skills** in all, of which the three above are one slice. What you get back is [where each of these stands](https://assessment.headwayskills.com/) against the other nine — so instead of a description of what a good update looks like, you have a specific part of your own version to work on. ## What changes once these calls get made on purpose Parts of this may already be familiar: the pause before sending something that contains bad news, the second look at a subject line, the feeling that you have written a great deal without saying much. Noticing that is most of the skill. The rest is repetition, and none of it asks you to become a different kind of writer — only that a handful of decisions you currently make by feel start getting made deliberately. The stakes climb quietly as well. Early on, an unclear update costs one follow-up message. Later, when more people depend on information only you hold and fewer sit anywhere near you, it costs a decision made on a wrong assumption. You went looking for the convention rather than guessing and hoping it landed, which is the part most people skip. What is left is finding where your own version sits. ## Find your starting point The only thing left is to look. The Job Skills Test is a **free** self-assessment of how you work: it puts real situations in front of you rather than asking what you know in theory, and scores you across all twelve skills — communication, the working relationship with your manager, and the credibility that follow-through builds among them. What comes back is ranked: which are already strong, and which one or two would repay attention over the next few months. There is no hurry attached to it. Take it when you have a quiet seven minutes, and the next update you write starts from a clearer sense of what you are actually working on. **[Take the skills test](https://assessment.headwayskills.com/)** *It's free, takes about 7 minutes, and your results appear right away.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? How to write an update email your reader can act on: nine rules covering the subject line, the opening status, blockers, next steps, and how long it should be. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Working with Your Manager, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/how-to-write-an-update-email/ Preferred summary: "How to write an update email your reader can act on: nine rules covering the subject line, the opening status, blockers, next steps, and how long it should be." ## Change log - 2026-07-07: Content collection version published.