
Case study: Ground & Air Emergency Dispatch Platform
Emergency dispatch, redesigned for speed & accuracy
How I redesigned the intake, search and quoting workflows of a legacy dispatch platform so operators capture what matters first.
Role
UX designer, from stakeholder interviews to developer handoff
Timeline
Sep 2023 – Jul 2024, Arcadea Group
Team
Developer, product, project and business managers
Scope
6 workflows, 50+ screens, 30+ component design system
Product
B2B SaaS dispatch web app for emergency ground assets & flights
Tools

Figma
Overview
In dispatch, every second counts. A caller talks out of order while the operator captures details, finds the nearest asset and takes notes.
Ask for the critical information first and let everything else wait
The problem
The legacy interface spent an operator’s scarcest resource, attention, poorly.
Weak hierarchy, hard navigation and unclear actions made three jobs harder: capturing details from a caller who talks out of order, finding the closest asset, and building a multi-leg quote.
Design questions
Critical information first
How might we let operators capture critical information first?
Assets within the call
How might we put asset availability next to the call?
A readable flight plan
How might we make a multi-leg plan readable at a glance?
Settings that feel organized
How might we make a large settings area feel organized?
Where it started
The brief was to make a legacy application look modern.
Polish alone wouldn’t help an operator under pressure, so I used the new look as the way in and improved structure too.
Reading the old screens
A retrospective review of the screens, not user research.

dispatch board
❌ Minimalist design
Rows, panels and text carry similar weight, so nothing says look here first.
❌ Recognition over recall
Colour separates rows, so operators must learn what each means.

trip detail
❌ Visual hierarchy
Small, tightly packed text makes key facts hard to scan.
❌ Clear actions
Buttons carry similar weight, so the main action isn’t obvious.

map view
❌ Focus
The whole country is on screen, with no framing around the incident.
❌ Recognition over recall
Near-identical icons are hard to tell apart.
Constraints
Time pressure
Operators triage incidents while the caller is still talking.
Data density
A lot of information on one screen, so grouping and spacing do the work.
Technical limits
Every pattern had to be buildable and maintainable by the dev team.
Familiarity
Stay close to the existing app so operators keep working the way they do.
How I worked
1
Understand
Stakeholder and product owner conversations, legacy screen review.
2
Define
Design questions and what an operator needs first.
3
Explore
Lo-fi wireframes in Figma comparing solutions before choosing one.
4
Design
High-fidelity screens with complete, incomplete and error states.
5
Hand off
Figma components and specs for the developer.
Exploring options in wireframes & understanding workflows
I compared several approaches in lo-fi wireframes before committing.




The redesign
Four workflows, one principle: show what matters now, hold the rest.
Goal: an operator should understand each screen by reading it, not by following a guide. I believe it’s simpler, but it still needs validation with real users.
1. Intake: critical information first

New request: required and additional tabs, a notes rail on the left, a map on the right.
Required first, additional later
Two tabs split what’s needed in the first minutes from what can wait. The form saves as the operator types.
Status you can see without reading
Section headers show Complete or an error count, and fields show valid and invalid states. Skipping required details shows exactly where.
Notes in the order the caller speaks
Callers don’t speak in form order, so a notes rail captures details as they come. The map pins the location as it’s entered.
2. Search closest asset, inside the request

Search Closest Asset: now sits beside Call Consult and Map inside the new request workflow.

Filters by asset type, patient weight, equipment and transport mode, with a live result count.
One workspace, one decision
Availability, asset type and details sit within reach of the call.
Status never relies on colour alone
Status is written out and tinted, never colour alone.
3. Flight quoting and chartering

Generate a Quote: when pick up location is selected, the possible drop off locations are highlighted on the map to select from.

Quote: A quote is the one place that has access to everything related to the quote such as the trip plan, general fees, other fees, patient/escort details and any related attachments.

Trip Plan view: legs as rows, with crew bars running down the legs they serve.

Add a leg, with a note that new fees will be added.

Add fee: live fee calculation shown before saving.

Print: preview on the left, settings on the right.
A plan you can read down the page
Each leg is a row with the same facts in the same order.
Quotes built from the plan
The plan generates the quote, and reminders can go to chosen recipients.
A print dialog people already know
The print dialog follows familiar conventions: document tabs and zoom beside the preview, settings beside that.
4. A settings template for a complex area

Settings: grouped navigation, filters and bulk actions, and a confirmation after saving.
Matching how people think about settings
Categories sit in a searchable navigation that matches how users think. One template serves every settings page, so users learn it once.
One call, start to finish
Follow one call and the four workflows become one story.
1
The call arrives
A new request shows its ID, creator, time and running duration.
2
Critical details first
Required Information holds caller, request, patient and location, and saves as the operator types.
3
The caller jumps ahead
Anything out of order goes into the notes rail, time-stamped.
4
The location lands on the map
The map pins the address as it’s entered.
5
Something is missing
Section headers show error counts, so the operator knows where to go back.
6
Find the closest asset
Search Closest, filters and sort by time to arrival, all inside the request.
7
Save and proceed
One clear primary action moves on; Cancel Request stays quieter.
Before and after
The same jobs, side by side.
Call Intake to Prioritized Data Fields
Before

After

Mandatory information is prioritized in the intake form.
A map provides visual support.
Active notes rail allows to take down notes anytime.
Trip detail to quote plan
Before

After

Each leg is a row with facts in a fixed order.
Crew bars run down the legs they serve.
Fees, patient, reminders and history sit in a side navigation, easily accessible.
Decisions and trade-offs
Every screen is also the result of things I said no to.
Tabs instead of one long form
One long form adds cognitive load and pulls attention from the key data. Splitting required from additional information gives the process a clear shape, and live colour feedback confirms correct input.
A map beside the form
It shows the pickup location at a glance, without switching interfaces. The pin lets operators confirm they heard the address right.
One workflow instead of separate features
Asset search used to be separate, and features sat side by side with no single workflow. After talking with the product owner, I merged them into one.
Evolution, not revolution
Drastic change could break operators’ efficiency and confidence, so I kept the structure familiar and focused on hierarchy, clarity and look.
What I rejected: choosing a request type first
I explored asking for a request type first (Scene Call, Neonatal and so on). I dropped it: it forces operators to pick the right answer at the worst moment.

Discarded concept: request type tiles shown before the form.
Design system
30+ components, built once and used everywhere.
Built in Figma with variables and shared libraries. Buttons, fields, tables, filters, modals and toasts repeat across every workflow, so the product feels like one tool.



Outcomes
Workflows and components were handed to development with specs.
The product owner said the new screens look better and still do the job. That’s stakeholder feedback, not user testing.
Looking back
What worked
The visual quality improved significantly; the changes still needed validation.
What I’d do differently
I’d start with a usability evaluation: real users doing the most frequent, important tasks, to see where they fail. Findings would drive the UX changes.
What I took from it
In time-critical software, hierarchy is a safety feature.
NEXT PROJECT
so… want to chat?
Let’s make something
people trust.
End-user needs
Utilitarian Design
Business goals
That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.
© 2026 Vinuri Hopman. All rights reserved.


