A weekly project-status report template that assembles itself
Most weekly status reports are written from memory on a Friday afternoon, which is why they read as reassurance rather than information. A useful report is assembled, not composed: every line is a number the work already produced, and the only judgement involved is what you are asking the reader to decide.
For the full set of numbers this template draws from, see the complete guide to Kanban metrics and reporting.
The seven-line template
Copy this into your update format of choice. Each line names where the number comes from, so nobody has to reconstruct it next week.
- Delivered this week. The count of cards completed in the range. One number, no narrative.
- Intake against output. Cards created versus cards completed for the same period. If intake keeps outrunning output, no amount of effort will close the gap and scope is the real conversation.
- Off track. Every card past its due date, with who is on it and how many days it has been. Add open cards flagged as delay risk - running longer than your team's median completion time, or with less time left than that median.
- Blocked. Cards with no activity for seven days or more. Name the handoff each one is waiting on, not the person holding the card.
- Slowest stage. The stage with the highest average days per card. This is the line that explains the other six.
- Load. Each person's share of active work against the team average, with anyone flagged overloaded called out by name.
- Decision needed. The one thing you want from the reader this week. If there is nothing, say so explicitly - that is information too.
Why the order matters
The template moves from outcome to cause to decision. Starting with what shipped keeps the report honest - it is hard to spin a completion count. Putting the slowest stage before the load line stops the conversation from turning into a performance discussion when the real constraint is a review queue. Ending with a single decision means the report has a purpose beyond being filed.
Making it repeatable
Scope a report to the boards in play, set the range to the last seven days, and read the seven lines off the screen. When the report needs to leave Otper - a client update, a partner summary, a record for the file - export it as CSV or PDF for exactly the boards and range you selected. Because you choose the scope before exporting, a client sees their engagement and nothing else.
The reports are derived from board activity rather than a separate reporting step, so the quality of the report is really the quality of the board. Cards with owners, due dates and honest list positions produce a report worth sending. Cards nobody has touched in a month produce a report that mostly measures neglect.
Download the template (Excel / PowerPoint)
Prefer to start from a file? The same seven lines are laid out as a one-page tracker with the columns Task, Owner, Status (R/A/G), Progress %, Done This Week, Next Week, Blockers. Fill it in by hand, or read the numbers off a Otper report and paste them in.
The .xlsx opens in Excel and imports into Google Sheets. R/A/G means red (off track), amber (at risk) and green (on track).
Weekly status report examples (filled-in samples)
Two illustrative samples. The numbers are made up; the structure is what to copy.
Example A: agency client delivery
| Task | Owner | Status | Progress | Done this week | Next week | Blockers |
|---|---|---|---|---|---|---|
| Homepage redesign | Priya | G | 80% | Final layouts approved | Hand off to build | None |
| Launch email sequence | Marcus | A | 45% | Drafts 1 and 2 written | Draft 3, client review | Waiting on client brand assets |
| Analytics setup | Dana | R | 20% | Access requested | Install tracking | No admin access, 9 days overdue |
Decision needed: the client must grant analytics access by Wednesday or the launch date moves.
Example B: small product team
| Task | Owner | Status | Progress | Done this week | Next week | Blockers |
|---|---|---|---|---|---|---|
| Onboarding flow v2 | Sam | G | 70% | 3 of 4 screens shipped to staging | Final screen, QA | None |
| CSV export fix | Lee | A | 60% | Root cause found | Patch and release | Stuck in review for 6 days |
| Pricing page test | Ana | G | 100% | Variant live | Read results | None |
Decision needed: pick a second reviewer for the CSV fix so it does not wait another week.
Agile / Scrum weekly report variant
If your team works in sprints, keep the same seven lines but change what you measure them against. Report against the sprint goal rather than a project end date: what shipped toward the goal, what carried over, and what you are cutting to protect it. Replace "Off track" with "At risk for the sprint goal", and keep "Blocked" exactly as it is - work with no activity for seven days or more is the earliest warning in any process.
Intake against output earns its place in a sprint report. If cards are being added faster than they are completed, say so and name what you will defer. Otper gives you completed and created cards for the range you choose, stuck cards and the slowest stage; it does not compute sprint velocity or burndown, so keep those in whatever you already use if you need them.
Status reporting across multiple projects
With several projects in flight, resist writing a separate narrative for each. Use the same seven lines for every project so readers can compare them, then add one summary line at the top: how many projects are green, amber and red, and which one needs the decision. Put the red projects first - that is where the reader's attention should go.
In Otper, scope a report to several boards at once to read delivered, off-track and blocked work across them, or to one board when a client should only see their own engagement. Our guide to managing multiple client projects covers setting up one board per engagement.
Skip the copy-paste - read your weekly status report off your board
Otper's automated project reporting builds delivered, off-track, blocked, slowest-stage and workload numbers from card activity, ready to export as CSV or PDF. Free for up to 3 teammates, no credit card.
Start free with OtperFAQ
What should a weekly project-status report contain?
What finished, whether intake is outpacing output, what is off track, what is blocked, where work is slowest, who is carrying too much, and the decision you need. Seven lines is usually enough.
How long should a status report take to write?
Minutes, if the numbers already exist. The only part that needs judgement is the decision you are asking for; the rest should be read off a report rather than recalled from memory.
Can I send the report to a client?
Yes. Scope the report to the boards that client can see, set the date range, and export it as CSV or PDF to attach or paste into your own update format.
What is the difference between a daily and weekly status report?
A daily report is a short check on what moved and what is blocked today, so problems are caught while they are small. A weekly report steps back: what finished, whether intake is outpacing output, what is off track, and the decision you need. Daily reports keep the work moving; weekly reports keep the reader informed.
Can a weekly status report be automated?
Partly. In Otper the numbers are generated from card activity, so you do not rebuild them by hand: pick the boards and date range and the report is ready to read or export as CSV or PDF. Otper does not email reports on a schedule, so someone still exports it and writes the one line that needs judgement - the decision you need.
Does Otper email the report automatically?
No. There is no scheduled report digest. You pick the date range and boards and export it yourself, which also means you control exactly what a client sees before it goes out.
Keep reading
- Knowing a project is slipping before the deadline
- Reducing status-meeting time
- Bottlenecks, overdue work and workload
Stop writing status reports from memory
Scope a range, read the seven lines, export as CSV or PDF when it needs to leave Otper.
Get started free