
Service businesses often know their revenue per job well, but few know what each job really costs. Yet margins in field service are decided by small inefficiencies multiplied across thousands of visits: twenty extra minutes of travel, a second trip because a part was missing, an hour spent typing up reports. Understanding and reducing cost per job is one of the most reliable ways to grow profit without raising prices.
What makes up cost per job
- Technician time on site — the productive work itself.
- Travel time and distance — between base, sites and suppliers.
- Idle time — waiting for assignments, access, parts or approvals.
- Repeat visits — return trips for the same issue.
- Parts and consumables — including wastage and unrecorded usage.
- Vehicle costs — fuel, maintenance, depreciation.
- Admin — logging, scheduling, report typing, invoicing, chasing payments.
- Overtime — often caused by poor scheduling rather than real demand.
Measuring it
Start simple. For one month, calculate total technician cost, vehicle cost, parts cost and office cost, and divide by jobs completed. Then break it down by job type — installation, breakdown, PM visit — because averages hide big differences. Once job time, travel and parts are captured in software, these figures can be calculated automatically every month.
Reducing travel
Assign technicians to zones, schedule jobs in geographic clusters, and give dispatchers a map view of open jobs and technician locations. Schedule PM visits for nearby sites on the same day. Starting technicians from home rather than the office can save an hour a day in large cities. See scheduling and dispatch.
Reducing repeat visits
Repeat visits double the cost of a job and annoy customers. The main causes are missing parts, missing information and skill gaps. Capture the fault, model and photos at booking; match technician skills to job types; and stock vans with the parts most often needed. See improving first-time fix.
Reducing idle time
Idle time hides in waiting: for the next assignment, for site access, for approvals on quotes. Publish next-day schedules in the evening, confirm appointments with customers the day before, and give supervisors mobile approval of quotes and parts issues so technicians aren't waiting on a phone call.
Controlling parts cost
Record every part used against the job, from van stock or the store. Reconcile van stock regularly. Track parts usage by job type and technician to spot unusual consumption. Use approved alternates where acceptable, and agree supply terms on high-volume items.
Cutting admin
When technicians complete digital reports on site with photos and signatures, nobody types reports in the office. Invoices can be generated at job completion, payment links sent automatically and customer updates triggered by job status. Admin hours per job often fall by more than half.
Reducing overtime
Look at when and why overtime happens. If it's caused by late assignments, long travel or jobs overrunning, scheduling and job time estimates can fix much of it. If it's genuine demand at certain times, plan shifts or temporary capacity instead.
Don't cut the wrong things
Reducing time on site by rushing checklists, skipping PM steps or using cheaper parts lowers cost briefly and raises breakdowns, complaints and repeat visits later. Focus on waste, not on the work customers value.
Common mistakes
- Looking only at total cost, not cost per job by type.
- Ignoring travel and idle time because they are "normal".
- Treating repeat visits as free because the customer isn't charged.
- Not recording parts used on the job.
How software helps
Field service software records time, travel, parts and outcomes on every job, so cost per job by type, technician, customer and branch becomes visible. With that data, scheduling, stocking and pricing decisions improve steadily. See field service management software.
Talk to us about measuring and reducing your cost per job.
An example: finding an extra job per day
An appliance repair company with sixty technicians in two cities averaged just under four jobs per technician per day. When it started capturing job start, finish and travel from the technician app, the breakdown surprised everyone: technicians spent nearly as long travelling and waiting as working. Jobs were assigned one at a time by phone, technicians often crossed the city between consecutive jobs, and roughly one in six visits ended with "part to be ordered", followed by a second trip. The company introduced zones, published next-day schedules each evening grouped by area, and asked call centre agents to capture the model number and a photo of the fault at booking so parts could be checked before the visit. It also increased van stock of the twenty most-used parts. Within a quarter, jobs per technician per day rose by about one, repeat visits fell and overtime almost disappeared — with the same team and no price increase.
Cost per job by job type
Averages hide the story. An installation, a breakdown visit and a PM visit have very different cost profiles. Calculate cost per job by type, then compare with the revenue each type brings — whether charged directly or covered by a contract. Some job types will turn out to be consistently under-priced; others subsidise the business. That insight shapes pricing, contract terms and where to focus improvement.
Getting started
For one month, capture job start and end times, travel, parts used and outcome (fixed or return visit needed) on every job. Calculate cost per job by type and identify the biggest waste: travel, idle time, repeat visits or admin. Fix the largest one first, measure again after a month, then move to the next.
Frequently asked questions
How do we calculate cost per job?
Add technician cost (time on job plus travel), vehicle and fuel, parts and consumables, and a share of office overhead, then divide by jobs completed. Calculate it by job type for useful comparisons.
What is usually the biggest cost driver?
For most service businesses, technician time — including travel and idle time — is the largest cost, followed by repeat visits and parts.
Does reducing travel really matter?
Yes. Travel is unpaid time in most service models. Better zoning and scheduling can add one or more jobs per technician per day.
Will cutting cost hurt customer service?
Not if you focus on waste — repeat visits, idle time, admin — rather than cutting time on site. Usually service improves too.
Can software show cost per job automatically?
Yes, if time, travel, parts and job types are captured in the system. Overheads can be allocated by simple rules.
