Catering reviews: who leaves them and how to ask

Restaurants get dinner reviews without asking because forty guests are forty potential reviewers. Catering does not work that way. Forty people ate, one person bought, and the other thirty nine have no idea who catered it.

That is why a restaurant with hundreds of dinner reviews often has none that mention catering at all, which is a problem for the exact buyer you want.

Who is actually in a position to review a catering order?

Three people, and they are worth different amounts to you.

The buyer. The office manager, the parent, the planner, the executive assistant. They placed the order, handled the money, and absorbed the risk. Their review is the one a future buyer will read closely, because it is written by someone who did the same job they are about to do.

The onsite contact. Sometimes the same person, often not. At a corporate event this is whoever met your driver at the loading dock. They know whether you were on time and whether the setup was what was described. That is a narrow review but a credible one.

A guest. Rare, low value, and usually vague. "Food at our office lunch was great" tells the next buyer almost nothing about whether you can handle their event.

So the ask goes to the buyer. Everything else is a bonus. One review written by a buyer who happens to name the headcount and the occasion outperforms ten guest reviews that say the food was good. You cannot ask them to name it, which is the next section, but you can ask the person most likely to.

When is the right moment to ask?

After the invoice settles, not on the day.

On the day, the buyer is working. They are running an event, herding people, and dealing with whatever else went wrong that has nothing to do with you. An ask in that moment is noise.

A day or two later they have heard the compliments, the room is cleaned up, and the payment is done. That is the window. Any longer and the event fades, response rates fall, and the review you get is generic.

For recurring corporate accounts, ask after the third or fourth order rather than the first. By then they have real evidence of consistency, and consistency is exactly what a future buyer is trying to verify. Asking a brand new account too early gets you a polite review with no substance.

Do not run the ask through the same automated flow as your dinner reviews. Catering buyers are not walkins with a receipt. They are a named person you have a relationship with, and a generic text blast to that person reads as a downgrade in the relationship.

What does Google actually allow you to ask for?

Less than most catering advice assumes, and this is where a lot of restaurants quietly break policy.

Google's Maps user generated content policy is explicit about what a merchant may do. Verbatim, merchants are allowed to "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."

And here is the clause that kills the standard catering review script. Under rating manipulation, Google states that when soliciting reviews, merchants "should not request that specific content be included," and names as examples "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."

So "if you could mention that it was a fifty person corporate lunch, that really helps us" is against the policy. It is a natural thing to say, it is what every agency template does, and it is not allowed. Ask openly, tell them why a review matters to a small business, and let them write whatever they write.

If you need the event detail visible to future buyers, put it on your own page. A short written testimonial you asked the client for directly, published with their permission and their name, is a different artifact under different rules, and it can name the headcount and the occasion.

Is there any compliant way to incentivise a catering review?

No. Not a discount, not a free tray next time, and not a raffle.

The raffle is the one worth naming, because it is the "compliant incentive" that gets proposed in almost every marketing meeting. It fails three separate tests.

Google bans incentives flatly. The allowance above is conditioned on soliciting "without offering incentives to do so." There is no size of incentive that is small enough.

The FTC's Rule on Consumer Reviews and Testimonials, 16 CFR Part 465, effective 21 October 2024, defines purchasing a consumer review to include contest entries. A raffle entry for customers who review sits inside the definition on its face. Section 465.4 bans providing compensation or incentives conditioned expressly "or by implication" on reviews expressing a particular sentiment, and those two words carry the weight.

The FTC Endorsement Guides, 16 CFR Part 255, name the mechanism directly. Section 255.5(a) lists "the possibility of being paid, of winning a prize" as a material connection requiring disclosure, and adds that it applies "regardless of whether the advertiser requires an endorsement in return."

The rule matters because it changed the FTC's enforcement posture. Before it, the agency generally needed a cease and desist order first. The rule gives it civil penalty authority for first time violations, reported by counsel at finalization as $51,744 per violation and adjusted annually. Confirm the current year figure before putting it in front of a client.

Do not ask your own staff or family to review the business without disclosure either, because Section 465.5 attaches liability for the omission itself, not just the review.

And do not point a catering review request at Yelp. Yelp's policy tells businesses not to ask anyone for reviews at all, and solicited ones get pushed out of the recommended set.

How many catering reviews do I actually need?

Fewer than you think, arriving more regularly than you think. Here is how to set the target.

