Renewal Calendar

See upcoming contract expirations, notice windows, auto-renewals, owners, and negotiation milestones on a shared calendar. This example brings Calendar and Contracts together so legal and operations teams can find the next task without losing context.

It includes representative records such as Atlas Cloud renewal and Northstar MSA notice. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Renewal Calendar
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Add renewal

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add renewal while keeping next 30d, auto-renew and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Calendar gives users an obvious place to start.
  • Supporting view: Contracts keeps the related context close.
  • Primary action: Add renewal stays visible when people need it.
  • First signal: Next 30d shows a useful value (18).
  • Second signal: Auto-renew gives additional context (7).
  • Sample record: Atlas Cloud renewal.
  • Next record: Northstar MSA notice.

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

Calendar → Contracts → Add renewal → Review outcome

Patterns used

Calendar, Calendar, Contracts, 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 calendar and contracts. People need to distinguish Atlas Cloud renewal from Northstar MSA notice. Keep next 30d 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 renewal”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Compliance Review, Matter Management, Legal Intake.

Start from this in Figr

Design a renewal calendar screen inside our existing product. Use our current components, tokens and content language. Include Calendar and Contracts views, credible records like Atlas Cloud renewal, and a clear “Add renewal” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr