Booking Admin

Run bookings with availability, resource, customer, status, conflict, and cancellation context visible in one weekly operations view. The screen connects Calendar and Bookings so growth teams can find the “New booking” action while checking bookings and available slots.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Studio A · Product shoot and Room 4 · Customer demo, rather than an empty visual shell.

Booking Admin
Use this template in Figr

Template facts

Screen

Calendar

Primary action

New booking

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Growth teams need a clear “New booking” action without losing sight of bookings, available slots and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New booking is clearly available where the task happens.
  • Main view: Calendar keeps the starting point obvious.
  • Connected view: Bookings supplies nearby context.
  • Metric: Bookings is visible with a meaningful value.
  • Another signal: Available slots helps people judge what to do next.
  • Representative record: Studio A · Product shoot makes the example specific.
  • Second record: Room 4 · Customer demo 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 bookings; clarify who can continue.
  • Success after choosing New booking; 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 → Bookings → New booking → Review outcome

Patterns used

Calendar, Calendar, Bookings, Resources, 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 Studio A · Product shoot with Room 4 · Customer demo. Make bookings clear, then use available slots 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 “New booking” action. The happy path alone is not enough.

Related UI examples: Vendor Management, Search Results, Marketplace Seller.

Start from this in Figr

Design a booking admin screen for our existing software product. Use our real design-system tokens, components and product language. Show Calendar and Bookings, include believable records such as Studio A · Product shoot, and make new booking easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr