# Sample Email to Your Boss About Work Progress: What to Send and When Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-boss-about-work-progress/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-boss-about-work-progress.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 A sample email to your boss about work progress, plus the five kinds of update and how to word a delay so it reads as information, not an excuse. ## Key facts - Title: Sample Email to Your Boss About Work Progress: What to Send and When - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Influence - Primary keyword: sample email to boss about work progress - Source page: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-boss-about-work-progress/ ## What this page covers - A sample email to your boss about work progress, plus the five kinds of update and how to word a delay so it reads as information, not an excuse. - Practical guidance for sample email to boss about work progress - How this topic connects to Working with Your Manager ## Detailed explanation The message is due, the cursor is sitting in an empty body, and you would rather adapt something than invent it. A sample email to your boss about work progress has six parts: a subject line naming the work and the period, one sentence saying whether things are on track, a short list of what you finished, what is still moving, anything blocking you, and whatever you need from your manager. There is a complete one below. What the template collections rarely mention is that there is more than one kind of progress email. Most of the trouble people run into comes from sending the wrong kind, not from wording any of them badly. ## What goes into a work progress email Managers do not read these the way you write them. You write forward from the start of the week; they scan for exceptions — what changed, what slipped, what needs a decision. That is the reason the standard shape is so consistent across sources that otherwise have nothing in common with each other. The first sentence carries the most weight. Fyxer's guidance on status emails puts it plainly: open by saying whether the work is on track, at risk, delayed, or complete, before any detail arrives. One of four states, chosen and stated up front. This is the part people most often bury, because leading with the word "delayed" feels like leading with failure. It is the opposite. A manager who learns about a slipped date in the first line still has time to do something about it. The second thing worth getting right is what goes in the bullets. Sources across this space, including InstantDocsAI and Clockify, push for outcomes rather than activities — what was finished and what it produced, not what you spent your hours on. That distinction quietly solves the problem most people are actually worried about here. "Spent three days on the migration script" reads as either busywork or self-justification, depending on the reader's mood. "Migration script finished and running against the test data" is just a fact, and facts do not sound like bragging. Then keep it short enough to read on a phone. The description that recurs across these sources is short, structured, factual, easy to scan, and the reasoning behind it is unsentimental: long updates, sent often, get skipped. Close with the specific thing you need, if anything. The standing advice is to say what you already tried before asking for help, which is the difference between handing your manager a problem and handing them a decision. Assembled, it looks like this: > **Subject:** Onboarding revamp — week of September 14, on track > > Hi Sarah, > > The onboarding revamp is on track for the September 30 handover. > > Finished this week: > > - New starter checklist signed off by HR > - First three welcome emails written and loaded into the system > > In progress: > > - Manager guide — draft ready Thursday > - Test run with the two September starters — results by September 25 > > Nothing is blocked, and I do not need anything from you this week. Next week I will finish the guide and start the test run. > > Best, > Tom Six lines of substance. That is the norm rather than a shortcut. If your own search turned up something far more elaborate — status colors, risk registers, a linked dashboard — look at who wrote it. Two very different populations publish on this topic: career and email sites writing for individual employees, and project-management vendors such as Asana, monday.com, Smartsheet, and Workamajig writing for project managers reporting to stakeholders. The second group's machinery is real and built for a different job. Borrowing it for your own weekly update mostly signals that you have over-engineered a message that should take four minutes to write. ## The five kinds of work progress email The other thing template collections flatten is that "progress email" covers several distinct messages. They differ in what sets them off, what they are for, and whether your manager is expected to do anything. Deciding which one you are writing settles most of the questions about length and tone before you start. ### The routine cadence update The recurring summary, sent on a schedule whether or not anything notable happened. Weekly or biweekly is the near-universal recommendation across Clockify, Maestro Labs, and Techno PM — though it is worth knowing that none of them cites a study for it. This is convention, not evidence, so a team norm beats any number you read online. Its value comes from being predictable rather than from any single message. A manager who knows an update lands every Friday stops asking and stops wondering. It is informational and one-way, and it needs no reply. The sample above is this type. ### The milestone or completion update Triggered by an event rather than the calendar, and narrow. One thing has finished — a phase, a deliverable, an approval — and the email says so, names what it unblocks, and hands over whatever needs handing over. The mistake is turning it into a full sweep of everything you are working on. If you have just finished the thing, the update is about the thing. This is also the one place where a link to the finished work or a screenshot earns its keep, since your manager may want to look before responding. ### The delay or blocker notification This is the only type that asks your manager to act, and both InstantDocsAI and Asana are explicit that it should be its own email rather than a line inside a routine update. The reasoning is mechanical: buried in the middle of a Friday summary, a slipped date gets scanned past, and the person who could have moved something around finds out a week late. Send it when the date is genuinely at risk, not once it has already gone. Four things belong in it — the revised expectation, the cause stated plainly, what you have already tried, and the specific decision or help you need. > **Subject:** Manager guide slipping to October 3 — one decision needed > > Hi Sarah, > > The manager guide will not be ready by September 30. Realistically, October 3. > > The test run surfaced two sections that do not survive contact with an actual new manager, and rewriting them properly takes two more days. I cut the appendix to buy back time; it was not enough. > > Two options: hold the handover to October 3, or hand over on the 30th with those two sections marked as drafts. I would go with October 3. Can you tell me which by Thursday? > > Best, > Tom This is the email people go looking for templates to avoid writing. The wording is not really the hard part. The judgment about when to speak up is, and that is a habit rather than a phrasing problem — a common one, and a fixable one. If you tend to sit on these longer than you should, it is worth seeing [where your own gaps are](https://assessment.headwayskills.com/) before the next one arrives. ### The requested catch-up update Your manager asks where things stand, usually with no format specified and often at short notice. The scope is set by their question rather than by you, so the discipline is answering exactly what was asked before adding anything else. If they asked about one project, lead with that project in the first line. Anything else you want them to know goes underneath, clearly marked as extra. A specific question met with a general survey of your week reads as evasion even when it is not. ### The period summary or review input The longer retrospective covering a month, a quarter, or the run-up to a review conversation. It aggregates outcomes rather than tracking live work, and it is the only type where setting out your accomplishments at length is appropriate rather than boastful. That is what the format is for. If you have been sending routine updates all along, this one largely writes itself out of them, which is a reasonable secondary argument for keeping the cadence even in quiet weeks. ## The skills that make these easier to write Read back through the five types and notice what actually decided each one. Almost none of it was wording. It was whether you told your manager early enough, whether you put the important thing first, and whether the record building up week after week matches what you have really done. **Working with Your Manager** is where this sits. The progress email is the ordinary instrument for making your results visible, which matters because your manager sees only the parts of your work that cross their desk. Treating the relationship as a partnership changes what you choose to include: you report so they can act, not so they can be reassured. It also covers the harder half — being honest when the news is bad, and bringing the decision alongside the problem rather than dropping the problem and waiting. **Communication** supplies the mechanics. Lead with the main message, be brief, use a subject line that says what the email is about, and send it only to the people who need it. It also covers the judgment underneath all of this: some things belong in writing and some belong in a conversation. A status summary is genuinely one-way information. A blocker that needs your manager's judgment often deserves five minutes of their time instead, with the email as the record afterward. **Influence** is the slow accumulation. Reporting your work accurately and consistently, including the parts that went badly, is how a junior employee becomes known for being reliable — not through arguing for it, but through a record that holds up. Following through on what you said you would do next week, and saying so when you have, is unglamorous and does more for your standing than any single well-written message. The free Job Skills Test asks about ordinary situations like these and shows you [which ones need attention](https://assessment.headwayskills.com/), across all twelve of the work skills this framework treats as learnable rather than fixed. Useful mostly because the weak one is rarely the one you would have guessed. ## Some of this is probably already how you work If you have ever rewritten a bullet to say what you finished instead of what you were busy with, or felt the pull to mention a slipping date before anyone asked, you have already been doing part of this without a name for it. The rest is learnable, and learning it does not require becoming a different person at work. These are behaviors, and a gap is just something nobody taught you yet. It is worth closing while the stakes are low, because the same habits get used later on higher-consequence messages — the ones that go to your manager's manager, or that decide whether a project gets more time. You have already done the part most people skip, which is stopping to ask what this email is supposed to do before writing it. The useful next step is knowing which of these three is currently your weakest. ## Find out which part is worth working on That is something you can settle on your own, before you write the next update. The Job Skills Test is a **free** self-assessment of your work skills. You answer questions about how you handle everyday situations at work, and it shows you where you stand across all twelve skills and which one or two would make the most difference to you right now. It takes about seven minutes, and nothing about it needs to be shared with anyone. You will still write the email either way. Knowing which habit underneath it needs attention is what makes the next one, and the fifty after that, less work than this one. **[Take the skills test](https://assessment.headwayskills.com/)** Free, about 7 minutes, and your results appear the moment you finish. ## 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? A sample email to your boss about work progress, plus the five kinds of update and how to word a delay so it reads as information, not an excuse. ### 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/sample-email-to-boss-about-work-progress/ Preferred summary: "A sample email to your boss about work progress, plus the five kinds of update and how to word a delay so it reads as information, not an excuse." ## Change log - 2026-07-07: Content collection version published.