Weekly Update to Your Manager: Template and What to Include

What Your Manager Actually Reads

Your manager gives this email about thirty seconds, often in the preview pane between two meetings. In that pass they are scanning for four things: what got done, what you’re doing next, what’s blocked, and any judgment calls you made on their behalf. The first three are the familiar status trio. The fourth is what makes the update worth reading: the scope you cut, the deadline you renegotiated, the fix you chose without a meeting. Your manager would much rather hear those from you on Friday than from someone else next month.

This guide is for an individual contributor writing to one manager. If you’re reporting program status to a steering committee, that’s a different document with different rules.

The Template

Copy this into a draft and fill it in. The first four sections are the ones your manager scans for; FYI is an optional fifth for anything they might get asked about by their own boss, and it drops out on weeks with nothing to report. Cut any other section that’s empty except Blocked, which stays in even when the answer is nothing, because a missing Blocked section is the first thing a nervous reader notices.

Subject: Weekly update - [your name], [date] Done - [Finished item, stated as an outcome, with a number or link if it has one] - [Second item] Next - [What you expect to be true by next week's update] - [Second item] Blocked - [What's stuck, who or what it's waiting on, and what you need to unstick it] - [Or: Nothing blocked this week.] Calls I made - [A decision you made without checking in, plus the one-line reason] FYI - [Anything your manager might get asked about by their own boss]

The section most templates skip is Calls I made. Including it does two things: it keeps your manager from being surprised later, and it builds quiet, weekly evidence that you can be trusted with bigger decisions.

A Filled Example

Subject: Weekly update - Priya, Mar 14 Done - Shipped the CSV export fix. Support tickets on it went from four a week to zero. - Finished the draft migration plan for the billing tables, now with Sam for review. Next - Start the billing migration behind a feature flag. Staging done by Thursday. - Write the on-call runbook before Dana's leave starts on the 24th. Blocked - Read access to the analytics warehouse (IT-4102, filed Monday). If it isn't granted by Wednesday, the usage dashboard slips a week. Calls I made - Deferred the icon refresh to next sprint so the export fix could ship this week. Easy to reverse if you disagree.

Two things to notice. Every Done item states an outcome, not an activity: tickets dropped, a document reached its reviewer. And the blocked item names the ticket number, what it’s waiting on, and the date the delay starts costing something, which turns a complaint into something a manager can forward with one line added.

Length and Cadence

Keep it under 200 words. The whole update should be readable in the preview pane without scrolling, because that is how it will usually be read. If yours keeps running long, you’re listing activity instead of outcomes.

Send it the same day at roughly the same time every week. Friday afternoon is the common choice, while the week is still fresh; Monday morning works if you’d rather frame the week ahead. The specific day matters less than never varying it. After a month of updates that arrive on schedule, your manager stops asking what you’re doing, and that is the real product. A quiet week still gets an update; it’s three lines and costs you two minutes.

Where Updates Go Wrong

The Activity Laundry List

Ten bullets of meetings attended, documents reviewed, and threads replied to. Activity isn’t progress, and your manager can’t do anything with it. Before sending, apply one test to each line: does this change what my manager knows or decides? If not, cut it.

The Buried Blocker

Two cheerful paragraphs, then “also, still waiting on warehouse access” in the third. The blocked item is the one part of your update a manager can act on, and burying it under good news guarantees they won’t see it. Blockers get their own heading, near the top, with the specific thing you need spelled out.

Vague “Made Progress On”

“Made progress on the migration” could mean nearly finished or barely started, and every manager knows it. Say what changed: staging done, two tables left, on track for the 22nd. If you can’t state the progress concretely, that’s information too; it usually means the task is too big to see the edges of and needs breaking down.

Keeping Source Material Without Extra Work

The hard part of a Friday update isn’t the writing, it’s the remembering. Reconstructing your week from the calendar, the sent folder, and closed tickets is archaeology, and it reliably misses the most valuable material: judgment calls leave no artifact. Nothing in your ticket tracker records that you decided to cut scope on Tuesday.

The fix is notes as you go. At the end of each day, write two or three plain sentences about what happened and what you decided. That’s it. When Friday comes, the update becomes an editing job instead of a memory test: read five short notes, pick what your manager needs, compress.

This is the loop Journaled is built around: you describe your day in free text, it turns that into structured entries plus a short written summary you can edit before saving, and the entries are searchable when you sit down to write the update. A plain text file works too. The habit matters more than the tool.

The same notes keep paying after Friday. Review season runs on exactly this material: at the end of each quarter, spend twenty minutes rolling that quarter’s updates into a short record of what shipped and what you decided. Keep those quarterly records and a self-assessment becomes something you assemble from them rather than reconstruct from a cold calendar.

Common Questions

What Day Should I Send It?

Any day you can hold every week. The edge cases matter more than the choice: if your send day falls on a holiday or you’re out, send a shorter update a day early rather than skipping, so the rhythm holds. On a distributed team, time it to land in your manager’s morning, not your own evening; a blocked item they read at 8 a.m. gets acted on the same day.

How Long Should a Weekly Update Be?

Under 200 words, fully readable in the preview pane. If you regularly need more space, put the detail in a linked doc and keep the email as the summary a busy person actually reads.

Should I Send an Update If Nothing Happened?

Yes. Three lines: what you worked on, what’s next, nothing blocked. Skipping quiet weeks makes your silence ambiguous, and ambiguous silence is what gets you chased for status, which is the thing the update exists to prevent.

Do I Report Team Work or Just Mine?

Yours. This is a personal update, not a project report. Name a teammate when the credit is part of your own item, but don’t carry status for work you don’t own; that belongs in the project’s own reporting.

What If My Manager Never Replies?

Silence usually means it’s working; a clear update needs no reply. You still get the benefits: fewer status pings, a record of your judgment calls, and raw material for review season. If you want a check, ask once a quarter whether the format is still useful to them.