Layered Geographic Timeline

1  Slide Type Name
Layered Geographic Timeline

2  One‑Sentence Purpose Statement
Shows “how the rollout or progress differs by region over the same period” by stacking parallel timelines for individual countries or geographic clusters on one shared time axis.

3  Visual Description (Designer Instructions)

• Use a 16 × 9 slide with a single horizontal time axis (quarters or months) running the full width near the centre.
• Stack 3‑7 horizontal tracks (one per region, country, or market) evenly spaced beneath the axis. Label each track on the far left in 11 pt bold (e.g., North America, EMEA, APAC).
• In every track, plot local milestones or duration bars at the correct dates—rectangles for programmes, diamonds for one‑day events. Keep the bars aligned precisely to the common time scale so comparisons are intuitive.
• Colour‑code milestones within each track by theme or work‑stream (optional), but keep track background neutral to let colour accents pop.
• If phases differ greatly by region, use shaded blocks spanning the exact start‑to‑finish dates (e.g., Reg Approval Window); add short leader lines to labels above or below the track to avoid crowding.
• Insert a vertical “Today” line cutting through all tracks so stakeholders see which regions are ahead or behind.
• To highlight sequence, add faint dependency arrows across tracks (e.g., APAC launch depends on EMEA lessons‑learned). Use 0.8‑pt grey arrows to avoid clutter.
• Reserve the top 15 % for the headline and legend (colour meaning or arrow explanation). Maintain ≥ 0.5 in margins to ensure no labels are clipped.
• Fonts: sans‑serif; milestone text 9 pt; axis dates 10 pt; headline 16 pt bold.

4  Business Questions This Slide Answers

• Which region is scheduled to hit each milestone first?
• How do regional launch windows overlap or cascade?
• Where are we currently ahead or behind versus the global plan?
• Are there cross‑regional dependencies that could cause delays?
• Does any market’s timeline push final global completion beyond target?

5  When to Use (Typical Situations)

• Global product or service roll‑outs (pharma, tech, retail).
• Regulatory compliance programmes with regional variations.
• Infrastructure build‑outs (data centres, manufacturing plants).
• Pan‑regional marketing campaigns or event calendars.
• Post‑merger integration showing different country legal‑entity close dates.

6  Core Data Fields Required

• Region / country names.
• Milestone titles and dates (or phase start & end) per region.
• Shared time‑axis scale.
• Current date (“Today”) marker.

7  Optional / Advanced Data Fields

• Colour palette to distinguish work‑streams (e.g., Tech vs Legal vs Ops).
• RAG or completion percentage badges next to each regional milestone.
• Dependency arrows or cross‑track connectors.
• Resource‑load or cost overlay per region (tiny bar or heat strip).
• Footnote or tooltip for region‑specific assumptions / constraints.