ReviewProof ⚖

How do you audit reviews across multiple locations?

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

Audit per location, judge per location, fix per location — then, and only then, look at the group picture. Each location imports its own file (Pro covers 3 locations; Agency is the multi-location tier at 50,000 reviews per import), gets its own risk score, signal breakdown and verified share, and runs the same frozen ask and moderation rules. The pattern to hunt is divergence: one location's gating count climbing while the others sit at zero is a local practice, and it will never be visible in a blended group average.

What is a multi-location review audit?

A multi-location review audit is the parallel application of the single-location audit — import, signals, provenance, logged moderation — across every site a business operates, under one shared standard. Its unit of truth remains the location, because solicitation habits, staff and review channels are local even when the brand is not. Group reporting is a summary of location audits, never a substitute for them.

One standard, locally evidenced

Standardise everything that must be defensible: the frozen ask, the cohort rule, the moderation states and reasons, the monthly import rhythm, the pack export. Localise everything that is evidence: the files, the scores, the flagged clusters, the corrections. When a location diverges — a burst after a local promotion, incentives quoted from one site's till cards — the standard is what lets you say, with a straight face and a dated record, that the group found a local deviation from a group rule, fixed it locally, and can show the before and after per location. Without the standard, the same finding reads as culture; with it, it reads as an exception. That difference is worth the Agency plan on its own in any serious conversation with a franchisor, buyer or regulator.

The workflow is the same on every plan, and the free tier does the complete job for one location: import by CSV upload or paste (up to 500 reviews per import on Free), read the full risk analysis and report, open a provenance certificate for any review, and publish the verified-experience widget. Pro ($29/month, 3 locations, 5,000 reviews per import) adds the full provenance chain detail, the evidence export, AI reply drafts and the reviewer-fraud graph. Agency ($79/month, 50,000 reviews per import) is the multi-location tier. Nothing about the free audit is a sample or a teaser — the report you get free is the real analysis of your real rows.

Rollout order: worst file first is usually wrong

Start the rollout with a cooperative, average location, not the suspected problem site. The pilot teaches the team the file-gathering realities (which exports carry references, which lose dates) on a location where the findings will be boring, and produces the internal how-to that makes the harder locations fast. Then proceed in any order — but import every location before announcing conclusions, because staff talk to each other and a forewarned location's sudden spreadsheet hygiene will contaminate its own audit. Historical imports, taken as found, are the baseline; the standard applies prospectively from the day the frozen ask lands.

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

Blending imports into one mega-file destroys per-location fingerprints of practice — always import by location. Announcing the programme location by location over months invites pre-cleaning that falsifies the baselines you most need honest. And ranking locations publicly by score inside the company turns an audit instrument into a league table; scores will then be managed instead of practices.

A detail worth knowing before you start: ReviewProof analyses what you give it. The CSV importer reads reviewer, rating, title, body, date and source columns, plus a verified-transaction flag and a transaction reference when you have them. Reviews with a transaction link are marked verified; reviews without one are marked UNLINKED — kept in the audit, visible in the report, but excluded from the verified-experience widget, which only displays reviews that are both transaction-linked and in a kept or published state. That single rule is the difference between a widget that markets and a widget that proves.

Worked example: six locations, one outlier, one afternoon

A fictional worked example, written to show the numbers and the decisions in practice.

A six-site fitness operator on Agency imported all six locations before reviewing any results: 1,874 reviews in total. Five locations scored between 4 and 11, gating at zero, verified shares above 60%. The sixth scored 34 — driven by 26 incentive rows quoting a 'free month for a review' offer from a site-level promotion, plus a burst on the promotion's launch weekend. Because every location ran the same standard, the conversation with that site's manager was short and documentary: the group rule, the site's rows, the fix (offer ended, rows flagged internally, manager briefed), and a re-import date. The group's other five audits were the evidence that this was one site's deviation, not the brand's method.

Your five-action checklist

  1. Import and report strictly per location; never blend files
  2. Freeze one group standard: ask, cohort rule, moderation states, rhythm
  3. Pilot the rollout on an average location and write the internal how-to
  4. Complete every location's baseline import before announcing conclusions
  5. Track divergence per signal per location, month on month

Frequently asked questions

Which plan covers multiple locations?

Free covers one location. Pro covers 3 locations at 5,000 reviews per import; Agency covers multi-location work at 50,000 reviews per import.

Should locations share one risk score?

No. Each location's file produces its own score and breakdown. A group figure may summarise, but decisions and fixes happen at location level.

What if one location's reviews were solicited badly for years?

Import as found, flag with reasons, fix the local practice, and let the record show the correction. The baseline's honesty is what makes the fix provable.

Can an agency run this for clients?

Yes — that is the Agency tier's purpose, with each client location's record kept separate so one client's evidence never mixes with another's.

Keep reading

Related guides from the ReviewProof library:

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.