Risk-Mitigation Overlay Timeline

1  Slide Type Name
Risk‑Mitigation Overlay Timeline

2  One‑Sentence Purpose Statement
Clarifies “when key risks materialise and exactly which mitigations will be in place at each point.”

3  Visual Description (Designer Instructions)

• Build a 16 × 9 slide with a classic horizontal project timeline (phases or milestones) running across the central band.
• Directly beneath that band, add a parallel, slimmer “mitigation lane” aligned to the same time scale.
• In the primary band, display milestones or phase blocks in muted project colours; attach small risk icons (e.g., ⚠) above the dates where a specific risk is expected to peak.
• In the mitigation lane, place coloured bars or labelled call‑out tags that span the exact period during which each control or contingency will be active; draw a subtle connector (thin dotted line) from each risk icon down to its corresponding mitigation bar.
• Use consistent colour‑coding: one hue for risk categories (e.g., red = schedule, orange = cost) and a complementary but distinct palette for mitigation bars.
• Add a vertical “Today” marker intersecting both lanes to show current coverage.
• Reserve the top 15 % for a concise headline plus a compact legend explaining icon colours and bar styles; keep legend elements fully clear of the timeline graphics.
• Maintain ample white margins and a clean sans‑serif font (time labels 11 pt bold; mitigation labels 9 pt regular).
  
  

4  Business Questions This Slide Answers

• Which project risks arise when, and how severe are they?
• Do we have mitigation or control measures in place before each risk window opens?
• Are there periods with overlapping high‑risk exposure and thin mitigation coverage?
• How does today’s position relate to upcoming risks and planned actions?
• What is the residual risk once mitigations are applied?

5  When to Use (Typical Situations)

• Steering‑committee or board updates that need assurance on risk management.
• Programme kick‑off decks aligning owners on mitigation timing.
• Regulatory projects where controls must be documented alongside the plan.
• Vendor‑transition or cut‑over timelines with high operational risk.
• Capital projects tracking safety or environmental risk reduction measures.

6  Core Data Fields Required

• Time scale (dates or phase labels).
• Risk event description, category, and trigger date/window.
• Mitigation activity name and start/finish dates.
• Current date (“Today”) indicator.

7  Optional / Advanced Data Fields

• Risk severity rating (e.g., High / Med / Low) shown by icon colour or size.
• Owner for each mitigation bar.
• Residual‑risk KPI after control (RPN, $ exposure) annotated beside bars.
• Confidence level or status (planned, in‑progress, complete) via bar shading.
• Dependency arrows if one mitigation relies on another finishing first.