Wednesday, October 7, 2026
They Buried
We Dug It Up
⌕ Search
ExplainerThe Republic

Ninety Minutes, No Phones, One Cut Cable. And 197 Breaches Caused By Daylight Saving.

The sealed room has never failed. The department's own five-year register, obtained on request, logs 214 embargo breaches: 197 were publishing systems firing an hour early. Three sanctions followed, two of them against the same four-person trade outlet.

Background written by the news staff. Contains no argument or recommendation.

?
Room 4.06 from the corridor side: sixteen desks, a high radio clock, and the box beside the door. Drawn from the correspondent's pencil notes. Engraved for They Buried

The box is not a safe. It is a box. Sixteen holes, a hinged lid, a brass hook, in use since 2011.

He then closed the door of Room 4.06 from the outside and stood in front of it for ninety minutes.

That is a statistics lock-up: sixteen desks, a clock, a monthly figure that moves the price of money, and a door held shut from the corridor side until 09:30.

We asked whether we could describe the room. We were told yes, on one condition — that we read the department's incident log as well.

Sixteen desks and one blanked faceplate

The desks are ordinary desks. Eight along each long wall, numbered on tape. There is a kettle.

The clock is radio-controlled. It is the only object in Room 4.06 that receives a signal from outside it.

By desk nine there is a data outlet with a blank plastic plate screwed over the hole. Somebody lifted a floor tile for us: four power runs, and one data run terminating in nothing. On the floor below, in riser cupboard 3.11, there is a taped cable end with a printed label reading DECOMMISSIONED and a date in November 2019.

A box, a door, a clock, and a socket that stopped being a socket seven years ago.

Figure The path a number would have to take to leave Room 4.06 early
Roof parapet, Corvin House0Level 5 · press officeNot part of the lock-up. Staffedfrom 08:15.−4.2mLevel 4 · Room 4.06, the lock-upSixteen desks, one clock, onedoor, one box.−8.1mRaised floor void, 600mmOne tile lifted for us. Four powerruns, one dead data run.−8.7mLevel 3 · riser cupboard 3.11A taped end labelledDECOMMISSIONED 11/19. Untraced.−12mDISPUTEDLevel 1 · communications roomWe were not admitted. Thedepartment says the run ends here.−20.4mIN NO PUBLISHED RECORDBasement · street duct chamberWhere a live run would meet thestreet.−24.9mIN NO PUBLISHED RECORD
Depths are measured down from the parapet and taken from the building's fire plan, which is public. Two levels are marked as being in no published record: our correspondent was not admitted to either, and the department's network schematic is withheld under the security exemption. The riser is marked disputed because we could see a taped cable end and a date on a label, and could not follow the run through the slab. They Buried, from the fire plan, the correspondent's notes and one lifted floor tile

What an embargo actually is

It is not a law. Nobody in that room has signed anything with a penalty clause. Pre-release access is a list — forty-one organisations, 108 named individuals — and the only sanction the department holds is removal from the list.

That is the whole mechanism. You get the number ninety minutes early so that what you publish at 09:30 is not nonsense. If you publish early, you can be taken off the list.

Two hundred and fourteen rows

We asked for the register in writing and had it in nineteen days: every detected pre-release publication from April 2021 to March 2026, 214 rows, one column withheld.

One hundred and ninety-seven of the 214 are automated scheduling faults. Not a person deciding to publish early. A content management system firing an item at the time it was told to fire it, in the wrong offset.

Seventeen were human. Seven were lines read out on air between forty and ninety seconds early. Four were notes sent to clients before the window opened. Three were social posts queued by hand. Two were regional print runs distributed early. One was a spreadsheet mailed to a list at 09:29.

The last Sunday in March

The 197 are not spread evenly. One hundred and twenty-one of them fall in the five working days after the last Sunday in March, which is the morning the United Kingdom moves to British Summer Time.

A scheduler holding an item at 09:30 UTC releases it at 10:30 once the clocks go forward, which is late and harmless. A scheduler holding it at 09:30 local, on a server whose clock has not been told, releases it at 08:30. That is an hour early, into a live market, and it is a breach.

Another thirty-one cluster in the three weeks each spring when the United States has changed and Britain has not, and the Atlantic gap is four hours instead of five. A release engineer reproduced both faults for us on a test system in under ten minutes.

The remaining forty-five are ordinary misconfiguration, scattered through the year.

Three sanctions

In five years the department applied a sanction three times.

