Technician scorecard: definition, formula, and dashboard example
A technician scorecard combines the metrics that determine whether a field tech is profitable, productive, and improving. Here is what belongs in one, how to calculate each component, and what a live version looks like on a home-service operations board.
Formula
Tech score = weighted sum of component scores (revenue per tech, average ticket, close rate, callback rate, membership conversion, and review score)
There is no single universal formula because the right scorecard depends on which outcomes matter most to your business model. The most common approach: assign each metric a weight (totaling 100%), score each technician as a percentage of their individual target, multiply weight by score, and sum the products. A tech who hits 95% of revenue target, 80% of close-rate target, and 100% of review target across a 40/30/30 weighted card earns a composite score of approximately 89 out of 100.
Weights and thresholds should reflect your company's current priorities. A growth-stage business may weight revenue per tech and close rate higher; a retention-focused operation may weight membership conversion and review score higher.
What is a technician scorecard?
A technician scorecard is a composite view of the key performance indicators that determine whether a field technician is meeting revenue, quality, and customer-experience expectations. Instead of reviewing average ticket alone or close rate in isolation, a scorecard rolls five to seven metrics into a single ranked view so a service manager can spot who is excelling, who needs coaching, and exactly which metric is driving the gap.
For most home-service companies, the accountability gap lives in the field. A CSR knows her booking rate by the end of every shift. A dispatcher can see capacity in real time. But a technician often does not know how his numbers compare to the team until a monthly one-on-one, when the month's revenue is already gone and the coaching is backward-looking. A live technician scorecard closes that gap: the tech sees his own metrics updated through the day, and the service manager can coach before the shift ends rather than after the month closes.
Which metrics belong in a technician scorecard?
The most commonly included metrics are revenue per technician (total revenue attributed to the tech in a period), average ticket (average invoice value per completed job), close rate on presented options, membership conversion rate (agreements sold on service calls), callback rate (return visits for the same problem), and review score (average star rating from post-visit surveys). Not every business tracks all six. Start with the three that most directly drive your profitability.
What a technician scorecard combines
A technician scorecard brings the metrics that define a strong tech into one view: revenue produced, close rate on presented options, membership conversion, callback rate, and review score, each read against its target. Some teams weight these into a single composite; others watch the components directly, spotting the one that is pulling an otherwise strong performer down. Datacube builds it from ServiceTitan's Technician Performance Report (completed revenue, opportunity job average, opportunity conversion rate, recalls caused, and total tech-lead sales), shown per technician, so the scorecard reflects real report columns rather than a hand-maintained formula.
Who owns the technician scorecard and how often to review it
The service manager owns day-to-day scorecard visibility. The GM or operations leader reviews it weekly in a team standup and monthly for compensation or recognition decisions. Techs should see their own data continuously, not just in the monthly one-on-one: real-time visibility is what lets a tech self-correct on close rate or membership pitch mid-week before the numbers are set.
What each scorecard component signals and what to do when it drops
| Metric | What a drop signals | Immediate action |
|---|---|---|
| Revenue per technician | Fewer jobs completed, lower ticket, or both; check dispatch efficiency and truck stocking | Review job count and average ticket separately to isolate whether it is a volume or value problem |
| Average ticket | Tech is not presenting all options or is defaulting to minimum repairs | Ride-along or call review; check option-presentation scripts in the CRM |
| Close rate on presented options | Customer objections are not being handled or pricing feels off for the market | Review declined jobs; distinguish price objections from trust objections to target the right coaching |
| Membership conversion rate | Tech is skipping the agreement pitch or presenting it late in the visit | Reinforce pitch timing in pre-shift briefing; compare against techs who convert well |
| Callback rate | Jobs not fully diagnosed or repaired; parts or skill gaps possible | Review the original job notes; identify whether it is a diagnosis, parts, or training issue |
| Average review score | Customer experience issue: cleanliness, communication, or unresolved concern | Read the actual reviews; look for a pattern (punctuality, attitude, explanation) rather than acting on a single low score |
What good and poor technician scorecard movement looks like
Targets vary by trade, season, market, and tenure. Use these as directional signals and set your own baseline from the last 90 days of your top-third techs.
- Tech composite score trending up month over monthRevenue, close rate, and quality are all improving in concertGood
- Current
- Target
- Revenue per tech up but callback rate also risingVolume growth may be hiding quality shortcuts; check repair completionWatch
- Current
- Target
- Wide spread between top and bottom techs on close rateCoaching and option-presentation consistency gap; ride-along with the bottom quartileWatch
- Current
- Target
- Composite score flat while job count is downDispatch or capacity issue, not a tech-performance issue; investigate schedulingWatch
- Current
- Target
- Average ticket falling alongside a drop in close rateTech is not presenting full options; revenue impact compounds quickly at scalePoor
- Current
- Target
- Review score below 4.0 and callback rate risingCombined signal of quality and experience failure; escalate before it appears in public reviewsPoor
- Current
- Target
| Metric | Current | Target | Status |
|---|---|---|---|
| Tech composite score trending up month over monthRevenue, close rate, and quality are all improving in concert | Good | ||
| Revenue per tech up but callback rate also risingVolume growth may be hiding quality shortcuts; check repair completion | Watch | ||
| Wide spread between top and bottom techs on close rateCoaching and option-presentation consistency gap; ride-along with the bottom quartile | Watch | ||
| Composite score flat while job count is downDispatch or capacity issue, not a tech-performance issue; investigate scheduling | Watch | ||
| Average ticket falling alongside a drop in close rateTech is not presenting full options; revenue impact compounds quickly at scale | Poor | ||
| Review score below 4.0 and callback rate risingCombined signal of quality and experience failure; escalate before it appears in public reviews | Poor |
Info
Before you build this: no universal technician benchmarks
A plumbing tech running emergency calls in a high-cost urban market will post very different average tickets than a garage-door tech in a suburban market during slow season. There is no single number that defines a good technician scorecard. Set your targets from your own data: use the last 90 days of your top-performing third as the baseline, then push the rest of the team toward it. Adjust for tenure, trade, and market before comparing individuals.
Technician scorecard on a live datacube Techs board
How a technician scorecard appears on a datacube Techs board displayed on the shop TV, refreshed throughout the day so the service manager can coach before the shift ends and techs can self-track without waiting for a monthly report.
Figures are illustrative. Your datacube Techs board reflects your own CRM, review platform, and revenue data, updated as your integrations allow.
Info
Owner takeaway: the scorecard is a coaching tool, not a punishment tool
The best technician scorecard builds are implemented with the field team, not imposed on them. When techs can see their own numbers live, most will self-correct before a service manager intervenes. The companies that get the most from a technician scorecard are the ones where the data is visible to everyone and the conversation is about helping the bottom performers reach the top, not just ranking people for the sake of ranking.
Related KPIs to read alongside the technician scorecard
| KPI | Why it pairs with the technician scorecard |
|---|---|
| Revenue per technician | The primary revenue component; separates job-count effects from ticket-value effects |
| Average ticket | Tracks option-presentation effectiveness job by job |
| Callback rate | Quality indicator; a rising callback rate often precedes review score drops |
| Average star rating | Customer experience output; confirms whether quality metrics translate to satisfaction |
| Job profitability | Adds cost context; a high-revenue tech may still run thin margins if labor or parts costs are high |
| Gross margin | Company-level check that tech revenue growth is flowing through to profit, not just top line |
Three things to get right before you launch a technician scorecard
- Define the denominator for each component consistently: close rate on what, exactly? All jobs, all estimates presented, only chargeable calls? Everyone on the team must count the same way.
- Weight the scorecard toward what actually drives your profitability today, not what sounds comprehensive. Three well-defined metrics beats seven poorly sourced ones.
- Make the scorecard visible to the techs, not just to management. Real-time self-visibility is what turns a scorecard from a report into a behavior-change tool.
Technician scorecard FAQs
See your technician scorecard live in datacube
Connect your CRM and review data and put a live Techs board on every service manager's screen and every shop TV. Coach during the shift, not after the month closes.
Keep exploring
Related
Go deeper