Why one market's calendar does not stretch to others
A home calendar encodes home assumptions: the holidays, the school year, the weather, the shopping peaks and the working week of one market. The localising websites and campaigns guide warns that seasons can be reversed and holidays and shopping peaks differ, so a seasonal sale copied abroad can arrive in the wrong season. The measuring and reporting guide adds that a public holiday or a local shopping event can move a market's results more than any campaign, and attaches a calendar of each market's key dates to the report for that reason.
Three more things change. Lead times grow, because every localised asset needs translation or transcreation and an in-country review before it can run. Clocks multiply, because each market has its own time zone and each ad account and analytics property has one too. Ownership splits, because the central team owns global moments and each market owns its own. A calendar for several markets has to show all of that on one timeline without becoming unreadable.
Before you start
- A working single-market calendar. The layers, fields and review habits in the campaign calendar guide are the base this tutorial extends.
- The market list and roles. Which markets are in scope and each one's role (pilot, growth, established), as the media and channels guide uses them for budget.
- A named owner per market. The person, partner or agency who will supply that market's dates and approve its view of the calendar.
- Past localisation jobs. Dates briefed, delivered, reviewed and published for recent localised assets, so lead times come from the business's own record rather than a guess.
- The time zones in use. Each market's time zone, and the time zone of every ad account, analytics property and email platform that will publish into it.
- The planning tool. Whatever the team uses as the single view of work, as the work management and marketing calendars guide describes, with a field for market.
The steps
Set the shared layer of global moments
Start with the moments that apply to every market: global product launches, brand campaigns run from the centre, company events, platform deadlines and the financial year. Put them on the calendar as a shared layer, marked global, with the central owner. Keep this layer short. A moment belongs here only if every market will act on it; anything that only some markets act on belongs in their own layers.
Ask each market for its own moments
Send each market ownerThe one named person accountable for a market's plan, channel mix, partners, results and commentary, and for commercial sign-off on its localised work. a short request: the public holidays, cultural and religious moments, shopping events, school terms, trade events and category moments that matter in their market, with the dates for the year and a line on why each matters to the business. Ask them to mark which they want to act on and which are dates to avoid. Do not compile this list at head office from general sources; the market knows which moments its customers notice and which only appear on lists. Record the source and the owner beside each date.
Mark seasons and peaks for each market
Add each market's seasonalityPredictable, repeating changes in demand tied to the calendar, such as months, holidays, weekdays or hours. from its own sales and search history where it exists, and from the market owner's knowledge where it does not. Mark the weeks when demand rises and falls, and the weeks when media prices typically rise around big local events. A product whose home peak is in one season may peak at a different time elsewhere; the calendar should show that difference side by side, not hide it under the home season's label.
Add localisation and review lead times backwards from each date
For every item a market will run, work backwards from its live date: in-country review and sign-off, translation or transcreation, the brief to the localisation supplier, and the master asset being final. Use the lead times from the business's own past jobs for each kind of asset and each language, not a general allowance. Put each milestone on the calendar as a dated task with an owner. This is the step that most often moves a date: it shows that a market's edition of a launch has to be briefed earlier than the central plan assumed. The backward planning framework shows how to read the slack and the clashes once every market's milestones are dated. When the localisation step is the one every launch slips at, the diagnosis page on localisation delaying every launch finds which part of that path, review, scope, briefing, triage or the dates, is the constraint.
Set release times in local and account clocks
For each release, record the intended local time in the market and the equivalent time in the system that publishes it. The ad schedules guide notes that an ad schedule runs in the account's time zone, and the measurement guide, drawing on Google Analytics Help, notes that analytics properties and ad accounts each have a time zone in which daily figures close. So a launch planned for a market's morning may need a schedule set for the previous evening in account time. Show both clocks on every release, and name the time zone each is in. Email sends follow the guide to email across countries and languages, which schedules in each market's local time.
Mark freezes and quiet periods by market
Add the periods when a market should not change or launch anything: its own peak trading weeks, when the change freeze method applies; periods of national mourning or sensitivity the market owner flags; and periods when the local team or partner is unavailable. Mark them per market, so a global launch can see that one market is frozen and plan its edition around it.
Check clashes between global and local plans
Filter the calendar week by week and look for four clashes: a global moment that lands in a market's freeze or quiet period; two campaigns reaching the same audience in the same market in the same weeks; a localisation milestone that falls on a market's holiday, when the reviewer is away; and a release whose local time is outside sensible hours. Resolve each with the owners concerned, and record the decision, including when a market launches later than the others.
Phase budgets against the calendar
Set each market's budget by period from its calendar, not from the home market's pattern. The media planning framework covers flightingScheduling advertising in bursts separated by periods of little or no activity.: when to run continuously, in bursts or with a base plus peaks. Apply it per market, so spend rises before each market's peak and not before the home market's. The marketing budget calculator works the totals from goals; the calendar decides when they are spent.
Publish one calendar with a market filter
Publish a single calendar that everyone works from, with a market field on every item and saved views for each market, the global layer and the central team's cross-market view. The content calendar template and the editorial calendarA shared schedule of what content will be published, on which channel, when and by whom. for each language plug into it as linked detail rather than separate copies. A market owner should be able to open their view and see everything that will reach their customers, including global work, in their own clock.
Review it with market owners each quarter
Hold a short review with every market owner each quarter: confirm the next quarter's dates, update moments that moved, record lead times from the jobs just finished, and add each market's lessons from the last peak. Track a small set of key performance indicators (KPIA metric tied directly to an objective.) about the calendar itself, such as items that launched on their planned date and localised editions that went live with the global launch, so the review has evidence. A calendar that is not reviewed by the people in the markets becomes the home calendar again. The multi-market marketing operations playbook holds this review beside the budgets and partners for every market, so the calendar stays part of a standing programme rather than a yearly file.
Calendar columns for several markets: a table
The campaign calendar guide lists the fields every item needs. A calendar for several markets adds these:
| Field | What it holds | Why it is there |
|---|---|---|
| Market | The market or markets the item reaches, or "global" | Drives the filter and every clash check |
| Layer | Global, market moment, season, launch, content, promotion, freeze | Shows whose decision the item is |
| Language | The language edition the item runs in | Links the item to its localisation work |
| Local live date and time | Date and time in the market, with its time zone | What the customer experiences |
| Account time | The same moment in the publishing system's time zone | What the scheduler must enter |
| Localisation milestones | Brief, translation, in-country review, sign-off dates | Makes lead times visible and owned |
| Source of the date | Market owner, partner, agency or sales history | Lets the review check where a date came from |
| Market owner | One name per market | Who approves the market's view |
| Budget by period | The market's spend in each period | Phases spend against the market's own peaks |
| Status and confidence | Confirmed, likely, provisional | Drives the quarterly review |
A stationery brand plans its year across markets (illustrative)
Nemrazzo Stationery builds one calendar for three markets
Nemrazzo Stationery, an invented maker of notebooks and pens, builds one calendar for its home market, Market A and Market B. The global layer holds 3 moments: a spring product launch, an autumn brand campaign and the financial year-end.
Market B's owner submits 11 local moments. Its back-to-school peak falls 5 months away from the home market's, so the autumn campaign, built around back-to-school at home, moves to Market B's peak, with its own budget phasing; the media plan puts 40% of Market B's annual spend into the 8 weeks before it.
Working backwards from the spring launch, past jobs show Market A's edition needs 6 weeks for transcreation and in-country review; the central plan had allowed 3. The Market A brief moves 3 weeks earlier, and the reviewer's 2-week holiday, flagged in the clash check, is planned around.
Every release lists the market's local time beside the account's. The spring launch goes live at 08:00 in each market, which in the shared ad account's time zone is 08:00 for the home market, 02:00 for Market A and 15:00 the previous day for Market B. At the first quarterly review, 14 of 16 items launched on their planned date, and both localised launch editions went live with the home launch.
Common mistakes
- Stretching the home calendar. Home holidays, seasons and peaks do not apply elsewhere. Build each market's layer from the market.
- Compiling local dates at head office. A general list misses what customers notice and includes what they do not. Ask each market owner, and record the source.
- Dating launches without localisation lead times. Work backwards from the live date with the business's own past lead times, or the edition misses the launch.
- Writing release times in one clock. Show the market's local time and the account's time on every release.
- Freezing only the home market. Each market has its own peak trading weeks; mark freezes per market.
- Phasing budget on the home pattern. Spend should rise before each market's peak, not the home market's.
- Separate calendars per market. Clashes between global and local plans stay invisible. Keep one calendar with a market filter.
- Never reviewing it with the markets. Dates move and lessons accumulate; review each quarter with the owners.
