The Story That Killed a Company

Step Into the StoryComing Soon

The story ran on the front page. The correction ran on page two, three months later. In between, a company died.

Kesterley District Council put its waste and recycling contract out to tender for the first time in fourteen years. The long-standing incumbent lost. The contract went to a smaller family firm, run by a woman named Frances Aubrey, on a bid nine per cent cheaper — the kind of result that should have been a good news story.

Six weeks before the new contract was due to start, The Kesterley Clarion ran a front-page exposé: leaked council correspondence and a payment record that, the paper said, proved Frances Aubrey had bought the contract. The council opened an investigation. The new firm's lender pulled its funding within nine days. A firm mid-way through fitting out vehicles and a depot, suddenly with no financing and no ability to earn, doesn't survive that. Ninety-one jobs went. The council quietly reverted to the old contractor — which is the detail almost nobody notices, and the one that matters most.

Three months later, the Clarion printed a correction: the leaked material couldn't be authenticated, and the paper accepted the allegations were unfounded. Frances Aubrey sued for defamation. And that's where you come in.

You're working for the paper that might have ruined her

You're forensic investigators, instructed by the solicitors defending the Clarion, which is fighting this on a public-interest defence. Your job is to reconstruct exactly what happened to those leaked documents — because the defence, and the newspaper's own insurance cover, both turn on one question: was the newsroom fooled, or was it complicit?

That's not a comfortable position to investigate from. You're working for a client whose survival depends on what you find, and there's a real chance what you find sinks them anyway. Nothing here is a crime scene. It's disclosure — committee minutes, tender sheets, weighbridge tickets, newsroom copy, an insurer's own claim file — produced by people who all had reasons to shape what they handed over.

The forged documents are sitting right in front of you

Here's the part that makes this case genuinely different: you don't read a description of the forgery. You get the actual leaked package, exactly as the newsroom received it — and half of it is completely real. A genuine payment, to a genuine firm, for genuine work, made years before any of this started. The other half was built to sit next to it and borrow its credibility. Working out which is which, and who could possibly have built it, is the entire investigation.

Along the way you'll meet a reporter who's been suspended over a story that wasn't entirely hers to get wrong, an editor who cut a verification step that exists for exactly this situation, a councillor with a real and properly declared financial connection to one of the leaked documents, and a council compliance officer twenty-two years into a job nobody ever looks at twice. Every one of them can explain a piece of what happened. Only one of them built the forgery.

What you'll actually be doing

This one doesn't ask you to read someone's private inbox — it asks you to search institutional records the way a real forensic accountant would. You'll be comparing a document-reference format against a system migration date to catch an anachronism nobody meant to leave behind, cross-checking a company register against a client's own ledger, and doing arithmetic on a weighbridge ticket book that looks perfectly ordinary until you sort it by load type.

By the end, you'll need to say — clearly, and with the paperwork to back it up — who built the leak, how it survived a legal read on deadline, and why. Get the who right and the why wrong, and the case still doesn't hold.