A project status update tells stakeholders where a project stands against its plan: what is done, what is next, what is at risk and what decision is needed. Short updates get read, and a clear headline rating lets busy readers act quickly.
Status reporting is a routine duty in the chief of staff role, and it falls to anyone who owns a deliverable for a sponsor, a client or a leadership team.
What a project status update is for
A status update has one job: to let a reader who is not in the day-to-day work make a sound judgment about the project in a minute or two. It is not a diary of activity, a defense of the team or a replacement for working sessions. Readers typically want to know whether the work is on course, whether anything needs their attention and whether they have a decision to make.
Government guidance on assurance reviews frames the underlying question as confidence in delivery. The UK Infrastructure and Projects Authority defines it as the confidence in a project’s ability to deliver its aims and objectives within timescales, within the cost envelope and to the quality requirements, as laid out in the most recent formally approved mandating document, according to its delivery confidence guide for review teams. A good update answers that same question in the author’s own project, using the approved plan as the baseline.
Because the baseline matters, an update should name what it is being compared with. Progress against an approved plan is a fact; progress against a private hope is not. If the plan has changed through an agreed change request, the update says so and measures against the revised baseline.
The core sections to include
Templates published by public bodies are consistent about the building blocks. The District of Columbia’s Department of General Services publishes a weekly project status report template whose sections include a project status summary, work completed last week, work planned for next week, open issues, open risks, deliverables and milestones, and open change requests. The same ideas appear in most well-run reporting, whatever the tool or format.
- Headline status. A single rating or sentence at the top: on track, at risk or off track.
- Progress since the last update. The milestones reached and deliverables finished in the period.
- Next period. The work and milestones expected before the next update.
- Risks and issues. A risk may still happen; an issue is already happening. Each one carries an owner and a planned response.
- Decisions and requests. Anything the reader must approve, unblock or fund, with a date.
- Schedule and cost position. How the forecast compares with the approved plan.
The template also tracks each milestone with a planned date, a forecast date and an actual date, plus a one- or two-word status. That three-date habit makes slippage visible without any commentary: when the forecast column drifts away from the planned column, readers see it at a glance.
Choosing a status rating readers can trust
A color rating is the fastest way to open an update, but it only works if the colors mean the same thing every time. The UK guide defines the three main colors by how likely successful delivery is and how much management attention is needed, and it allows amber-red and amber-green for in-between positions.
| Rating | What it signals |
|---|---|
| Green | Successful delivery appears highly likely, with no major outstanding issues threatening it. |
| Amber | Delivery appears feasible, but significant issues already exist that need management attention and appear resolvable. |
| Red | Successful delivery is in doubt, with major risks or issues in key areas and urgent action needed. |
These definitions paraphrase the UK delivery confidence guide, which states that definitions are given only for red, amber and green and that amber-red and amber-green can reflect a status in between.
Some organizations replace judgment with thresholds. The District of Columbia template notes that a variance of +/- 5% will typically warrant a yellow cautionary color and +/- 10% a red warning color, while projects needing tighter control use narrower limits and looser projects use wider ones, as its status report template explains. The exact numbers matter less than agreeing them in advance and applying them consistently.
Whatever scheme is used, any constraint that is yellow or red should come with a brief explanation of the reason. A bare amber invites questions; an amber with a one-line cause and a recovery step answers them before they are asked.
Keeping the update short
Length is a choice made by the writer. The template guidance says the summary is meant for high-level management, so it should not get too much into the details of the project while still highlighting anything that should be brought to their attention. That is a useful test for every line: would the reader act differently if this line were missing?
A few habits keep an update compact without making it thin.
- Lead with the conclusion. Put the rating and the one-sentence reason before any detail.
- Report changes, not everything. Skip tasks that are progressing as planned and note only milestones, slippage and new risks.
- Limit bullets. A handful of completed items and a handful of planned items is usually enough; link to the tracker for the rest.
- Use the same layout every time. Readers learn where to look, so they scan instead of reading line by line.
- Write numbers once. Give the forecast date or the variance, not a paragraph about how it was calculated.
- Cut adjectives. Replace words like “good progress” with the milestone that was reached.
Detail that does not fit belongs in an attachment or a linked page, not in the body. The update is the front door to the project record, not the record itself.
Writing risks, issues and asks
The sections that readers value most are usually the ones that ask something of them. The District of Columbia template asks for a list of open issues with their status and how they will be resolved, and a list of open risks, meaning risks that have occurred or are on the verge of occurring, with how they will be resolved. Each entry works best as a short chain: the problem, the effect on the plan, the action being taken and the owner.
Requests deserve their own line. State the decision needed, who must make it and the date by which it matters, then say what happens if it is late. Burying a request in the middle of a progress paragraph is the most common reason it goes unanswered.
Honesty is part of the format. An update that shows green until the week a deadline is missed teaches readers to distrust the rating. Reporting an amber early, with a plan to return to green, protects credibility and gives sponsors time to help. Managers who hand work to others often build this habit by pairing it with clear checkpoints, a theme covered in delegation for managers.
Choosing the format and rhythm
The right frequency follows the pace of the work and the needs of the audience. Fast-moving projects may justify a weekly note; steady, long-running programs can report monthly with a short summary in between. Fix the schedule, publish it and keep to it, because predictability is what lets readers rely on the update instead of asking for ad hoc briefings.
Format follows audience. Executives usually want the headline, the rating and the asks on a single screen. Working teams want the milestone table and the risk list. One update can serve both when the top section stands alone and the detail sits beneath it.
A written update also changes what live time is for. When the status is already on the page, a meeting can focus on decisions and blockers instead of reading out progress. The same logic applies to one on one meetings, which are more useful for coaching and problem-solving when the routine status has been shared in writing beforehand.
Frequently asked questions
How long should a project status update be?
Show answer
As short as the reader’s decisions allow. A headline, a few lines on progress and plans, the top risks and any request usually fit on a single screen, with links to the tracker for everything else.
How often should status updates go out?
Show answer
Match the cadence to the pace of the work and agree it with stakeholders in advance. Weekly suits fast-moving work and monthly suits slower programs; consistency matters more than the exact interval.
What is the difference between a risk and an issue?
Show answer
A risk is something that may happen and could affect the plan. An issue is a problem that is already happening. Each should have an owner and a response, and a risk that materializes moves to the issues list.
Should a status update ever be red?
Show answer
Yes, when delivery is in doubt and urgent action is needed. Reporting red with a clear cause and a recovery request is more useful to a sponsor than a green that later collapses.
Who should receive a project status update?
Show answer
The sponsor and the decision-makers who can unblock the work, plus any stakeholders who depend on the outcome. Keep the list deliberate so that each recipient has a reason to read it.