Start with your competitors, not with a benchmark. Whitespark's Darren Shaw gives the method in one line: "How often are your top competitors getting new reviews? If the answer is twice a month, you should also aim for that, plus one." Open the three businesses ranking above you for your main catering search and count their new reviews over the last ninety days.

Say the three competitors gained 6, 9 and 3 new reviews in that window. That is 2, 3 and 1 a month, so the median is two, and your target is three new reviews a month, or 36 a year across the whole business.

Now the catering share. Four catering orders a month is 48 buyers a year you can ask. You will have to measure your own response rate, because no published benchmark for review request response rates in catering exists with a disclosed sample. Ask all 48 for a quarter and count what comes back. Even a modest rate produces a stream of reviews written by buyers rather than guests, which is the only kind a catering prospect reads carefully.

The reason cadence matters more than total is recency. In Whitespark's 2026 Local Search Ranking Factors survey, in which 47 local search experts scored 187 factors, Recency of Reviews ranks eleventh among local pack factors and "Sustained Influx of Reviews Over Time (rather than bursts)" ranks fourteenth. That is expert opinion rather than test data, and the publisher says so. But the direction is corroborated by field work: Sterling Sky documented a client whose rankings dropped after a review audit showed the review flow had flat lined, recovering as reviews resumed, and another business that got filtered after going more than three years without a new review.

Two more things from the same source. Shaw's stated view is that a negative review is better than no new review at all, because recency moves regardless of sentiment. And a business that asks everyone should expect roughly thirty positive reviews for each negative one, which is the arithmetic that should stop you filtering.

Ask every buyer, every time. Do not filter for the ones you think are happy. Sorting customers by expected sentiment before you ask is banned by a single clause in Google's policy, which prohibits merchants from "discourag[ing] or prohibit[ing] negative reviews, or selectively solicit[ing] positive reviews from customers." It also makes your review profile look staged.

Where do catering reviews go and do they help?

They land on your main Google profile with everything else, which is both the limitation and the point.

You do not get a separate catering profile. Every catering review sits mixed in with dinner reviews, and a buyer researching you will scroll looking for anything that mentions an event. If nothing does, they assume you do not really do catering, whatever the page says. That assumption costs you before your menu ever gets read.

If you run several locations, be deliberate about which profile the catering buyer is sent to. Sending them to the wrong one splits your proof across profiles, which is one flavor of the problem covered in multilocation restaurants competing against themselves in search.

Reviews also feed the referral side. A hotel sales manager deciding whether to send you overflow will read your reviews first, and getting catering referrals from hotels that turn business away depends on public evidence that you can execute offpremise.

Judge the effort honestly. Catering review volume will always be low, and a low number is not a failure, so measure it the way you should measure anything else with small numbers, which is the same discipline as measuring conversion honestly when your traffic is small.

Where does this break down?

Two places, and the second one is the trap.

When the ask is automated. Everything above assumes a person sends it. The moment it goes into a bulk flow, the wording drifts back toward scripting content, the timing detaches from the event, and the corporate buyer receives something that reads like a receipt survey.

When the platform notices the pattern. Google can show a public consumer alert banner on a business page when it detects suspicious review activity, restrict posting, or hide reviews for a period. A posting freeze stops your review flow dead while competitors keep accruing, which is exactly the condition the recency evidence says costs you rankings. The compliance argument and the ranking argument point the same way, which is unusual and worth noticing.

What to do this week

Read your existing reviews and count how many mention catering, an event, a party, or a delivery. That number is what a catering buyer sees.

Count your top three competitors' new reviews over the last ninety days and set your monthly target at their median plus one.

Add the ask to your catering closeout process. Same list as the final invoice. One line, one owner.

Write the two sentence ask and save it where the person who handles catering can find it. Check it says nothing about what the review should contain.

Then email the last three catering buyers you served, even if it has been a while. The worst outcome is silence.

Want help writing the ask for your last few events?

Email me at eric@seod.com with the last five catering events you delivered. Just the occasion, the headcount, and who the contact was, no names needed. I will write the specific ask for each one, tell you which buyer is most likely to write something useful, and flag the one I would skip.

The wording changes a lot between an office manager and a parent, and that is most of why generic requests get ignored. I will also tell you if your current request is scripting content, because most of the templates in circulation are. I do this myself and there is nothing behind it.

There is more on catering and event business to read next.