How to Write an Email to Your Manager Regarding Updates

To write an email to your manager regarding updates, name the project and the status in the subject line, open with one sentence saying whether things are on track, then set out what is done, what is in progress, what is blocked, and what you need from them. Close with dated next steps.

The wording is rarely the real problem. What stalls an update is the worry sitting underneath it — that reporting a delay will read as an excuse, or that sending anything at all is bothering someone who is already busy. Both worries push in the same direction: vaguer emails, sent less often. That happens to be the exact opposite of what the person reading them needs, and the reason becomes clear as soon as you look at the update from their side of the inbox.

What to include when you write an email to your manager regarding updates

Your manager is probably reading this in the two-minute gap between meetings, having spent the morning switching between other people’s problems. LinkedIn’s guide to status updates makes that its starting point: remind them where you left off, because they are not carrying your project in their head the way you are.

Two failure modes follow from that, and the guides name both. One is vagueness — an update so general that it conveys nothing your manager did not already assume. The other is density: long emails packed with background that bury the point, so decisions slow down and follow-up questions go up. Everything below aims at the narrow band between the two.

1. Put the project and the status in the subject line

The most-cited mistake is a subject line that reads “Update.” It cannot be prioritized in a crowded inbox and it cannot be found again three weeks later. Name the project, then say what this message is: a weekly status, a possible delay, an approval you need. Where the email requires something from your manager, the guides recommend signaling it in the line itself — “approval required,” “possible delay” — so it gets sorted correctly before it is even opened.

2. Open with a one-line verdict

Before any detail, give the answer: on track for the March 14 milestone, or two days behind and here is why. Fyxer’s project-status template leads with exactly this kind of line, and the point of it is generous rather than dramatic. If everything is fine, your manager can stop reading after the first sentence and get on with their day. Add one clause of context after it, enough to reorient someone who last thought about this a week ago.

3. Reuse the same headings every time

Pick a small set of headings — completed, in progress, next steps, blockers, support needed — and keep them identical from one week to the next. Sources recommend this for the reader’s sake, since a familiar shape can be skimmed in seconds. The bigger benefit is yours. A fixed template turns into a checklist, and the section you would otherwise be tempted to leave out on a bad week is sitting there, empty, asking to be filled in.

4. Report outcomes, not activity

Under completed work, the recurring advice is to be specific and outcome-focused. There is a real difference between “worked on the account migration” and “migrated the final twelve accounts; the old system is now read-only.” The first describes how you spent your time; the second describes what changed. Only the second is something your manager can act on, plan around, or pass upward without calling you first for the details.

5. Put blockers near the top, with the impact and a suggested fix

Hiding blockers is the mistake sources warn about most, and burying them works the same way as hiding them: an issue sitting in paragraph four gets skimmed past or underestimated. Raise it early instead, and give it three parts — what is stuck, what it costs if it stays stuck, and what you suggest doing about it. That structure changes what the message is. It stops being a confession of a problem you failed to solve and becomes a decision put in front of the person whose job includes making it, while there is still time to make it.

6. Say exactly what you need, or say that you need nothing

Ambiguity about whether a reply is owed carries its own small cost. If you need a decision, ask for it plainly, and ask early rather than in the final line. If you need nothing, say so — one of the more useful points in the search results is to make sure your manager knows when an update is purely an FYI. Otherwise every message you send carries an unspoken question mark, and busy people postpone anything they are not sure how to answer.

7. End with dated next steps

Leaving out next steps is another named mistake, and the consequence is predictable: ambiguity generates follow-up questions, which cost more time than the sentence you skipped. Say what happens next, when it lands, and who owns it — including anything you are waiting on from someone else. The date is what makes the difference. “Continuing with testing” is not a next step; “testing complete Thursday, results to you Friday morning” is.

8. Send on a predictable schedule

Send at roughly the same time each week so people know when to expect it. Cadence advice varies by audience, with weekly updates suggested for your team and manager and monthly reporting for a client. Consistency does something a single well-written email cannot. An update that lands every Friday stops being an interruption and turns into something your manager plans around — and it quietly retires the question nobody enjoys being asked, which is what exactly you have been working on.

Why a routine update is more than a report

Eight rules for one email is more scaffolding than the task appears to deserve, until you notice what the emails add up to. Your manager builds their picture of your work mostly from what reaches them, and for anything they do not directly observe, these messages are the picture. Sent well and sent regularly, they make your results visible, keep expectations aligned, and surface problems early enough for someone to help. If the difficult part for you is not the format but knowing what is worth raising and when, that is a working habit rather than a writing one — and it is worth knowing where that habit stands before you rewrite another draft.

The habits underneath a good update

Read back through those eight and notice how few of them are about writing. Naming what your manager needs to know, judging when a risk is worth flagging, deciding to send anything at all in a week when the news is bad — those are ways of working, and every one of them can be practiced.

Working with Your Manager is the relationship the update serves, and this framework treats it as a partnership with a shared purpose rather than a reporting line. Two of its plainest habits are doing the communicating instead of avoiding it, and making your results visible instead of assuming they get noticed. A third explains rule five: bring solutions, not just problems. Being honest about a slipping deadline while there is still room to act on it is the kind of honesty the partnership runs on, even when it feels risky to send.

Communication supplies the mechanics, and the framework’s version of them lines up closely with what the career sites recommend: state the main point first, be brief, keep the subject line short and specific, include only the recipients who need to be there. Its more useful contribution is the judgment about medium — writing is the right tool for one-way information and for anything you want on the record, which is precisely what a status update is.

Influence is the part nobody types into a search bar. Volunteering a clear update on a rhythm nobody imposed is one of the ways a reputation for reliability gets built, and that reliability is what makes your later asks land. It also covers the follow-through: checking that what you flagged actually got picked up, rather than treating the sent folder as the end of your responsibility.

Which of the three is your weak spot is hard to see from the inside — most people assume it is the writing when it is the judgment. The free Work Skills Test is a quick way to settle that, reading all twelve of the work habits this framework covers, these three included, so you can see the one to work on first. None of them is fixed; you only need to know where to put the effort.

Where this leaves you

Some of this may already match how you work — the instinct to flag a slipping date before it slips, or to lead with the answer because you know your manager reads on the move. Those are worth building on, and the parts you do not do yet are habits you can add one at a time, without becoming a different kind of employee in order to do it. It matters more as you go, too: the more responsibility you carry, the more of your work travels to other people in writing and has to make sense without you in the room to explain it. You went looking for how to word this properly rather than sending something vague and hoping — that instinct is most of what the eight rules above are made of.

Find out which of these comes hardest

You know what belongs in the email now; what decides how well it lands over the next year is which of these comes easily to you and which you have been quietly working around. The free Work Skills Test is a short self-assessment of your own work skills that shows where you stand across all twelve, including the manager and communication habits that every update email depends on, and points you to the one worth starting with.

Take the skills test

Free to take, and about seven minutes from start to finish.