August 2026 · Marketing operations · 8 min read

The Marketing Plan That Survives Ten Time Zones

Most multi-market marketing plans fail the same way: they are written once, live in ten different files, and get checked when it is already too late.

Reporting works better when nobody has to be awake for it

A marketing plan for one office is a document. A marketing plan for ten offices in ten time zones is an operating system, and most companies try to run the second using the habits of the first.

The symptom is always the same. Everyone agrees on the annual plan in January. By April nobody knows who is behind. By the time it shows up in the quarterly numbers, the quarter is gone.

Why the usual plan fails

Three reasons, in order of damage:

• It lives in the wrong place. Ten offices, ten spreadsheets, ten column layouts. Consolidation becomes a monthly manual job, so it happens less often than it should.
• It is written in outputs, not inputs. "Grow bookings 20%" is a wish. Nobody can be behind on it until it is too late to act.
• Review depends on a meeting everyone can attend. Across ten time zones, that meeting does not exist. So review becomes rare, and rare review means late detection.

One shared view, filled in locally

The core of what I run: every office's marketing plan, targets and performance sit in one shared view, maintained by each office in the same structure.

Same fields, same definitions, same update rhythm. Not a shared document everyone edits into chaos, and not ten private files. One structure, many owners.

The value is not the plan. The value is that all ten plans are comparable on the same day.

What each office actually fills in

Kept deliberately short, because a long template gets filled in badly:

• Objective for the quarter, in one sentence, in their own words
• Two or three target numbers, with a stated definition so two offices count the same thing
• The activities behind them: campaigns, events, partner pushes, with dates
• Leading indicators: the inputs that predict the target, such as meetings booked or partners activated
• Blockers: what they need from head office and by when

That last field does more work than the rest combined. It turns the plan from a report card into a two-way conversation, which is the only reason people keep it current.

The plan is only useful if all ten are comparable on the same day

Cadence beats meetings

The rhythm I use, tuned for people who are never awake at the same time:

• Monthly, asynchronous: every office updates its numbers by a fixed date. No meeting. The system produces the consolidated view.
• Monthly, targeted: I look for the gap between leading indicators and targets, then talk to the two or three offices that need it. Not all ten.
• Quarterly, live: one real conversation per office about the next quarter, scheduled in their working hours, not mine.

Fixed dates matter more than the meeting. When the update deadline is the first working day of the month, every month, it becomes routine rather than a request.

Catching drift before quarter end

An office is not off plan when the revenue number misses. It is off plan weeks earlier, in the inputs.

So the monthly check is not "did you hit the number." It is:

• Are the planned activities actually happening, on the dates they were planned?
• Are the leading indicators tracking, even if the outcome number has not moved yet?
• Has anything in the blockers field been sitting unresolved for more than a month?

Two consecutive months of soft leading indicators is a conversation now, not a post-mortem in ten weeks.

Local autonomy inside a shared frame

The tension in any multi-market system is standardisation versus local judgement. Push too hard on standards and you get compliance without thinking; push too little and you get ten unrelated businesses.

Where I land: the structure is fixed, the content is local. Every office reports the same fields on the same rhythm with the same definitions. What they choose to do, which channels they use and how they phrase their objective is theirs. Nobody in head office knows their market better than they do.

When performance slipped in specific markets, the fix was almost never a blanket policy. It was reading the data, isolating where that market was slipping, and changing only that process. Blanket policy is what you issue when you have not looked closely enough.

What good looks like after two quarters

• The consolidated view is produced without anyone chasing anyone.
• Offices update because they get something back, not because they were reminded.
• Leadership asks questions of the view rather than of people.
• Drift gets named in month two, not quarter three.

None of that requires new software. It requires the same fields, the same definitions and a date that does not move.

Updated: August 2026