What I Learned Managing 3 QSR Locations at Once
Multi-site QSR management reality: how I structured my week across three stores, the difference between presence and productivity, and tactics you can steal.
Wednesday, 11:47 AM. I'm standing in the Broadbeach store watching the lunch rush build when my phone buzzes. Bundall has a no-show on the grill station. Palm Beach has a customer complaint escalation. I've been at Broadbeach for 90 minutes and haven't finished what I came here to do.
That was a typical week when I first started managing three GYG locations simultaneously. I was everywhere and nowhere. Present in three stores but productive in none of them.
Multi-site management is one of those roles that sounds straightforward until you're actually doing it. "Just visit each store regularly and make sure they're performing." Right. And a pilot just steers the plane.
Here's what I actually learned about making multi-site work, after a lot of trial and error across Broadbeach, Bundall, and Palm Beach.
Communication breaks before food quality does.
This was the first and most important lesson. When a multi-site operation starts to slip, the root cause is almost never the food, the equipment, or even the staff. It's communication. Information stops flowing between stores and between me and the GMs.
The GM at Bundall doesn't know about the new prep procedure. Palm Beach hasn't heard that we changed the promotional display. Broadbeach is doing something slightly different from the other two stores and doesn't realise it.
These small communication gaps compound fast. Within a few weeks, you've got three stores running three slightly different operations, all under the same brand, and nobody knows which version is correct.
I fixed this by creating a single weekly communication cadence that ensures every GM gets the same information at the same time. A Monday group message with the week's priorities. A Wednesday check-in call. A Friday data review. Simple, consistent, non-negotiable.
How I structured my week.
After months of reactive chaos — going wherever the fire was — I moved to a fixed schedule. Each store gets a dedicated half-day visit per week, plus one flex day for issues that can't wait.
Monday morning: Broadbeach. This is the highest-volume store, so it gets the first visit of the week. I review the weekend performance data with the GM, walk the store during the transition from breakfast to lunch, and identify any maintenance or staffing issues.
Tuesday morning: Bundall. Same format — data review, store walk, issue identification.
Wednesday morning: Palm Beach. Same again.
Thursday: flex day. This is reserved for follow-ups, deeper work on one specific store, or handling whatever came up during the week that needs more attention. Some Thursdays I'm back in one of the stores. Some Thursdays I'm at my desk doing analysis.
Friday: administration. Data compilation, reporting, planning the following week, shift leader meeting prep.
This schedule only works if I protect it ruthlessly. The temptation to respond to every mid-week crisis by jumping in the car and driving to a store is real. But every time I deviate from the schedule to deal with something urgent, I lose the time allocated for something important. And the important stuff — coaching, system building, preventive maintenance — is what prevents the urgent stuff from happening in the first place.
Being present versus being productive.
Early on, I confused presence with productivity. I thought that being physically in a store was the same as improving it. It's not. I've had days where I spent six hours in a store and accomplished nothing measurable. I walked around, chatted with staff, watched service, and went home feeling like I'd done something. But what actually changed?
Now, every store visit has a specific purpose defined before I leave my house. "Today at Broadbeach, I'm doing three things: reviewing last week's speed of service data with the GM, observing the 12:00-12:30 rush to assess deployment, and checking the walk-in cool room organisation." Three things. In and out.
If I finish those three things and there's time left, I might stay and observe. But the three objectives come first. This approach transformed my effectiveness. Instead of being a visible but passive presence, I became someone who showed up, made things better, and moved on.
Tactical things other multi-site managers can steal immediately.
One: standardise your GM communication rhythm. Same format, same cadence, every week. Don't let it be ad hoc. Ad hoc communication is how standards drift.
Two: create a "store visit checklist" that fits on one page. Before every visit, know exactly what you're checking and what a good result looks like. Don't wing it.
Three: compare stores to each other, openly. I share performance data across all three stores in the same communication. Broadbeach's speed of service is 2:47. Bundall is 3:12. Palm Beach is 2:55. The GMs can see where they rank. That transparency creates healthy competition without me having to push.
Four: build relationships with shift leaders, not just GMs. The GM tells you their version of how the store runs. The shift leaders tell you how it actually runs. I make a point of having informal conversations with shift leaders during every visit — not to undermine the GM, but to get ground truth.
Five: protect your planning time. Multi-site management is so reactive by nature that you can spend an entire week dealing with issues and never do the proactive work that prevents future issues. Block time in your calendar for analysis, system building, and strategic thinking. Treat it like a store visit — non-negotiable.
Six: use data as the starting point for every conversation. Not opinions, not feelings, not complaints from customers that the GM hasn't verified. Data. What does the speed of service average tell us? What does the labour cost percentage say? Let the numbers open the conversation, then dig into the why.
Managing three locations taught me that multi-site success isn't about working harder or being more available. It's about structure, rhythm, and discipline. The managers who burn out are the ones who try to be everywhere. The ones who thrive are the ones who build systems that work whether they're in the store or not.
If you manage multiple sites and want to compare notes, drop me a line — daine@dainereid.com.