What goes in a project status report?

A useful status report has an overall health signal, a one-line summary of where things stand, what was accomplished this period, what is planned next, the risks and blockers in play, and any decisions you need from the reader. The decisions section is the one most reports forget, and it is the reason executives open the email.

How long should a status report be?

Short enough to read on a phone. One screen is the target. A health color, a single summary line, and a handful of bullets under each section is plenty for a weekly update. If the reader has to scroll twice, the signal is buried. Detail lives in the linked plan, not in the status email.

What do Green, Yellow, and Red mean in a RAG status report?

RAG stands for Red, Amber, Green, the health colors. Green means on track to hit scope, schedule, and budget with no help needed. Yellow means at risk, with a specific concern and a plan to recover. Red means a commitment will be missed without intervention, and it names what you need. Honest yellow early beats surprise red late.

How often should you send a status report?

Match the cadence to the audience. Weekly works for a working team and most program stakeholders. Executives often want biweekly or monthly with only the exceptions. The rule that matters more than frequency is consistency: same day, same format, every time, so readers know when to expect it and where to look.

Project Status Report Generator

Fill in the left, get a clean status report on the right. Set the health color, write a one-line summary, and list accomplishments, next steps, risks, and decisions needed. Copy, export, or print. Everything saves in your browser. No signup.

Program name

Reporting period

Overall health

Summary (one line)

Accomplishments

Next steps

Risks & blockers

Decisions needed

How to write a status report executives actually read

The job of a status report is to move information to the people who can act on it, in the time they will actually spend reading. That means a health signal they can see at a glance, a single summary line that tells them whether to relax or lean in, and short lists under the rest. The decisions section is the part most reports drop, and it is the only part an executive is scanning for.

Honesty about color is what makes the report trusted. A status that is green every week until the week it is red trains people to ignore it. Yellow is not failure, it is an early flag with a recovery plan, and it is the most useful color you have. Keep the format identical every period so readers learn where to look and stop reading the words they already know.

Common mistakes to avoid

No decisions section. If you never ask for anything, the reader has no reason to engage. Name the calls you need made and by when.
Burying the risk. The point of yellow is to surface a concern while it is still cheap. Hiding it to keep the report green is how programs go from green to red overnight.
Writing a novel. Detail belongs in the plan. The report is the signal layer.
Changing the format every week. Consistency is what lets a busy reader find the one thing they care about in five seconds.

For the full version of this thinking, read the status report executives actually read in the Insights.

Built by Arsenii Samoilov, a Senior Technical Program Manager with 19+ years at Intuit, Atlassian, Adobe, Salesforce, Roku, and Apple. If your team needs help standing up program governance, get in touch.

Read the Insights →