Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

All tools › Project status report

Saved in this browser only

The tool · project delivery

Project status report

Project
Reporting period
Project manager
Report date
1

Health at a glance

rate each area on its own
AreaStatusWhy, in one line
2

Done since last report

accomplishments, not activity
What shipped or finishedOwner
3

Coming up next

what the reader should expect
WhatOwnerBy whenConfidence
4

Risks and issues worth the reader’s time

top three, not all of them
Risk or issueOwnerWhat happens next
5

Decisions needed from you

the reason executives read these
Decision, with the recommendationFrom whomBy when

What makes a status report worth reading

Rate schedule, budget, scope, and risk separately. A project can be green on time and red on budget; one overall light hides that.

Amber means something. If everything is always amber, nothing is; amber is "will go red unless the named thing happens."

Lead with decisions needed. Executives skim; the ask should not be on line forty.

One page. The second page is where status reports go to be unread.

Send it on a cadence, even when nothing changed. A skipped report reads as a hidden problem, and the week you most want to skip is the week the reader most wants it.

Print or save as PDF and it is the report you send. Everything saves in this browser only.

Prefer paper? Download the blank sheet as a PDF. The thinking behind it, and the nine tools it works with, is in The Project.

General guidance from practice, not legal, HR, or financial advice. Everything you type stays in this browser and is never sent to a server.