Incident Timeline

Track incident milestones, alerts, mitigations, deploys, owners, and communications in one chronological operational view. This example brings Timeline and Impact together so engineering teams can find the next task without losing context.

It includes representative records such as Alert triggered and Rollback started. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Incident Timeline
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Add event

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to add event while keeping duration, responders and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Timeline gives users an obvious place to start.
  • Supporting view: Impact keeps the related context close.
  • Primary action: Add event stays visible when people need it.
  • First signal: Duration shows a useful value (47m).
  • Second signal: Responders gives additional context (8).
  • Sample record: Alert triggered.
  • Next record: Rollback started.

States worth designing

  • No slots in selected range: say what changed, protect progress, and offer a clear next step.
  • Timezone mismatch: say what changed, protect progress, and offer a clear next step.
  • Booking conflict: say what changed, protect progress, and offer a clear next step.
  • Booking confirmed: say what changed, protect progress, and offer a clear next step.
  • Reschedule failure: say what changed, protect progress, and offer a clear next step.
  • View-only permission: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Timeline → Impact → Add event → Review outcome

Patterns used

Calendar, Timeline, Impact, contextual actions, error recovery

Why these choices work

Show the timezone, resource and conflicting time slots before confirmation. Recovery should preserve the selected date and context.

Pay attention to timeline and impact. People need to distinguish Alert triggered from Rollback started. Keep duration visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add event”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Service Catalog, Infrastructure Overview, Cloud Cost Explorer.

Start from this in Figr

Design a incident timeline screen inside our existing product. Use our current components, tokens and content language. Include Timeline and Impact views, credible records like Alert triggered, and a clear “Add event” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr