In This Guide
- ✓Field Service KPI Definitions at a Glance
- ✓Set the Measurement Rules Before Reading the Numbers
- ✓1. Completed Jobs
- ✓2. Revenue per Technician
Answer first: Field service KPIs are useful only when every metric has a written formula, a fixed reporting window, and consistent inclusion rules. Start with job volume, revenue per completed job, technician utilization, first-time fix rate, cancellation rate, estimate conversion, and invoice timing. Compare your own trend over time before comparing your company with an industry benchmark.
This guide defines 12 practical field service KPIs, shows the denominator for each one, and uses an illustrative data set so the calculations can be checked. It does not present universal targets: plumbing, HVAC, cleaning, appliance repair, and commercial maintenance have different job lengths, margins, and repeat-service patterns.
Field Service KPI Definitions at a Glance
| KPI | Formula | Primary decision |
|---|---|---|
| Completed jobs | Count of jobs closed in the period | Capacity and demand |
| Revenue per technician | Recognized job revenue / active technicians | Team output |
| Average job value | Recognized job revenue / completed revenue-generating jobs | Pricing and job mix |
| Technician utilization | Billable field hours / available technician hours x 100 | Scheduling efficiency |
| First-time fix rate | Jobs resolved on first visit / eligible completed jobs x 100 | Diagnosis, skills, and parts |
| Jobs per technician-day | Completed jobs / technician-days worked | Daily capacity |
| Estimate conversion | Accepted estimates / decision-ready estimates x 100 | Sales follow-up and fit |
| Cancellation rate | Customer-cancelled appointments / booked appointments x 100 | Reminder and booking quality |
| Callback rate | Unplanned return visits tied to prior work / eligible completed jobs x 100 | Quality control |
| Days to invoice | Invoice-sent timestamp minus job-completed timestamp | Billing speed |
| Collection time | Paid timestamp minus invoice-sent timestamp | Cash flow |
| Repeat customer rate | Customers with another completed job / eligible customers x 100 | Retention |
Set the Measurement Rules Before Reading the Numbers
A KPI can move because the business improved, or because someone changed the definition. Write down these rules before building a dashboard:
- Reporting window. Use full weeks or calendar months and keep the timezone consistent.
- Job status. Decide which status means completed. Exclude drafts, duplicates, internal tests, and cancelled work.
- Revenue basis. Choose invoiced revenue, paid revenue, or recognized revenue. Do not mix them in one trend.
- Technician population. State whether owners, apprentices, subcontractors, and part-time staff count.
- Return-visit policy. Separate warranty callbacks from planned multi-visit work and new problems at the same address.
- Decision-ready estimates. Exclude open estimates that the customer has not had time to consider.
Keep a short metric dictionary beside the report. If a rule changes, mark the change date and avoid comparing the new series with the old one as though nothing changed.
1. Completed Jobs
Formula: count jobs that entered the agreed completed or closed status during the period.
Use this measure to understand throughput. Break it down by service type, territory, and technician only when the sample is large enough to be useful. A completed inspection and a full installation are both one job, so the count needs context from job value and labor hours.
Exclude test records, duplicate work orders, cancellations, and jobs that remain open. For multi-day work, count the job once at final completion unless your operating model treats each visit as a separate work order.
2. Revenue per Technician
Formula: recognized job revenue divided by the number of active technicians in the same period.
This metric helps compare output with staffing. A head-count denominator is simple but can hide part-time schedules. A more precise companion measure is revenue per technician-hour.
Do not attribute deposits twice. Decide how to handle subcontracted work, refunds, taxes, tips, membership revenue, and material-only sales. Document the choice and keep it stable.
3. Average Job Value
Formula: recognized job revenue divided by completed revenue-generating jobs.
Average job value can rise because prices improved, technicians presented a broader scope, or the job mix shifted toward larger work. Review the distribution as well as the average: one installation can distort a month of smaller repairs.
Segment by service category before acting. A falling average for diagnostic visits may be expected if the company is deliberately using them to create later estimates.
4. Technician Utilization
Formula: billable field hours divided by available technician hours, multiplied by 100.
Define available hours carefully. Start with scheduled working hours, then subtract approved leave and company closures. Decide whether training, vehicle loading, paid breaks, and meetings stay in the denominator. Billable hours should come from job time records under one consistent policy.
Utilization is not a quality score. Pushing it upward without watching callbacks, overtime, and customer delays can create a worse operation. Review it beside first-time fix rate and schedule adherence.
5. First-Time Fix Rate
Formula: eligible jobs resolved on the first visit divided by eligible completed jobs, multiplied by 100.
The hard part is defining eligible. Exclude planned inspections, quoted work awaiting approval, installations designed for several visits, and parts-dependent work that was identified as multi-visit before dispatch. Count an unplanned return connected to the original problem as a failure, even if a new work order was created.
Review failures by cause: incomplete intake, wrong skill assignment, unavailable part, inaccurate diagnosis, scope change, or customer decision. That cause list turns the KPI into an operational action.
6. Jobs per Technician-Day
Formula: completed jobs divided by technician-days worked.
Use this for similar short service calls, not as a universal productivity league table. A crew completing one replacement project may create more value than another completing several minor repairs. Segment by work type and pair the result with labor hours, revenue, and callback rate.
7. Estimate Conversion Rate
Formula: accepted estimates divided by estimates with a final decision, multiplied by 100.
Define the decision window. An estimate sent yesterday is usually open, not lost. Exclude duplicates, internal revisions that belong to one customer decision, and estimates the business withdrew because it could not perform the work.
Track conversion by lead source, service type, price band, and response time. Avoid comparing technicians until assignment rules and opportunity mix are reasonably similar.
8. Cancellation Rate
Formula: customer-cancelled appointments divided by booked appointments, multiplied by 100.
Separate customer cancellations, company cancellations, reschedules, and no-access visits. A reschedule should not automatically count as lost work if it is completed later. Track how far in advance the change occurred so the office can distinguish recoverable capacity from an empty same-day slot.
Connect scheduling, dispatching, invoicing, and configured phone answering. Start with a one-time allowance of 50 AI credits and no credit card; plan and phone limits apply.
Get Started Free9. Callback Rate
Formula: unplanned return visits related to prior work divided by eligible completed jobs, multiplied by 100.
Create a required link from the callback to the original job. Without that relationship, the report will miss returns recorded as new work orders. Exclude planned follow-ups and unrelated failures. Review the reason and resolution instead of treating every return as technician error.
10. Days to Invoice
Formula for each job: invoice sent timestamp minus job completion timestamp. Report the median and the 90th percentile as well as the average.
The median shows the normal process; the 90th percentile exposes the long tail. Segment jobs that require office review, purchase-order approval, or final documentation. The goal is to find workflow delays, not to force every complex commercial invoice into the same path as a residential service call.
11. Collection Time
Formula for each paid invoice: paid timestamp minus invoice sent timestamp.
Report unpaid invoices separately. Calculating only paid invoices can make collection look faster while old unpaid balances disappear from the measure. Pair collection time with accounts-receivable aging buckets and disputed invoice count.
12. Repeat Customer Rate
Formula: eligible customers who complete another job within the selected window divided by eligible customers from the starting cohort, multiplied by 100.
Choose a window that matches the trade. A weekly cleaning customer and a homeowner replacing equipment have different natural return cycles. Exclude duplicate customer records and merge households or commercial locations according to a documented rule.
Worked Example: One Week of Field Service Data
Assume an illustrative company records the following for one complete week:
- 48 booked appointments
- 4 customer cancellations and 44 completed jobs
- 36 jobs eligible for first-time fix measurement; 31 resolved on the first visit
- $13,200 in recognized job revenue
- 4 technicians working 40 available hours each
- 116 billable field hours
- 18 decision-ready estimates; 9 accepted
- 3 unplanned callbacks among 40 callback-eligible jobs
- invoice-send delays of 0, 0, 0, 1, and 4 days for a five-job sample
The calculations are:
- Cancellation rate = 4 / 48 = 8.3%
- Average job value = $13,200 / 44 = $300
- Revenue per technician = $13,200 / 4 = $3,300 for the week
- Utilization = 116 / 160 = 72.5%
- First-time fix rate = 31 / 36 = 86.1%
- Estimate conversion = 9 / 18 = 50%
- Callback rate = 3 / 40 = 7.5%
- Median days to invoice in the sample = 0 days; average = 1 day
These figures are examples, not Fixlify customer results or industry benchmarks. Their purpose is to make each denominator visible.
How to Build a KPI Review That Leads to Action
Start with three to five metrics tied to one current constraint. If schedule capacity is the problem, review utilization, drive time, jobs per technician-day, and cancellations. If cash is the problem, review days to invoice, collection time, aging, and disputed invoices.
For every metric, assign an owner and one follow-up question. A change in utilization might lead to a review of gaps between visits. A change in first-time fix rate might lead to a parts or intake audit. Keep the raw record links available so a manager can inspect the jobs behind the chart.
Compare four-week or monthly trends and annotate unusual events such as storms, holidays, price changes, a new dispatcher, or a major contract. Small samples can swing sharply; display the numerator and denominator beside every percentage.
Using Fixlify Data for KPI Reporting
Fixlify connects customer, request, job, estimate, and invoice records in one workspace. Use its reporting and analytics views to review the records available in your account, and confirm which metrics are shown directly versus calculated after export. Do not assume that every formula in this guide is a native dashboard tile.
A practical setup is to standardize job statuses, require completion timestamps, link returns to the original job, and review a small sample for data quality. Then export or report on the same definitions each period. See the separate field service KPI dashboard guide for dashboard design, and the field service management software guide for platform selection.
Frequently Asked Questions
What is the most important field service KPI?
There is no universal single KPI. Choose the metric closest to the current constraint: utilization for unused capacity, first-time fix and callbacks for quality, estimate conversion for sales, or invoice and collection timing for cash flow.
How many KPIs should a small service business track?
Start with three to five metrics that someone will review and act on. Add another metric only when its definition, data owner, and decision are clear.
Should I use industry KPI benchmarks?
Use benchmarks only when the source explains its sample, trade, geography, company size, period, and formula. Your own consistent trend is usually safer for operational decisions than an unattributed number from a software article.
Can field service software calculate every KPI automatically?
It depends on the product and the quality of the underlying records. Some measures may appear in a dashboard; others require an export or calculation. Confirm the exact report, fields, filters, and denominator during a trial.
How often should KPIs be reviewed?
Operational measures can be reviewed weekly; finance and retention measures often need a monthly or cohort-based window. Use a period long enough to reduce noise while still allowing the team to act.