The first year I ran a multi-state region I did the math wrong. I promised myself I would visit every one of my 21 units every month. I built a calendar that looked heroic. I got through it, most weeks. By month nine I was making decisions that were technically correct and quietly stupid, because I was running on airport sleep and a rotating cast of hotel breakfasts.
The units I visited most often were not the ones that needed me most. They were the ones closest to a direct flight. The units in the harder-to-reach markets, which happened to be the ones with the biggest operational headaches, got the least of my attention. Nobody had asked for that distribution. My travel calendar had just quietly made it.
Tier the region before you build the calendar
The single most useful thing I did in year two was stop pretending every unit deserved the same visit cadence. They do not. Group your units into three tiers, based on two axes: recent risk and revenue weight.
Fig. 1 · Not every unit needs the same visit frequency. Match presence to signal.
The tier is not permanent. It is a quarterly assignment. A unit that has just gone through a general manager change is Tier 1 for at least a quarter, even if it is a small revenue contributor. A unit that has been operating cleanly for six months can drop to Tier 3 for the next quarter, even if it is one of your bigger revenue contributors, because your presence is not what is holding it together anymore.
Draft the whole year before you commit any week
The mistake almost everyone makes with travel is planning it month by month. That guarantees you will over-commit early quarters and under-plan late ones. Draft the entire calendar year on one page before you commit any week to a specific trip.
The repeating four-week pattern I use, adjusted around holidays and blackouts:
- Week 1: In market A. Three to five units in one geographic cluster. Four days on the ground, one working travel day.
- Week 2: Home. Local calls, deep work, one-on-ones with area directors, planning for the next in-market week.
- Week 3: In market B. A different geographic cluster. Same shape as week 1.
- Week 4: Corporate or virtual. Corporate office if you have one, otherwise the standing regional operating review and quarterly work.
Over 12 months that gives you 24 to 26 in-market weeks. Enough to hit every Tier 1 unit monthly, every Tier 2 unit every six to eight weeks, and every Tier 3 unit every quarter, with room for one wildcard trip per month for whatever the region throws at you.
The travel calendar is not a to-do list. It is the shape of your attention. Whatever it puts you in front of is what your region will get the most of.
Cluster trips or the math does not work
The temptation, especially in the first year, is to visit one unit at a time. A general manager needs a coaching session, so you fly out for two days and come back. Do that four times in a month and you have burned eight travel days for the equivalent of one week of good field time. The math punishes you.
Every in-market trip should hit at least three units in the same geographic cluster. If a unit is too remote to bundle, then it is a Tier 3 unit and it lives in your quarterly rotation, not your monthly one.
The exception: a crisis. A location that is actively failing gets an on-the-ground visit regardless of cluster. But log that trip separately in your annual grid, because if you are running more than one crisis trip per quarter, your operating model has a problem the travel calendar is masking.
Anchor every trip in a working shift
The most valuable field time is not the meeting time. It is the shift time. Every in-market week should have at least one Friday dinner or Saturday lunch or Sunday brunch shift on it, and you should be at the pass, not in the office. That is where the operating system is under load. That is where you see it flex or snap.
The rest of the week is one-on-ones, walkthroughs, and working sessions with the area director. Not a parade of meetings. A working week has whitespace in it, on purpose, so that when something breaks you have the room to sit with it.
Protect the recovery window
Every trip has a return-day cost you probably underprice. The day you fly back is not a full workday no matter what your calendar says. Block it. Not for a meeting. Not for calls. Block it for the region catching up with you: the messages that arrived while you were in the air, the decisions that got stacked while you were with another unit, the small fires the area director handled that you should still know about.
Fig. 2 · One in-market week. Block the following Monday, always.
The rhythm is more important than the room
The single most tempting thing to cancel while traveling is the standing meeting. Do not. The Monday weekly with the area directors, the Wednesday one-on-one with each direct report, the monthly regional operating review, all of these get taken from wherever you are. Airport lounge. Hotel room. Rental car in a Sam's Club parking lot. It does not matter.
General managers do not care that you sound tired on the call. They care whether the meeting happened. When you cancel a standing meeting because of travel, you teach them that your calendar is more important than theirs. Which is not the lesson you want them to learn from you.
The three habits that break the calendar
- The last-minute add. A general manager asks if you can swing by while you are in market. You say yes. Twelve of those in a year is a month of extra time you did not budget. Fix: any add lands in next month's grid, not this one, unless it is a crisis.
- The Sunday night flight. Looks efficient. Steals your only recovery day. Fly Monday morning whenever possible. The two extra hours of sleep on Sunday buy you six good hours of Monday work.
- Front-loading Q1. Everyone wants to get on the road and build relationships in January. By June the calendar has eaten you and Q3 planning suffers. Even distribution beats heroic launches.
Honest note on year one
The first year I ran this schedule, I still traveled roughly 145 nights. In year two, with the tiering and clustering above, I dropped to about 105 nights and the region's numbers improved. The units I had been over-visiting in year one had learned to over-rely on me. Pulling back gave the general managers back their own operating authority. Which was the whole point of building the region in the first place.
You are not a better regional director because you slept in more hotels. You are a better regional director because the units you built can run when you are not in them.
Booking discipline that pays for itself
The mechanical parts of travel are boring and almost every regional director underinvests in them. A little booking discipline recovers hours per month and dollars per quarter that nobody will ever thank you for saving.
- Book flights three to four weeks out for planned in-market weeks. The Tier 1 units are on a known cadence. There is no reason to be buying tickets ten days out for a monthly rotation you have been running for two years.
- Use the same one or two hotel chains per market. Points programs matter when you are on the road 100 nights a year, and more importantly, a consistent hotel means one less decision to make on a tired Tuesday.
- Rent the same car category every time. Familiar controls reduce the friction of driving into your third market this month.
- Keep a permanent packed travel bag. The 20 minutes you save by not packing is 20 minutes you get to spend with your family the night before you leave.
The family calendar rule
The single most important travel discipline I have learned in ten years of multi-state work is this: your family calendar is not a residual of your work calendar. It is a peer document. Certain dates on it are as immovable as any board meeting. Recitals. School events. Birthdays. A spouse's important work commitments. Anniversaries.
Every year I mark these dates first, before any regional travel gets scheduled. They become blackouts. Then the year's travel plan gets built around the blackouts. This costs almost nothing in terms of coverage. Fifteen or twenty blackout dates spread across twelve months does not meaningfully constrain a well-designed travel plan. What it does is prevent the slow erosion of family credibility that happens when work dates keep winning the coin flip.
The rule I have shared with every direct report who does multi-market work: your family is not a stakeholder in your career. Your family is the whole point of your career. Build the calendar accordingly.
One more note on the family calendar rule. Share it with your general managers explicitly. Not as a policy. As a description of how you personally work. When they know their leader has real family limits and communicates them proactively, they feel more permission to do the same, which is the culture you want.
There is a second-order benefit that only shows up in year two of running this discipline. General managers watch what you do more than what you say. When they see that you have real family limits, they start to model theirs the same way. The regional director who never misses a recital gives their general managers implicit permission to build a life outside the restaurant. That permission produces more retention than any compensation adjustment I have ever seen budgeted. The travel calendar is a leadership document, not a logistics one.
The point
A regional director's travel calendar is not a to-do list. It is the physical shape of your attention across the region. If you do not design it deliberately, geography and last-minute requests will design it for you, and the design will be wrong.
Tier your units. Draft the year. Cluster your trips. Protect the recovery window. Never break the standing rhythm for a flight. Do those five things and the twelve months hold. Skip any of them and by month nine you will be making the kind of decisions that only look right if you have not slept.