Managing reviews across 40 locations without losing the thread

Single-site businesses notice a bad review the day it lands. Groups notice when the brand average moves, which is roughly three months late.

Start with an inventory, not a dashboard

Before any tooling: list every public profile that exists for the brand, including duplicates, unclaimed listings and pages created by aggregators. Most groups discover between 10% and 30% more listings than they thought they had, and the forgotten ones collect reviews nobody answers.

Fix attribution before you fix ratings

Reviews routinely land on the wrong branch — the customer searched the brand, clicked the first result and reviewed a site they never visited. These are eligible for removal on Google when the content clearly describes another location, and they distort branch-level data until they go.

Alerting has to be per branch

A group-level average hides everything. What a regional manager needs is: this site got a one-star review yesterday, here is the text, here is whether it looks removable. Same day, not in the monthly pack.

What the monthly report should contain

• Rating and review volume per location, with the direction of travel
• Response coverage — how many reviews were answered, and how fast
• Recurring complaint themes by site, which is operational data, not marketing data
• Open removal cases and their status

The franchise wrinkle

Where franchisees own their listings, head office often cannot act directly. The workable pattern is central auditing and casework with per-franchisee approval, and reporting split so commercially sensitive detail stays where it belongs.