Reverse timeline counting down to a fixed deadline (e.g., regulatory go-live), with risk flags and completion percentages.
1 Slide Type Name
Compliance‑Countdown Timeline
2 One‑Sentence Purpose Statement
Shows “how much time and work remain until the non‑negotiable compliance deadline” by counting down to Day 0 and flagging risks or completion percentages on the way.
3 Visual Description (Designer Instructions)
- Create a 16 × 9 slide with Day 0 (the hard deadline) anchored on the far right of a horizontal timeline; label it prominently (e.g., “Reg Go‑Live • 1 Jan 2027”).
- Plot preceding dates backwards from right to left in equal time units (weeks or months): Day ‑30, ‑60, ‑90, etc. Show these ticks and minor grid lines to reinforce the countdown direction.
- For each key deliverable or work‑stream, draw a horizontal progress bar that starts at its kickoff date (left) and ends at its planned finish (counting toward Day 0); fill the bar proportionally to % complete, using a muted colour for remaining scope.
- Place risk or status icons (⚠ at‑risk, ✔ completed) directly on the bar at the current progress point; add small labels above the icons if space allows.
- Include a large numeric “T‑” counter near the top right (e.g., “T‑73 Days”) updating automatically before presentations, or a “Weeks Remaining” badge.
- Add a vertical “Today” line that intersects all bars, visually separating work completed (left side) from work outstanding (right side). Shade the overdue section of any bar red if the planned finish date is left of “Today.”
- Reserve the top 15 % for a headline and a legend that explains bar‑fill colours and risk icons. Keep text away from the extreme right so Day 0 stands out.
- Fonts: sans‑serif; deliverable labels 9 pt; axis tick labels 10 pt; headline 16 pt bold.
4 Business Questions This Slide Answers
- How many days/weeks remain until the compliance deadline?
- Which work‑streams are on‑track, at‑risk, or already overdue?
- What percentage of each deliverable is complete today?
- Where are schedule buffers thin or nonexistent?
- Are critical dependencies likely to breach the fixed date?
5 When to Use (Typical Situations)
- Regulatory or audit readiness (e.g., GDPR, SOX, Basel III).
- Safety certifications or medical device filings with immovable dates.
- Contractual “go‑no‑go” cut‑over events (data‑center shutdown, carve‑out TSA).
- Public‑company IPO readiness checklists.
- Any programme where missing Day 0 incurs heavy penalties.
6 Core Data Fields Required
- Fixed compliance deadline (Day 0).
- Key deliverable or work‑stream names.
- Planned start and finish dates per deliverable.
- Current % complete for each bar.
- Current date (“Today”) for live countdown.
7 Optional / Advanced Data Fields
- Risk status or RAG flag per deliverable (icon or bar colour).
- Dependency arrows between bars.
- Buffer days displayed as small gaps to Day 0.
- Owner or accountable executive initials on each bar.
- Cumulative completion metric (e.g., “Portfolio 84 % done”) shown as a gauge or donut.