Why does a London content calendar fail across Scotland and Wales?

What to take away

Why a London-built calendar drifts

Scotland and Wales run on the same clock as London. GMT and British Summer Time cover all of Great Britain.

The mismatch is in the working day. A London calendar assumes a commuter morning, an office lunch break and an evening scroll after the train home. Cardiff and Glasgow audiences may work shifts, start earlier or finish later.

Platform reporting will not flag this. A UK account usually reports in London time, so soft Scottish engagement has no visible cause.

Sources that should set your posting windows

Three ONS datasets carry most of the weight. The regional accounts break down economic activity by nation, so Scotland and Wales can be compared with London on the same footing.

The cultural identity releases cover national identity, language and belonging. They shape tone, and in Wales they shape timing too.

The employment and employee types data covers self-employment and working patterns, which move the usable windows.

Ofcom nation-level reporting adds viewing peaks and platform mix for both nations. The guide to audience research for social scheduling shows how to sample a regional audience before you commit to slots.

Dates that break a London grid

Scotland's school year returns in mid-August, weeks before England. Its October break falls in a different week and the summer term ends in late June or early July.

Welsh terms sit closer to England's but differ, and Welsh-medium schools can differ again. St Andrew's Day on 30 November is a Scottish bank holiday. St David's Day on 1 March is not a bank holiday in Wales.

Events pull attention too. The Edinburgh Festival runs through August and the National Eisteddfod moves each summer.

Example: one back-to-school push, three date variants

A retailer schedules its back-to-school push for the first week of September, when English schools return. Scottish pupils went back in mid-August, so the push reads as late.

Welsh timing sits nearer England, but Welsh-medium schools can differ. Term dates are one layer, and three dated checks for UK seasonal peaks covers the retail and cultural peaks sitting above them.

How to build and test region-specific slots

The grid below is an illustrative starting point, not evidence. Treat every time as untested until your own account data confirms it.

When one national calendar is still enough

Keep one national calendar when the message is genuinely nation-neutral, when the regional audience is too small to segment, or when the campaign window is short. Move the date table with it regardless, because holidays still shift.

Paid budgets need the same treatment as organic. A mis-timed first touch in Scotland builds a retargeting pool from the wrong moment, so the cost repeats.

Common questions

Do Scotland and Wales use a different timezone from London?

No. Both use GMT in winter and BST in summer, exactly as London does, so platform reports set to London time stay comparable.

Which sources should set regional posting windows?

ONS regional accounts, cultural identity and employment releases give the national picture. Ofcom nation-level reporting adds viewing peaks and platform mix. Your own twelve-week slot data sets the final times.

Do I need Welsh-language content and separate paid budgets?

Welsh-language feeds are a primary source for part of the audience, so the variant and its budget are worth planning separately. Cardiff and Belfast on bilingual scheduling compares the Welsh and Northern Irish markets.