Listen on Spotify

Where is the technician, exactly?

Cold open

The customer says no one arrived. The dispatcher says someone was assigned. The field lead says the tech was rerouted. The technician, last seen in a WhatsApp thread with three map pins and no timestamps anyone trusts, may or may not be heading to the original site.

This is how a simple service day becomes a group exercise in location-based fiction.

HR-Z0 case note: if location is guessed, dispatch is gambling with labor.

The horror

Dispatch chaos creates compound operational pain:

Symptoms

The symptoms are always recognizable:

  • assignments change without clean visibility
  • site handoffs get missed
  • customers get inaccurate arrival expectations
  • supervisors spend time reconstructing movement
  • technicians inherit confusion they did not create

The problem is not only lateness. It is that the business cannot see the state of work clearly enough to intervene before the miss becomes public.

Cost

The cost is not abstract.

  • Time: technicians finish work once, then re-document it three times for three different stakeholders.
  • Money: manual proof chasing delays invoicing and inflates cost per completed job.
  • Trust: clients escalate when appointment history and completion evidence do not match reality.

The root cause

The incident happened in the field, but the root cause was authored in process design.

1

Dispatch logic lives in conversation, not workflow

When routing, reassignment, and status updates happen through chat and calls instead of a real work-order model, visibility degrades immediately.

2

Real-time status is weak

If dispatch cannot see who is assigned, en route, delayed, or blocked with confidence, every update is part estimate and part negotiation.

3

Automation is underused where it matters

Field ops should not depend on humans manually relaying routine status changes that a system could capture or trigger.

4

Field completion and office visibility run on different clocks

Field ops should not depend on humans manually relaying routine status changes that a system could capture or trigger.

The fix

Galaxie removes the paperwork ghost chase by redesigning proof capture and routing.

1

NorthStar maps the dispatch operating model

NorthStar identifies how work orders are created, assigned, rerouted, and closed, and where current coordination fails under daily conditions.

2

Astro and Orion improve field coordination

Astro helps establish:

  • clearer dispatch and reassignment logic
  • work-order state changes
  • notifications and triggers for handoffs
  • better real-time visibility

Orion supports the shared workspace and operating structure around the teams coordinating the work.

3

Evidence capture becomes part of doing the job, not post-job cleanup

Required proof artifacts are collected in workflow context and validated before closure. Office teams get usable records without radio drama.

Location should be data, not folklore.

HR-Z0
HR-Z0
Comms Officer

Comms Officer HR-Z0 (a.k.a. “H.R. Zero”) is Galaxie’s deadpan broadcast voice for the Office Horror Stories series — part dispatcher, part incident historian, part morale damage control.
Built from equal parts helpdesk transcripts, post-mortems, and calendar trauma, HR-Z0 doesn’t “tell stories.” It files reports from the front lines of messy operations — where ownership evaporates, folders time-travel, and a “quick change” becomes a six-month saga.

Give us a call

Available from 9am to 8pm, Monday to Friday.

Send us a message

Send your message any time you want.

Our usual reply time: 1 Business day