Leave Management

Plan time off with team coverage, balances, approval status, holidays, and overlap visible before a manager approves leave. The screen connects Calendar and Requests so product teams can find the “Request leave” action while checking away today and pending requests.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Maya · PTO and Jon · Sick leave, rather than an empty visual shell.

Leave Management
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Request leave

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 “Request leave” action without losing sight of away today, pending requests and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Request leave is clearly available where the task happens.
  • Main view: Calendar keeps the starting point obvious.
  • Connected view: Requests supplies nearby context.
  • Metric: Away today is visible with a meaningful value.
  • Another signal: Pending requests helps people judge what to do next.
  • Representative record: Maya · PTO makes the example specific.
  • Second record: Jon · Sick leave 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 calendar without changing the layout unexpectedly.
  • Slot conflict or reschedule; explain the problem and preserve work.
  • Permission denied for requests; clarify who can continue.
  • Success after choosing Request leave; 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

Calendar → Requests → Request leave → Review outcome

Patterns used

Calendar, Calendar, Requests, Balances, 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 Maya · PTO with Jon · Sick leave. Make away today clear, then use pending requests 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 “Request leave” action. The happy path alone is not enough.

Related UI examples: Hiring Pipeline, Performance Reviews, Employee Directory.

Start from this in Figr

Design a leave management screen for our existing software product. Use our real design-system tokens, components and product language. Show Calendar and Requests, include believable records such as Maya · PTO, and make request leave easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr