How should a restaurant prove its reviews are real?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
Link reviews to bookings and orders, and stop soliciting at the table. A restaurant proves its reviews by importing them with the reservation or order reference attached (so the certificate and widget can stand behind them), replacing the table-side script ('if you loved tonight, mention us online') with one transaction-triggered ask sent to every booking, and auditing monthly for the trade's three classic patterns: incentive offers at the till, bursts after opening or PR events, and duplicate wording from a suggested phrase on a comment card.
What is restaurant review provenance?
Restaurant review provenance is the practice of tying a restaurant's reviews to the meals they describe — booking, order or receipt references — and keeping a chain of custody over how they were solicited and moderated. Restaurants are the most-reviewed local businesses and the most temptation-dense: the ask happens face to face, at an emotional peak, with a staff member whose evening is judged by the score. Provenance is how a good restaurant separates its genuine reputation from that pressure.
The table is the worst place to ask
Face-to-face solicitation manufactures both gating and incentives without anyone deciding to cheat. The server who asks only the laughing table is gating. The manager who appears with a complimentary dessert and a suggestion is incentivising. The comment card with an example sentence is scripting duplicates. Move the entire ask out of the room: one message, triggered by the booking or order record, identical for the anniversary couple and the table that sent a dish back. Your floor team keeps one job — the meal — and the audit's gating and incentive lines become the proof that they are no longer carrying the marketing department's target.
The audit mechanics do not change by trade: import the reviews, read the signals traced to your own rows, and publish only what carries a transaction link. What changes is where the risk hides. Service businesses collect reviews at emotional moments — after a repair, a meal, a treatment — and staff under pressure reach for shortcuts: a discount offered at the till, a tablet handed over with the review page already open, a quiet word that unhappy customers should call first. Those shortcuts are precisely the gating and incentive patterns the analysis weights most heavily, and precisely what the FTC rule prohibits. Finding them in your own data first is the cheapest fix there is.
Bursts a restaurant can defend, and one it cannot
Openings, festival weeks, a television mention: restaurants have legitimate bursts, and their shape is their defence — varied wording, a real spread of ratings (a packed opening week produces complaints too), and transaction links to the booking system that was visibly full. The indefensible burst is the quiet one in a normal week: uniform five stars, UNLINKED, similar phrasing, from a 'reputation service' invoice nobody can quite explain. Monthly imports catch both early, when the legitimate one can be documented contemporaneously (the booking diary beside the pack) and the illegitimate one is eight reviews, not eighty.
In practice the routine takes minutes. Export or copy the reviews for the location, import them into ReviewProof by CSV or paste, and read the report top-down: total rows, flagged count, risk score, then the per-signal breakdown. Open the flagged rows themselves — the report traces each signal to its row precisely so you can do this. Decide moderation openly (kept, published, or flagged internally; there is no delete), check which reviews carry a transaction link, and publish or refresh the verified widget so the public claim matches the audited record. On Pro, export the evidence pack while the file is fresh.
Mistakes that undo the work
Training servers to 'mention reviews' keeps the pressure in the room even with a clean script — the transaction-triggered message exists to remove the topic from the floor entirely. Offering a digestif, dessert or discount in the same breath as the ask is an incentive however warm the intention. And answering negative reviews with 'we have no record of your visit' when your records were never imported is a claim your own audit should be able to check before you make it.
Volume matters differently per business, too. A location with forty reviews cannot absorb a burst the way a location with four thousand can: five same-day reviews are a rounding error in one file and an eighth of the entire profile in the other. ReviewProof detects a burst when at least five reviews land on one day and that day holds at least 40% of the import, which is why the report must always be read against your own baseline. The worked example on this page uses a small file on purpose: small profiles are where provenance work pays back fastest, because every single review is visible.
Worked example: a bistro replaces the card on the table
A fictional worked example, written to show the numbers and the decisions in practice.
A 40-seat bistro imported 386 reviews for its first audit. Findings: 12 incentive rows mentioning a free liqueur 'for a review', dating from a manager's winter promotion; a duplicate cluster of 7 reviews sharing a sentence that matched — word for word — the example printed on its old comment cards; one burst day from a food festival, 23 reviews, 19 of them booking-linked, kept with the festival diary page filed beside the pack. The bistro retired the cards, moved the ask to a post-booking message, flagged the 12 and 7 with reasons logged, and watched the next quarter's imports come back with zeros on both lines. Its widget now shows 4.5 from linked reviews only — the number it quotes to the guidebooks.
Your five-action checklist
- Move the ask off the floor: one message triggered by booking or order
- Attach the booking or order reference in the request record for linking
- Remove comment cards and scripts that suggest wording or offer treats
- Audit monthly for incentive, duplicate and burst patterns specific to the trade
- File event evidence (festival diary, opening coverage) beside legitimate burst packs
Frequently asked questions
Can staff ever mention reviews to guests?
The safe design removes solicitation from the room entirely: the ask is a standard message after the transaction. A guest who raises reviews can be thanked — not steered, rewarded or scripted.
How do we link reviews when most bookings are by phone?
Capture the booking reference in whatever system took the phone booking and use it in the request record. Walk-ins will yield more UNLINKED reviews — an honest label, improvable at the margins, never by invention.
Our opening week produced a huge burst. Is that a problem?
Only if it cannot be evidenced. Varied, booking-linked, mixed-rating rows plus contemporaneous evidence of the opening is a defensible surge; file them together.
Which plan does a single restaurant need?
Free covers one location's full audit, certificates and widget. Pro adds the evidence export and reply drafts most restaurants want once a dispute or a guidebook vetting arrives.
Keep reading
Related guides from the ReviewProof library:
- How should a dental clinic handle reviews and provenance?
- How should a hotel prove its reviews came from real stays?
- How should a salon keep its reviews honest and provable?
- How should a plumber or trades business prove its reviews?
- How should a law firm handle client reviews and proof?
- How should an auto repair shop prove its reviews?
- How should a gym keep member reviews honest?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.