Field Service Jobs: Parts, History & the Second Visit You Should Not Need
The second visit is where field service profitability goes. A technician who arrives without the part, without the history, or without knowing what was promised will be back — and the return trip costs more than the margin on the original job.
Field service businesses tend to measure jobs completed, technicians deployed and response times. The number that actually decides profitability is one almost nobody tracks: the proportion of jobs that required more than one visit.
A second visit consumes a technician for half a day, a vehicle and fuel, and a slot that a new job could have filled — against a job whose price was set assuming one visit. On a service call worth a few thousand shillings, the return trip does not reduce the margin; it removes it and starts eating into the next job.
Why technicians go back
The causes are unglamorous, repetitive and almost entirely preventable — which is why measuring them is worth doing.
| Cause | Underlying failure | Where it is fixed |
|---|---|---|
| The part was not on the van | The fault was not diagnosed before dispatch | Intake — asking better questions when the job is logged |
| The wrong technician was sent | Skills not matched to the job type | Scheduling, and knowing what the job actually is |
| Nobody was on site with access | Appointment not confirmed | Confirmation the day before, which costs one message |
| The history was unknown | Previous visits not recorded against the asset or customer | Records — the cheapest fix on this list |
| The customer expected something else | Scope not agreed at booking | Intake again, in writing |
Two of the five are intake problems, which is the consistent finding when businesses first analyse this. Field service failures are usually created at the desk, not in the field, and the technician gets blamed for a job that was under-specified before they left.
Field service failures are created at the desk. The technician who arrives without the right part is usually executing a job that was under-specified before they got in the van.
The van is a stock location
Most field service businesses treat parts on a van as consumed at the moment they leave the warehouse. That is convenient and wrong, and it produces two familiar problems: nobody knows what is actually on each van, and parts fitted at a customer site are never billed because no record connects them to a job.
Treating each van as a stock location with a named custodian changes both. Stock transferred to the van remains stock; a part fitted is issued against the job; what is left is countable. A monthly van count then takes twenty minutes and tells you something true.
-
Transfer to the van, do not write off to the van
A transfer keeps the value visible and attributable. A write-off makes the van a black hole with a technician's name on it.
-
Issue parts against the job, at the job
This is what makes the part billable and the job costable. Reconstructing it from memory at the end of the week loses parts and revenue in both directions.
-
Count each van monthly
Twenty minutes per vehicle. It catches the slow divergence that otherwise appears as an unexplained annual shrinkage figure nobody can attribute.
-
Restock from a list, not from a request
A standard van kit per technician type, replenished to par, beats reacting to "I need another one of those" — and it is what stops the same missing part causing a second visit twice.
Parts fitted but never billed
In most field service businesses this is a larger number than parts lost. A technician solves the problem, fits a component, and the invoice reflects labour only because nothing recorded the part against the job. The customer is not disputing it — nobody asked them to pay.
What a job record should contain
A field service job is a small project, and the record that makes it profitable is short.
- What was reported, in the customer's words, at intake.
- What was found, in the technician's words, on site — frequently different, and the difference is the diagnostic value.
- What was done, including parts fitted and time on site.
- What remains outstanding, if anything, with a date. This is the field that prevents an unplanned second visit from becoming a surprise.
- Which asset it relates to, where you service equipment rather than premises.
The last one matters more than it looks for anyone maintaining customer equipment. A history attached to the machine — what has failed before, what was replaced, when it was last serviced — is what lets the next technician arrive prepared, and it is the difference between a service business and a series of unconnected call-outs.
Costing a job honestly
One service call, one visit versus two
Illustrative, in KES. A perfectly ordinary job that made a reasonable margin becomes a loss on the second visit — and the customer is not unhappy, the technician did good work, and nothing in a monthly revenue report shows any of it. Only job-level costing makes this visible.
What we do and do not do
What AWRA OpsHub does today
- Jobs as projects or tasks, carrying time entries, parts, expenses and status.
- Vans as stock locations with named custody and transfers in and out.
- Parts issued against a job, so they are costable and billable.
- Assets with service history, where you maintain customer or your own equipment.
- Mobile offline capture, so a job is recorded on site rather than from memory afterwards.
- Tickets for intake, including a tokenized portal so customers can log a request without an account.
What it does not do
- No dispatch board or scheduling optimiser. Who goes where, in what order, is decided by you — there is no map, no drag-and-drop schedule and no route optimisation.
- No technician skills matrix. Matching a job type to a qualified technician is your knowledge, not a system rule.
- No customer appointment notifications. Nothing tells a customer their technician is on the way.
- No live technician tracking. Location can be captured on records; there is no real-time view of where people are.
The dispatch gap is the significant one. If your business turns on a scheduling board with live status across twenty technicians, that is a dedicated field service platform and this becomes the costing, stock and asset layer beneath it. Under about ten technicians, most businesses schedule on a whiteboard or a group chat perfectly well and get more value from knowing what each job actually cost.
Our take
Measure the proportion of jobs needing a second visit — that single number will tell you more than your revenue report. Then fix it at intake, where two of the five causes live, treat each van as a counted stock location, and issue parts against the job at the job. The parts you are currently fitting and never billing are usually enough to pay for the discipline on their own.
See field operations support
Jobs carrying time, parts and expenses, vans as stock locations with custody, asset service history and offline capture on site.
Explore field operationsFrequently asked questions
What is the most useful field service metric?
The share of jobs requiring a second visit. It is rarely tracked and it decides profitability, because a return trip consumes a technician, a vehicle and a slot against a job whose price assumed one visit. Once you measure it, the causes turn out to be a short and repetitive list — and two of the most common are intake failures rather than field failures, which is not where most businesses look first.
How should parts on a van be handled?
As stock in a location with a named custodian, not as consumed the moment they leave the warehouse. Transfer to the van keeps the value visible, issuing a part against the job at the job makes it billable and costable, and a monthly count of twenty minutes per vehicle catches divergence early. Writing parts off to the van turns each vehicle into a black hole that eventually surfaces as unexplained shrinkage.
Do you provide a dispatch or scheduling board?
No — there is no dispatch board, no route optimisation, no skills matrix and no live technician tracking. Under roughly ten technicians most businesses schedule effectively on a whiteboard or a group chat, and the greater gap is not knowing what each job cost. Above that, a dedicated field service platform is warranted and this becomes the costing, stock and asset layer beneath it.
Why are parts fitted but never billed?
Because nothing recorded them against the job. The technician solves the problem, fits the component, and the invoice reflects labour only — the customer is not disputing the charge, nobody asked them to pay it. In most field service businesses this is a larger loss than parts going missing, and it is fixed by issuing the part against the job on site rather than reconstructing the week on Friday.
Should job history be attached to the customer or the equipment?
To the equipment, wherever you service machines rather than premises. A history on the asset — what has failed before, what was replaced, when it was last serviced — is what lets the next technician arrive prepared, and preparedness is the single biggest lever on the second-visit rate. Attaching everything to the customer works until they have three machines and the history becomes unreadable.
