Lifeline Emergency Dispatcher Console

The challenge

Before

Lifeline Ambulance operates a fleet of 28 vehicles across emergency-tier and patient-transport tiers across the wider Auckland region. The dispatcher console — the screen six dispatchers stare at for ten-hour shifts — had been built incrementally over six years and was the loudest, most consistent complaint from operations staff. Dispatchers reported visual fatigue, repeated mis-clicks under stress, and an information density that had become impenetrable to new starters. Critical information about incoming calls was buried; non-critical information dominated the screen.

• Six-year-old dispatcher console assembled incrementally with no UX baseline
• Visual fatigue reported by dispatchers across ten-hour shifts
• Repeated mis-clicks under stress, especially during high-call-volume periods
• Critical call information buried under non-critical metadata
• New starters taking eight weeks to become solo-shift competent
• Color usage inconsistent — same color meaning different things in different panels
• Alarm sounds layered on top of each other indistinguishably
• No way to see the state of the fleet without scrolling across multiple screens

The solution

What we built

We redesigned the dispatcher console from a clean slate, with dispatchers as research partners through the entire project. Information hierarchy was rebuilt — incoming critical calls always occupy a dedicated zone with consistent placement; fleet state has its own zone; call queue has its own. Visual density was tuned for ten-hour shifts using high contrast on critical elements and lower contrast on supporting context. Color usage was unified across the console with a documented semantic palette — red is exclusively critical, amber exclusively warning, green exclusively confirmed-and-in-progress. Sound design was reworked with distinct earcons that dispatchers can identify without looking. New starters get a guided overlay for their first two weeks. Mis-click risk was reduced by separating destructive actions into a confirm-band rather than relying on modal dialogs that get reflexively dismissed. The whole console runs on the same operational backend — no data migration risk.

How the system flows

1. Call Intake→Critical Zone→Priority Visual + Earcon
2. Triage Decision→Tier Assignment→Vehicle Recommendation
3. Dispatch→Vehicle Confirmed→ETA Updated→Caller Notified
4. Fleet State→Persistent Zone→Status at Glance
5. Hand-off→Crew Update→Hospital Pre-alert→Documentation
6. Shift Change→Open Issues Walk-through→Acknowledged Handover

• Guided overlay for new starters during first two weeks of solo shifts
• Documented semantic palette with red/amber/green meanings consistent
• Distinct earcons for critical events identifiable without looking
• Destructive actions gated behind confirm-band, not dismissible modal