To report a red status without looking like you lost control, tell your sponsor yourself before the report goes out, and bring the cause, the actions you have already taken, the options, and the decision you need. Delivered that way, a red status shows you spotted a problem early and are asking for the help it needs.
When should I tell my sponsor the program is going red?
Tell your exec sponsor that the program is going red before the red status appears in any report, ideally after an earlier amber warning. Hearing it from you first gives the sponsor time to ask questions, and gives you the chance to present the cause, the actions already taken, and the decision you need.
Elizabeth Harrin puts it plainly: your sponsor won't like it if they find out about it through the weekly portfolio report and not from you. She also suggests showing the report to the sponsor and the finance lead before you submit it.
Work in this order:
- Confirm the facts behind the change: which milestone, budget line, or scope item is now outside tolerance, and the evidence that shows it.
- Book a short private conversation with your sponsor before the next report deadline. A call is better than an email for the first word.
- Send the written report only after that conversation, and say in it that the sponsor has already been briefed.
- Keep circulation to the people who normally receive the report. Harrin advises against copying a red report to a wide audience.
What do I say to my sponsor in the pre-brief?
The pre-brief with your sponsor should cover, in order, what changed, why, what you have already done, the options, your recommendation, and the decision you need. Keep it short and lead with the status itself. The sponsor should leave knowing the problem, your plan, and their part in it.
Script you can use as it is:
"I want you to hear this from me before the report goes out on [date]. [Program name] moves to red this week. The reason is [one-sentence cause], which puts [milestone or budget line] at risk by [amount or date range]. We found it through [how you found it: test results, vendor notice, forecast review]. Since then we have [action already taken] and [second action already taken]. I see [number] options: [option A], [option B], and [option C]. I recommend [option], because [reason]. What I need from you is [specific decision or help] by [date]. I will report back on [date] with [what you will show]."
Then stop and let the sponsor respond. Treat questions as engagement with the plan, and answer them from your evidence.
How do I separate the cause from my own performance?
Separate the cause from your performance by naming the cause as a fact, with its source and evidence, and owning your part in one plain sentence if you have one. Do not over-confess, and do not list everyone else's failings. Your sponsor needs the cause to choose a fix.
Harrin lists typical causes: testing that finds more bugs than expected, a vendor who cannot deliver on time, or estimates that were poor or scope that was missed. Some of those are outside your control and some are not. Sort yours before the pre-brief, then use the matching wording:
| Cause type | What to say |
|---|---|
| External (vendor, regulator, another team), such as a key vendor pulling out | [Vendor or team] notified us on [date] of [change]. The notice is attached. |
| Discovered (testing, data, integration) | [Activity] showed [finding]. We raised it as soon as the results were in. |
| Your planning or estimate | Our estimate for [work] was too low. Here is what we have changed so it does not repeat. |
| Shared | Two things combined: [cause one] and [cause two]. Here is who owns each fix. |
If part of the cause is your own planning, own it in one sentence with the correction attached. Harrin is matter-of-fact about poor estimates and missed scope: "It happens. All experienced project managers have been there." Keep the apology to that one sentence and spend the rest of the conversation on the fix. Before the pre-brief, check that you can explain the cause in a sentence or two.
What goes in the first line of a red status report?
The first line of a red status report should state the status, the cause, and the decision you need, in that order. Sponsors read the top and often stop there, so the opening line has to carry the whole message. Put the recovery path and the evidence directly beneath it.
Scribbl's template guide argues that a report should state what changed and what you need, not what you did, and notes that stakeholders read top-down and stop early. So open with the change and the decision, and leave the list of completed tasks on your project board.
Template:
Overall status: RED (was [previous status] on [date])
First line: [Program] is red because [cause]. [Milestone/budget] is at risk by [amount].
We need [decision] from [sponsor name] by [date].
Sponsor briefed: [sponsor name] on [date]
What changed: [fact, with link to evidence]
Cause: [cause and where it came from]
Already done: [action], [action]
Options:
A. [option]: effect on [time/cost/scope]
B. [option]: effect on [time/cost/scope]
C. [option]: effect on [time/cost/scope]
Recommendation: [option] because [reason]
Route back to amber: [conditions] by [date]
Next report: [date]
Illustrative example, a vendor delay with placeholders kept for every name, date, and amount:
Overall status: RED (was AMBER on [date])
First line: [Program] is red because [vendor] has moved delivery of [component] to [new date]. Go-live on [date] is at risk by [number] weeks.
We need a decision from [sponsor name] by [date]: approve option A or option B.
Sponsor briefed: [sponsor name] on [date]
Cause: [Vendor] notified us on [date] that [reason given]. Notice attached: [location of notice].
Already done: [action, such as requesting a partial delivery]; [action, such as checking lead times with an alternative supplier]
Options:
A. Move go-live to [new date]: no change to cost, [number] weeks later.
B. Source [component] from [alternative supplier]: keeps go-live on [date], adds [amount].
Recommendation: [A or B] because [reason].
What options and decision should I bring to my sponsor?
Bring your sponsor a small set of real options, each with its effect on time, cost, and scope, plus your recommendation and a date the decision is needed. Red means the fix sits beyond your own authority, so the decision request is the reason the report exists.
Harrin defines red as needing management attention beyond what you can give as a project manager. That framing helps you: you are escalating something only the sponsor can unblock. Her recovery options are the usual set: add people, add money, cut scope, or add time.
To make the request easy to answer:
- Phrase it as a choice: "Approve option [A] or option [B]."
- Say what happens if no decision arrives by [date]: "Without a decision, we will [default action], which means [effect]."
- Name the help precisely: a budget line, a named person, a scope cut, or a conversation with [stakeholder].
In Unblockd: asks to the sponsor by email with one-tap answers (no account), or answered by replying to the email.
How do I run the steering meeting once the program is red?
Run the steering meeting for a red program as a decision meeting. Open with the status and the decision, confirm the sponsor was briefed, take the options in turn, and close by reading back the decision, the owner, and the next report date so everyone leaves with the same record.
Agenda you can paste:
- Status and decision needed (opening line from the report).
- Cause and evidence, briefly.
- Actions already taken.
- Options and recommendation.
- Decision, owners, and dates.
- Route back to amber and next report.
Agree with your sponsor in the pre-brief who will speak to the recommendation. Having the sponsor back it in the room shows the group the plan has senior support.
What if red was never defined, or my sponsor reacts badly?
If red was never defined, state the criteria you are applying in the report and ask the sponsor to confirm them. If the sponsor reacts badly, stay on the facts, restate what you need, and offer a follow-up. Both moves keep the discussion on the program and the decision ahead.
Harrin recommends agreeing what red means before you have to use it, so the conversation can start from "this project now meets the criteria for Red reporting". If that never happened, say: "I am reporting red because [milestone/budget] is now outside [tolerance you are using]. I propose we adopt these definitions going forward: [definitions]."
For a sharp reaction, try: "I understand this is not what you wanted to hear. That is why I wanted you to have it early. The decision that changes the outcome is [decision]. Can we settle it by [date], or would you like me to come back with more detail on [option]?"
How do I show the route back to amber?
Show the route back to amber as a short list of conditions, each with an owner and a date, and report against that list every time. Agree the list with your sponsor when the decision is made, so you both know what has to happen before the status changes.
After the decision, Harrin advises getting the approvals, updating the budget and schedule, and reporting recovery regularly. Write the exit conditions like this:
- [Condition one, such as revised plan approved]: owner [name], by [date]
- [Condition two, such as new resource in place]: owner [name], by [date]
- [Condition three, such as forecast back within tolerance]: owner [name], by [date]
Move to amber once every condition is met, so the status changes once and stays changed.
Your next step: before the next report deadline, write the opening line and the decision request from the template above, then book the pre-brief.