The URL on the Form Is a Promise. Britain Keeps Breaking It.

A letter lands on the doormat. It is the usual mix of good intentions and small print: a council tax adjustment, an NHS appointment, a benefits review. Somewhere near the bottom is a web address. Not a fancy app link. Not a QR code. Just a line of text beginning with www, printed in a font that suggests someone once cared about readability.

You keep the letter, because that is what you do with official post. Three months later you need the guidance it mentioned. You type the address. The browser returns a page so blank it feels personal. Not found. No helpful redirect. No explanation. Just the digital equivalent of a locked door with the sign taken down.

This is link rot in the public sector, and it is not a niche webmaster problem. It is a service-design problem that lands on people who are already dealing with the state at its most administrative. A dead link in a letter is not a broken hyperlink. It is a broken promise with a timestamp.

Print is a CDN with no cache invalidation

Digital teams like to talk about content lifecycle. Printed letters do not have one. Once a leaflet, notice or appointment slip is in the post, it is immutable. It sits in a kitchen drawer, a wallet or a pile by the door. It may be read six weeks later or two years later. The URL on it, meanwhile, is living in a CMS that someone is about to migrate, a domain that someone is about to retire, or a section that someone is about to rename because the old name tested badly in a workshop.

That mismatch is the whole problem. Public bodies treat the URL as a bit of decoration on the page. Citizens treat it as the route to the answer. Both sides are reasonable. Only one side is planning for the future.

GOV.UK has generally been better at this than the long tail of local government, quangos and NHS trusts, partly because it has a central content team and a strong culture of redirects. But Britain's public services are not one website. They are thousands of domains, portals, PDF libraries and third-party forms. The further you get from the centre, the more likely you are to find a link that works in the office and dies in the wild.

What actually breaks

The causes are mundane, which is why they keep happening. A council consolidates its website and forgets to carry over old paths. A department moves from one case-management portal to another and leaves the old URL pointing at a homepage that no longer mentions the form. A shortlink service is decommissioned because nobody remembers who owns it. A PDF is deleted because it contained outdated guidance, but the letter that sent people to it is still in circulation. A page is renamed from housing-benefit to council-tax-support and the redirect is logged as technical debt.

None of these are dramatic. They are the ordinary weather of web operations. The failure is not that content moves. The failure is that printed material is not treated as a dependent system.

There is also a quieter issue: the URL often points to a generic landing page rather than the exact task. Even when it works, it can dump you on a homepage and ask you to guess which of 40 links is the one you need. That is not link rot. It is link drift, and it is almost as annoying.

The pre-print test

Any team that puts a URL on paper can run a simple link-rot test before sending the artwork to the printer. It takes less time than arguing about the font.

First, list every URL and QR code in the document. Not just the main one. Every one. Give each a named owner.

Second, test from outside the corporate network, on a mobile connection, in a private browser window. Internal networks have a habit of resolving things the public cannot.

Third, follow the full redirect chain. A 200 status is not enough. You want to land on a page that answers the question the letter is asking. If the final destination is a homepage, a search page or a contact form that requires a login, the link has failed in practice even if it has succeeded technically.

Fourth, check the page for the specific task. If the letter says 'visit this address to book your appointment', the page should let people book an appointment. If it says 'read the guidance', the guidance should be there, not a news article about the guidance.

Fifth, set a review date. Printed material has a shelf life, and so should the link. Put the URL in a register with a review date and an owner. When the page moves, update the redirect. When the redirect is retired, check what printed material still points at it.

Sixth, print a fallback. A phone number, a textual route through the site, or a short human-readable address that a person can read aloud. QR codes are fine, but they are not a universal access strategy. They are a convenience for people who already have a camera, a data connection and the patience to fight a cookie banner.

The promise on the page

There is a temptation to solve this with a new platform, a link shortener or a procurement framework. Britain does not need another portal. It needs public bodies to accept a boring operational truth: a URL on a printed page is a long-lived commitment. It should be stable, owned, monitored and redirected when it changes.

That means content teams and print teams talking to each other. It means redirects being treated as part of the service, not as cleanup. It means a council website migration plan that includes the leaflets already in people's kitchens. It means accepting that the person reading the letter may not be the person who typed the URL six weeks ago, and that they should not be punished for the gap.

The web is very good at moving things. Paper is very bad at following. Until public services design for that mismatch, Britain will keep printing promises that 404 at the exact moment someone needs them. And the citizen will be left doing what they always do: guessing which department has swallowed the guidance, and whether the phone line is open before 4pm.