The compliant way to incentivize staff to ask for reviews

That single distinction is the whole article, and almost every review contest running in a restaurant or clinic right now is on the wrong side of it.

The board in the back of house that reads "most five star mentions this month wins a gift card" is a policy violation with the business owner's name on it. Nobody involved thought they were cheating. They thought they were running a normal sales contest.

What does Google actually prohibit?

Two specific things, both aimed at the incentive structure rather than the asking.

The Maps user generated content policy is worth reading in its own words, because the wording is narrower and sharper than the summaries of it. Under rating manipulation, Google says merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included. It then enumerates what that includes: merchants requesting that staff solicit a certain number of reviews, and merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member.

A quota tied to reviews received is the first named behavior. The name mention contest is the second.

The permitted side of the same policy is equally specific. Merchants may solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review. Asking is fine. Paying the customer is not. Paying your team to ask is not addressed, because it is not what the policy is about.

Both prohibitions exist for the same reason. A quota on outcomes creates pressure to manufacture the outcome. Staff who need three more reviews by Friday start asking family, start leaving reviews themselves, start selecting only the guests likely to comply. The moment the incentive attaches to the review instead of the request, the incentive is asking your team to distort the record.

Enforcement is not a warning letter. Google's consumer alerts documentation describes what happens when it detects suspicious review activity: it may display a public banner on the business profile, impose review posting restrictions, or hide reviews for a period. A banner is visible to every prospect who looks you up. A posting freeze stops your review program dead while competitors keep accruing. The reviews you paid bonuses for can disappear in a batch, which is a bad month twice over.

Yelp says the same thing in four words. Its guidance for business owners states that your staff should never compete to collect reviews.

What is the federal rule nobody mentions?

The one that makes an employee's own review your problem, not theirs.

The FTC's Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465, took effect on 21 October 2024. Section 465.5 covers insider reviews. An officer, manager or employee reviewing their own employer has to clearly and conspicuously disclose that relationship.

Here is the part that catches owners. Liability attaches for an omission. The rule reaches a business that did not instruct prospective reviewers to disclose, clearly and conspicuously, their relationship to the business. An owner who says "hey, leave us a review" in a preshift meeting, and says nothing about disclosure, is the party in violation. The employee who writes it is not the only exposure, and in practice is not the exposure anyone pursues.

"Clear and conspicuous" is defined, and the definition is strict. Among other requirements, a disclosure is not clear and conspicuous if a consumer has to take an action such as clicking a hyperlink or hovering over an icon to see it. So the disclosure has to be inside the review text itself. Which is why the honest instruction to staff is simply: do not review your own workplace.

The Endorsement Guides at 16 CFR Part 255 reach further. Section 255.5 names a business, family, or personal relationship as a material connection requiring disclosure, which covers the manager's spouse and the owner's cousin as well as the employee.

Section 465.4 handles incentives directly. It prohibits providing compensation in exchange for, or conditioned expressly or by implication, on a review expressing a particular sentiment. Those three words, or by implication, are the ones that matter. A staff bonus announced in the same breath as "we need to get our rating up" is conditioned by implication even if the written rule says otherwise. Write the rule down and announce it the same way you wrote it.

Counsel reporting at the rule's finalization put civil penalties for knowing violations at $51,744 per violation, adjusted annually for inflation, so confirm the current year's figure before anyone puts it in front of a client. The structural change matters more than the number. Before this rule the FTC generally needed a cease and desist order first. Now it has civil penalty authority for a first violation.

What can I reward instead?

Anything you can observe on your own floor without looking at Google.

Reward requests made. A server hands out the card or the guest scans the code at the table. That is a countable behavior, it happens in your building, and it does not depend on what the guest does next.

Reward process compliance. The ask happened at the right moment, in the right words, on the right share of checks. If you already do table touches or job completion walkthroughs, this is one more line on a form you already use.

Reward the team, not the individual. A shared goal for the shift or the store removes the pressure that makes people cheat, and it removes the name mention problem entirely because nobody needs their own tally.

