A weekly record of a store's Google reviews, replies and actions taken.
Selected questions from each section. Try them.
Showing 9 of 10 items. The full template comes with weights, fatal items and the score formula.
Q1. Which week does this log cover, from Monday to Sunday?*
Q2. How many new Google reviews did the store's profile receive this week?*
Q3. What is the average star rating of this week's new reviews?*
Q4. How many of this week's reviews were rated three stars or below?*
Q5. What did the negative reviews complain about, such as wait time, staff attitude, stock or billing?*
Q6. Has a polite, specific reply been posted to every review of three stars or below, and within how many hours?*
Q7. Can you attach a screenshot of the store's Google profile showing this week's reviews?*
Q8. What action was taken in the store on each complaint theme, and who owns it?*
Q9. Which staff members were named in positive reviews, so they can be recognised in the huddle?*
GPS and time on every shot. No gallery uploads.
Drishti checks the photo against your standard.
Every miss gets an owner and a deadline.
Operations score next to the selling score.
A Google review log template is a weekly record of what customers said about a store on its Google profile and what the store did about it. The Store Manager fills it once a week, counting new reviews, noting the average rating, listing complaint themes from reviews of three stars or below, confirming a reply was posted to each and recording the action taken in the store. A screenshot of the profile is attached as proof. The Area Manager reviews it the same week. It is a log, not an audit, so there is no score. Its value is in the pattern: the same complaint appearing across weeks, or across stores, is a problem worth fixing.
A single bad review is noise. The same complaint three weeks running is a signal. A weekly log turns scattered reviews into a record the Area Manager can read in two minutes, and it makes sure every negative review gets a reply while the customer still cares. Across stores, it shows which complaints are local and which point to a brand-wide issue, such as a pricing change or a slow exchange process.
The brand decides, but the reply should always be polite, specific and posted within a day or two. Many brands let the Store Manager reply using an approved tone, while others route replies through a central team. Either way, this log records that a reply was posted and how quickly, so a review never sits unanswered because everyone assumed someone else had done it.
No. It is a log, not an audit, so the pass mark is zero and nothing is fatal. The value is in completeness and in the pattern over time. In BorentisOps a complaint theme can be turned into a ticket with an owner and a deadline, so the action written in the log is followed up rather than forgotten by the next week.
Yes. The Excel download keeps the same columns BorentisOps uses: section, item, question, answer type, photo rule, weight and fatal flag, so it imports as a checklist without retyping. A Borentis onboarding person maps the roles and stores, sets who fills it and who reviews it, and schedules it so it reaches the right phone at the right time. You can edit, add or remove items before or after the import.
Borentis is a retail conversation intelligence platform: Borentis Floor captures and scores the in-store sales conversation with the customer's consent. BorentisOps, which runs this template, is the store operations half, so that the operations score can be read next to the selling score on one card per store. The category is explained at what is retail conversation intelligence and how to measure in-store sales interactions.