The first regional role I ever ran, my communications rhythm was accidental. I sent an update when something happened. I read updates when I remembered. I ran meetings when they got scheduled. By month four, I had two general managers I liked whose units were quietly falling apart, and I did not know it until the monthly close, which is roughly six weeks too late to act.
The rhythm below is what I built after that year. It is not new. Every good multi-unit operator has some version of it. What is worth writing down is the specific shape, the specific templates, and the two or three behaviors on the leader's side that determine whether the rhythm holds or dissolves.
Why bad news travels slower than good news
In a healthy region, bad news moves at the same speed as good news. In an unhealthy region, bad news moves slower. The gap is not a moral failing on the field's part. It is a physics problem created by the leader.
General managers, area directors, and shift leads all do the same math. If sharing a problem early consistently gets them help, they share early. If sharing a problem early consistently gets them scrutiny they cannot yet defend, they wait until they have a fix ready. In the wait, small problems become medium ones, and medium ones become resignations, walkouts, and $40,000 R&M surprises.
You cannot demand a no-surprises culture. You can only build one by consistently making it safer to be early with bad news than late with a fix.
The three cadences
The rhythm is three overlapping cycles, each with a different purpose and a different format. Together they cover the ways information wants to move in a multi-unit region.
Fig. 1 · Overlapping cadences, not sequential ones.
Weekly: the numbers update
Every general manager sends a weekly update to their area director, who summarizes to the regional director. Ten lines. Always in the same shape. Sent by Monday 10am for the prior week.
- Sales, actual versus plan, dollars and percent.
- Labor as percent of sales.
- Food cost as percent of sales.
- Top three items sold by unit.
- Top three misses or issues from the prior week.
- One thing you are trying to change this week.
That is the whole email. It should take a general manager 15 minutes to write. If the template drifts into paragraphs, the rhythm has already started to fail.
Monthly: the working meeting
Once a month, in person if possible, every general manager and area director in a room. Each general manager presents their prior month in five minutes. Their numbers, their two biggest wins, their two biggest misses, their plan for next month. Peer accountability is doing most of the work here. General managers will prepare harder for a peer audience than for a manager one.
The regional director speaks last, briefly, with one or two regional trends worth naming. This is not a town hall. This is an operating meeting. The audience is field leadership only.
Quarterly: the narrative memo
Every quarter, the regional director writes a three-page memo. Not a slide deck. A memo. What we did well, what we did badly, what we are changing next quarter, and the one or two strategic bets that will decide the year. The memo goes to the CEO, the CFO if there is one, the field leadership team, and the board if there is one.
The writing itself is the point. A memo forces the regional director to have an actual picture of the quarter, not a slide deck's version of one. If the memo is hard to write, the picture is not clear yet, which is a signal worth catching before the quarter ends.
The two-way rhythm
Communication only up is reporting. Communication only down is broadcast. Neither one is a rhythm. The rhythm is two-way, on a matched cadence.
Fig. 2 · Every field cadence has a matching leader cadence. The pair is the rhythm.
Monday morning note from the regional director
Two paragraphs. Sent by 8am Monday. What the region is focused on this week, one specific shout-out to a unit or a person by name, and a note on any decision the field can expect to hear about in the next seven days. That is the whole thing. It should take you 20 minutes to write. The point is not eloquence. The point is that Monday starts with a signal the field can point at.
The 24-hour acknowledgement rule
Every field update gets a response inside 24 hours. Not a long one. Two sentences is fine. The response references something specific from what you read, so the sender knows you actually read it. A general manager who has sent five weekly updates in a row without a single specific acknowledgement will stop sending them, and you will not know why.
The two behaviors that build or break the rhythm
You can install the rhythm perfectly and still have it collapse if either of these two leader behaviors is missing.
1. Read the updates the field sends
Actually read them. Reference specific items in the next week's one-on-one. If a general manager mentioned a walk-in refrigeration issue in last week's update and you do not ask about it this week, you have quietly told them the rhythm is a paperwork exercise. Every general manager in the region has the same conversation with their assistant manager within a month.
2. Do not punish bad news that arrives on time
This is the harder one. When a general manager includes a real miss in their weekly update, the temptation is to want to know more, and the next thing that happens is the general manager feels investigated. If the miss is significant, respond with two sentences of acknowledgement and take the followup to the one-on-one. Do not chase in email. Do not copy peers. If they told you early, they were doing the right thing. Reward the behavior even when the news is bad.
The moment a general manager learns that early bad news gets them a lecture and late bad news gets them a coaching call, the whole rhythm dissolves.
What the rhythm actually catches
The point of all of this is not tidiness. It is signal. A working communications rhythm catches, on average, three or four kinds of problems a month earlier than an ad-hoc approach does.
- Labor drift. Weekly percent-of-sales report in the same shape every week makes a 2-point drift visible in week two, not month two.
- Silent resignations coming. A general manager whose weekly updates start getting shorter and later is almost always three to eight weeks from resigning. The rhythm makes that shift visible in a way that guessing does not.
- Retail partner friction. A single mention in a monthly meeting of "we had a scheduling issue with the Whole Foods store manager" is a signal, not a story. Left alone it becomes a category review problem in the quarter.
- Vendor drift. A quiet mention of "our produce delivery has been late three times" in a weekly update points at a vendor relationship that needs a call before it becomes a food cost problem.
What kills the rhythm most often
Three patterns kill regional communications rhythms more than any others.
- The regional director travels and cancels the standing meetings. Even one cancellation a quarter is enough to teach the field the meeting is optional.
- The template drifts. "Just add a few notes on the local promo" and inside two months the weekly update has grown to 30 lines and nobody sends it on time.
- The regional director starts skipping the acknowledgement. Even one week of silence in response to a weekly update tells the sender that you are no longer paying attention. Two weeks and the sender is right.
The channels question
Most regional directors underestimate how much of the communications rhythm's success depends on channel discipline. Email, Slack or Teams, phone, text, video, in-person. Each one has a right use and a wrong one, and mixing them randomly turns the rhythm into noise.
- Email is for asynchronous decisions and durable references. Weekly updates, monthly recaps, quarterly memos. Anything you want to find again in six months goes here.
- Slack or Teams is for daily operating chat that is not shift-critical. A photo of a new menu item, a question about a vendor, a heads-up about a promotion. It is not for emergencies and not for anything that needs a signature.
- Phone is for anything time-sensitive that involves a decision or a real emotion. Bad news, hard coaching, or anything a text would be misread.
- Text is only for logistics. "Running 10 minutes late." That is the whole use case. Any operational content in text is a mistake.
- Video is for scheduled one-on-ones and standing meetings. Not for ad-hoc syncs unless the other person has explicitly agreed to it.
- In-person is for coaching depth, hard conversations, and celebrations. Everything else is fine remote.
When you name the channel discipline out loud with the field, two things happen. First, the volume of low-quality communication drops. Second, the important communication starts landing on the channel it deserves. A regional director who receives operational updates on all six channels is the regional director who quietly stops reading any of them.
The escalation channel
Every rhythm needs an explicit escalation channel that lives outside the normal cadence. A general manager who has a real emergency at 11pm on a Saturday should not be trying to remember whether that goes in the Monday update or the weekly one-on-one. They should have one channel, one number, one clear rule.
The rule I use: any situation that involves guest safety, staff safety, or a threat to the unit's ability to open the next day is a phone call to me directly, at any hour. Everything else waits for the normal cadence. Naming that specifically once, in writing, at the start of the relationship, prevents both under-escalation on real emergencies and over-escalation on things that could have waited.
The point
A regional communications rhythm is not about paperwork. It is about making sure important information moves at a predictable speed, so that when something breaks, you hear about it in the week it broke, not in the quarter it stopped hiding.
Ten-line weekly. Working monthly. Written quarterly. Two-paragraph Monday note down. 24-hour acknowledgement up. Never punish early bad news. Do those six things for a year and surprises become rare, and the small ones that still happen become manageable. Cadence beats charisma.