Trade service businesses run two operations at once: a planned maintenance schedule that can be optimised weeks ahead, and an emergency response operation that destroys the plan daily. Software that handles only one of them fails.
The dual operation
| Planned | Emergency | |
|---|---|---|
| Scheduling horizon | Weeks | Hours |
| Duration predictability | Reasonable | Poor |
| Parts requirement | Known | Unknown |
| Route efficiency | Optimisable | Secondary to response time |
| Revenue per job | Lower, contracted | Higher, premium rates |
| Customer expectation | Convenience | Speed |
The operational skill is protecting enough capacity for emergencies without leaving technicians idle, and absorbing emergencies with minimal disruption to planned work.
Common structures:
- Dedicated emergency technicians — simple, and expensive if demand is variable
- Reserved capacity — a proportion of each technician's day held for reactive work
- Displacement rules — defined criteria for which planned jobs can be moved and how customers are informed
- Tiered response — emergency, urgent, routine, with different commitments and pricing
Without explicit displacement rules, every emergency displaces whichever planned job the dispatcher happens to pick, and the customers who get moved are effectively chosen at random.
First-time fix economics
The dominant metric. Each return visit costs a full visit against no additional revenue, plus a dissatisfied customer.
Causes of failure, in typical order:
- Parts not carried. The technician diagnosed correctly and could not complete.
- Diagnosis incorrect at the first visit, often from insufficient information at booking.
- Skills mismatch — the technician sent was not qualified for what was found.
- Access failure — could not reach the equipment, no key, occupant absent.
- Additional authorisation required and not obtainable on site.
Software levers for each:
- Parts prediction from job type, equipment model and site history, driving van stock
- Better booking information — equipment make, model, symptom, age, service history
- Skills matching in the scheduler, with equipment-specific competence
- Access information captured and displayed before the visit
- Mobile quoting and authorisation so work can be approved on site
Van stock
The parts on the vehicle determine first-time fix more than any other single factor.
- Standard van stock list by technician type, reviewed against actual usage
- Job-specific parts picked and loaded for planned work
- Van stock visibility to the scheduler, so jobs are assigned to technicians who carry what is needed
- Inter-technician transfers where a part is on another van
- Automatic replenishment from usage
- Parts usage analysis to refine the standard list quarterly
The standard list is frequently set once and never revisited, which means it reflects the equipment mix of several years ago.
Equipment and site history
Trade service is asset-centric: the customer has equipment with a history, and that history determines both the work and the commercial opportunity.
Requirements:
- Asset register per site: make, model, serial, installation date, warranty
- Full service history per asset
- Recurring maintenance schedules per asset, not per customer
- Warranty status visible at the point of quoting
- Replacement recommendation triggers from repair history and age
- Photographs of installations and access routes
The replacement trigger is commercially significant: a boiler or unit that has needed three repairs in eighteen months is a replacement sale, and identifying that automatically converts a service business into a sales pipeline.
Quoting and payment on site
- Mobile quoting with parts and labour pricing
- Customer approval captured digitally
- Variation handling when the job differs from the quote
- Payment on site — card or link
- Warranty and guarantee documentation issued immediately
- Follow-up work scheduled before leaving
Capturing payment or approval on site materially improves cash flow and conversion compared with office-generated quotes sent afterwards.
Common questions
How do we handle emergency calls without destroying the schedule?
Reserve explicit capacity, define displacement rules in advance, and communicate proactively with the customers who are moved. Capacity reserved for emergencies looks like idle time in a utilisation report — measure it as protected capacity rather than as inefficiency.
What first-time fix rate should we target?
It depends on trade and equipment complexity, so the useful goal is a rising trend and a shrinking dominant failure cause. Analyse failures by cause; the fix for a parts problem is different from the fix for a diagnosis problem.
How much stock should technicians carry?
Enough to cover the parts that appear most often in your actual job history, weighted by how expensive a return visit is. Derive the list from usage data and review it quarterly rather than inheriting it.
Should technicians do their own scheduling?
Experienced technicians handling stable planned work often schedule well, and it improves ownership. Where emergency work is significant, centralised dispatch handles the trade-offs better because it can see the whole picture.
Do we need field service software or will route planning do?
Field service software, in almost all cases. Skills matching, parts on the van, quoting, asset history and variable job duration are core to trade service and are absent or shallow in delivery routing products.