Twice to Frayne Bulk Index of Hull: four people, a dry-bulk freight letter, no lawyer. Suspended six months in November 2022, removed permanently in February 2025, both times for a client note sent inside the window.

The other two client-note breaches in the same period were sent by organisations employing more than four hundred people each. Both were written to. Neither was suspended, and the department declines to name them.

The third sanction was applied to nobody. In March 2024 an account belonging to another government department published a derived chart at 09:26. The outcome cell reads: Referred. No action available.

What the room is for

The room works. It has held for ninety minutes a month since 2011 and the man who stands in front of the door says nobody has ever tried it.

Everything around the room is a spreadsheet, a clock-change bug, and a judgement about who can be removed from a list without it becoming a problem. The sealed part is the part that never fails, which may be why it is the only part anybody photographs.

Rosalind Teversham-Achebe's reply is below, in full, and it takes the word "cut" out of our headline with a maintenance ticket. It also contains a sentence we would not have got any other way: she has asked four times for a lockable cabinet to replace the wooden box, and been refused four times, and the cabinet costs about nine hundred pounds.

Sources & Method

We asked to be admitted to a lock-up as an observer and were, on the condition that we also read the department's incident log. We took no equipment in and wrote in pencil. We then requested the five-year register in writing, received 214 rows, sorted them by date, and had a release engineer reproduce the commonest fault on a test system so that we could watch it happen.

Who we spoke to

  1. Embargo incident register, 1 April 2021 to 31 March 2026, The department's own log of every detected pre-release publication. Requested in writing; released as a spreadsheet in nineteen days, 214 rows, with one column withheld May 2026 Published in full with this story. The withheld column is headed 'contact'. Forty-one outcome cells are empty.
  2. Rosalind Teversham-Achebe, Deputy Director for Statistical Publication. Interviewed twice in her office, once for fifty minutes; authorised the visit and read the full draft June and July 2026 Her reply is at the foot of this page and takes a word out of our headline. We kept the word.
  3. Bevis Nkemdi-Larkin, Security officer; holds the door of Room 4.06. Spoke to us for eleven minutes in the fourth-floor corridor, with his line manager's permission and his own July 2026 Has held the door on 118 releases. Says nobody has ever tried it.
  4. Desmond Frayne-Okoli, Editor, Frayne Bulk Index, Hull — a four-person trade letter on dry-bulk freight. Interviewed by telephone twice, and sent the passages about him before publication June 2026 The only subscriber removed from the list in five years. Employs nobody with a legal qualification.
  5. Ottilie Vasquez-Rennard, Release engineer; has configured publishing schedulers for three organisations on the list. Interviewed at a keyboard, and walked us line by line through a scheduler configuration on a test system July 2026 Supplied the demonstration of the offset fault described in the fourth section.

What we could not confirm

  • Whether the register is complete, or even close. It records what the department detected, and the department detects by monitoring publishing endpoints. A machine that fires early leaves a timestamp. A person who telephones one client at 09:28 leaves nothing at all. The ratio of 197 machine faults to 17 human ones describes what a monitor can see, and we cannot say it describes the world.
  • Whether the run we were shown in riser cupboard 3.11 is the run that once served Room 4.06. We saw a taped cable end and a printed label with a date on it. We could not follow the cable through the slab, and the network schematic that would settle it is withheld under the security exemption, which we did not challenge.
  • Why forty-one of the 214 outcome cells are empty. The department says they are duplicate entries generated when one publishing fault triggered two monitors. That is plausible and we could not test it, because testing it needs the contact column, which is the column we did not get.
Disclosure. This newspaper holds pre-release access to no statistical release and has never applied for it. Our correspondent was admitted as an observer, not a subscriber, and signed the same undertaking as everybody else in the room. No payment was made or received.

How Others Covered This

The same events, as reported elsewhere on the same day. We list what each outlet had that we did not, as well as what we had that they did not — including where we come off worse. Why we print this.

  1. The Hollow Post
    The Room Where The Number Is Agreed Before You Are Allowed To See It

    Took the lock-up as the place where figures are settled, and the ninety minutes as the window in which settling happens.

    Had that we did not

    The layout of the room, accurately, and credited to our published description.

    Left out

    That there is no machine in Room 4.06 capable of altering a figure, and that the department will walk any reporter through the point at which the number is frozen, which is the previous afternoon.

  2. Signal & Ledger
    Pre-Release Access: What Your Desk Must Change Before The March Changeover

    Read the register as an operations checklist and told subscribers how to configure a scheduler so the fault does not happen to them.

    Had that we did not

    The scheduler configuration itself, explained more clearly than we managed to explain it.

    Left out

    The sanctions column, entirely. Their readership is made up of the outlets large enough not to appear in it.

  3. They Buriedthis newspaper
    Ninety Minutes, No Phones, One Cut Cable. And 197 Breaches Caused By Daylight Saving.

    Sat in the room for the full ninety minutes, then read five years of the department's own incident log against what the room is supposed to prevent.

    Had that we did not

    The register in full, including the forty-one rows whose outcome column is blank and which we cannot account for.

    Left out

    We put 'cut cable' in the headline because of the picture it makes. It was decommissioned in a maintenance ticket in November 2019 by a contractor who pulled a run back and screwed a plate over the hole. Rosalind Teversham-Achebe told us this before publication. We printed her objection and kept the word. — V. Ashcombe-Doyle, standards editor

