Most field service business owners have a rough sense of what’s happening in their operation. They know which engineers are busiest, which customers call most often, and whether the phone seems to be ringing more or less than usual. The problem is that instinct only gets you so far.
As a business grows, gut feel becomes less reliable. Small inefficiencies that were once easy to spot start hiding in the day-to-day workload. Callback rates creep up. Invoices take longer to get paid. Engineers spend more time travelling and less time on billable work. Profitability starts slipping, but it’s not always obvious why.
The businesses that stay ahead of these problems don’t necessarily have more data. They simply know which numbers matter and review them consistently. The right metrics can reveal issues long before they become expensive, highlight opportunities for improvement, and give you a clearer picture of what’s really driving performance.
In this guide, we’ll explain the difference between metrics and KPIs, look at the numbers field service businesses should be tracking, and show how to turn operational data into better decisions.
Table of Contents:
- Metrics vs KPIs
- How many metrics should you track?
- Lagging vs leading indicators
- The core metrics: by category
- The operational metrics most businesses miss
- How to start tracking if you currently track nothing
- Data only matters when you act on it
- Managing metrics in Fieldmotion
- FAQs
Fieldmotion Brochure
See how Fieldmotion helps field service teams manage jobs, schedule staff, create invoices, and communicate with customers — all from one easy-to-use system.
Metrics vs KPIs
The terms are used interchangeably in most conversations, but they mean different things.
A metric is any measurable data point from your operations: number of jobs completed this week, average drive time per engineer, number of invoices outstanding. Metrics are the raw measurements of what is happening.
KPIs (key performance indicators) are metrics selected because they directly connect to a business goal. First-time fix rate is a KPI because fixing jobs on the first visit reduces costs and affects customer retention. Average drive time per engineer might be a metric you track without it rising to the level of a KPI, or it might be central to your business if fuel costs are eating your margins.
The distinction matters because KPIs deserve a review cadence, a target, and someone accountable for them. Metrics can be tracked passively. Treating everything as a KPI is how dashboards end up full of numbers nobody acts on.
How many metrics should you track?
This question comes up more than almost any other in field service management discussions, and there is a clear answer from people who have worked with hundreds of service businesses: somewhere between four and seven KPIs is the right number for most operations.
Fewer than four and you are likely missing something important. More than ten and you are creating a reporting exercise rather than a management tool. As the Field Service News analysis put it, too many KPIs and you cannot see the wood for the trees. A business tracking fifteen metrics at once is probably giving serious attention to none of them.
Choose your KPIs the way a doctor chooses a treatment: after evaluating the patient, not from a standard list. The metrics that matter for a six-engineer heating maintenance business are different from those that matter for a thirty-engineer multi-trade contractor doing commercial work. Start with the goals you care most about: reducing callbacks, improving cash flow, growing revenue. Work backwards to the numbers that tell you whether you are heading in the right direction.
Lagging vs leading indicators
Before getting into specific metrics, this distinction is worth understanding because it changes how you use what you track.
A lagging indicator tells you what has already happened. Customer satisfaction scores, revenue for the month, total jobs completed: these are retrospective. They are useful for understanding past performance and spotting trends, but by the time you see a problem in a lagging indicator, the problem has already happened.
Leading indicators tell you what is likely to happen if you do not act. A rising mean time to repair is a leading indicator of growing customer dissatisfaction and potential contract penalties. A declining first-time fix rate is a leading indicator of increasing costs and eroding customer confidence. Travel time per engineer gradually creeping up is a leading indicator of utilisation problems.
Most businesses only track lagging indicators. The more useful habit is to identify the leading indicators specific to your business, and to watch those as closely as the retrospective ones.
The core metrics: by category
Job completion quality
First-time fix rate (FTFR)
First-time fix rate measures the percentage of jobs completed on the first visit without a return trip. It is the single metric most closely tied to the financial and operational health of a field service business.
According to the Aquant 2024 Field Service Benchmark Report, the median FTFR across field service industries is 71.9%. The top 20% of organisations achieve 76% or above. Companies with FTFR above 70% retain 86% of their customers annually; those below 70% retain 76%. A ten-point difference in FTFR corresponds to a ten-point difference in customer retention and a measurable difference in service revenue growth.
A slipping FTFR nearly always points to an upstream issue: jobs arriving at engineers without enough information, parts not on the van, diagnostic work being rushed at the scheduling stage, or too many jobs packed into a day with not enough preparation time. The 10 metrics guide covers what to look for when first-time fix starts trending down.
Repeat visits and rework rate
Repeat visits are the visible symptom. Rework rate captures a slightly different thing: jobs that needed to be redone because the original work was inadequate. Both are expensive. Every repeat visit consumes a slot in the engineer’s diary, adds travel cost, and tells the customer something they would rather not conclude.
Track repeat visits by engineer, by job type, and by asset or equipment type. An engineer returning to 30% of jobs while others average 10% is a training issue. A specific boiler model generating repeat visits across multiple engineers is an information or parts problem. Aggregate data cannot answer these questions. Job-level data can.
Mean time to repair (MTTR)
Mean time to repair measures how long it takes from when a job is logged to when the problem is resolved. Shorter is better, but the more important use of MTTR is trend analysis: is it getting longer? And if so, where in the process is time being added?
Workforce efficiency
Technician utilisation rate
Utilisation rate measures how much of each engineer’s working day is spent on billable work, as opposed to travel, admin, waiting, or unavailability. Industry benchmarks put a healthy utilisation rate between 60% and 80%.
Rates below 60% typically indicate a scheduling problem, excess travel, or time absorbed by administration. Rates consistently above 85% are not necessarily good news. They can indicate engineers are being overloaded, which tends to manifest in declining FTFR and higher rework.
Tracking utilisation by engineer reveals variations that aggregate data hides. One engineer at 45% while others sit at 75% is a scheduling problem. A whole team dropping from 70% to 55% over three months is something structural.
Travel time per job
Travel is non-billable. It costs fuel, engineer time, and vehicle wear. A team spending 35% of their working day in transit is a team that cannot take on the jobs it otherwise could.
Track travel time per job and per engineer. Look for patterns: are certain geographic areas consistently generating high travel time? Are engineers being dispatched in ways that create unnecessarily long routes? Would smarter scheduling (grouping nearby jobs, assigning engineers based on current location) move that number?
Schedule adherence
Schedule adherence measures how closely actual job timing matches the schedule. Jobs consistently starting late, running over, or being moved on the day indicate either poor job information at the planning stage, unrealistic scheduling, or problems with how jobs are being prepared and communicated to engineers.
Financial health
Jobs completed vs jobs invoiced
Jobs completed vs jobs invoiced reveals one of the most common revenue leakage points in field service: the gap between work completed and work billed. A job completed on Tuesday that doesn’t get invoiced until the following Monday has created a cash flow delay for no good reason. A job that falls through the cracks entirely (completed but never invoiced) is simply lost revenue.
According to industry research, businesses that invoice within 24 hours of job completion collect payment faster and have fewer invoice disputes, because the detail of what was done is still fresh. Every day between job completion and invoice creation is a day of unnecessary exposure.
Days sales outstanding (DSO)
Days sales outstanding measures the average time between raising an invoice and receiving payment. Cash is the oxygen of any service business, and DSO is one of the clearest measures of cash flow health. A business with strong revenue but high DSO is a business that is owed a lot of money and may still be under cash pressure.
Reducing DSO typically comes from invoicing promptly, providing clear invoices that customers can approve without querying, and having a follow-up process for overdue accounts. The late payments guide covers the practical steps.
Cost per job / cost to serve
Cost per job brings together labour, travel, parts, and overhead to give the actual cost of delivering a job. Without it, you cannot know whether a job type is profitable. You can only know whether it generates revenue.
A business that has tracked cost per job for six months often finds that certain job types or certain clients cost considerably more to serve than others. Not because they are difficult, but because they require more travel, more preparation, or more follow-up. That information changes decisions about how to price work and which work to prioritise. The job costing guide goes into this in full.
Billable vs non-billable time ratio
Closely related to utilisation, the billable ratio breaks engineer time into revenue-generating and non-revenue-generating time. Admin, toolbox talks, depot time, training: all legitimate, but all non-billable. Understanding the ratio over time tells you whether admin burden is growing, whether training is pulling engineers off revenue work in unsustainable ways, or whether certain job types are generating more non-billable wrap time than expected.
Customer experience
Customer satisfaction score (CSAT)
CSAT captures customer experience at the job level, typically a simple rating collected immediately after the visit. The timing matters: satisfaction data gathered within 24 hours of job completion is far more reliable than surveys sent weeks later when the memory has faded. A short, frictionless rating mechanism sent the same evening as the invoice generates response rates and useful data that lengthy surveys do not.
Track CSAT by engineer as well as in aggregate. If one engineer consistently scores 4.8 and another consistently scores 3.2, that is a coaching conversation. If the business average drops by half a point over three months, something upstream has changed.
Net Promoter Score (NPS)
Where CSAT measures satisfaction with a specific job, NPS measures overall loyalty: how likely a customer is to recommend you to a colleague or contact. NPS is a lagging indicator by nature, but it captures something CSAT misses: the cumulative impression of the relationship over time.
Commercial contract businesses should give NPS particular attention. A contract coming up for renewal from a customer sitting at 6/10 is a renewal at risk. One sitting at 9/10 is a retention conversation, not a competitive negotiation.
SLA compliance rate
For businesses with service level agreements (response time commitments, completion deadlines, uptime guarantees), SLA compliance is both a customer metric and a financial one. Missed SLAs can trigger penalty clauses, and a consistent pattern of SLA breaches puts contracts at risk. Track compliance at the contract level, not just in aggregate, to catch problems before clients raise them.
Response time
How quickly enquiries are acknowledged and converted to booked jobs is one of the most studied metrics in field service. The Fieldmotion speed-to-lead research shows that response within five minutes increases enquiry conversion by up to 100 times compared to a 30-minute delay. Response time is a leading indicator of conversion rate, and conversion rate is one of the most impactful numbers in the business.
The operational metrics most businesses miss
There is a category of metrics that experienced field service operators track that most smaller businesses have not yet considered. These are not glamorous, but they have a disproportionate impact on revenue and operational efficiency.
Jobs arriving on time, not only the first
An operator with a large HVAC contracting business made an observation that applies across field service: the only job you can guarantee arrives on time is the first one of the day. Track on-time arrival rate across the day, not just for the morning slot. If engineers are consistently late to afternoon and evening jobs because the morning ran over, the scheduling model needs adjusting.
Cancellation rate by engineer
Most businesses track cancellations as a total number. The more revealing cut is cancellations per engineer, because the variation is usually much larger than expected. An engineer with a 17% cancellation rate on booked work is a fundamentally different problem from one at 3%, and the cause is different too. One might be a communication issue, another a travel time problem, another a scheduling mismatch. The aggregate hides all of this.
Quote conversion rate and time-to-quote
For engineers who generate quotes from work identified during visits, track both approval rate and how long it takes to get the quotes out. Quote approval rate drops sharply with every day of delay. A quote sent within 24 hours of the visit has a materially higher conversion rate than one sent five days later, because the customer’s recollection of the problem, and their motivation to act, fades.
Pull-through revenue rate
Pull-through is the additional work identified and quoted during a planned or reactive visit. An engineer who services a boiler and notices the pressure relief valve is worn, documents it, and generates a quote has created pull-through revenue opportunity. Track what proportion of your visits generate a pull-through quote, and what proportion of those convert. This is one of the least-tracked but most valuable metrics in field service, particularly for businesses running PPM contracts. The service agreements guide covers how to build this into contract structures.
How to start tracking if you currently track nothing
The most common mistake is trying to track everything at once. The second most common is building a dashboard that nobody looks at because the data takes too long to compile.
A better approach, used by operators across the industry, is to start with one or two metrics, establish a baseline, set a target, and review weekly. Once those become routine, add the next layer.
Step one: pick the metric most tied to your current biggest problem. If callbacks are your most visible issue, start with first-time fix rate. If cash flow is tight, start with days sales outstanding and jobs completed vs invoiced. If you feel like the business is busy but not profitable, start with cost per job.
Step two: establish a baseline. You cannot improve what you have not measured. Your first month of data is not a result. It is a starting point. Avoid the temptation to act on the first number you see. Look for patterns over four to six weeks before drawing conclusions.
Step three: set a target, not a ceiling. Targets should be specific and time-bound. “Improve first-time fix rate from 65% to 72% by the end of Q3” is a target. “Get better at fixing things first time” is not.
Step four: review regularly and act on what you find. A weekly or fortnightly look at key metrics, in a brief team discussion, is more valuable than a monthly deep-dive that nobody has time to prepare for. The goal is not a reporting exercise. It is a habit of visibility.
Data only matters when you act on it
There is a trap in field service businesses that have started tracking metrics: dashboards full of numbers that look impressive but do not change decisions. Tracking first-time fix rate to four decimal places is less useful than tracking it to the nearest percent and using it to have one coaching conversation a week.
An owner of a 25-year-old plumbing and HVAC business who introduced real-time dashboards to his operation described spending an hour each morning, across his entire management team, compiling data manually before every huddle. When the dashboards went live and data updated automatically, the first thing he noticed was not the time saved. It was that people started caring about numbers that had previously meant nothing to them, because they could now see them moving in real time.
As he put it: the data was already there. It just was not in a form anyone could use.
Making metrics visible, keeping them simple, and connecting them to conversations is more valuable than any dashboard. Not reports that go into inboxes and get skimmed. Conversations about why a number moved and what to do about it.
Managing metrics in Fieldmotion
The metrics above are only as good as the job data behind them. If jobs are being classified incorrectly, materials are not being recorded against visits, or engineers are completing jobs without logging finish times, the numbers that come out are unreliable. As more than one experienced operator has put it: garbage in, garbage out.
Fieldmotion’s reports and dashboards pull from the same job records engineers complete on site, so the data reflects what actually happened rather than what someone remembered to enter later. Jobs completed, parts used, travel time, invoice status, and engineer activity are all captured as part of the normal workflow rather than as a separate reporting exercise.
The mobile app captures completion data on site, in real time, without engineers needing to call the office or fill in paper records later. The job management platform connects those job records to scheduling, invoicing, and customer history, so when you pull a report on first-time fix rate or DSO, the numbers are built from a complete picture of each job rather than fragments from different systems.
For more on using data strategically as you grow, the field service data and strategic insights guide goes deeper into benchmarks and what the numbers mean at different stages of growth.
Book Your Free Demo
Discover how our job management software can streamline your operations, reduce paperwork, and keep your field teams on track.
FAQs
What is the difference between a field service metric and a KPI?
A metric is any measurable data point from your operations. A KPI is a metric that has been deliberately chosen because it connects to a business goal you are actively managing. First-time fix rate is a KPI for most field service businesses. The number of invoices raised on a Tuesday might be a metric worth tracking without being a KPI. The distinction matters because KPIs need targets, review cadences, and accountability. Metrics can be tracked passively.
How many KPIs should a field service business track?
Between four and seven is the range most experienced field service operators settle on. Fewer than four and you are likely missing something important; more than ten and you create a reporting exercise rather than a management tool. Start with the metrics most closely tied to your current biggest operational problem, establish a baseline, then expand from there.
What is first-time fix rate and why does it matter?
First-time fix rate (FTFR) measures the percentage of jobs completed on the first visit without a return trip. It is the single metric most closely tied to operational and financial health in field service: connected to customer retention, engineer efficiency, parts management, and scheduling quality. The industry median is around 71.9% (Aquant, 2024). Businesses above 70% retain considerably more customers than those below it.
What is the difference between lagging and leading indicators?
Lagging indicators tell you what has already happened: customer satisfaction scores, revenue, jobs completed. Leading indicators tell you what is likely to happen if you do not act. A rising mean time to repair signals future customer dissatisfaction before it shows in CSAT. Most businesses only track lagging indicators. The more useful habit is to identify the leading indicators specific to your business and watch those as closely as the retrospective ones.
What field service metrics should I track first?
Start with the metric most tied to your current biggest problem. If callbacks are your most visible issue, start with first-time fix rate. If cash flow is tight, start with days sales outstanding and jobs completed vs invoiced. If the business feels busy but margins are thin, start with cost per job. Trying to track everything at once is the most common mistake. It creates dashboards that nobody acts on.
What is days sales outstanding in field service?
Days sales outstanding (DSO) measures the average time between raising an invoice and receiving payment. A high DSO means the business is owed a lot of money and cash is under pressure even if revenue looks healthy. Reducing DSO typically involves invoicing promptly after job completion, providing clear invoices with full job details, and following up systematically on overdue accounts.
Related reading
- 10 metrics every growing field service business should track — a deeper look at the ten specific metrics that matter most during growth
- What your field service data is actually telling you — using operational data strategically, with industry benchmarks
- Job costing software — tracking actual costs against every job to understand true profitability
- Field service enquiry response time — the data on why speed of response matters more than most businesses realise
- What field service customers expect in 2026 — the customer side of the metrics picture
- Service agreements in field service — how PPM contracts change your metrics picture
