A Simple Google Review Policy for Employees

Your whole team should know exactly how your business handles review requests, and the most reliable way to ensure that is a short written policy. The goal is not legal complexity or a thick handbook nobody reads — it is consistency and professionalism. A one-page policy turns review collection from something that happens only when an employee happens to remember into a standard, repeatable part of how your business operates, the same way you already have a standard way of greeting customers or closing out a sale. It also protects you: a clear, written rule against incentivizing or gating reviews keeps every employee on the right side of Google's policies — even the brand-new hire who would otherwise have no idea those rules exist.

What the policy should include

Keep it to a single page covering four essentials, each stated plainly enough that a brand-new employee could follow it on their first shift:

• Who is responsible for asking — whether it is every customer-facing role or a specific person at a specific step, so the ask never falls through the cracks because everyone assumed someone else would handle it
• When the ask should happen — the exact moment, such as checkout, job completion, or the end of an appointment, rather than a vague "whenever it feels appropriate"
• Which tools to use — the QR card, the text link, the email follow-up, and where to find each one
• What language to use and what to avoid — the approved one-line script, plus the specific things never to say

That is the entire policy. Resist the urge to pad it; a longer document is simply a document nobody reads.

The approved script

Include the exact words you want staff to use, so nobody has to improvise under pressure with a customer standing right in front of them. Something like: "If you had a good experience today, we'd really appreciate a quick Google review — I can text you the link." Having one sanctioned line means the ask is consistent across every employee and every shift, sounds professional rather than awkward, and never accidentally drifts into pressure or incentivization. It also makes training almost trivial: instead of coaching judgment and tone, you are teaching a single sentence anyone can deliver naturally after saying it out loud a few times.

What to avoid — and why it matters

Three hard rules belong in every policy, and each one protects your profile from a real, specific consequence. Do not offer incentives — discounts, freebies, loyalty points, or entries into a drawing — in exchange for reviews; this violates Google's policies and can get your reviews stripped or your profile penalized, erasing the very reviews you worked to collect. Do not pressure customers or ask the same person repeatedly, which reads as harassment and can provoke the negative review you were trying to avoid. Do not "gate" reviews by routing only happy customers to Google while diverting everyone else — selectively filtering who gets asked is explicitly against the rules. The compliant approach is simpler and works better anyway: ask everyone, offer a private feedback channel so unhappy customers can reach you directly first, and let each customer decide what to post publicly.

Handling negative situations

Your policy should tell staff exactly what to do when a customer is visibly unhappy, because that is the moment most likely to go wrong without guidance. The rules: do not ask them for a public review in the moment, route them to a manager or a private feedback channel, and put the focus entirely on resolving the issue. This protects your rating from an in-the-moment one-star, and handled well it frequently turns a frustrated customer into a loyal one who later leaves a positive review on their own. Make it explicit to the team that the goal is to fix the problem, not to suppress or hide the review — customers can tell the difference, and trying to silence feedback backfires far worse than an honest negative review handled with grace and a genuine fix.

Keep it living

Review the policy every quarter rather than writing it once and filing it away forever. As you learn which timing and which channels actually convert best for your business, update the approved script and the process to match — a policy built on last year's assumptions slowly drifts out of step with what really works. Onboard every new hire with it on day one so the habit is built in from the start, instead of bolted on after they have already formed sloppier ones. A short, living, genuinely-known policy is the difference between a team that collects reviews consistently and one where it depends entirely on who happens to be working that day.