Status Report

A status report is a recurring engagement artifact that communicates the current health of a project to stakeholders, covering progress against milestones, budget and schedule position, open risks and issues, and decisions needed. In professional services, it is typically delivered weekly on active engagements and is the primary touchpoint between the delivery team and the client sponsor between formal steering committee meetings.

What a status report must cover

A status report that omits any of these five elements is incomplete:

1. Overall RAG status: one color (Red, Amber, Green) for the engagement overall, with separate ratings for schedule, budget, and scope
2. Milestone progress: what was planned to complete in the current period, what actually completed, and what is now at risk
3. Budget position: spend to date versus plan, projected final cost, and any approved or pending change orders
4. Open risks and issues: the top three to five items from the RAID log that require client awareness or a decision
5. Decisions needed: explicit asks of the client, each with a deadline, so the report drives action rather than awareness

Format discipline

Status reports fail when they are too long. A single page or screen is the right size. Narrative paragraphs about what the team did last week add little; the milestone table covers that. Reserve prose for interpretation: why a workstream is amber, what the delivery team is doing about it, and what is needed from the client.

Status reporting as a risk management tool

A status report that consistently shows Green and then delivers a surprise Red indicates a failure of honest communication. Amber is not a bad status; it is the signal that allows early intervention. Delivery teams that hold at Green until a problem is undeniable are the ones who face escalations at the end of the engagement rather than resolving issues during it.

Issue log and risk register entries should feed directly into the status report. When those records are maintained between reports, the status report becomes a summary of already-documented information rather than a document written from memory the night before a client call.