The Paper Trail That Won't Retire: Britain's Stubborn Analogue Workflows

The machine in the corner

The fax machine is not supposed to be here. It belongs to the same mental cabinet as the Filofax, the fax-modem handshake and the phrase 'please find attached'. Yet in 2026 you can still find one humming in a solicitor's back office in Leeds, a care home in Devon, a builder's merchant in Glasgow, and more than a few corners of the public sector. It is not there because nobody has heard of email. It is there because something downstream still expects a page to arrive with a timestamp and a telephone number attached.

That is the first thing to understand about Britain's analogue habits: they are rarely standalone quirks. They are load-bearing. The fax is not a machine. It is a handshake between two organisations that have agreed, perhaps without ever saying so, that this is the format that counts.

Trust, not nostalgia

It is tempting to file all this under nostalgia or laziness. That is too easy. A wet signature on a contract, a printed email filed in a binder, a landline call tree that routes you through three recorded menus before a human answers: these are not romantic relics. They are trust mechanisms that predate the tools we now prefer.

A printed email feels evidential. A signed page feels final. A recorded phone call feels like something you could point to later. In sectors where disputes are expensive and regulators ask awkward questions, people reach for formats that have already survived an argument. Email is fine until someone needs to prove who sent what, when, and whether the attachment was the version that mattered. A fax carries a header. A wet signature carries a pen mark. A printed email carries the weight of having been physically handled.

That does not make these workflows efficient. It does make them sticky.

Compliance keeps the printer warm

Ask a UK SME why it still asks for a wet signature and you will often hear a version of: 'Because that is what the other side wants.' Ask the other side and the answer travels back around the loop. The requirement is not always in legislation. It is in habit dressed as compliance, or compliance interpreted once in 2014 and never revisited.

There are genuine legal and regulatory reasons for some analogue steps, especially in areas such as conveyancing, probate, care records and certain public-sector processes. But the full picture is messier. Many firms are maintaining a paper process because a counterparty, an insurer, a funder or a legacy system expects it. The fax survives not because the law demands a fax, but because a chain of dependencies has formed around one.

This is where digital transformation gets humbled. You can buy a shiny new client portal, but if the client's finance team still needs a signed PDF by close of play, the portal becomes a sidecar. You can move to e-signatures, but if one counterparty's legal team insists on a 'proper' signature, the printer stays plugged in.

The wet signature has a bodyguard

The wet signature is a good example because it has acquired a bodyguard of workarounds. Couriers, scanned PDFs, 'print, sign, scan, send' instructions, and the strange ritual of printing an email so that someone can sign the printout and email it back. None of this is irrational at the level of the individual transaction. It is just exhausting at the level of the system.

The cost is rarely visible in one line of the budget. It shows up as delay, rework, postage, storage, and the low-grade frustration of chasing a piece of paper around a business park. It also shows up as risk: paper gets lost, scanners jam, and the person who knows which cabinet holds the original retires.

How to retire one workflow without breaking the building

The wrong way to retire an analogue habit is to announce that it is over. The right way is to map what depends on it. Pick one workflow — not 'all paper', just one — and trace every place it touches. Who initiates it? Who signs? Who stores it? Who asks for it later? Which supplier, regulator or customer has a written requirement, and which is simply repeating an old instruction?

Then build a bridge rather than a cliff. Keep the old format available for the counterparties that genuinely need it, while making the new route the default for everyone else. Add a clear audit trail. Show where the record is stored. Explain how long it is kept. Give the nervous party a way to verify it that does not involve printing anything.

For a small British firm, the practical version might be simple: an e-signature tool with a proper audit log, a shared inbox rule that stops people printing emails, and a written note to key counterparties explaining the new process. For a larger organisation, it might mean a pilot in one department, a named owner, and a monthly check on how many faxes or wet signatures are still crossing the desk.

The fax machine will not disappear because someone declares it obsolete. It will disappear when the dependency map is empty, or when the cost of keeping it alive finally becomes more annoying than the cost of changing. Until then, it is not a museum piece. It is a small, noisy reminder that adoption is not a software problem. It is a trust problem wearing a phone cord.