The weekly report is a genre almost everyone writes badly, mostly because nobody has ever said what it is for. Written as a list of everything you did, it is a defence against an accusation nobody made, and it gets skimmed. Written as a briefing for someone with limited attention and specific responsibilities, it takes fifteen minutes, gets read, and does real work — for your manager and for you.
What your manager actually needs
Not proof that you were busy. Three things:
- Anything they need to act on. A decision only they can make, an escalation, a resource they need to unblock. This is the most valuable content and it should be first.
- Anything they will be asked about. Managers get questioned by their own manager, by other teams, by clients. A report that lets them answer without coming back to you is worth a great deal.
- Whether the things they are accountable for are on track, and if not, what is being done.
Everything else is context. The most common failure is producing an accurate, complete inventory of your week that contains none of these three.
A structure that works
Four sections, in this order:
Needs you. What you need from your manager, specifically, with a deadline. If nothing, write "Nothing this week" — its absence is information, and its presence at the top means it never gets missed. This section is empty most weeks and is the reason the report gets read on the weeks it is not.
Status of the main things. Two to four items maximum, each with a state and one line of substance:
Migration — on track. Two of five services moved, remaining three scheduled for next week. Vendor review — at risk. Waiting on legal's contract comments since Tuesday; will slip a week if not received by Thursday.
Use a consistent vocabulary — on track / at risk / blocked / done — so a reader can scan the states and stop.
Notable. Two or three things worth knowing that do not fit above: a decision made, a problem discovered, something learned, a customer reaction. This is the section that makes the report interesting rather than mechanical, and the part managers most often say they value.
Next week. Three or four lines. It sets expectations and gives your manager the chance to redirect you before you spend the week, which is worth more than any retrospective account of the last one.
Half a page. Anything longer gets skimmed, which defeats the purpose.
Writing the status lines
Lead with the state, not the narrative. "At risk" first, explanation second. A manager scanning eight reports needs the state in the first two words.
Be specific about numbers and dates. "Nearly done" means different things to the writer and the reader. "Two of five complete, remainder by Friday" does not.
Report bad news early and plainly. The instinct is to soften or defer until you have a solution. Resist it: the cost of a problem is proportional to how late it surfaces, and a manager who learns about a slip from someone else stops trusting the report entirely. Say what is wrong, what you are doing, and what you need. See communicating delays and bad news to customers for the external version of the same skill.
Do not report tasks as achievements. "Attended three meetings" is not a result. What came out of them is.
Distinguish blocked from at risk. Blocked means work has stopped and someone must act. At risk means it will slip if something does not change. Conflating them either wastes your manager's urgency or fails to summon it.
What to leave out
- Routine work that always happens. Nobody needs a weekly report that you did your job.
- The full task list. If your manager wants task-level detail, it belongs in the tracker they can look at, not in the report. Task management best practices.
- Justification. A report that reads as self-defence signals a problem in the relationship that the report cannot fix.
- Hedging. "Hopefully we should be able to more or less finish" communicates nothing. Give a date and a confidence level.
- Other people's failures, characterised. "Waiting on legal since Tuesday" is a fact. "Legal is being obstructive" is a judgement, and it will be forwarded.
Make it cheap to write
If the report takes an hour, it will be late, resented, and eventually abandoned.
- Keep a work journal and write the report from it. Fifteen minutes with notes beats an hour of recall, and it is more accurate. See keeping a work journal.
- Use a template — the four headings above, pasted in each week.
- Write it at the same time every week, Friday afternoon or Monday morning. Consistency matters more than which.
- Reuse the previous week's status lines and edit them. Most of them have not changed, and diffing against last week is itself informative.
- Do not gold-plate it. A plain text update sent on time beats a formatted document sent late.
Format and channel
Match the medium to how your manager works. A message in the team channel, an email, or a shared document all work; a slide deck almost never does.
- In the body, not attached. An attachment adds a click and halves the read rate. This applies to almost all internal status communication — see email vs document: choosing the right medium.
- Same channel, same time, every week. Predictability is what makes it get read.
- A running document — one page, newest entry at the top — has an advantage over separate messages: it accumulates into a record that both of you can search when the question is "when did that slip start?".
What you get out of it
The report is usually framed as something you do for your manager. The returns to you are larger than that suggests:
- A record of your own work, which is the raw material for reviews, promotion cases and handovers. Twelve weekly reports is a year of evidence you did not have to reconstruct.
- A weekly forcing function to notice what is at risk, which is a planning benefit independent of anyone reading it.
- Visibility, which is not politics but the ordinary condition of being managed by someone who cannot see most of what you do.
- A written trail on anything you flagged. "Raised as at risk on 14 July" is a useful sentence when a project runs late.
If your manager does not ask for one
Send it anyway, briefly. Most managers are pleased to receive a short, well-structured update they did not have to request, and the alternative — them asking, periodically and unpredictably, for status — is worse for both of you.
If they genuinely do not want it, keep writing it for yourself. The record is worth having regardless of who reads it.
Summary
Open with what you need from them, then two to four status lines with a consistent state vocabulary, then a couple of things worth knowing, then next week — half a page, same time, same channel. Report bad news early and plainly, be specific about dates and numbers, and leave out the routine work and the justification. Write it from a journal rather than from memory, and keep the archive: it is the most complete record of your own work you will ever have.
