Field service reporting is the routine of turning job records into a small set of KPIs, reviewed on a fixed schedule, that tell you whether your crews are productive, your customers are served on time and your jobs make money. A good report is one page, compares this week to a baseline, and ends with a decision.
The problem with most field service reporting isn't missing data. It's that every number arrives without context. Utilization is 87 percent. Is that good? Compared to what? Measured how? A report that can't answer those questions gets skimmed and ignored.
This guide gives you a report structure that fits on one page, the formula behind each metric, and the common way each one lies. It fits inside a broader approach to field service management, and it pairs with our Field Notes article on the scheduling KPIs worth tracking.
Three rules for a report people read
Rule 1: Every number needs a baseline
A metric without a comparison is a fact, not a signal. Show each KPI next to last week, the trailing four-week average and the same week last year if your work is seasonal.
Rule 2: Every number needs an owner
If drive time goes up, who looks into it? If callbacks rise, who pulls the jobs? Put a name next to each section. Unowned metrics drift.
Rule 3: Every report ends in a decision
The last line should say what you'll do differently next week, even if the answer is "nothing, numbers in range." That habit turns a report into a meeting worth having.
The one-page weekly report
Group the metrics into four sections. Each one answers a different question.
Section 1: Volume (are we busy?)
- Jobs completed. Count by job type.
- Jobs booked for the next two weeks. Your forward-looking demand signal.
- Backlog. Requests received but not yet scheduled, and the age of the oldest one.
Volume is the easy section. Its main use is context for everything else. A drop in productivity during a slow week means something different than the same drop during a busy one.
Section 2: Productivity (are we using the crew well?)
- Jobs per technician per day.
Jobs completed ÷ technician-days worked. - On-site utilization.
On-site hours ÷ paid hours. Use on-site time, not booked time. See the technician utilization rate entry for why. - Windshield time share.
Drive hours ÷ paid hours. - Idle time share.
Paid hours − on-site − drive − known non-job time, ÷ paid hours.
The trap here is booked utilization. A board that's 100 percent booked can contain hours of driving. If you report booked time as utilization, your best-looking number hides your biggest cost. The Field Notes article on booked vs. utilized walks through an example.
Both numbers describe the same week. Only the second one tells you how much capacity you could recover.
Section 3: Quality (are we doing it right?)
- First-time fix rate.
Jobs resolved on the first visit ÷ jobs that needed resolving. - Callback rate.
Return visits for the same issue within N days ÷ jobs completed. PickN(often 30) and keep it fixed. - On-time arrival rate.
Arrivals within the promised window ÷ total arrivals. - Customer feedback. If you run a survey, report the response count with the score. A score from six responses isn't a trend.
These three move together more often than people expect. Late arrivals push the rest of the day, technicians rush, and rushed jobs come back. When on-time arrival drops, check callbacks two weeks later.
Section 4: Money (does the work pay?)
- Revenue per technician.
Revenue ÷ technicians, weekly. See revenue per technician. - Average ticket.
Revenue ÷ jobs completed, by job type. - Gross margin per job.
(Revenue − labor − parts − direct costs) ÷ revenue. This depends on job costing being recorded at the job level. - Overtime hours and cost. Overtime is often the first place a capacity problem shows up in money.
Money metrics usually come from a different system than operations metrics. That's fine. What matters is that they're on the same page so you can see when a productivity change shows up in margin.
How to read the report: four patterns
The value is in the relationships between numbers. A few patterns come up again and again.
Pattern 1: Jobs per day flat, drive time up
Your crews are working as hard and completing as much, but spending more of the day in the truck. Common causes: bookings spreading across a wider area, a new account at the edge of the territory, or a dispatcher filling slots in phone-call order. Look at backtracking: days where a truck crossed its own path.
Pattern 2: Utilization up, on-time arrival down
The board is fuller, and the crew is late more often. This usually means slots are being booked without checking whether the drive fits. The day looks feasible on a calendar and isn't on a map.
Pattern 3: First-time fix down, average ticket flat
More return visits without more revenue per job. Check parts availability and job-type mix. A rise in parts-related returns points at truck stock; the inventory management guide covers how to fix it.
Pattern 4: Revenue per technician up, margin down
You're selling more, but each dollar costs more. Overtime is the usual suspect, followed by underpriced job types. Compare average ticket and margin by job type to find which work is subsidizing which. The field service pricing guide covers how to reprice.
Building the data behind the report
A report is only as good as the job records under it. Four fields do most of the work:
- Arrival and departure timestamps per job, captured on site. These give you on-site time, drive time, idle time and on-time arrival.
- Job type, from a short fixed list. Free-text job types can't be grouped.
- Outcome: resolved, needs return, needs quote. This gives you first-time fix.
- Parts and labor recorded against the job. This gives you job costing and margin.
If any of these is missing or entered after the fact, fix that before adding more metrics. The work order management guide covers how to structure job records so these fields are reliable.
Drive time is the hardest to measure
Most systems record when a job starts and ends, not how long the drive before it took. You can estimate it from the gap between one job's departure and the next job's arrival, then compare that gap to a realistic drive estimate to split travel from idle. Our article on windshield time walks through it.
Some scheduling tools keep drive time visible as its own block rather than folding it into the job. CrewLink schedules crews around the drive, with travel sitting next to each job instead of hidden inside it, which makes this section of the report much easier to fill in honestly.
Weekly, monthly, quarterly
Not every metric needs the same cadence.
| Cadence | What to review | Decision it supports |
|---|---|---|
| Daily | Today's on-time arrival, open emergencies, tomorrow's board | Dispatch adjustments |
| Weekly | The four-section report above | Scheduling, staffing, coaching |
| Monthly | Margin by job type, callback causes, technician trends | Pricing, training, truck stock |
| Quarterly | Capacity forecast, hiring plan, territory changes | Hiring, territory, strategy |
The weekly report is the core. The quarterly view connects it to capacity planning and hiring.
Reporting on individual technicians
Per-technician numbers are useful and easy to misuse. A technician with low jobs per day might be the one you send all the hard diagnostic calls to. A technician with a high callback rate might be the newest, still learning.
- Compare technicians doing the same job types in the same territory.
- Look at trends over several weeks, not single weeks.
- Use the numbers to start a conversation, not end one.
Used badly, technician scorecards push people out the door. The field technician retention guide covers why that matters, and the managing field technicians guide covers how to coach from the numbers.
What to take away
- Keep the weekly report to one page, in four sections: volume, productivity, quality and money.
- Show every KPI against a baseline, give each section an owner, and end the report with a decision.
- Report on-site utilization, not booked utilization. Booked time hides drive time.
- Read the metrics in pairs. Utilization up with on-time arrival down usually means slots are being booked without checking the drive.
- Fix job records first: on-site timestamps, fixed job types, outcomes and parts against each job.
Common questions
What KPIs should a field service company track?
Start with a small set across four areas: volume (jobs completed, backlog), productivity (jobs per technician per day, on-site utilization, drive time share), quality (first-time fix rate, callback rate, on-time arrival) and money (revenue per technician, average ticket, gross margin per job, overtime).
How often should field service reports be reviewed?
Review the core KPI report weekly. Check dispatch-level numbers daily, margin and callback causes monthly, and capacity and hiring plans quarterly.
What is the difference between booked and actual utilization?
Booked utilization counts all scheduled time as productive, including the drive hidden inside each appointment. Actual or on-site utilization counts only time spent on the work. The gap between them is mostly drive and idle time.
How do you measure drive time without GPS?
Use job timestamps. The gap between one job's departure and the next job's arrival is travel plus slack. Compare each gap to a realistic drive estimate for those two addresses at that time of day to separate travel from idle time.
Should technician KPIs be shared with technicians?
Sharing can help if the comparison is fair: same job types, same territory, trends over several weeks. Use the numbers to start coaching conversations. Ranking technicians on raw numbers without context tends to damage trust.