# How to Write an Update Email to Your Boss Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-an-update-email-to-your-boss/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-an-update-email-to-your-boss.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer An update email to your boss has a standard shape. What to include, how long it should be, how often to send one, and how to report a delay without excuses. ## Key facts - Title: How to Write an Update Email to Your Boss - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Influence - Primary keyword: how to write an update email to your boss - Source page: https://headwayskills.com/knowledge/working-with-your-manager/how-to-write-an-update-email-to-your-boss/ ## What this page covers - An update email to your boss has a standard shape. What to include, how long it should be, how often to send one, and how to report a delay without excuses. - Practical guidance for how to write an update email to your boss - How this topic connects to Working with Your Manager ## Detailed explanation You have something to tell your manager, the cursor is sitting in an empty message, and the hard part turns out not to be the news itself but deciding how much of it to write down. There is a standard answer to this. To write an update email to your boss, open with one line on where things stand, list what you finished since the last update, name any delay or risk alongside the step you are already taking, say what comes next, and close with anything you need a decision on — kept short enough to skim in about two minutes. That shape holds for nearly every update you will ever send. What changes is the kind of update you are writing, and there are five of them that do quite different jobs. ## What every update email to your boss needs The structural advice in this area is unusually consistent. Across the guides that dominate the topic — Indeed, Fyxer, Techno-PM and the project-management template collections — the same six elements recur: [a descriptive subject line](/knowledge/communication/business-email-writing/), a one-sentence bottom line at the top, completed work as scannable bullets, any risk or blocker paired with a response, next steps, and an explicit ask if you need something from your manager. You are not expected to invent a format here. Matching the one your manager already recognizes is most of the job. Four of those elements are worth spelling out, because they are where updates usually go wrong. The subject line is a filing tool rather than a headline. Indeed's guidance treats it as the place your manager decides how urgently to open the message and, three weeks later, how to find it again. Name the project and the nature of the message — a completion, a delay, a request — instead of writing something general like "Quick update." Length is set by the decision, not by the effort. Fyxer's rule is that an update should be long enough to support whatever action it needs and short enough to skim quickly. That is the reason all the formatting advice exists: bullets, labels and a summary line are there so the message survives being read on a phone between two meetings. A long update is not evidence of a productive week. It is a cost you are handing to someone whose inbox is already full. Write in the register your manager already uses. The most practical tone advice in this area, also from Fyxer, is simply to mirror the tone of your manager's own emails. It removes the guesswork about formality, and it means you never have to decide in the abstract how formal to be. Do not re-explain what they already know. Woculus warns against technical vocabulary your manager does not share, and against restating background they already hold. An update is a reminder and a decision aid, not a briefing document. Over-explaining is the standard failure of a careful writer trying to show effort, and it reads as the opposite. ## Five kinds of update email, and what each one is for The sources that treat this seriously use the word "update" for several different messages. Working out which one you are actually sending settles most of the questions about length, tone and timing before you write a word. ### The recurring progress update A scheduled message on a fixed rhythm, summarizing what moved since the last one, what is in flight now, and what comes next. Its value comes from the rhythm rather than from the content of any single instance, which means a quiet week is still worth reporting — the absence of one of these is itself a signal to your manager. On frequency, the advice across Fyxer, Techno-PM and SafeMailer is explicitly situational: weekly is the common default, biweekly or monthly suits slower-moving work, and daily updates are warned against on the grounds that they overwhelm the reader and dilute the signal. No source claims a universally correct rhythm, which is the useful part. It is something to [agree with your manager once](/knowledge/working-with-your-manager/one-on-one-with-manager/) rather than something to look up. ### The milestone or completion update Event-triggered rather than calendar-triggered. It confirms that a defined piece of work is finished, names what was delivered and when, and points at whatever comes next. Subject-line patterns like "Task Completed — [task title]" show up repeatedly in the template collections for exactly the reason above: this is the message your manager will search for later. Keep it short. Its job is to close a loop they have been holding open. ### The risk, delay, or blocker update The only type where timing matters more than wording. Its usefulness decays quickly, and sent late it stops being an update and becomes an explanation. Report the problem with its impact, and pair it with the step you have already taken or [the specific help you need](/knowledge/teamwork/ask-for-help-at-work/) — never as a bare problem statement. Techno-PM and Unichrone both give the same practical reason rather than a moral one: a manager reading a bare blocker has to do the diagnostic work themselves, which is what makes the message feel like a burden. Sending this one early, with a proposed response attached, is what keeps a delay from looking like carelessness. ### The decision request An update whose real purpose is to get an answer. It carries just enough context for your manager to choose between named options, says what will happen by default if no answer arrives, and gives the date by which you need one. Because they have to do something after reading it, the ask has to be single and unmissable. Two questions buried in six paragraphs is how a decision request quietly becomes a message that gets marked as read. ### The escalation The message that leaves your own [decision-making authority](/knowledge/working-with-your-manager/how-to-align-expectations-with-your-manager/) behind. Project-management sources treat it as a separate genre from the routine status update: state the issue, its impact, why it needs your manager's authority specifically, and what guidance or approval you are asking for. This matters because the hardest case for most people is precisely the one where the recurring update is the wrong vehicle — the problem is not that you worded it badly, but that it should not have been a bullet inside a weekly summary at all. ## How to decide what is worth including The single most useful idea in this landscape is not about wording. May Busch's guidance is to filter for what affects timing, risk, cost or priorities, and to leave out routine housekeeping unless it carries real weight — because what you choose to include tells your manager whether you see the bigger picture. That reframes the problem you actually have. The difficulty in an update email is rarely the sentences; it is the judgment about what matters to someone whose view of the work is wider than yours. That judgment is a work skill rather than a writing trick, which also means it is something you can measure and build instead of guess at, and a short assessment will [show where your skills stand](https://assessment.headwayskills.com/) before you settle into a habit you will repeat every week for a year. ## The skills behind an update your manager can use Notice how little of the above was really about writing. The subject line and the bullets are quick to learn. What takes longer is knowing what your manager needs to hear, saying it plainly, and being someone whose reports are trusted when the news is bad. **Working with Your Manager** is the skill doing most of the work here. The update email is the everyday instrument of two things this skill treats as central: actually communicating rather than quietly avoiding it, and making your results visible instead of assuming they are noticed. It also covers bringing a proposed response rather than a bare problem, being honest when the honest version is uncomfortable, and agreeing with your manager what you are free to decide alone. Once the rhythm and the level of detail are settled with the one person who reads these, most of the second-guessing goes away. **Communication** covers the mechanics, and they are specific: lead with the main message, keep the subject line concise, be brief, send it only to the people who need it, and proofread before it goes. It also covers choosing the medium in the first place. A serious blocker is often better said in person or on a call, with the email following as the record — which is a decision worth making deliberately rather than defaulting to whichever feels less uncomfortable. **Influence** is what a steady, honest update quietly builds. Reporting consistently, being straight-talking about problems rather than political, and thinking past your own task to what a delay costs the wider plan is how someone early in their career earns a reputation worth having. When the update carries an ask, the preparation that works is understanding what actually matters to the person you are asking, and then following up on what was agreed rather than letting it lapse. None of the three is fixed equipment you were either issued or not. They are habits, and they sit inside the **twelve work skills** the free Job Skills Test measures. If your updates keep landing flat, it is more useful to take [a short skills self-assessment](https://assessment.headwayskills.com/) and find out which of the three is the weak link than to rewrite the same email a fourth time. ## What this looks like for you Some of this may already be how you work. Maybe you send a short note the day a date starts to look shaky, before anyone thinks to ask you about it. The parts that do not come naturally yet are learnable, and building them does not require becoming a different person at work — the habits change, you do not. They also count for more as you go: the more people depend on the work you are holding, the more of your standing rests on whether they hear about the problems from you first. The fact that you went looking for how to do this properly, instead of sending whatever came to mind, is already the habit the whole thing depends on. ## Find out which of these you already do well You have the shape of the email now. What is left is an honest read on the judgment underneath it. The **free** Job Skills Test is a short self-assessment that shows you where you stand across all twelve work skills — including the manager, communication and influence habits that an update email leans on — and points you to the one that would make the most difference for you right now. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, results shown instantly.* ## 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? An update email to your boss has a standard shape. What to include, how long it should be, how often to send one, and how to report a delay without excuses. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, 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/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.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/working-with-your-manager/how-to-write-an-update-email-to-your-boss/ Preferred summary: "An update email to your boss has a standard shape. What to include, how long it should be, how often to send one, and how to report a delay without excuses." ## Change log - 2026-07-07: Content collection version published.