Introduction
Most field service dashboards have between thirty and two hundred metrics on them. Almost all of the operational outcome variance, in practice, comes from a much smaller set — usually six to eight. Operations leaders who instrument those six to eight well, watch them daily, and act on them quickly outperform organizations with more metrics and worse focus by a wide and consistent margin.
This article is about that core set: which KPIs actually predict outcomes, how they relate to each other, where they get conflated, and what each one is sensitive to. It is intended for VPs of Operations, dispatch leaders, and finance partners who are tired of dashboards that show everything and tell them nothing.
Technician utilization
Technician utilization is the percentage of the technician's paid shift spent on productive work — driving to a customer, on-site at a customer, completing the job in the customer's home or facility. Idle time, excess driving time, depot time, administrative time, and re-work time all subtract from utilization. Mature operations report utilization in the 65–80 percent range; below 60 percent is a sign of dispatch inefficiency, above 85 percent is a sign of an overstretched workforce that will leak quality.
Utilization is the single most useful operational metric because almost every other operational lever moves through it. Better routing improves utilization; better scheduling improves utilization; better mobile UX improves utilization; better parts inventory improves utilization (fewer return trips). The KPI is sensitive to definition — operations that include driving time as productive will see higher numbers than those that exclude it — so the dashboard has to publish the formula alongside the number, and the executive review should always compare against the same formula.
First-time fix rate
First-time fix rate is the percentage of customer-reported issues resolved completely on the first technician visit, with no follow-up visit required. It is the headline customer-experience KPI: a customer whose problem is solved on the first visit reports dramatically higher CSAT, generates fewer escalation tickets, and is materially more likely to renew the service contract. Mature operations target 80–90 percent for routine work, with lower targets for complex equipment categories where parts diagnosis is a known constraint.
First-time fix is sensitive to four upstream inputs: diagnosis quality on the inbound call (was the issue characterized accurately), skill match (did the right technician arrive), parts availability (did the technician have the right parts), and authority (was the technician allowed to make the necessary decisions on-site). Operations that focus on first-time fix without fixing the upstream inputs will see the number stick at its current level; operations that address the upstream inputs move first-time fix consistently.
SLA compliance
SLA compliance is the percentage of jobs that meet the contractual or regulatory time-to-arrive or time-to-resolve commitment for their priority class. For B2B and regulated operations, this is the most consequential KPI on the dashboard — missed SLAs translate directly into financial penalties, regulator findings, or contract risk. Mature operations track SLA compliance per priority class (P1, P2, P3) because the policy and the financial exposure differ across classes.
The right way to instrument SLA compliance is to publish two numbers: the topline percentage achieved and the breakdown of the misses by cause. The cause taxonomy should be small (typically: capacity, dispatch decision, parts, customer-not-home, third-party delay) so the operations team can act on the leading source of misses week over week. SLA dashboards that publish only the topline percentage without the breakdown tell the operator what is happening but not why, which limits what they can do about it.
Jobs per technician per day
Jobs per technician per day is the throughput KPI: how many completed visits does the average technician deliver in a productive shift. The number is highly category-dependent (residential pest control might be eight visits a day, a complex industrial repair might be one) so the right benchmark is always against the operation's own historical trend and against peer operations in the same vertical, not against generic industry averages.
The metric is most useful as a leading indicator. A sudden drop in jobs-per-day points to dispatch inefficiency, technician productivity issues, scope-creep on visits, or seasonal demand-supply imbalance. The metric is least useful as a target — pushing jobs-per-day up by squeezing visit times degrades first-time fix and CSAT in ways that compound badly. The right framing is: optimize for first-time fix and CSAT, watch jobs-per-day as the leading indicator of dispatch and routing health.
Customer satisfaction and NPS
Customer satisfaction (CSAT) for the individual visit and Net Promoter Score (NPS) for the relationship overall are the two outcome KPIs that field service operations should track religiously. Per-visit CSAT is captured via the post-visit survey (ideally on WhatsApp for LATAM operations, with a single-tap rating and an optional one-line comment), and rolls up to the operations dashboard the same day. NPS is captured less frequently — quarterly, sometimes semi-annually — and reflects the cumulative customer relationship across all touchpoints, not just the field service interaction.
Both metrics are sensitive to capture rate. CSAT scores from a 10-percent response rate are almost meaningless; CSAT scores from a 60-percent response rate are highly directional. WhatsApp-based capture typically drives response rates two to three times above email or SMS in LATAM. The operations team should target a minimum response rate (50 percent or above for CSAT, 30 percent or above for NPS) before treating the topline number as decision-grade.
Contractor health (for blended operations)
For operations with mixed employed-and-contracted workforces, contractor health is a distinct KPI from employee technician health, and it deserves its own dashboard panel. The components are: average jobs-per-day per contractor, first-time fix rate per contractor, CSAT per contractor, on-time arrival per contractor, document-and-certification currency, and acceptance-rate of dispatched jobs. Each component should be tracked at the contractor population level (cohort, geography) and at the individual contractor level for performance management.
The single most-leveraged contractor-health metric is acceptance rate — the percentage of dispatched jobs the contractor accepts versus declines. A drop in acceptance rate is a leading indicator of contractor disengagement, rate-misalignment with the market, or a competing platform pulling capacity away. Operations that watch acceptance rate weekly can intervene early; operations that watch only the topline contractor cost find out about disengagement when capacity vanishes during a peak demand window.
Unit cost per completed job
Unit cost per completed job is the finance partner's view of operational health. The numerator is the fully-loaded operational cost of the field service organization (labor, contractor payouts, vehicle and fleet, parts shrinkage, mobile and platform tooling, dispatch and back-office); the denominator is the count of completed jobs in the same period. The number is rarely meaningful in isolation, but the trend line is very meaningful — operations whose unit cost is trending down quarter over quarter are improving; operations whose unit cost is trending up are not.
Unit cost is the metric that connects field operations to the P&L most directly, and it is the metric the CFO will ask about. Operations leaders who can break down the unit-cost trend into its underlying drivers (labor productivity, contractor rate movement, parts cost movement, vehicle cost) are equipped for productive finance conversations; operations leaders who can only quote the topline number are not. The right design is a unit-cost panel that publishes the trend, the drivers, and the projection for the next two quarters under current conditions.
Cycle time from lead to invoice
Cycle time from lead to invoice is the underappreciated KPI that captures end-to-end operational excellence. The clock starts when the customer issue or order arrives (a service request, a quoted job accepted, an inbound case) and stops when the invoice for the work is issued to the customer. For service operations where payment is collected at the visit, the cycle is the same window. For B2B operations where the invoice closes a multi-step engagement, the cycle can stretch across weeks.
Shortening the cycle drives cash flow and reduces dispute risk. The longer the gap between work delivered and invoice issued, the higher the dispute rate, the slower the collection, and the more working capital the operation has tied up. Operations that target cycle-time improvement consistently see compounding gains: faster scheduling, faster work-order closure, faster invoicing, faster collection — each step compresses the cycle and improves the operation's economics. The KPI is sensitive to mobile UX (slow closure flows lengthen the cycle), to e-invoicing readiness (manual back-office invoice generation lengthens it), and to payment-rail integration (delayed reconciliation lengthens it).
KPIs that look important but rarely move outcomes
Several metrics that appear on field service dashboards do not, in practice, move outcomes. Total dispatcher count is one — the right number depends on dispatch-platform efficiency, not headcount targets. Average call-handling time in the contact center is another — it conflates throughput with quality and incentivizes the wrong behavior. Total work-order count without a completion qualifier is a third — work orders that linger open for weeks are not the same as completed jobs and should not be counted together.
Another category is metrics that are interesting but lagging. Annual technician retention is meaningful at the strategy level but useless for weekly operational decisions. Customer lifetime value is meaningful for finance but operates on a horizon that does not match field-operations decision cadence. The right design is to publish lagging metrics on a quarterly cadence (CLV, retention, NPS trends) and leading metrics on a weekly cadence (utilization, first-time fix, SLA compliance, acceptance rate, CSAT). Mixing them on the same dashboard at the same cadence creates noise.
How to wire these into a weekly operational rhythm
The mechanical pattern that works is a thirty-minute weekly operations review with a fixed agenda. The agenda walks through the eight core KPIs in order, with each metric showing this week, last week, four-week trend, and the leading driver of any movement. The operations leader runs the meeting, the dispatch lead and the area managers report on their domains, the finance partner attends to keep the unit-cost conversation honest, and a single action list comes out of the meeting with owners and due dates.
The discipline that separates effective operational rhythms from theatrical ones is the action loop. Each weekly meeting closes the previous week's actions, opens this week's actions, and stamps each open action with an owner and a deadline. Operations that publish dashboards but do not close action loops see the same problems recur for quarters. Operations that close action loops weekly see the underlying drivers improve quarter over quarter, even when the dashboard design is otherwise unremarkable.