The 3am Publish: Pre-Built Short Links for Councils and Utilities

There is a particular kind of quiet in a council comms team at 3am. Then the phone goes. A water main has gone, a gritter has hit trouble on a bypass, or the Met Office has moved a weather warning from amber to red. Someone in the duty room needs a public link in the next ten minutes, and the person who normally creates short links is asleep.

That is the moment a break-glass link kit earns its keep. Not a sprawling folder of every URL the organisation has ever used — just a small, pre-approved set of short links, redirects and QR codes that duty teams can publish without waiting for a comms officer to log on.

Start with the jobs, not the links

It is tempting to begin with a list of pages and work backwards. Better to begin with the situations that actually wake people up. For a council, that might be severe weather, school closures, bin collection changes, rest centre openings, road closures and emergency housing. For a utility, it might be supply interruptions, boil-water notices, sewer flooding and planned works that suddenly become urgent.

For each situation, ask two questions: what does the public need to know first, and where should they be sent? Often the answer is not a campaign page at all. It might be a live service status page, a map, a registration form for updates or a simple frequently-asked-questions page. The short link is the signpost, not the destination.

Keep the kit deliberately small. If it has forty links, nobody will remember which one to use at 3am. Six to ten well-chosen entries per organisation is usually enough, with a clear note on when each one applies.

Name it like a duty officer, not a brand manager

Short links live or die on naming. A duty officer should be able to glance at a list and know instantly which link is for a rest centre and which is for a bin collection change. That means plain, functional names rather than campaign slogans.

A useful pattern is service, scenario and location, in that order. Something like council-name/rest-centre-north or utility-name/supply-update-area-3 tells the story without a decoder ring. Avoid dates in the short link itself unless the link is genuinely date-bound, and avoid internal jargon that means nothing outside the building.

This is also where QR codes need a little care. A QR code printed on a rest centre notice or a temporary road sign should point to a short link that can be redirected later if the destination changes. Do not encode a deep URL that will be stale by lunchtime.

Approve the link, not every message

One of the biggest delays in an emergency is not creating the link. It is waiting for sign-off on the wording around it. A break-glass kit cannot remove the need for sensible approvals, but it can separate two things: the link destination and the live message.

Get the destinations approved in advance. That means the page owner confirms the page will stay live, the content lead confirms it is suitable for public use, and the comms lead confirms the short link and redirect are acceptable. Record who approved what and when. Then, when an incident happens, the duty team can publish the approved link alongside an operational message without reopening the whole debate.

This is not about bypassing governance. It is about doing the slow thinking on a Tuesday afternoon so that the fast publishing on a Saturday night is still safe.

Test on the worst phone in the building

A link that works on a desktop in the comms office is not necessarily a link that works on a wet phone in a car park. Test every break-glass link on a cheap handset, on a slow connection if you can simulate one, and with the browser cache cleared. Check the redirect chain. Check the landing page on mobile. Check that the page does not sit behind a login or a cookie banner that swallows the whole screen.

For QR codes, print one out and scan it from the distance someone would actually scan it — from a noticeboard, a van door or a temporary sign. If it needs a magnifying glass, it is not a public safety tool.

Store it where the duty rota lives

A break-glass kit that lives in one person's bookmarks is not a kit. It needs a home that duty teams can reach without hunting through shared drives. That might be a pinned page in the incident management system, a printed card in the duty folder or a short internal link that itself is easy to remember.

Keep the public-facing links and the internal instructions together. The kit should say what each link is for, who owns it, when it was last tested, when it expires and who to call if it breaks. A one-page table is often enough.

Keep the tracking clean

Emergency links and campaign links should not share the same tracking parameters. If a break-glass link is tagged like a seasonal marketing campaign, your analytics will be muddy for months. Use a separate naming convention for incident links, and make it obvious in reports that these clicks are not part of business-as-usual acquisition.

That does not mean abandoning measurement. It means measuring the right thing: whether people reached the service information they needed, whether they clicked through to the relevant form, and whether the link held up under pressure. A simple UTM set or an internal reference code is enough. The point is to keep emergency traffic distinguishable from the rest.

Expiry dates and link rot

Break-glass links should not live forever. Set a review date, and retire links that are no longer needed. A redirect that once pointed to a rest centre page should not quietly send people to a closed page two years later. If a link is seasonal, say so. If it is incident-only, give it an expiry and a named owner.

Link rot is especially dangerous in public service because people trust the link they were given. A dead short link during an outage is not just an inconvenience; it undermines the next message too. Treat the kit as a living document, not a one-off project.

The handover note matters

The final piece is the handover. Duty teams change. Agency support changes. The person who built the kit moves on. Leave a short note that explains the logic, the approvals, the testing routine and the review date. If someone new picks it up at 3am, they should be able to use it without a induction session.

A good break-glass kit is unglamorous. It is a short list, a clear owner, a few tested redirects and a storage place everyone can find. But when the phone goes at 3am, that unglamorous preparation is the difference between a public message that lands and a comms team scrambling for a login.