12 Mar 2026

Weekday send windows that survive a UK bank holiday

A send window that says “Tuesday, 10:00, BST” looks adult until the first May bank holiday. Recipients are not at a desk. Support is on a skeleton rota. The job still fires because nobody named the holiday as a clock, only as an out-of-office.

In the Davington studio we keep a public holiday table next to the seven-day map. It is not decorative. Each message family must declare: hold until the next civil working morning, send anyway because the event is time-critical, or switch channel. Password resets send anyway. A “we miss you” note does not.

The failure mode we see in UK product teams is importing an American weekday file and then adding Scotland, England, and a local council day as afterthoughts. Wales and Northern Ireland disagree with each other often enough that a single “UK holiday” boolean is already a lie. Notification Timing Optimization, in this country, starts with that disagreement on paper.

Practical rule from Send-Window Architecture: the holiday list has an owner with a surname, a review month (we use January and September), and a fallback if the owner is on leave. If your map cannot name that person, you do not have a window. You have a hope.

We also ask learners to pick one historical miss — a campaign that landed on a silent Tuesday — and rewrite the hold. The rewrite is usually boring: queue Sunday night, release 09:35 the next working day, log the delay as success. Boring is the point. Drama belongs in the copy, not in the clock.