How to write a weekly status your manager can use
A weekly status is a decision aid, not a diary. Three lines your manager can forward beat a page they will not read. Write what changed, what is stuck, and what you need.
Write for the person who has twelve of these
Your manager is not reading to enjoy your week. They are scanning for risk and for a decision only they can make. If the note takes more than a minute to read, the risk is buried.
Skip the mood. “Busy but good” does not tell them whether the vendor file shipped. Start with the outcome. The effort belongs in your own notes, not in the status.
Send it at the same time each week, in the same place. A moving target gets skipped. Friday afternoon or Monday morning is fine if the team already has a habit. Do not invent a new channel for one note.
Three lines, in this order
Done: one or two results, with a scale if you have it. “Closed 18 refund tickets; the queue over two days is now zero.” Not “worked on refunds.”
Stuck: one fact and the date it started. “Waiting on legal since Tuesday for the clause in section 4.” Name the blocker, not a person as the villain. If nothing is stuck, write “nothing blocked.” An empty stuck line looks like you forgot.
Need: a question with a deadline. “Need a yes or no on the Thursday mail by Wednesday noon, or I will send the shorter version.” If you need nothing, write “no ask.” Managers trust a note that can be empty in that slot.
- Done: what changed
- Stuck: since when, on what
- Need: the decision and the time
Numbers only when you can point at them
A count, a date, or a percent from a report you can open is enough. Do not round a feeling into “about 30% better.” If the report says 6% then 2%, write those. If there is no baseline, say so.
Separate this week from the project. A status that only repeats the annual goal teaches nothing. “Goal is still May; this week the draft went to review” ties them in one line.
Do not paste a dashboard screenshot full of other people’s names or pay. A ticket id and the outcome are usually enough. If the company limits what you can copy out, keep the note inside that system.
What to leave out
Leave out the play-by-play of meetings you attended. Attendance is not a result. If a meeting changed a date or an owner, write the change, not the hour you sat there.
Leave out blame. “Alex is slow” will be forwarded, and it will come back. “The review copy has been with design since Monday; I pinged once” is the same fact without a character judgment.
Leave out a hidden ask for a raise or a promotion. The status is the wrong envelope. A pattern of results across months can support that talk later. One Friday note cannot.
If nobody replies
No reply is often a good sign: nothing required a decision. Do not send a second note that only says “following up” unless the Need line had a deadline that passed.
If the same Stuck item survives three weeks, stop repeating it in the same words. Write what you will do on Monday if it is still stuck: ship a smaller version, or move the date you promised a customer. Ask them to correct that plan.
If your manager says the note is too short, add one line of context, not a journal. Ask which decision they could not make from the last one. Write to that gap next week.
A note you can reuse
Keep the weekly lines in the same file as your performance notes. At review time you will not be reconstructing March from memory. The status is the raw log. The review page is the sorted version.
When you are out, the last status is also a handoff. Write the Need line so a coworker can act without asking you. “If the vendor replies, Sam sends the file; the folder is linked” is a status and a cover plan.
This format will not make a chaotic project calm. It only makes the chaos visible early enough that someone can choose. It is not a performance rating, and it is not a record you should fill with other people’s private details.