How to Write a Project Status Report (Template + Examples)

A project status report has one job: to tell people where the project stands, quickly enough that they can act on it. When reports are vague, long or late, people stop reading them, and problems that could have been fixed early turn into surprises. When they are short, specific and regular, they become the easiest way to keep a sponsor, a client or a team on the same page.

This guide explains what to put in a project status report, how to write one step by step, and how to keep the habit going without it eating your week. It includes a copy-ready template and example reports for construction and field teams, healthcare operations and small businesses.

What is a project status report?

A project status report is a short, regular update that compares where the project is with where the plan said it would be. It usually covers schedule, budget, scope, risks and the next steps, and it ends with anything the reader needs to decide or do.

It is different from a final report or a detailed progress log. A status report is a snapshot for a specific period (often a week, sometimes two weeks or a month) and it is written for people who are not in the daily details: sponsors, clients, department heads, owners or other teams who depend on your work.

What to include in a project status report

Most good status reports use the same core sections. You can shorten or rename them, but try not to skip any of them entirely.

• Project name, period and author: what the report covers, the reporting dates and who to contact with questions.
• Overall status: one clear signal, such as green (on track), amber (at risk) or red (off track). Some teams also give separate signals for schedule, budget and scope.
• Summary: two or three sentences that a busy reader could stop after and still know what matters.
• Completed this period: finished tasks, deliverables and decisions, not activity for its own sake.
• Planned for next period: what is coming up, with the key dates and any tasks that depend on something else finishing first.
• Key dates and checkpoints: planned date versus forecast date for the important points in the schedule.
• Budget: budget, spent to date and remaining, with a one-line explanation of any variance.
• Risks and issues: the few that matter right now, each with an owner and a next action.
• Decisions or help needed: what you need from the reader, by when.

How to write a project status report in 6 steps

1. Know who is reading and what they need

A sponsor wants to know whether the project is healthy and whether they need to step in. A client wants to know whether their date is safe. A delivery team wants to know what is blocked and who is unblocking it. Write for the main reader. If two audiences need very different detail, send a short version to leadership and a fuller one to the team, both built from the same facts.

2. Pull the facts from your plan, not from memory

Before you write a word, open the schedule, the budget and the risk list. Check which tasks were due this period and whether they finished, which ones are overdue, how much has been spent, and which risks changed. A status report written from memory tends to be optimistic. One written from the plan is easier to trust and easier to defend when someone asks a follow-up question.

3. Choose the overall status honestly

Agree in advance what each colour means so the signal is not a mood. For example: green means the current plan still meets the agreed dates and budget; amber means there is a real risk to a date or budget, but you have a recovery plan; red means a date or budget will be missed without a decision from someone above the project team. The most common failure is staying green until the week everything turns red. Amber early is far more useful than red late.

4. Write the summary last, but put it first

Once the detail is written, go back to the top and write two or three sentences: the status, the most important change since the last report, and anything you need. Be specific. "Electrical first fix is two days behind because a cable delivery slipped; the inspection date still holds" tells the reader much more than "Some minor delays on site."

5. Keep risks and issues short and owned

A risk is something that might happen; an issue is something that is already happening. List only the ones that need attention now, and give each one an owner and a next step with a date. If you keep a full risk register, the status report should point to the top few, not copy the whole list.

6. Ask clearly for what you need, and send it on schedule

End with decisions or support needed, the deadline for each, and who should provide it. Then send the report on the same day and at the same time each period. A predictable rhythm matters more than polish: people learn when to expect it and start to rely on it.

Project status report template

Copy this structure into an email, a document or a shared note and fill it in each period:

• Project / period: [Project name], [start date] to [end date]
• Prepared by: [Name, role]
• Overall status: Green / Amber / Red. Schedule: [ ] Budget: [ ] Scope: [ ]
• Summary: [Two or three sentences: status, biggest change, what you need]
• Completed: [Three to five finished items]
• Next period: [Three to five planned items, with dates]
• Key dates: [Checkpoint: planned date, forecast date]
• Budget: [Budget, spent to date, remaining, variance note]
• Top risks and issues: [Item, owner, next action, due date]
• Decisions or help needed: [What, from whom, by when]