Right of Reply

They Buried contacted Rosalind Teversham-Achebe, Deputy Director for Statistical Publication on 26 June 2026 in person, and again on 29 July with the full draft, the sorted register and the figure, with fourteen days to answer. Replied in writing on 11 August 2026 and asked that it run whole. Printed unedited.

You have written a careful piece and you have called my incident log a breach register, and those are not the same document.

It is a log. We write down everything, including things that did not reach a reader, including things that were our fault, including the occasions where a system published a chart with no numbers on it eight seconds early. We log at that level deliberately, because an organisation that only records the incidents worth punishing very quickly stops finding out about the incidents worth fixing. You have taken a maintenance record and read it as a charge sheet, and then you have counted the charges and found them trivial. Of course they are trivial. That is what a good log looks like.

The 197 does not embarrass me and I would ask your readers to consider why. Those 197 are instrumented. We know about them because we watch publishing endpoints, we know within seconds, and twice a year the fault is the same fault and I know the week it is coming. Your own Unverified section makes the point better than I could: the failures I should be frightened of are the ones that leave no timestamp. I would trade you a hundred more logged machine faults for one fewer telephone call I will never hear about.

On Mr Frayne-Okoli I am going to disagree with you flatly, and I accept that I will lose the argument in print because he is four people and I am a directorate.

He was not sanctioned for being small. The sequence in his case was a letter, a second letter, a meeting he attended by video, a written undertaking he signed, a third letter, and then the same breach again fourteen months later. Two other organisations sent client notes inside the window in the same period. Both were written to. Both changed their procedure. Neither did it twice. You would like me to name them, and I am not going to, and I want to be precise about why: the letters work because they are not publications. The moment a first letter becomes a news story, the first letter stops being a way to fix something and becomes a thing to be resisted by lawyers. You are asking me to make my only effective instrument useless in the name of showing you that I use it fairly.

I would say the same of the entry you describe as a sanction applied to nobody. I have no power to sanction another department. Writing 'no action available' in an outcome cell is not indulgence, it is a statement of jurisdiction, and it is honest. What I did instead was ask for a change to the shared publishing platform, and I got it: since November 2024 that platform will refuse a scheduled publication time that falls inside another department's declared embargo window, and it has refused eleven of them. That is worth more than a sanction I could not have imposed. Your story has room for the sanction and no room for the eleven.

On the cable I simply think you are wrong, and I told you so, and I see from your standards column that you knew you were going to keep it anyway. Nothing was cut. In November 2019 the room went to a one-way feed and a contractor pulled a run back into the riser, taped the end, labelled it, and screwed a blanking plate over the outlet. There is a ticket. I offered you the ticket. 'Cut cable' is three syllables of theatre attached to a maintenance job, and every reader who remembers your headline in a year will remember a man with cutters and not a man with a screwdriver.

I will give you the box. The box is a box. I have asked for a proper lockable cabinet in four consecutive budget rounds and been refused four times on cost, and the sum involved is about nine hundred pounds. Print that. It is the most useful sentence in your piece and it is mine, not yours.

And your closing line, that everything around the room runs on a spreadsheet — yes. Everything around every room in this building runs on a spreadsheet. So, I would gently suggest, does your newspaper.

Published unedited under our right-of-reply guarantee.

How was this story?

We publish the result, whatever it is. Reader verdicts appear on the front page and in our newsroom metrics.

328 verdicts · 99.4% loved it

Readers' Letters 0

Printed at once under the name you give and read by the desk afterwards; anything unfit is removed, with a note saying so, and nothing else is ever deleted — only corrected. Letters that changed something in the story carry a mark saying so, and there are 5 of those across the archive.

  1. No letters yet on this story. Yours would be the first.

Write to the desk