Field note · 2 April 2026
What the dispatcher sends is not what the phone shows
A gate code typed into a notes blob at 6.15 a.m. can arrive on the technician’s screen as a wrapped line nobody scrolls. The handoff is a layout problem as much as a people problem.
The Pasir Gudang plant had a new gate contractor. The night dispatcher, to her credit, typed the code into the job at 6.12 a.m. She put it in Notes because Notes is the field that always exists, even when the vendor has locked the custom fields.
On the technician’s phone, Notes sits under the customer name, under the map thumbnail, under the “call customer” button, as a single line that ends in an ellipsis. Opening it takes a second tap most people do not make while holding a permit lanyard in their teeth.
He rang the office from the barrier. She was already on another job. He waited fourteen minutes. The plant’s security had the code on a laminated card, which he eventually used. The job app still contained the correct information. Nobody had seen it.
The export will not save you here
Closed-job exports often store the dispatcher’s note in full. A desktop reading looks clean. App analytics for field service apps that never opens the technician layout will miss the ellipsis. That is why a Dispatch Handoff Study includes a morning at the desk and an afternoon in the van, not one or the other.
A small change that is actually small
On that crew, promoting the access code into the first field the phone displays — the one already used for unit location — stopped the barrier calls within a week. Nobody retrained twelve people. Nobody bought a different app. The dispatcher kept typing at 6.12. The difference was where the type landed.
If your pantry argument is “we sent it” versus “I never got it,” sit both people in front of the same job on two different screens before you write a policy.