Project status report examples

The examples below are made up for illustration. They show the level of detail that makes a report useful, not real projects.

Construction or field team: weekly site update

Status: Amber. Summary: Framing on the second floor finished on plan, but the window delivery has moved back by one week. The site lead has resequenced interior work so crews stay busy, and the roof-tight date still holds for now. We need the client to confirm the alternative window supplier by Thursday if the new date slips again.

• Completed: second-floor framing, plumbing rough-in on the first floor, weekly safety walk.
• Next week: roof sheathing, start electrical rough-in on the first floor, schedule the framing inspection.
• Top risk: further window delay pushes the weather-tight date. Owner: project manager. Next action: confirm backup supplier pricing by Wednesday.

Healthcare operations: process change rollout

Status: Green. Summary: The new patient check-in workflow is live in two of four clinics. Staff training for the remaining clinics is booked, and the feedback form from the first two sites has been reviewed by the operations lead. No decisions needed this week.

• Completed: go-live in clinics A and B, first round of staff feedback collected.
• Next period: training sessions for clinics C and D, update the front-desk guide based on feedback.
• Top issue: one shared printer at clinic B is slowing check-in. Owner: facilities coordinator. Next action: replacement ordered, due next Tuesday.

Small business: new service launch

Status: Red. Summary: The booking page is not ready, so the planned launch date will be missed by about one week. Content and pricing are done. We need the owner to choose between launching with a temporary contact form or waiting for the full booking page.

• Completed: service pricing, landing page copy, photos.
• Next period: finish booking integration and test payments, prepare the launch email.
• Decision needed: launch with a contact form or wait. From: owner. By: Friday.

Common status report mistakes

• Reporting activity instead of progress: "Held three meetings" says less than "Approved the final layout."
• Hiding bad news: a late amber is worse than an early one, and readers lose trust when red appears with no warning.
• Too much detail: if it takes more than a few minutes to read, the important part gets missed. Link to detail instead of pasting it.
• No owners or dates: a risk without an owner and a next step is just a worry on paper.
• Inconsistent timing: reports that arrive whenever someone has time are easy to ignore.
• Burying the ask: if you need a decision, say so in the summary, not in the last line.

Make status reporting faster

The quickest status reports come from a plan that is already up to date. If tasks are marked complete when they finish, overdue items are visible, and the budget and risks live next to the schedule, writing the report becomes a matter of reading the plan and adding judgement. A few habits help:

• Update task progress during the week, not just before the report is due.
• Review overdue tasks and the top risks in a short weekly meeting, then write the report straight after.
• Keep the same template every period so changes stand out.
• Save past reports in one place; they become a useful history of decisions.

Quick checklist before you send

• Does the summary make sense on its own?
• Is the overall status honest and based on agreed definitions?
• Are completed items real outcomes, with dates?
• Do the key dates show planned versus forecast?
• Does every risk and issue have an owner and a next step?
• Is the ask clear, with a deadline?

Using GanttMaster to keep your status report honest

The numbers at the top of a status report should come from the plan, not from memory. In GanttMaster on iPhone and iPad, the Projects screen gives each project a card with a progress bar and a short status summary: Total Tasks, Overdue Tasks and Project Members. That is a quick first read on whether the project is moving and how much is late.

For the schedule section, open the Gantt chart. Bars are colored by task status, so in the example below on-track tasks show green and overdue tasks show red, and Finish-to-Start, Start-to-Start and Finish-to-Finish dependencies show which upcoming work is waiting on something else.

Each project also has a Stats screen with Total Tasks, Completed Tasks, Overdue Tasks, Project Members, Project Teams and a Task Progress percentage bar. Those figures map directly onto the summary and progress lines of your report.

For the rest of the report, the project dashboard has a Project Risks card and a Budget card, so you can check open high risks and how much budget is used and remaining before you write those sections. Comments, file links and notifications keep the team's updates attached to the tasks they belong to, and the Today view with reminders helps you set a fixed time each week to write and send the report.