Skip to content

Dashboard template

Helm

The operations dashboard: what is happening today and what is going wrong.

Design-partner previewBuilt and demonstrable; onboarding a limited number of design partners.

Live preview

Change the palette and watch it repaint

This is the template rendering in the browser right now, not an image of it. Every colour comes from the scheme selected beside it.

Admin / Operations

Operations

Last 30 days

3 exceptions need a human

Open queue
bkg_01JQ8YB4Supplier timeout · outcome unknown · reconciling
bkg_01JQ8YC1Rate withdrawn between check and book
bkg_01JQ8YC7Payment captured, supplier declined

Bookings today

184

+12%

Value

AED 712k

+8%

Failed

3

−2

Departures

26

Bookings, last 14 days

Supplier health

sup_alpha812 msok
sup_beta1.44 sok
sup_gammatimeoutshed

The thinking

Why it is laid out this way

Designed around the question an operator actually opens a dashboard to answer, which is never 'how many bookings did we take'. It is 'is anything broken right now'. Exceptions sit at the top; the vanity numbers sit below them.

Built for

Operations teams

What the template decides

  • Exception queue first: failed bookings, unknown outcomes, supplier errors
  • Today's departures and arrivals
  • Booking volume and value, with yesterday and last week for context
  • Supplier response health inline
  • Role-based views so support and finance see different defaults

Next

A design is a starting point, not a platform

Behind every one of these screens sits the booking core, the pricing rules and the supplier connectivity that make it function. That is the part worth evaluating hardest.