Add project details or files (optional)
I could use help with Optional

I usually reply within one or two business days to discuss the scope and next step.

PITCHWAVE®
HomeInsightsGuide

Guide

How to Present a Project Timeline on One Slide

A board or client reading “Setup in Month 1, migration in Month 2, launch in Month 3” can see an intended order, but not what has to be ready for the next step. I would use the timeline to show the work, the handover and the condition that controls the next start. Here is a worked example for a customer-records migration.

by Seva Latin · 4 min read ·

In this guide
01 / Guide

Replace broad phases with the work being planned

Consider a team preparing customer records for a test import into a new system. A draft slide shows three equal boxes: “Setup”, “Migration” and “Launch”, each assigned a month. These labels leave important questions open. Does setup include agreeing which source fields map to the new system? When is the source file ready to use? Is a test import the same as a launch?

The revised slide narrows the plan to the work the team can describe. Field mapping is agreed in Month 1. Source-file preparation runs across Months 1 and 2. The file is accepted at the end of Month 2, and the test import is planned for Month 3, subject to both prerequisites. It makes no promise about a later production launch.

Use the project team’s maintained schedule for real dates, durations and dependencies. The example demonstrates what to show on a slide; its three-month arrangement is invented, not a delivery benchmark.

02 / Guide

Show work periods and milestone events differently

A bar shows the planned period for an activity. A diamond marks the point at which an event is expected. In this example, preparing the source file occupies time; acceptance of that file is a milestone. The month labels use one shared scale, so parallel preparation and mapping are visible.

The U.S. Government Accountability Office’s Schedule Assessment Guide distinguishes milestones, which have no duration, from work activities. It also recommends clear milestone completion conditions. Applied here, “Source file accepted” needs an agreed meaning: the receiving team has checked the file against the agreed format and required fields. “Migration” alone does not identify that handover.

Illustrative example

Test import depends on agreed mapping and an accepted source file

Draft · phase labels

Month 1Setup

Month 2Migration

Month 3Launch

Revision · planned work and handover

Customer-records migration · preparation for test import

  1. Agree field mappingMonth 1
  2. Prepare source fileMonths 1–2
  3. Source file acceptedEnd of Month 2
  4. Run test importMonth 3 · conditional

Start test import only after mapping is agreed and the source file is accepted.

Planned work periodPlanned milestone

1Bars show work periods on the same month scale.

2The diamond marks acceptance; the next start still has a condition.

Fictional planning example, not a client schedule or a delivery benchmark. Months are relative to kickoff. All work and events are planned; bar fill does not show completion.
03 / Guide

Keep the start condition beside the next activity

The test import requires both an agreed field mapping and an accepted source file. Put that condition on the slide next to the import activity. A marker at the end of Month 2 should not imply that acceptance automatically happens because the calendar reaches that point.

GAO describes a finish-to-start dependency as one where a successor cannot begin until its predecessor finishes. It does not mean the successor must start immediately afterwards. On a summary slide, show the relationship that matters to the discussion without drawing every link from the detailed schedule.

If acceptance slips, ask the schedule owner to confirm the effect on the import date. Do not keep the old date by shortening the bar in the presentation. The underlying plan needs to support the revised timing.

04 / Guide

Build and review the summary in PowerPoint

PowerPoint’s SmartArt timeline can show a short series of target dates. Microsoft documents Insert → SmartArt → Process for desktop timeline layouts. For the parallel work and activity spans in this example, editable shapes arranged against a shared month scale give you more control over the distinction between work and events.

Before sharing, check the following against the maintained schedule. If you are presenting current progress rather than a future plan, add an as-of date and distinguish actual completion from forecast timing. The example below is entirely planned work, so none of its filled bars means “complete”.

  • Name the event behind each milestone and agree what counts as completion.
  • Keep parallel activities aligned to the same calendar scale.
  • Make the prerequisite for the next important start visible.
  • Label dates as planned or actual, and name the source schedule and its version.
  • Keep the detailed schedule available for questions about other dependencies or timing.

Send me your project timeline and tell me which handover the reader needs to understand.

Sources and technical guidance

Have a case to make?

Tell me what you’re working on. A rough idea or an existing deck is enough to start.

Start a conversation ↗