Most status reports are written to prove that the writer was busy. Long lists of tasks, meetings attended, emails sent. The person reading it, usually a boss, a client or a board, skims it, cannot tell whether the project is in trouble, and replies "So are we on track?"
A good status report answers that question in the first line. Then it tells the reader what is coming and what you need from them. That is the whole job.
Know Who Is Reading
Before you write, picture the reader. An owner or executive wants to know if they need to worry. A client wants to know if they will get what they paid for, on time. A team member wants to know what they are doing next week. If your report goes to all three, write the top for the busiest reader and let the details sit lower down.
Start With the Status
Many teams use a simple color code at the top:
- Green — on track. No help needed.
- Yellow — there is a risk or a slip, and you are handling it, but the reader should know.
- Red — something will be missed (a date, the budget, a goal) unless something changes. You usually need a decision or help.
Be honest with the color. A project that has been "green" for two months and suddenly goes "red" tells the reader that the report was not telling the truth. A yellow that shows up early, with a plan attached, builds trust.
Right after the color, write one or two sentences of summary. "On track for the March launch. Vendor contract signed this week; testing starts Monday." If the reader stops there, they still know what they need to know.
The Sections That Matter
- Done since last report. Finished work only, and only the pieces that matter. "Training materials drafted and sent for review" is useful. "Worked on training materials" is not.
- Next up. What will happen before the next report, with who is doing it.
- Risks and issues. An issue is a problem happening now. A risk is a problem that might happen. List each with what you are doing about it.
- Decisions or help needed. The most important section and the one most often missing. If you need the reader to approve, choose, or unblock something, say so plainly, with a date.
- Key dates. The next few milestones and whether each is still on schedule.
A Status Report Template
[Project Name] — Status Report
Report date: [date] Period covered: [start date] to [end date]
Prepared by: [name]
Overall status: [Green / Yellow / Red]
Summary: [One or two sentences. Are we on track, and what is the most important thing that happened?]
Done since last report:
[Completed item]
[Completed item]
Next up:
[Planned item] — Owner: [name] — Due: [date]
[Planned item] — Owner: [name] — Due: [date]
Risks and issues:
[Risk or issue] — Impact: [what it affects] — Action: [what is being done] — Owner: [name]
Decisions or help needed:
[What you need] — From: [name] — By: [date]
Key dates:
[Milestone] — [date] — [On track / At risk / Missed]
Use the same headings every time. Readers learn where to look, and you spend less time deciding how to lay it out.
How to Report Bad News
Every project hits a problem eventually. The status report is where people find out, and how you write it decides whether they trust you afterward.
- Report it as soon as you know. Bad news does not get better with age. A problem raised early has options. The same problem raised the day before the deadline has none.
- Put it near the top. If the project is red, the color and the problem belong in the first two lines, not under "Other notes."
- Say what it affects. "The vendor shipment is two weeks late, which pushes testing back two weeks and puts the launch date at risk."
- Bring a plan. Say what you are already doing and offer options if there are any.
- Ask for what you need. If you need a decision, name it and give a date.
Skip the blame. The reader needs to know what happened and what comes next, not whose fault it was.
Mistakes That Make Reports Useless
- Too long. If it runs past one page, cut the "done" list down to what matters and move detail to an attachment.
- Activity instead of progress. Meetings held and hours spent are not results. Report what changed.
- Vague dates. "Soon" and "in progress" tell the reader nothing. Give a date, even if it is an estimate, and say it is an estimate.
- No ask. If you needed something and did not say so clearly, you will not get it.
- Inconsistent schedule. A report that shows up whenever you remember trains people to stop reading it.
Email or Document?
For a small team, a short email with the same headings is usually enough. Put the status and the project name in the subject line, for example "[Project] status, [date]: Yellow," so it can be found later. Our business email guide has more on subject lines that get opened.
For a client project or anything with a board or funder watching, keep each report as a one-page document in a shared folder. Over time that folder becomes the history of the project, which is very useful when someone asks, months later, when a decision was made. If something needs a real conversation, use the report to set up the meeting, and our meeting agenda guide will help you run it.
Questions people ask
What should a project status report include?
The overall status, a short summary, what was finished since the last report, what is planned next, any risks or problems, decisions you need from the reader, and the key upcoming dates. If it does not fit on one page, it is too long.
How often should you send a project status report?
Often enough that nothing important surprises anyone. Weekly works for most active projects. A long, slow project may need only every other week or monthly. Pick a schedule, tell people what it is, and stick to it.
What does red, yellow and green mean in a status report?
Green means on track. Yellow means there is a risk or delay that you are managing but the reader should know about. Red means the project will miss a date, budget or goal unless something changes, and you usually need help or a decision.
How do you report bad news in a status report?
Early and plainly. Say what happened, what it affects, what you are already doing about it, and what you need from the reader. Do not bury it at the bottom or soften it until it means nothing.
Should a status report be an email or a document?
Either works. For a small team, a short email using the same headings every time is often enough. For a larger project or a client, a one-page document kept in a shared folder gives you a running history.
This article is general guidance on business documents, not legal, tax or accounting advice. A template is a starting point, not a document drafted for your situation. Before you sign, send or rely on anything with legal or financial consequences, have it reviewed by an attorney or accountant licensed in your state.