You Did That Job Twice

A technician arrives at a restaurant in Plano at ten past two on the hottest afternoon of the year. He diagnoses a failed condenser fan motor in eight minutes. He is right.

He does not have the motor. The next slot is Friday.

Every fact needed to bring that part was recorded before he left the yard at seven. The equipment record held the model and the install date. The service history showed two prior visits to that unit. The customer's phone call described a noise and then silence. The firm had replaced eleven of those motors on that exact model in three years, all at eight to ten years of age.

Four facts, four systems, nobody joining them. So the van was loaded on the basis of what one man remembered running short of in March.

The second visit was not bad luck. It was arithmetic, and the firm ran the same arithmetic 938 times last year.

This is not a field services problem. It is what happens when the inputs to a decision live in different places and the assembly step is a person.

Field services. 4,800 calls, 68% fixed first time, 938 return trips for a part. $291,000 a year in driving to jobs the firm had already visited.

Accounting. Karen in Portland built 412 engagement letters each January by working from last year's document. Twenty-three went out carrying the previous year's fees. The current schedule existed. It was in a different file from the one she was editing.

Construction. A subcontractor builds to the drawing on his phone. The revision was issued eleven days earlier and lives in the document management system nobody opens on site. $8,400 to take it down and do it again.

Property. Dave in Chicago approved $4,200 for a compressor replacement. The warranty record was in his own spreadsheet, correct and unconsulted, because nothing put it in front of the invoice.

Legal. A conflicts check performed by asking whether anyone recalls the name. Twenty-two years of client records exist. The retrieval mechanism is a managing partner's memory under time pressure.

Healthcare. A patient arrives for a consultation and the referral letter, imaging and prior notes are in three systems. The appointment becomes a data-gathering exercise and a second appointment is booked.

The shared structure: the organisation holds every fact it needs. The facts sit in separate systems. Assembly depends on a person remembering, under time pressure, to go and look.

Three reasons, none of them about competence.

Nobody experiences the gap until it is expensive. Luis does not feel a missing fact at seven in the morning. He feels it at 2:40pm in front of a customer, which is the first moment the assembly failure produces a symptom. Every process where the cost of an omission lands hours or weeks after the omission will accumulate omissions, because the feedback arrives too late to change the behaviour that caused it.

Assembling properly costs more than it appears to save. Checking four systems before every job is twenty minutes per call. Across 4,800 calls that is 1,600 hours, which nobody will authorise to prevent a problem that occurs 20% of the time. The individual instance is never worth the effort. The aggregate always is, and the aggregate is invisible from inside any single job.

Memory is a plausible substitute right up until it is not. Luis's recollection of what he ran short of in March is genuinely useful information. It is simply worse than nine years of records, and the difference is invisible because a technician who arrives prepared and a technician who arrives lucky look identical at the time.

Worse, the process passes inspection. There is a service history. There is a document management system. There is a current fee schedule. An auditor would find every required record present and correctly maintained. All of that is true. None of it is assembled.

This is why "be more thorough" fails as a remedy. The people in these stories were thorough. Karen worked from last year's letter because that is how you produce 412 documents in a month. The remedy has to change when the assembly happens, not how hard people try.

Across the Blueprint series, every agent that removed rework did the same three things.

It assembled before the work started, not during. The parts agent enriches the job at booking, hours before the technician loads the van. Karen's agent builds each letter from the current schedule rather than from last year's document. The assembly happens at a moment when acting on it is still cheap.

It ranked rather than asserted. A prediction with a confidence score can be acted on proportionately. Certainty cannot. The parts agent predicts nothing below a confidence floor and marks the job diagnostic, because a wrong part produces the same second visit with more steps and less trust.

It checked rather than assumed. Predicting the part is half of it. Checking whether that part is already on the van is the half that generates the pull ticket. A recommendation nobody verifies against reality is a suggestion.

Dave's agent compares the warranty date to the invoice before approval. Kathy's compares every commission line to the contracted rate rather than four carriers out of eleven.

The mechanism is always the same: the reading across systems happens without a person having to remember to do it, so the human arrives already holding what the job needs.

Running costs across these designs: $32 to $280 a month. Set against a third of your jobs being done twice.

Find the work your business does twice. Return visits. Reissued documents. Rebuilt sections. Follow-up appointments that exist because the first one lacked something.

Then ask three questions.

Did we already hold the information that would have prevented it? Usually yes, in a system somebody could have opened.

Who was supposed to assemble it, and when? If the answer is the person doing the work, at the moment of doing it, then it happens when there is time and not when there is not.

What does the repeat get recorded as? A callback, a revision, a follow-up. Never as the fifteen minutes of assembly nobody had, which is why the number never falls.

Doing the job twice is not a failure of skill. Everyone in these stories was good at their job and got the diagnosis right. It is a failure of sequencing: the facts were gathered after the moment they would have changed the outcome.

Every Blueprint in the archive closes a gap like this one. Architectures, build guides, cost breakdowns, failure modes. Free to read. Free to build from.

57 agent designs. Your version of the forty-mile drive is probably already in there.

Subscribe to AdAI News. New blueprint every week.

by SP, CEO - Connect on LinkedIn
for the AdAI Ed. Team