An area manager with eight restaurants spends more of the week in the car than in any one of them. Too often the visit starts at the door with "so, how's it going?", and the first twenty minutes go on finding out what the last two weeks already recorded.
The visits that change something start before the engine does. Ten minutes with the right five questions turns a general walk-around into a visit with a purpose, and lets the manager spend the time in the store on the one or two things that need a person there.
The five questions to answer before you leave
1Which checks did this store miss, and on which days?
Not the completion percentage, the pattern. A store that misses the closing check every Sunday has a rota problem. One that misses random checks has a habit problem. They need different conversations.
Where it comes from: the store's run history for the last two weeks, laid out by day.
2Which step fails most, here and nowhere else?
If every store fails the same step, the standard is the problem, not this store. If only this one does, that step is what the visit is for.
Where it comes from: failed steps for this store, compared with the same steps at your best store.
3What fixes are still open, and how old are they?
A broken freezer seal raised nine days ago and still open is the first thing to ask about, before anything new is added to the list.
Where it comes from: open fixes for the store, oldest first, with who owns each.
4What do the photos show that the ticks do not?
A display ticked complete every day but photographed half-empty twice a week is worth more attention than any score.
Where it comes from: this store's photos for the display and opening checks, side by side with your best store's.
5What did I promise to check last time?
The quickest way to lose a store manager's trust is to agree three things on a visit and never mention them again.
Where it comes from: the close-out notes from the last visit, and whether those fixes held.
What the brief looks like on one page
- Missed checks
- Closing check missed 3 of the last 4 Sundays. Every other day complete.
- Step that fails
- "Display cabinet full to the line" failed 6 of 14 mornings. Downtown failed it once.
- Open fixes
- Freezer door seal, raised 9 days ago, owner: store manager. Washroom dryer, 2 days.
- Photos
- Cabinet half-empty in morning photos on Mondays and Tuesdays, after the weekend delivery gap.
- Last visit
- Agreed: second person on Sunday close. Check whether the rota changed.
- Focus
- Sunday rota, Monday stock levels, and the freezer seal. Leave the rest to the checklist.
An illustrative example with made-up stores and numbers, to show the shape of the brief.
Notice what is not on it: the twenty things that went fine. The brief is short because the daily checklist already covers the routine. The visit is for what the checklist cannot fix by itself.
What changes on the visit itself
- Walk the whole store looking for anything wrong
- Find the freezer seal by accident, or not at all
- Leave with a long list nobody owns
- Start from scratch next time
- Go straight to the two or three known issues
- Spend the time on causes: rota, delivery timing, training
- Leave with three fixes, each with an owner and a date
- Start the next brief by checking whether they held
The area manager store visit checklist follows this shape: first impression, display, service, the store's own records, team, and a close-out of three fixes with owners. Each fix can follow the fix follow-up template until it is proven closed.
Where the five answers live
If the store runs its checks on paper, the brief means a phone call and a pile of photocopies. If it runs them in a checklist app, the answers are already there: every run with a name and a time, the failed steps, the open fixes, and the photos side by side with your best store's. In RakuOps that is the store's page and the scorecard, so the brief is a ten-minute read rather than an afternoon of chasing. For the wider case, our guide to checklist and SOP software for restaurants and food service covers what to look for in the tool, and how to run a site visit that changes something covers the visit itself.