Most status reports take thirty minutes to write and thirty seconds to read. The writer pastes in everything they did this week, the reader skims for the word 'blocked', and nobody can say afterwards whether the project is actually on track.
A good status report fixes that. It tells the reader how things are going, what changed, what's stuck and what you need from them, in that order. This guide covers what a status report is, the different types, what to include and how to write one. You'll also find a copy-ready project status report template, filled-in status report examples, and templates for daily, monthly, client and executive updates.
What is a status report?
A status report is a regular update that tells stakeholders how a project, team or goal is tracking. It covers overall health, progress since the last update, key metrics, risks and blockers, and next steps, so the reader can see at a glance whether anything needs their attention.
Whether you're leading a small project or running a company-wide initiative, status reports connect what's happening day to day with where you're trying to go. At their best, they:
- Keep everyone aligned on progress without another meeting
- Surface blockers before they become problems
- Create a written record of decisions and changes
.png)
As your organisation grows, keeping everyone informed gets harder. It can feel like overkill to standardise updates, but that's exactly what makes them happen. Without a shared format, status reporting quietly drops off the moment things get busy, which is precisely when you need it most.
Types of status reports
Status reports vary by how often you send them and who reads them. Here's a quick breakdown of the most common types of status reports:
| Type | Cadence | Main reader | What it covers |
|---|---|---|---|
| Daily status report | Daily | Your team | What was done, what's next, any blockers |
| Weekly status report | Weekly | Manager or stakeholders | Wins, progress against goals, risks, next week's priorities |
| Project status report | Weekly or fortnightly | Project sponsor and stakeholders | Overall health, milestones, timeline, budget, scope, risks, decisions |
| Monthly status report | Monthly | Department heads | Trends, performance against targets, lessons, focus for next month |
| Quarterly status report | Quarterly | Leadership team | OKRs and KPIs, strategic progress, plan for next quarter |
| Executive status report | Weekly or monthly | Leadership | Exceptions only: what's off track and what needs a decision |
| Client status report | Weekly or monthly | Clients | Deliverables, progress against scope, what's coming next |
| OKR status report | Weekly | Goal owners and leaders | Progress and confidence on each objective and key result |
A team status report usually sits between the daily and weekly versions: one short update per person or per team, shared internally. The quarterly version overlaps heavily with a QBR, which is why we built a separate quarterly business review template for it.
.png)
What to include in a status report
The right level of detail depends on cadence. Daily and weekly reports should be quick to write, or people stop writing them. Monthly and quarterly reports can go deeper, but should still favour clarity over volume. Whatever the cadence, the format of a status report usually comes down to seven parts:
- Header: project or team name, owner, and the period it covers.
- Overall status: one call, usually green, amber or red (sometimes called a RAG status), with a sentence on why.
- Progress: what was achieved since the last update. Outcomes, not a task list.
- Metrics: the numbers that show whether things are working, such as your KPI reporting or OKR progress.
- Risks and blockers: anything slowing you down, who owns it, and what would unblock it.
- Next steps: the priorities for the next period.
- Decisions and asks: what you need from the reader, and by when. Put this near the top if it's urgent.
For a project status report, add three more: the next milestone and whether its date has moved, budget spent against plan, and any change to scope. These are the details project sponsors look for first, and the reason a generic team update rarely works for a project.
Why context matters
A number on its own doesn't tell a story. 'Signups: 285' is a data point. 'Signups: 285, up from 240, driven by the new pricing page' is a status update. Adding context helps the reader understand why something happened, and forces the writer to think critically about progress instead of just reporting it.
The 'bad' update includes a metric but no insight. Look back at it in a month and you'll be asking 'OK, but why?'. The 'good' one adds interpretation, comparison and next steps, which is what makes it useful.
How to write a status report
Here's how to write a status report people actually read, in six steps:
- Start with the reader. Ask who reads it and what they do with it. An executive wants exceptions and decisions. A project team wants dates, owners and dependencies.
- Make the call first. Open with the overall status. Green, amber or red, no hedging. If the reader stops after one line, they should still know how things are going.
- Report outcomes, not activity. 'Shipped the onboarding checklist, activation up 4%' beats 'worked on onboarding'.
- Put the bad news high. Risks and blockers buried at the bottom get skimmed. Name the risk, the owner and what you need.
- Add the numbers and the why. One or two metrics with a line of context each. Skip the vanity numbers.
- End with next steps and asks. What happens next, and what decision or help you need from the reader, with a date.
Keep it to one page. If the same field is empty three weeks in a row, delete it. A good status report format should get shorter over time, not longer. The Project Management Institute makes a similar case in its anatomy of an effective status report: the best reports are built around what the reader needs to decide.
Project status report template
This project status report template covers the details stakeholders ask about most: health, milestones, timeline, budget, scope, risks and decisions. Hit copy and replace the brackets.
If you report weekly, our weekly status report template guide has four shorter formats for teams, projects, goals and executives.
Status report examples
Templates are easier to use once you've seen them filled in. Here are two status report examples, one for a project and one for a team.
Project status report example
Project: Single sign-on (SSO) launch for a B2B onboarding platform | Owner: Priya, Product lead | Period: 6 to 17 October
Overall status: Amber. Build is on track, but security review is a week behind and puts the launch date at risk.
Summary: Okta and Google SSO are code complete and in QA. Azure AD support slipped to the next release. Launch is still planned for 3 November if security review closes by 24 October.
Milestones: QA complete, done. Security review, at risk (was 17 October, now 24 October). Customer beta, 27 October.
Budget: $41,000 of $55,000 spent (75%). On budget.
Scope: Azure AD moved to the next release to protect the launch date.
Risks: Security reviewer on leave until 20 October. Owner: Priya. Mitigation: second reviewer booked for 21 October.
Decision needed: Approve moving Azure AD to the next release. From: Head of Product, by 20 October.
Team status report example
Team: Customer Success | Week ending 17 October
Overall status: Green.
Wins: Net revenue retention at 108% (target 105%). Onboarding time down from 21 to 16 days after the new kickoff call.
Blockers: Two enterprise renewals waiting on a pricing decision. Needs: answer from Finance by Wednesday.
Next week: Roll the new kickoff call out to all mid-market accounts. Run the first quarterly health check with the top 20 accounts.
Notice what both status report samples have in common. The call comes first, every number has a reason next to it, and the reader knows exactly what's needed from them.
More status report templates
Different cadences need different formats. Copy the one that matches how often you report.
Daily status report template
Daily updates work best when they're async. If your team still does this in a meeting, here's how to move to asynchronous daily standups.
Monthly or quarterly status report template
Client status report template
Best practices for writing better status reports
- Keep it short and skimmable. Headlines, not a play-by-play.
- Use the same format every time. Readers learn where to look, and writers stop starting from scratch.
- Include metrics or confidence ratings. 'On track' means nothing without a number or a confidence call behind it.
- Highlight risks early. Better to flag something that turns out fine than to surprise people later.
- Automate the reminders. A recurring prompt on the same day each week does more for consistency than any template.
How to get your team to write regular progress reports
What difference does a great status report make if nobody writes it? Getting a team to report consistently can feel like herding cats, especially when it feels like busywork. Set a fixed rhythm (every Friday morning, or the end of each sprint), keep the template small, and send automatic reminders so nobody has to chase. Some teams even turn it into 10 minutes of reflection people look forward to. That's what happened at Huzzle, who turned their nagging check-ins into a meaningful OKR reflection.
Status reporting tools
Most teams build status reports from three kinds of tools:
- Task management tools such as Asana, Trello, Jira and monday.com show what's done, in progress and late. Great for daily and weekly updates, less so for showing whether the work is moving a goal.
- Reporting and analytics tools such as Amplitude, Tableau, Stripe or a spreadsheet hold the numbers your metrics section needs.
- Docs and slides such as Notion, Google Docs and PowerPoint are where the report usually ends up.
The catch is that the report lives in one tool, the numbers in another and the context in someone's head, so every status report starts with copying and pasting. If you're comparing options, see how Tability stacks up as an Asana alternative for goal tracking and reporting, or browse our roundup of the best OKR software.
How Tability turns status reports into a view, not a chore
In Tability, the status report is already written by the time you need it. Each goal has an owner, a target and a running list of check-ins, and every check-in has the same parts as a good status update: a score for the metric, a confidence rating (green, yellow or red) and a short note on what drove the change. Automated reminders keep the updates coming without anyone chasing.
- Dashboards for every audience. Tability reporting gives you live dashboards, filtered by team, owner or confidence, plus a presentation mode with export to PowerPoint or Google Slides.
- Reports that write themselves. Ask Tability AI Mode for 'a status report for the marketing team this month' and it builds it from your latest goals and check-ins. Set it as a scheduled task and the report lands in your inbox each week or month.
- Bring your own AI. Connect ChatGPT, Claude or another assistant through the Tability MCP server and let it combine your goal data with other sources. We wrote about why agents write better status reports than humans, and how we fixed status reporting with Cowork and the Tability MCP.
The result: you stop writing status reports from a blank page and start reading them from data that's already there. If you want to see what that looks like, start free or check Tability pricing.
Status report FAQ
What is the difference between a status report and a progress report?
A progress report focuses on what's been completed. A status report is broader: it gives an overall health call, flags risks and blockers, and asks for decisions. In practice many teams use the terms interchangeably, but a status report should always tell the reader whether they need to act.
What should a project status report include?
Overall status (green, amber or red), a short summary, milestones and dates, progress since the last report, budget against plan, scope changes, top risks with owners, next steps and any decisions needed.
How often should you send a status report?
Weekly suits most teams and projects. Daily updates work for fast-moving work or standups, and monthly or quarterly reports suit leadership and strategic reviews. Pick a cadence and stick to it.
How long should a status report be?
One page or less. If it takes more than five minutes to read, cut it down to the exceptions and link to the detail.
Who should receive a status report?
Anyone who needs to make a decision or adjust their own work based on it: your manager, project sponsor, dependent teams or clients. Everyone else can read it in a shared space.
Good status reports are critical to team alignment
A well-written status report isn't a box to tick. It's the habit that keeps teams aligned, surfaces problems early and turns meetings into decisions. Lead with the call, back it with numbers and context, and always say what you need. Whether you're tracking weekly progress, updating leadership or keeping a client in the loop, the templates above give you a head start.
Want status reports that write themselves from live goal data? See how Tability reporting works, start free, or book 30 minutes with us.
.jpg)
