What a status report is actually for
A project status report is a short update that tells people outside the project team how it is going. That is all. It is not a diary, and it is not a place to prove everyone has been busy.
Key takeaways
- A project status report answers three questions: where are we against the plan, what is at risk, and what do you need from the reader.
- Keep it to one page. Lead with an overall status, then progress, risks, and decisions needed. Everything else is detail nobody asked for.
- The report goes stale because someone retypes it. If your tasks, milestones, and owners live in one place, most of the report can come from there.
The readers matter. A sponsor wants to know if the date and budget still hold. A department head wants to know if their people are being pulled in at the wrong time. A client wants to know if they need to do something. Write for the person with the least time and the most authority, and the rest follows.
It also does one quiet job that is easy to miss. It forces the project lead to look at the whole project once a week, and to say out loud whether it is on track. Teams that skip this tend to find out they are late when someone else tells them.
What to include in a project status report
You do not need twelve sections. You need these.
- Overall status. One word and a colour: green, amber, or red. Green means on track. Amber means something could slip and you are handling it. Red means the date, budget, or scope will not hold without a decision.
- Progress since last report. What was finished, in plain terms. "Checkout design approved" is useful. "Worked on design" is not.
- Milestones. The next two or three, with dates, and whether each one is on time.
- Risks and blockers. What could go wrong, how likely it is, and who owns the fix. Be specific. "Supplier may be late" is vague. "Supplier confirmed delivery for 24 October, we need it by 17 October" is a risk someone can act on.
- Decisions needed. The things only the reader can do. Approve a change, release budget, pick between two options. If this section is empty, say so.
- Next period. What the team plans to finish before the next report.
What to leave out
Skip the task list. Skip the hours. Skip anything that would not change what the reader does. If you are unsure, ask whether someone would act differently after reading the line. If not, cut it.
Why status reports go wrong
Three habits ruin most reports.
Everything is green until it is red
Nobody wants to be the first to say amber. So a project sits at green for eight weeks and then jumps to red, and the sponsor feels ambushed. Amber is not an admission of failure. It is the warning that makes red avoidable. Agree with your readers up front that amber is normal and welcome.
It is written from memory
If the report is written on Friday afternoon by someone trying to recall the week, it will miss things and flatter the team. The facts already exist in the project: which tasks closed, which milestone moved, which item has been stuck for nine days. The report should read from them, not from a person's recollection.
It is a different document every time
When the layout changes each week, readers have to hunt for the news. Fix the format. Same order, same headings, same colour code. After three weeks people will read it in two minutes because they know where to look.
A simple format you can reuse
Here is a layout that fits on one page. Copy it into whatever you use.
| Section | What goes in it | Length |
|---|---|---|
| Status | Green, amber, or red, plus one sentence on why | 1 line |
| Done this period | Finished deliverables and milestones | 3 to 5 bullets |
| Coming up | What the team will finish before the next report | 3 to 5 bullets |
| Milestones | Next milestones with date and on-time or late | A small table |
| Risks | Risk, impact, owner, action | 2 to 4 rows |
| Decisions needed | What you need, from whom, by when | 0 to 3 bullets |
The first line is the one most people will read, so make it count. "Amber: design sign-off is two weeks late, which pushes launch from 14 November to 28 November unless the client approves by Friday." That sentence tells the reader the status, the cause, the effect, and the ask.
If you are still building the plan the report will track, our guide on how to write a project plan covers milestones and ownership, and the RACI matrix helps you decide who owns each risk.
Build it from live data
The best way to stop writing status reports by hand is to stop collecting the facts by hand. A report needs completed work, milestone dates, owners, and workload. If those sit in a spreadsheet, a chat thread, and someone's head, you will always be copying.
If they sit in one project tool, the report mostly writes itself. Closed tasks since last week are your progress section. Milestones with their dates are your milestone table. Overdue items are your first draft of the risks. You still add the judgement, because the colour and the decisions are human calls. But the typing goes away.
A few things make this work in practice:
- Milestones with real dates. Not "Phase 2" but "Phase 2 complete, 21 November". A Gantt timeline makes slippage obvious.
- Tasks with one owner each. A task with three owners has none.
- A workload view. Many red projects are really overloaded people. See resource management software for how to spot it early.
- Status that updates itself. If a task moves when work moves, you do not need a Friday cleanup.
WeldFlow is the project management app in WeldSuite. Tasks, subtasks, milestones, and owners live together, and each project can be viewed as a Gantt timeline, a board, a sheet, a calendar, or a doc. It has a workload view to spot overload, recurring tasks, and rules and triggers that update status automatically. Comments sync to WeldChat, so the discussion reaches the people who need it, and WeldAgent can run tasks. That means the data behind your status report is already there when you sit down to write it.
WeldFlow is one of twelve apps included in every WeldSuite tier, and WeldSuite is a complete software suite for mid-market and enterprise teams, priced per user per month. There is a free plan for a single user. Business runs $49 a month, or $42 per user per month billed annually, for up to ten seats. Scale runs $69 a month, or $59 per user per month annually, for eleven seats and up. Enterprise is custom, with SSO, SAML, and a 99.999% uptime SLA.
Sources
- Wikipedia: Project management https://en.wikipedia.org/wiki/Project_management
- Wikipedia: Traffic-light rating system https://en.wikipedia.org/wiki/Traffic-light_rating_system
Frequently asked questions
What is a project status report?
It is a short update for people outside the project team. It says whether the project is on track, what was finished, what is at risk, and what decisions are needed. Most are one page and sent weekly or every two weeks.
How often should I send a project status report?
Weekly suits most active projects. Every two weeks works for slower ones. Pick a rhythm and keep it, because a regular report is read, while an irregular one gets ignored.
What does RAG status mean?
RAG stands for red, amber, green. Green means the project is on track. Amber means something may slip and is being handled. Red means the date, budget, or scope will not hold without a decision from someone.
What is the difference between a status report and a progress report?
People use the terms interchangeably. If there is a difference, a progress report looks back at what was done, while a status report also states the current health of the project, the risks, and what is needed next.
Can a status report be generated automatically?
Most of the facts can. Completed tasks, milestone dates, owners, and overdue items all come from the project data. The overall colour, the risk commentary, and the decisions needed still need a person.
See it all work together
WeldSuite brings CRM, helpdesk, accounting, mail, projects and more into one connected platform. Change something once and it shows up everywhere.
Keep reading
Project Plan Template (Free Download + Guide)
A free project plan template plus a plain, step-by-step guide that keeps scope, schedule, and budget under control.
Project managementWhat Is a Gantt Chart, and When Should You Use One?
A Gantt chart is a horizontal bar chart that maps your project schedule over time. Here's how to read one, the parts it's made of, and when it beats a plain to-do list.
Project managementResource Management Software: How to Stop Guessing Who Has Capacity
Every growing team eventually loses track of who is buried in work and who has room for more. Here is why spreadsheets and gut feel stop working, and what resource management software actually needs to do.