Red Is a Decision Point: A Two-Day Recovery Protocol for Delivery Teams

When a workstream turns red, the first meeting often produces a larger status pack and a longer list of caveats. That is a reporting response to a delivery problem. Recovery requires a different sequence: convene the right people, establish the facts, decide whether the slip is recoverable, and tell stakeholders what will change before rumour writes the narrative.

For UK delivery teams, a red is rarely a surprise at the individual level. The people closest to the work usually know that a dependency has drifted, a decision has stalled, or a supplier milestone has lost credibility. The difficulty is that the organisation's reporting rhythm lags behind that knowledge. A two-day protocol is not a cure. It is a controlled way to close the gap between signal and action.

Hour Zero: Establish a Recovery Cell, Not a Review Panel

The delivery lead should convene the recovery cell as soon as the red is credible. The programme sponsor is notified immediately, but the cell itself should remain small: the delivery lead, the workstream lead, a PMO analyst with access to the plan and evidence, the business owner affected by the outcome, and a supplier representative only where a supplier dependency is central to the slip. A finance representative may attend for a single fact-check if cost exposure is material. The cell is not a governance forum. It is a temporary decision unit with a named chair and a single facts log.

The sponsor's role is to make the escalation path explicit, not to chair every conversation. In UK programme environments, the senior responsible owner or sponsor often becomes the default arbiter of every red. That slows the first day and blurs accountability. The sponsor should agree the cell's authority, set the threshold for re-baselining, and remain available for the decision at the 48-hour mark.

First Four Hours: Freeze the Story and Capture the Facts

The initial instinct is to revise the plan. Resist it. The first task is to freeze the story: what was baselined, what has actually happened, what is now forecast, and what evidence supports each statement. The cell should maintain three short lists: known facts, open questions, and working assumptions. Each item needs an owner and a date by which it will be resolved or accepted.

This is not an exercise in exhaustive documentation. It is a defence against speculative recovery. A common failure is to accept the first plausible explanation because it allows the meeting to end. The cell should ask what would have to be true for the slip to be recoverable, and then test whether that condition is evidenced. If the answer depends on a decision that has not yet been taken, a resource that has not yet been confirmed, or a supplier commitment that has not yet been tested, it belongs in the open questions list, not the recovery plan.

Day One: Separate Recoverable Slippage from Structural Failure

Not every red is the same. Some slips are finite, owned and recoverable within the existing mandate. Others reveal that the plan's underlying assumptions no longer hold. The cell should apply five tests before choosing a path.

First, critical path impact: does the slip affect the sequence of work that determines the end date, or is it absorbable within float? Second, decision latency: is the delay caused by a choice that has not been made, and can that choice be made within the cell's authority? Third, dependency integrity: are the commitments from other teams or suppliers still credible, or have they become aspirational? Fourth, capacity: can the recovery be delivered with named people who are genuinely available, or does it rely on the same constrained specialists already committed elsewhere? Fifth, scope and benefits: if the date is held, what is being quietly de-scoped, and who has accepted that trade-off?

Recoverable slippage has a finite cause, a named owner and a credible route back to the baseline. Structural failure has multiple unresolved unknowns, a governance blockage or a material impact on benefits. Most reds sit between the two. The cell should describe the position precisely, for example "recoverable with conditions", rather than force it into a binary label.

Day One to Day Two: Choose a Path, Not an Action List

By the end of the first day, the cell should choose one of three paths. The first is recover: a short recovery plan with no more than five critical actions, each with an owner, a date and an acceptance test. The second is re-baseline: a revised plan with a new date or scope, approved by the sponsor and recorded as a formal change. The third is stop or re-scope: a controlled decision that the workstream should not continue in its current form.

The temptation is to produce a long action list that keeps the red in place while creating an impression of activity. That is reporting theatre. A recovery path must change something material: the sequence, the resourcing, the decision rights or the scope. If none of those changes, the cell has not recovered the workstream; it has merely described it.

Before the 48-Hour Mark: Communicate the Change, Not the Anxiety

Stakeholders should hear from the sponsor or delivery lead before speculation fills the gap. The message should be short and factual: what has changed, what is known, what is not yet known, what decision has been taken, and when the next checkpoint will be. Avoid false reassurance. Avoid predicting a recovery date that has not been tested. Avoid distributing the full status pack as a substitute for a decision.

In UK organisations, informal networks often move faster than formal governance. A concise note to the programme board, the affected business area and any material supplier is usually more effective than a lengthy pack that invites interpretation. The sponsor should own the message to the board; the delivery lead should own the message to the delivery team. One version of events should be in circulation.

The PMO's Role: Keep the Record Clean

The PMO should not be asked to produce a bigger deck. Its role is to keep the record clean: decision log, action log, evidence trail and assurance checks. The RAG status should be updated only after the path is chosen, not before. If the workstream remains red, the record should show why, who owns the recovery and what would change the status. That is more useful than an early return to amber.

What Good Looks Like After 48 Hours

A red may still be red after two days. That is acceptable. What matters is that it is no longer undefined. There should be a named chair, a facts log, a chosen path, a sponsor decision where required, and a next checkpoint with a date. If the cell cannot choose a path, the escalation should be explicit: the sponsor decides, or the workstream is paused until the decision can be made.

The purpose of this protocol is not to turn red into amber. It is to prevent a red from drifting into an unmanaged condition. A calm, repeatable response gives delivery teams the best chance of recovering what can be recovered, and the clarity to stop what cannot.