Reward the underlying thing, which is service. If your incentive is genuinely about guest experience, review volume follows on its own and you have nothing to explain to anyone.

The tooling should make the ask nearly free. If a request means typing a URL from memory, it stops happening by week two. A short link, a card, or a code at the point of sale removes the friction, and there is a compliant way to build those into the flow.

What do the numbers look like on a real contest?

Here is a full month, with figures you can swap for your own.

A restaurant runs 14 server shifts a week. The preshift target is 10 asks per shift, which is a scan or a card at ten tables. That is 140 asks a week and about 560 a month.

The prize is a $200 gift card, split as a team bonus at the end of the month.

Cost per ask: $200 divided by 560 is about 36 cents.

Now convert asks into reviews using your own measured rate rather than a vendor's. Say one review lands for every seventeen asks, which you got by counting for thirty days. 560 asks produce about 33 reviews a month, and the incentive cost per review earned is roughly $6.

Set that against the benchmark. If the three competitors above you collect five a month each, 33 is not a stretch goal, it is a different weight class, and the constraint was never the prize size. It was that nobody was asking.

Now price the non compliant version of the same contest. Pay the same $200 for reviews received and you have created a per person quota, which is the behavior Google names. The downside is not the $200. It is a consumer alert banner on the profile, a posting freeze during your best quarter, or a batch of legitimate reviews filtered out, plus federal exposure if the payout implies sentiment. Same cost, same team, completely different risk, and the compliant version collects more reviews because it rewards the part your staff actually control.

How do I run a contest that does not break the rule?

Change what you count and change what you print.

Count requests, not reviews. If a contest scoreboard has a column for stars received, redesign it.

Never script a name mention. "If you have a minute, a review helps us a lot" is fine. "Mention me by name" is not.

Never set a number of reviews per person. A weekly team target for requests made is fine. A per server quota of reviews received is the named violation.

Keep it simple enough that a new hire understands it on day one. The training script should be short and it should sound like a human being, because an ask that sounds needy gets ignored regardless of what you are paying for it.

Write the policy down. One page, posted, covering what staff may say, what they may not say, and what happens if someone posts a review from their own account. That last one matters more than people expect, and section 465.5 is why.

While you are writing the script, drop the keyword coaching. Telling staff to get guests to say the service name in the review is wasted effort. A controlled test found that keyword text inside reviews does not affect map pack rankings, so the only thing that instruction adds is an unnatural sounding review and a compliance risk.

What does this look like on a real shift?

It looks like one line added to something you already do.

Preshift, the manager names the target. Twenty requests this shift, team goal, tracked on the same sheet as everything else.

At the table or at the counter, the ask is a single sentence attached to a moment that already exists. Dropping the check. Handing over the bag. Confirming the next appointment.

Post shift, the count goes on the board. Requests, not reviews. Nobody is looking at Google to score it.

The manager checks the actual review flow weekly, separately, as an operating metric rather than a scoreboard. That separation is the whole design. Staff are accountable for the behavior they control, and the owner watches the outcome nobody should be paid for.

Incentives do move this, which is the uncomfortable part of the story. Sterling Sky documented a client whose local rankings slipped after the owner stopped rewarding staff for reviews, and recovered once the flow resumed. His structure was the wrong one, because he was paying on reviews received. The lesson is not that incentives do not work. It is that they work well enough to be worth building correctly.

What to do this week

Walk into the back of house and read whatever is posted about reviews. If it names individuals or counts reviews received, take it down today.

Rewrite the incentive around requests made. Team based, weekly, tracked on paper you already keep.

Write the one page policy and hand it to every manager. Add the line that says employees do not review their own workplace, and say why.

Then run a benchmark count so the target is grounded in your market rather than pulled from the air.

Questions about your staff incentive?

Email me at eric@seod.com with a photo of your review contest board or a copy of the script your team uses. I will tell you which parts are compliant, which parts are not, and give you a rewrite you can post the same day. Two minutes of my time, and it removes a risk most owners do not know they carry.

Otherwise keep reading the reviews and reputation library.