Tech Commission on Reviews for Contractors: The Google-Compliant Way

Every contractor has had the same idea: "I'll pay my techs $10 per Google review and watch the numbers climb." It works — briefly. Then Google's systems flag the pattern, the reviews disappear, and in serious cases the profile takes a hit. The instinct is right (techs drive reviews); the mechanism is banned. This post gives you the compliant version that works just as well.

What Google's policy actually says (plain English)

Google's review policy prohibits businesses from offering incentives — money, discounts, freebies, contest entries — in exchange for reviews. Key points contractors get wrong:

• "$X per review" to techs is still incentivized. It doesn't matter that the customer didn't get paid. If the review exists because someone was compensated for producing it, it's an incentivized review in Google's eyes.
• "Only if it's 5 stars" is worse. Conditioning any reward on the rating is the clearest possible violation — and it's also review gating adjacent, which Google separately prohibits.
• Selective solicitation is banned too. Only asking happy customers for reviews (and quietly skipping the unhappy ones) violates the policy against review gating. Ask everyone, every job.
• Consequences are real: Google removes incentivized reviews, and patterns of manipulation can lead to review restrictions on the profile. One shortcut can erase years of legitimate review building.

The rule of thumb: if a bonus would change whether a review gets written, it's too close to the line. Compliant incentives reward the service quality that earns reviews — never the reviews themselves.

Compliant approach 1: Team bonus tied to overall service quality

The cleanest structure: a quarterly team bonus tied to company-wide service metrics — average rating, response rate, callback rate, customer satisfaction scores. Nobody gets paid per review. The bonus rewards the outcome (great service, consistently delivered) that produces reviews organically.

• Tie it to the team, not the individual. Team bonuses avoid the per-tech-per-review pattern entirely and build peer accountability — techs remind each other to do the little things that earn 5 stars.
• Use multiple metrics. Average Google rating + callback rate + on-time arrival rate, for example. A bonus based on service quality broadly is unambiguously compliant.
• Pay it quarterly. Frequent enough to stay motivating, infrequent enough to measure real trends instead of noise.

Compliant approach 2: Recognition leaderboards (no money attached)

A per-tech review leaderboard with recognition, not cash — tech of the month, the preferred parking spot, first pick of schedule, their name on the shop wall. Recognition motivates without compensation entering the picture:

• Track reviews per completed job (not raw count — that favors whoever runs the most calls). Publish the ranking monthly where the team sees it.
• Celebrate the ask, not just the result. Recognize techs with the highest review-request rate — the behavior you control — rather than only the highest review count.
• Keep prizes non-monetary. Trophies, preferred shifts, public recognition. The moment the leaderboard pays cash per position, you're back in the danger zone.

Compliant approach 3: Bonus the review-generating behaviors

Instead of bonusing reviews, bonus the specific behaviors that produce them — all of which are legitimate service-quality metrics:

• The verbal ask. Mystery-shop or audit whether techs are actually asking every customer. Bonus the ask rate (measured by spot-checks), not the review count.
• Photo documentation. Techs who send before/after photos on every job earn more reviews because customers have something to rave about. Bonus the photo-completion rate.
• Follow-up communication. The "here's what we did" summary text after every job. Bonus completion of the communication checklist.
• Callback rate. The inverse metric — techs with the lowest callback rates are delivering the service that earns reviews. Bonus low callbacks.

None of these pay for reviews. All of them produce reviews. That's the line, and it's a bright one.

The tech's 30-second review ask (give them the words)

Incentives only work if techs know how to ask. Give every tech this script — laminated, in the truck:

The last sentence is doing heavy lifting: it surfaces problems while the tech is still on site (when they're fixable) and makes the review ask feel earned rather than transactional. Then the automated review-request text fires within the hour with the link — the tech plants the seed, the system waters it.

What to do about existing violations (clean it up now)

If you've been running per-review payments: stop them immediately, replace with one of the structures above, and retrain the team on the why ("Google removes these reviews, so we were paying for reviews that disappear"). Don't try to quietly keep the old system alongside the new one — patterns are what get flagged. Going forward, document your incentive structure in writing; if Google ever questions a review pattern, a written quality-bonus policy is your evidence of good faith.

Three mistakes that get profiles in trouble

• Paying per review, any amount. $5 or $50, it's the same violation. Kill it entirely, not partially.
• Only asking happy customers. Cherry-picking who gets the review link is review gating. The ask goes to every customer, every job — the unhappy ones get the "tell me now so I can fix it" line first.
• Contests for "most 5-star reviews." A contest with a prize for review volume is an incentive program with a trophy. Recognition leaderboards are fine; review-count contests with rewards are not.

Related guides in this series

Know the rules with Google's Review Policy in Plain English, build the leaderboard with Per-Tech Review Leaderboards, and understand the line with What Is Review Gating?.

The done-for-you version

This post is part of the Leveraged Owner 8-system framework — the done-for-you version with the full setup guides, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.

Stats sourced as labeled: BrightLocal 2026 (68% 4-star+ threshold). Google's review policy summary is the author's plain-English interpretation — read the official policy for the authoritative text, and always measure your own numbers.