A timeline highlights events and milestones along a time axis. Use it to explain a launch, a historical sequence or a project’s major commitments. Give actual dates where they matter and distinguish confirmed milestones from tentative targets.
Separate events from durations
A milestone occurs at a point in time. A phase spans a period. Include start and end dates if a phase’s length matters; otherwise the viewer may read spacing as duration even when the layout is illustrative. State the year and timezone for time-sensitive schedules.
When the brief only gives an order, use an ordered sequence with no invented dates. Ask for clarification before turning “next month” into a specific day.
Choose the right level of detail
A stakeholder overview needs a few meaningful milestones. A working schedule may need dependencies, owners and progress for individual tasks. Use a Gantt chart for overlapping task durations; a timeline alone does not explain whether a delayed task blocks launch.
Keep captions short and move detailed notes below the relevant event. If several events happen on one date, show them as concurrent rather than spreading them across invented days.
Review changed dates
After asking to move a milestone, check adjacent events and any stated dependencies. A visual revision does not update your calendar or project management system. Confirm the new dates with the people responsible before sharing the exported schedule.
For the approval decisions leading up to a launch, see the approval workflow example.
Make it about your work
Edit this starting prompt, then send it when you are ready.