Project Timeline

Map milestones and work across time so dependencies, overlaps, and schedule risk are obvious before a deadline slips. The screen connects Timeline and Milestones so product teams can find the “Add milestone” action while checking milestones and on track.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Billing migration and Mobile onboarding, rather than an empty visual shell.

Project Timeline
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Add milestone

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Add milestone” action without losing sight of milestones, on track and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Add milestone is clearly available where the task happens.
  • Main view: Timeline keeps the starting point obvious.
  • Connected view: Milestones supplies nearby context.
  • Metric: Milestones is visible with a meaningful value.
  • Another signal: On track helps people judge what to do next.
  • Representative record: Billing migration makes the example specific.
  • Second record: Mobile onboarding shows the pattern works beyond one item.

States worth designing

  • No availability in selected range; show what people can do instead of leaving a blank panel.
  • Loading timeline without changing the layout unexpectedly.
  • Slot conflict or reschedule; explain the problem and preserve work.
  • Permission denied for milestones; clarify who can continue.
  • Success after choosing Add milestone; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Timeline → Milestones → Add milestone → Review outcome

Patterns used

Calendar, Timeline, Milestones, Dependencies, accessible states, contextual actions

Why these choices work

Show timezone, time range and conflicts before a user commits. Offer a clear path back to available slots.

In this design, people should be able to compare Billing migration with Mobile onboarding. Make milestones clear, then use on track to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add milestone” action. The happy path alone is not enough.

Related UI examples: Task Board, Sprint Planning, Product Roadmap.

Start from this in Figr

Design a project timeline screen for our existing software product. Use our real design-system tokens, components and product language. Show Timeline and Milestones, include believable records such as Billing migration, and make add milestone easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr