Field note · 18 May 2026
Reading a fortnight of tickets without naming anyone
Stripped exports are enough to see weekly rhythms: serial numbers that vanish on the senior tech’s Kluang day, photos that share the same car-park light.
Managers sometimes worry that a ticket audit is a hunt for a junior technician to blame. We refuse exports that still contain customer names, phone numbers, or exact house addresses. What we need is a job identifier, a time, a GPS crumb if you have one, and the fields the sheet already stores.
That is enough. It is often more than enough.
Patterns that show up in two weeks
A medical-equipment crew in Johor filled the unit serial on Monday and Tuesday and left it blank after Wednesday. The senior technician spent Wednesday and Thursday on a Kluang hospital contract. The juniors knew how to change a pump. They did not know where the serial was stamped, and the job sheet offered no photo hint. The pattern was coverage, not character.
A residential HVAC crew took warranty photos with identical shadow angles at 12.40. GPS put three vans in the same hypermarket car park. The units in the photos were real; the time of capture was not the time of the visit. The sheet required two photos before close. The car park was where that requirement could be met without a toddler in the frame.
What we will not do with the file
We will not rank technicians in a table for the manager to pin on a wall. We will not hand the export to anyone outside the engagement. After the brief is delivered we delete the file on the timetable in our privacy notice. If a manager wants a named conversation with one person, that conversation is theirs; our brief stays at the level of patterns.
App analytics for field service apps that turns into a scoreboard in the pantry is just a more expensive way to sour a crew. The export is for seeing the sheet and the week, not for catching a man at lunch.