Service history is the record of all past work at a customer, site or piece of equipment: each visit's date, technician, problem found, work done, parts used and outcome. It is built from completed work orders.
It answers the question a technician should ask before every visit: what has already happened here?
How to measure service history
A history is only useful if the records are complete. Check a sample:
Record completeness = Completed work orders with problem, work done and parts filled in ÷ Completed work orders sampled
Say you pull 50 work orders from last month and 34 record the problem found, the work done and the parts used. Completeness is 34 ÷ 50, or 68%. The other 16 visits added a date to the history and little else.
A second check is linkage: what share of visits are tied to a specific piece of equipment rather than just an address. That depends on your asset management records.
Why it matters
Service history changes what happens before the truck leaves. If the dispatcher can see that the same unit was serviced twice in three months for the same symptom, they can send a senior technician, bring the likely part and book more time. That raises first-time fix rate and cuts return trips.
It also helps on site. A technician who knows what was tried last time doesn't repeat it. They can see warranty dates, previous recommendations the customer declined and access notes, such as a gate code location or a dog in the yard.
For the customer, a clear history is part of good service. Being able to say "we replaced that part in March" builds trust. The customer communication guide covers using history in conversations with customers.
It also feeds the numbers. Mean time between failures, callback tracking and warranty claims all depend on visits linked to the right site and unit.
A common mistake
Free-text notes only. "Checked unit, all good" tells the next technician nothing. Require a few structured fields, such as problem category, work done and parts used, with notes for the rest.
Related terms
- Work order is each entry in the history.
- Asset management ties the history to specific equipment.
- Callback rate is easier to measure with a complete history.
Common questions
What should a service history include?
For each visit: date, technician, reported problem, problem found, work done, parts used, recommendations made and whether the issue was resolved. Photos help.
How far back should service history go?
As far as you have reliable records. For equipment, the full life of the unit is most useful. Older records matter less for scheduling but help with warranty and replacement decisions.
Should customers see their service history?
Many companies share it on request or with each invoice. It shows the value of a maintenance agreement and helps the customer when selling the property.