Completion rates are theater. How the best operators measure training effectiveness for field service teams: by tying it to the metric the role owns.
When the operators writing the biggest checks ask us how to measure training effectiveness for field service teams, the metric they no longer trust is the one almost every platform hands them first: the completion percentage. One ops exec running a private-equity-backed home-services group — roughly 1,400 technicians across a handful of brands — told us what "success" actually meant to him. Not a finished course. "An ability to measure if people are staying at the same level of performance," he said, and to "track against their metrics." Whether the work held up. Not whether a video got watched to the end.
That's the shift we're hearing in call after call this quarter. The buyers spending the most on training have quietly stopped caring whether their people finished the training. They want to know whether it changed the number — and completion rates are starting to read as theater.
Push these operators on the one metric that matters, and they don't reach for a learning dashboard. They reach for the P&L. That same ops exec went straight there: "Closing ratio," he said — then caught himself — "but I could have pushback; it might be revenue per lead." He already runs a weighted sales leaderboard in Power BI. What he wanted from training wasn't a report that people attended. He wanted, in his words, "the before and the after."
A founder rolling up a roughly 30-store auto group described the same instinct in plainer language: "I need a platform that holds people accountable — see who's not training, who is training. Then I'd like to correlate that to their success and failures." Read that last sentence twice. The training data only gets interesting to him at the moment it's joined to performance data. On its own, it's trivia.
This is a higher bar than the one most of the industry cleared a year ago. Measuring competency instead of completion — checking whether someone can do the job, not just whether they sat through the lesson — was a real step forward, and we still believe in it; we made that case in why a competency check beats a completion checkbox. But the operators writing the biggest checks have moved the goalposts again. Competency tells them a tech is capable. It still doesn't tell them the closing ratio went up.
Here's the uncomfortable part. A completion percentage measures attendance, not change. It confirms a course was opened and a "next" button was clicked enough times to reach the end. It says nothing about whether that tech closes more jobs, generates fewer callbacks, or rings more revenue per head than they did the month before. It is, at best, a proxy for effort — and the people approving these budgets have stopped accepting a proxy.
Worse, a number that only measures attendance has a way of going stale without anyone noticing. One renewal customer — an auto-diagnostics company with a couple hundred learners — admitted they "have not worked particularly hard lately on the monitoring," and hadn't produced new courses in a while. Their reporting never climbed past completion-level, so the program slowly drifted into the background: technically running, quietly irrelevant. That's the "set it and forget it" trap we've watched hollow out training programs in other industries too — and completion dashboards are exactly what make it so easy to fall into. The headline number stays green while the program dies underneath it.
So what does it look like to measure training effectiveness for field service teams the way these operators want it measured? The pattern isn't a fancier learning metric. It's borrowing the metric the role already lives by.
Every frontline role already has a number that defines whether it's working. For a sales-leaning tech, it's closing ratio or revenue per lead. For a service tech, it's callback rate, first-time fix, or revenue per head. The operators getting this right don't invent a brand-new training KPI — they tie the training to the number the role is already judged on, and they look at the before and the after. Did the people who actually did the training move that number more than the people who didn't?
That reframes what a training platform is even for. It stops being the place completions go to be counted and becomes the layer that connects "who learned what" to "whose numbers moved" — the exact join the auto-group founder was asking for. The measurement that matters isn't generated inside the course. It's the delta in the business metric on either side of it.
It also exposes the programs that were never measurable in the first place. When training happens by shadowing — a new hire trailing whoever's free that day — there's no before, no after, and nothing to correlate. We've written about why that kind of informal training quietly fails; the measurement problem is the part nobody mentions. You can't measure your way out of a program that was never built to be measured.
The unit of measurement is moving. "Did they finish it?" is being replaced by "did the number move?" — and the gap between those two questions is where a lot of training budgets are being quietly re-evaluated right now. The operators writing the biggest checks aren't asking their teams to prove engagement. They're asking them to prove impact: a before and an after, against the metrics the business already runs on.
That's a harder bar, and a healthier one. It means training stops being a cost center scored by activity and starts being an input scored by output — judged the same way every other function in the business is judged. The companies that make that move stop arguing about whether training is "worth it." They can see it.
If you're trying to prove your field-service training actually works and your reporting still stops at a completion percentage, the fix isn't a better-looking dashboard — it's connecting what your people learn to the numbers they're already judged on. That's what we built Quinn to do: tie training to the metric each role owns, and show you the before and the after. If your completion rate is green but you can't say what it changed, that's the place to start.