By Ryan Kramer, founder of Wisegrid. Last updated November 2026.
A project status report template is a reusable page that shows, in the same order every week, where a project stands: overall health, schedule, budget, risks, decisions needed and next steps. Filling the same template each time lets a principal or client read ten projects in ten minutes and spot the one that needs help.
Most status reports fail for one of two reasons. They are written from memory, so the numbers do not match the budget sheet, or they list activity instead of answering “are we on track?”. This guide shows the seven sections to include, a worked example from a small engineering firm with fee and forecast math that adds up, a weekly version for the team, and how to stop retyping the same numbers every Friday.
Key takeaways
– Lead with one health call per project. Green, amber or red, with the reason in one sentence.
– Compare percent spent with percent complete. A project 65% spent and 50% complete is heading over budget, whatever the activity list says.
– Forecast the finish, not just the spend to date. Spent ÷ percent complete gives a simple estimate at completion.
– Ask for decisions by name and date. A blocker without an owner is just a complaint.
– Pull numbers from the live sheet. A report typed by hand drifts from the budget within weeks.
What is a project status report?
A project status report is a short, regular update that tells stakeholders whether a project is on schedule, on budget and on scope, and what needs their attention. Atlassian describes it as “a concise, timely update on your project’s progress”. It is different from a progress report, which lists completed tasks, and from a risk register, which tracks every risk in detail.
In engineering and architecture (A&E) firms, the status report usually goes two ways. Project managers send a weekly report up to principals, and principals send a monthly summary to clients. Both should come from the same numbers: the fee, hours and invoices you already track in your budget vs actual sheet.
What should be included in a project status report?
A good report answers seven questions in a fixed order. The table shows each section, the question it answers and a short example. Keep the whole report to one page per project.
| Section | Answers | Example |
|---|---|---|
| Overall health | Are we on track? | Amber: forecast 13% over fee |
| Summary | What changed this week? | Hydraulic model finished |
| Schedule | Will we hit the next milestone? | 60% design due Dec 12 |
| Budget | Spent vs complete, forecast | 70% spent, 62% complete |
| Risks and issues | What could go wrong? | Survey data late |
| Decisions needed | Who must act, by when? | Client: pick pump option by Nov 20 |
| Next steps | What happens next week? | Start electrical layout |
Atlassian suggests keeping the executive summary to no more than six sentences. In practice, one sentence per section is enough for most weekly reports. Put detail in the attached sheet, not in the report.
Worked example: a multi-project status report
Here is the status view for a small civil and architecture firm with four active projects. Spent is labor and expenses charged to date. Complete is the project manager’s estimate of work done. The bold row is the project that needs a principal this week.
| Project | Fee | Spent | Complete | Health |
|---|---|---|---|---|
| Riverside pump station | $180,000 | $99,000 | 60% | Green |
| Elm St. bridge rehab | $240,000 | $156,000 | 50% | Red |
| Library renovation | $95,000 | $38,000 | 45% | Green |
| Wastewater plant study | $60,000 | $42,000 | 62% | Amber |
| Total | $575,000 | $335,000 |
The health column comes from a forecast, not a feeling. The estimate at completion is spent to date divided by percent complete. If Elm St. has used $156,000 to get halfway, it will cost about $312,000 to finish at the same rate. That is $72,000 over a $240,000 fee.
| Project | Fee | Forecast | Variance | Health |
|---|---|---|---|---|
| Riverside pump station | $180,000 | $165,000 | +$15,000 | Green |
| Elm St. bridge rehab | $240,000 | $312,000 | −$72,000 | Red |
| Library renovation | $95,000 | $84,444 | +$10,556 | Green |
| Wastewater plant study | $60,000 | $67,742 | −$7,742 | Amber |
| Total | $575,000 | $629,186 | −$54,186 |
What this tells you: the firm looks fine in total spend, with $335,000 used of $575,000. The forecast says otherwise: the portfolio is heading $54,186 over fee, and one project accounts for all of it and more. The rule used here is simple. Green means the forecast is within fee. Amber means up to 15% over. Red means more than 15% over. Pick your own thresholds, write them on the report and keep them fixed.
The forecast is only as good as the percent complete. Ask project managers to estimate it from deliverables, such as sheets drawn or calculations checked, not from hours used. Our guide to the utilization rate for engineering firms explains why hours alone mislead, and the free cost variance calculator checks the math.
How do you write a project status report?
- Update the numbers first. Post hours and invoices to the project sheet before writing a word. The project budget template holds fee, spent and percent complete in one place.
- Set the health call. Apply your green, amber and red rule to the forecast. Do not soften a red to amber because the client reads the report.
- Write one summary sentence. What changed since last week, in plain words.
- Check the next milestone. Compare the date with the plan in your Gantt chart. If it moved, say why and by how much.
- List risks and issues. Pull the open items from your RAID log, meaning the list of risks, assumptions, issues and dependencies. Show only the top three.
- Name the decisions you need. Who, what and by when.
- Send it on the same day every week. A predictable report gets read. A surprise report gets skipped.
Weekly project status report template
Inside the team, a lighter weekly report works better than the full one-pager. It uses four columns and four categories. These match the weekly sheet in Wisegrid’s free executive project status report template.
| Category | Item | Owner | Date |
|---|---|---|---|
| Done | Hydraulic model finished | Priya | Nov 4 |
| In progress | Electrical one-line diagram | Marcus | Nov 14 |
| Planned | 60% design review | Priya | Dec 12 |
| Blocked | Survey data from county | Dana | Nov 10 |
The weekly sheet feeds the executive report. When every project manager fills the same four categories, a principal can sort by “Blocked” across all projects and see where to step in. The free status report generator turns these rows into a formatted summary.
Common status report mistakes
- Green until it is red. Without a forecast, a project shows green for months, then jumps to red. Amber exists so problems show early.
- Activity instead of status. “Held three meetings” does not say whether the project is on track.
- Numbers typed by hand. When the report and the budget sheet disagree, nobody trusts either.
- Too long. If it takes more than two minutes to read, the decisions at the bottom get missed.
- No owner on blockers. Every blocked item needs a name and a date.
- Changing the format. Readers learn where to look. Keep the order fixed.
From a spreadsheet report to a live Wisegrid sheet
Most firms build status reports in Excel or PowerPoint, and that works for one or two projects. It breaks when ten project managers each send a file and someone copies the numbers into a summary. Files get out of date, and edits made at the same time can overwrite each other, the problem described in why collaborative spreadsheet edits disappear.
Wisegrid, a spreadsheet-native work management app, keeps the same grid but makes it shared and live. Each project keeps its own sheet with a dropdown health column. A portfolio sheet reads fee, spent and percent complete from every project sheet with cross-sheet references, so the status report updates when the numbers do. A date-triggered automation can remind each project manager on Thursday to update percent complete. Clients and principals can view for free. It is a grid, not a full accounting system, so invoices still come from your accounting software. You can start from the project tracker Excel template and import it as it is.
FAQ
How often should you send a project status report?
Weekly is the usual rhythm for the project team and principals, and Atlassian suggests weekly as a starting point. Clients often prefer monthly, matched to the invoice. Fast-moving projects may need a short daily update. Whatever you choose, send it on the same day each time so readers know when to expect it.
What does a project status report look like?
It is usually one page. At the top is a health call, green, amber or red, with one sentence of summary. Below that come schedule, budget, risks, decisions needed and next steps, often as a short table. A multi-project version shows one row per project with fee, spent, percent complete and health.
What is the difference between a status report and a progress report?
A progress report lists what has been completed. A status report judges where the project stands overall, including budget, schedule and risks, and asks for decisions. A project can show plenty of progress and still be in trouble, which only the status report reveals.
How do you calculate percent over budget in a status report?
First forecast the final cost: spent to date divided by percent complete. Then compare it with the fee or budget. In the example, $42,000 spent at 62% complete forecasts $67,742, which is $7,742 or about 13% over a $60,000 fee.
Can I make a project status report in Excel?
Yes. A table with fee, spent, percent complete and a formula for the forecast covers most needs. The limits appear when several people update it at once or when you combine many project files into one summary. That is the point where a shared, live sheet saves time.
Sources
Run every project’s status from one live sheet
Track fee, spent and percent complete per project and roll them into one portfolio view in Wisegrid. Start with the executive project status report template, plan people with the resource planning template, and set fees with the project budget template.
Start free → · Status report generator → · Budget vs actual guide →
About the author Ryan Kramer is the founder of Wisegrid, a higher-capacity work management grid built around a 1,000,000-cell-per-sheet limit, date-triggered automations with run history, and cross-sheet reporting. He writes about the project management documents teams actually keep updated. More from Ryan →