Per-Tech Review Leaderboards for Multi-Truck Shops

Three techs, three trucks, one review system — and all the reviews mention the same tech's name. The other two aren't worse at their jobs. They just never ask. A leaderboard doesn't shame them; it makes the invisible visible, and the visible gets done.

This is the team layer of the review engine. The pillar post covers the ask itself; this post covers making sure every tech actually makes it.

Why leaderboards work (and when they don't)

Techs are competitive by nature, and the scoreboard taps into that honestly — nobody wants to be the blank row. But a bad leaderboard is worse than none: if the scoring is unfair, the team learns that the system is rigged and stops playing. The entire design below exists to keep the game fair.

The fair scoring formula

Raw review counts are unfair: the tech doing 8 small jobs a day will always beat the tech doing 2 big installs. Score on what each tech controls:

• Ask rate: what percentage of completed jobs got the review ask? Track via the job-completion checklist in your field service management (field-service software) software (field-service software = the software running your scheduling, dispatch, and job records). This is the primary metric — it's 100% in the tech's control.
• Mention rate: reviews that name the tech, divided by their jobs. This measures the quality of the customer experience, not just the ask.
• Score both, weight the ask. A tech with a 95% ask rate and few mentions needs coaching on the customer experience. A tech with a 40% ask rate needs accountability on the habit. The leaderboard shows both columns so the diagnosis is visible.

Normalize by job count, always. The leaderboard's unit is "reviews per 10 jobs," not "total reviews." The install tech and the service tech are playing the same game.

Building the board

• Where it lives: physically in the shop (whiteboard by the time clock) and digitally in the team chat. Physical beats digital for daily visibility — techs see it every morning.
• What it shows: tech name, jobs completed (month), asks made, ask rate, reviews mentioning them, reviews per 10 jobs. Six columns, updated weekly. No more — a cluttered board gets ignored.
• The timeframe: monthly, resetting on the 1st. Monthly is long enough to be meaningful and short enough that a bad week doesn't end the game. Keep a year-to-date column for the long view.

Incentives: recognition over cash

This is the compliance-sensitive part, so read carefully. Google's policy prohibits compensating customers for reviews — and while paying your techs per review isn't the same as paying customers, per-review cash bonuses create exactly the wrong incentive: techs pressuring customers, or worse, fabricating. Keep incentives clean:

• Reward the ask rate, not the review count. "Tech of the month" for 100% ask rate rewards the behavior you control. Rewarding raw 5-star counts rewards luck and invites gaming.
• Recognition, not per-unit pay. A preferred parking spot, first pick of the schedule, public acknowledgment at the team meeting, a gift card for the monthly winner — all fine. "$5 per review" is not.
• Never tie employment to review counts. The leaderboard is a coaching tool, not a disciplinary one. A tech with a low ask rate gets a conversation, not a write-up.

The coaching upside (the real prize)

The leaderboard's hidden value isn't motivation — it's diagnostics. Patterns in the data tell you things no ride-along will:

• High ask rate, low mention rate: the tech asks, but customers don't remember them fondly enough to name them. Coach the in-home experience: the walkthrough, the shoe covers, the explanation.
• Low ask rate, high mention rate: customers love this tech, but the ask isn't happening. Usually a confidence issue — role-play the ask until it's comfortable.
• Low ask rate, low mention rate: the full conversation. Is it training, attitude, or a bad fit? The data starts the discussion; it doesn't end it.
• Reviews mentioning a tech by name for great service: read these aloud at the team meeting. Public celebration of specific behaviors ("Mrs. [Name] said you explained everything before starting") teaches the whole team what good looks like.

Rolling it out without a mutiny

• Announce it as a team goal first. "We're going to 200 Google reviews this quarter as a shop" — the leaderboard is the tool for a shared goal, not a surveillance program.
• Run one month unranked. Track the numbers privately for a month so the first public board has real data and nobody starts at zero publicly.
• Let the techs see their own numbers first. Private week-one, public week-two. Nobody likes being surprised on a whiteboard.

The monthly 10-minute review huddle

The board needs a ritual or it becomes wallpaper. Once a month, 10 minutes at the team meeting:

• Read the top 3 named-praise reviews aloud. Specific, by name, in front of everyone. This is the most motivating 3 minutes in the meeting.
• Name the ask-rate winner. Recognition for the behavior, not just the outcome.
• One coaching takeaway from the data. "Our mention rate dipped on install jobs — let's talk about the end-of-job walkthrough." Data-driven, blameless, actionable.
• Reset the board. New month, clean slate. Last month's winner starts at zero like everyone else.

Ten minutes, once a month, keeps the game alive all year. Skip the huddle and the board quietly dies within a quarter — the ritual is the system.

A worked example

Example: a 4-truck HVAC shop launches the board. Month one (private): the owner sees the spread — two techs asking consistently, two rarely asking. The shop owner has individual conversations — the lowest-ask tech admits he feels awkward asking; they role-play the script twice. Month two (public): ask rates climb across the board, and reviews mentioning techs by name start appearing — the owner notices the previously quiet tech's mention rate is the highest on the team. Customers love him; he just wasn't asking. By month three, the board has become the coaching map: every tech's ask habit is visible, the conversations are specific, and review volume is growing from a system instead of luck. The board didn't just generate reviews; it made the team visible to itself.

Related guides in this series

The leaderboard drives the ask — the ask itself is detailed in the review engine pillar post. When reviews name your tech (good or bad), the response protocol covers exactly what to do. And for the physical leave-behind that makes the ask easier, read the review card guide.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full 5-step setup guide, every script, the worksheets, and click-by-click setup instructions for all 8 systems. The Starter Pack includes the leaderboard template and the tech ask-rate tracking sheet.

Stats sourced as labeled: no third-party statistics used in this post; the worked example is illustrative, not a customer result.