What a Path to Green report is not
The most common mistake in recovery reporting is confusing a Path to Green with a project status report. A status report describes the current state. A Path to Green prescribes the recovery. Leadership does not need another description of the problem when the project is red — they need a credible, specific plan that they can hold the delivery team accountable to.
The second mistake is writing a Path to Green as a mitigation plan rather than a recovery plan. A mitigation plan says "we will reduce the impact of the risk." A recovery plan says "we will do these five things, in this order, by these dates, and this is how each one moves us from red to green." The specificity is not optional — it is the entire value of the document.
The third mistake is writing it without authority alignment. A Path to Green that requires decisions, resources, or priority changes that the PM cannot make unilaterally must name the decision owners explicitly. Leadership needs to know not just what must happen, but who must decide to make it happen — including themselves.
The structure of an effective Path to Green
An effective Path to Green report has six components. The order matters — each section sets up the next.
Current RAG status by dimension
A one-line RAG rating for each major dimension: scope, schedule, budget, resource, and process. Each rating should be accompanied by a single sentence explaining why that dimension is rated as it is. This is not the problem narrative — it is the baseline from which recovery is measured. Keep it to one page maximum.
Root blockers — not symptoms
The two or three root causes driving the overall status. Not "the project is behind schedule" — that is the symptom. The root blocker is the specific decision not made, the resource not allocated, the dependency not resolved, or the assumption that proved false. Leadership can only act on root blockers, not symptoms.
Numbered recovery actions
A numbered list of specific actions, in priority order, that address the root blockers. Each action must have: a clear description of what must happen, the person responsible for it, the date by which it must be complete, and — critically — who has the authority to make it happen. Actions that are within the PM's authority are different from actions that require leadership decisions. Both must appear, but they must be clearly distinguished.
What moves to green if each action completes
For each recovery action, a one-line statement of what dimension moves from its current rating to green if the action completes. This is the accountability mechanism — it allows leadership to track not just whether actions were completed, but whether they had the expected effect. A recovery action that was completed but did not improve the rating is diagnostic information.
Decisions required from leadership
A separate section listing decisions that cannot be made at delivery level — priority calls between workstreams, resource additions that require budget approval, scope reductions that require business owner sign-off, dependency resolutions that require executive sponsorship. These are presented as specific decision requests, not general asks for help. Each should state what must be decided, by whom, and by when.
Recovery timeline
A projected timeline showing when each dimension is expected to return to green, conditional on the recovery actions and decisions completing. This is not a guarantee — it is a conditional projection. "If action 1 completes by [date] and action 2 completes by [date], schedule returns to amber by [date] and green by [date]." Conditional language is not weakness — it is honesty about the dependencies the recovery relies on.
How to present it without undermining your position
The Path to Green report is often presented in the same steering committee meeting where the PM is explaining why the project is red. This is the highest-stakes communication context in project delivery, and the framing matters as much as the content.
The most effective framing is forward-looking and action-oriented without being defensive. "Here is where we are, here is what caused it, here is what must happen to recover" — in that order, with equal weight on each part. The cause section should be factual and specific, not apologetic. Leadership is not helped by apology — they are helped by understanding.
The decisions-required section is where the framing is most delicate. The PM who presents this section as "I need you to fix this" will produce defensiveness. The PM who presents it as "these are the decisions that only you can make, and here is the impact of each on the recovery timeline" gives leadership agency and positions themselves as a trusted advisor rather than a PM in crisis.
Finally — bring data. A Path to Green presented with supporting evidence from the project record (decision log extracts, variance history, pattern data) is more credible than one presented from the PM's narrative alone. The evidence shifts the conversation from "whose account is correct" to "what do we do about what the record shows."
How often to produce it
A Path to Green is not a regular cadence document — it is a document produced when a project is amber or red, or when there is a genuine risk of becoming amber or red in the next reporting cycle. Producing it too early (before leadership has visibility of the problem) can create alarm disproportionate to the situation. Producing it too late (after the problem has already been escalated informally) weakens its impact.
The right trigger is the PM's own assessment — not the formal RAG status, which often lags reality. If the PM's judgment is that the project is genuinely at risk and recovery actions are needed, that is the moment to produce the Path to Green — before the formal status turns red, not after.
Once produced, the Path to Green should be updated at each steering committee until all dimensions return to green. Each update should show whether the recovery actions were completed and whether they had the expected effect on the RAG status. A Path to Green that tracks its own effectiveness over time is a significantly more powerful document than one produced once and then superseded by the next status report.
The delta indicator — showing direction of travel
The most underused element in recovery reporting is the trend indicator — showing not just the current status but the direction of travel since the previous report. A project that is amber but improving is a very different situation to a project that is amber and deteriorating. Without a delta, leadership cannot make this distinction.
For each dimension, a simple indicator — improving, stable, or deteriorating — alongside the RAG status gives leadership the context they need to calibrate their response. A project that is red but improving on all dimensions may need monitoring rather than intervention. A project that is amber but deteriorating on two dimensions may need immediate action despite the nominally better overall status.