A technician with thirty years on one class of equipment gives notice. The knowledge transfer plan is two junior techs riding along for a few days with notebooks. Everyone in the room understands this is inadequate. Nobody has a better plan.
I have watched versions of this play out across our customer base, and the organizational response is almost always the same. Roughly 20 to 25% of skilled
trades workers in North America are over the age of 55, according to the US BLS and Statistics Canada. Operations leaders read that number as a staffing problem and structure the solution accordingly: one-for-one hiring against every retirement, better onboarding, heavier reliance on third-party teams. All of it is worth doing. None of it addresses what actually leaves.
A thirty-year frontliner is not a replaceable name on a roster. They are decades of accumulated pattern recognition, enough to diagnose a failure in two minutes from a sound or smell that doesn’t appear in the manual. Hire their replacement on day one and you have solved for headcount. You have not solved for expertise.
“Ninety minutes of expert reasoning, and the system kept eleven words of it, entered from a truck at the end of a shift into a form designed for an auditor.”
Most field organizations believe they handled this years ago, when they digitized their workflows. They can point to a decade of work order history, completion records, parts usage, and resolution codes, all of it searchable. What they have is a record of outcomes. What retires with your best technician is judgment, and judgment was never in the system to begin with.
Take one work order. The record reads: “replaced valve assembly, 90 minutes, closed.” Here is what happened: a technician with twenty years on that equipment heard something wrong in the first two minutes. He skipped the diagnostic sequence the manual prescribes, because he already knew where it led. He checked three things that don’t appear on any checklist. He ruled out the two most likely causes. Then he replaced the valve. Ninety minutes of expert reasoning, and the system kept eleven words of it, entered from a truck at the end of a shift into a form designed for an auditor.
Across the organizations surveyed for this report, six percent describe their field data as high quality and ready for analytics and AI. Six percent. That number is the story, and it is the part of the AI conversation most vendors would rather not raise.
The knowledge exists. The record of it does not. Give a model ten years of outcome records and it learns, faithfully, to reproduce outcome records. It will tell a newer technician what got replaced on similar jobs. It cannot tell them what the veteran ruled out, or why, because that reasoning was never written down for any model to learn from. Swap in a better model and you get a more fluent version of the same blind spot. Nothing in the standard field stack was built to capture how a decision gets made.
So, the question is not which model to buy. It is how to capture the right knowledge, while the people who hold it are still on the payroll. Four conditions determine whether you build a data layer that makes intelligence possible or spend another decade recording results without the reasoning behind them.
1
Capture at the moment of decision, not at the end of the day
Reasoning is perishable. Anything that waits for the end of a shift collects a summary, and the summary is precisely where the logical chain gets dropped. The technology has to be present during the work, not after it.
2
Structure the judgment, not just the result
Ask instead: what did you rule out? Which path did you skip, and why? What did you notice that nobody asked about? These are answerable in seconds when the workflow asks well, and unrecoverable when it does not.
3
Subtract keystrokes before you add any
Ask a technician to document more and they will document less. Their day is already full, and they are measured on throughput, not on the thoroughness of their paperwork. Every field you add has to be paid for by removing two the technician resents.
4
Return value inside the same workflow
A technician who sees the system give something back will feed it. One who feels audited will give it the minimum. If the reasoning captured across the last thousand jobs surfaces as guidance on the next one, that guidance is itself the reason to keep contributing.
The fast test
If you want to know where your own operation stands, there is a fast test. Pull ten closed work orders from your most complex equipment class. Ask whether a competent technician who has never seen that machine could reconstruct, from the record alone, why the work was done the way it was done. If the answer is no, you do not have a problem a model will solve.
A dashboard tells you what happened. A model trained on outcomes will tell you the same thing, more fluently. Field intelligence is the layer underneath: the sound the veteran heard, the causes he ruled out, and his reasons for ruling them out, captured while he is still standing at the equipment.
That judgment is in your building today. In five years a great deal of it walks out the door permanently, and it does not come back. The only question worth asking is how much of it you will have captured before then.
“A technician who sees the system give something back will feed it. One who feels audited will give it the minimum. If the reasoning captured across the last thousand jobs surfaces as guidance on the next one, that guidance is itself the reason to keep contributing.”
