WEEKLY STATUS REPORT
A weekly status report answers one main question: where does the work stand now? It should make current health, recent movement, risks, and decisions easy to find without forcing the reader through every task from the week.
A status report is a snapshot. It tells a manager, sponsor, client, or project team what is on track, what is moving, what is stuck, and what needs a decision now.
That is slightly different from a broad weekly report. A general weekly report may cover several kinds of work. A status report is usually narrower and more operational: it is centered on the present state of a project, workstream, or team.
“Had three meetings” is activity. “Launch remains at risk because the final design is one day late” is status. The second sentence tells the reader what the work actually looks like now.
COPYABLE TEMPLATE
Use the sections that match the work. If there is no decision needed this week, remove that heading instead of leaving an empty box.
On track / At risk / Off track — one sentence explaining why.
Decision, approval, or help required.
COMPLETED EXAMPLE
The example below uses a simple status label, but the explanation matters more than the color. “At risk” is useful only when the reader can see what is causing the risk and what happens next.
Overall status: At risk. Core page work is largely complete, but mobile navigation still has two blockers and the analytics migration has not been verified. The launch date remains possible, but it should not be treated as confirmed until those items are closed.
STATUS VS. PROGRESS
The two formats overlap, but they put the emphasis in different places.
Best when the reader asks: “Where do we stand?” Emphasis: - current health - risks / blockers - decisions needed - whether plan or timing is at risk
Best when the reader asks: “What moved this week?” Emphasis: - work completed - movement against plan - milestones - work still in progress
If you mainly need to show movement against a plan, use the weekly progress report guide. If the current health of the project is the important part, stay with a status report.
HOW TO WRITE IT
Write “on track,” “at risk,” or another plain-language status only when you can explain what supports it.
A task that moved forward is not automatically complete. Keep “completed” and “in progress” distinct.
Do not bury a schedule slip, unresolved dependency, or unverified metric under a long list of accomplishments.
If a manager needs to decide, approve, or unblock something, say exactly what and by when.
Paste the week you already have and organize it before you review the final status update.