Field Service KPIs: The 12 Metrics That Matter, and Which Software Can Actually Show Them

Every list ranking for “field service KPIs” was written by a software vendor or an ERP company, and every one stops at definitions. None of them answer the question an owner actually has: where does this number live in the software I already pay for?

Field service KPIs are the operating numbers that tell a home-service shop whether its crews, schedule, and cash are performing, not just whether everyone is busy. The unit of production in this business is a crew-day. The KPIs that matter are the ones that show whether each crew-day earned what it should.

We build reporting dashboards and integrations on Jobber, Housecall Pro, and ServiceTitan APIs. Clients have asked us for every number below. We know which ones the platforms hand you, and which ones we had to compute from raw records. That second column is this post. We are not affiliated with any of these platforms and take no referral fees.

The 12 KPIs and where they live

This is the matrix. “Out of the box” means a built-in report or dashboard shows the number. “Partial” means the pieces exist but the number itself needs assembly. “Not natively” means export plus spreadsheet math, or API work.

A note on how this table was filled in. It is conservative by design, checked against our own builds and platform documentation. Last verified 2026-08-14. Where we could not confirm a built-in report, the cell says “not natively” rather than guessing in the platform’s favor. If a platform ships a report we missed, the cell is wrong in the safe direction.

Count the cells. Out of 36, only about a quarter are a clean yes, and most of those belong to ServiceTitan, which is also the platform priced for shops much larger than 5 to 30 crews. That gap between “KPIs every article says to track” and “KPIs your software will show you” is exactly why the weekly export-and-spreadsheet ritual exists. We wrote up what Jobber can and cannot export separately.

Money coming in

1. Booked revenue is the dollar value of jobs sold in a period, whenever the work happens. It is your sales pulse: if booked revenue dies in September, your January is already decided.

2. Scheduled revenue is the dollar value sitting on the calendar ahead of you. Booked tells you sales worked; scheduled tells you whether that money has a date. A gap between the two is jobs sold but not slotted, which is where revenue quietly leaks.

3. Collected revenue is cash that actually arrived. Every platform is strongest here, because payments are where the software industry gets paid too. The trap is running the whole business on this number alone, because it describes the past.

4. Quote-to-book rate is the percentage of quotes sent that turned into booked jobs. It prices your sales process. A shop sending 60 quotes a month at 35 percent versus 45 percent is the difference of dozens of jobs a year, with zero extra marketing spend.

Crew output

5. Crew utilization is the share of available crew-days filled with revenue-producing work. This is the most important number in a full-day-install business and the one no platform will show you directly. An owner of a multi-crew install company put the problem to us like this:

“Just because we have eight crews doesn’t mean we’re doing eight jobs that day. Jobs one through four could take two crews each.”

Eight crews across five days is 40 crew-days. If 31 carried booked work, utilization was 78 percent, and the other nine crew-days were payroll with no revenue against it. No dashboard in the matrix above states that number for a multi-crew shop. Owners find it by clicking through the calendar day by day, which is exactly why they stop looking.

6. Jobs per crew per day is completed jobs divided by crew-days worked. For service trades running multiple stops a day, this is the throughput number. For full-day-install shops it hovers near 1.0, and the interesting signal is when it drops below: crews burning a day on callbacks or half-done jobs.

7. Callback rate is the percentage of completed jobs that required a return visit to fix something. It is your quality number, and it compounds: every callback consumes a crew-day that produces zero revenue and blocks a paying job. Tracking it requires tagging return visits consistently, which is a process decision before it is a software feature.

Cash and quality

8. Days-to-invoice is the average time from job completed to invoice sent. Pure discipline metric. Nobody’s customer pays an invoice that has not been sent, and in busy months this number stretches silently.

9. Days-to-paid is the average time from invoice sent to money received. Together with days-to-invoice it tells you how long your revenue sits as paper. Trimming the pair from three weeks toward one is often worth more than a point of price increase, and costs nothing.

10. Revenue per crew is collected revenue divided by number of crews, per month or quarter. It makes crews comparable and makes the “should we add a crew” decision arithmetic instead of vibes: a new crew makes sense when existing crews are near capacity at healthy revenue, not before.

11. Backlog weeks is scheduled work divided by weekly capacity: how many weeks you could run if sales stopped today. Under two weeks means crews may sit idle soon. Past six or eight, you are quoting lead times that lose jobs. No platform in the matrix shows it, and every owner we work with wants it.

12. Review rate is the percentage of completed jobs that produced a public review. Reviews are the highest-value output of a finished job besides the check, and the rate, not the count, tells you whether asking is part of the process or an afterthought.

Why the matrix looks like this

The pattern in the table is not an accident. Platforms are strongest exactly where the money touches them, collected revenue and payments, and weakest on cross-record math like revenue per crew or days-to-invoice, because those numbers require joining jobs to invoices to timesheets, and built-in reports ship one record type at a time.

ServiceTitan closes more cells because it sells custom reporting to enterprise shops, at enterprise cost. Jobber and Housecall Pro cover the basics and stop. And the two KPIs that matter most to a multi-crew install business, crew utilization and backlog weeks, are native nowhere.

So the honest options for a 5 to 30 crew shop are the same three as always: accept the export-and-spreadsheet ritual, upgrade platforms and pay for reporting depth you will partly use, or compute the KPIs from the platform’s API into a dashboard you own. That third path has real constraints worth reading before you commit: we measured a single KPI dashboard load at 13,456 to 20,762 query-cost points against Jobber’s 10,000 point rate budget, which forces a specific architecture. The numbers are in our production measurements of the Jobber API.

Building these dashboards is what we do. Our custom Jobber reports and KPI dashboards page covers reporting builds on Jobber, and custom software covers the same work on Housecall Pro, ServiceTitan, and whatever else your numbers live in. Or book a discovery call and bring the three KPIs you cannot get today. If your platform can already show them and you just need the report switched on, that answer is free.