BSR Information Requests: What "Show Me" Looks Like

The message is short, which is what makes it unnerving. A client's compliance manager, or the principal contractor's design lead, forwards something that begins "the Regulator has asked for" and ends with a date that is closer than you would like. It does not ask whether your records exist. It asks you to show them.

What's Actually Being Asked

The Building Safety Act 2022 and the regulations that came in with it did something quietly significant to the information about a higher-risk building: they made it something that has to be kept, kept current, and produced when it is asked for. The golden thread is not a report written at the end of a job. It is the building's safety information, held electronically, in a state where somebody who was not in the room when it was created can find it and understand it, and passed on when responsibility moves.

That obligation shows up as a request. While the Building Safety Regulator is assessing a gateway application, questions can come back before it decides, and on a higher-risk building it can require information at any point while it is checking that the work complies. During construction, change control on a higher-risk building generates its own trail, and the Regulator can ask about it. Once the building is occupied, the accountable persons hold the golden thread information for the parts of the building they are responsible for, and the principal accountable person holds the safety case report. Both can be called for. Different stages, same shape of demand: show me the information you are required to hold, in a form I can read, now.

The duty sits with the dutyholders and accountable persons named on the building. But none of them holds the whole record themselves, so a request that lands at the top comes back down the supply chain as a schedule of things each package has to produce. At that point the deadline you are working to is usually the one written into your appointment, while the building regulations already ask contractors on this work to co-operate and to pass on the information the client and the designers need. This is how these requests behave in practice rather than legal advice: what you owe, and by when, sits in your appointment and in the regulations that apply to that particular building.

The Evidence That Answers It

A "show me" request rarely asks for a narrative. It asks for records, and it asks for them in a state that lets a reader test them. For a specialist package, that usually comes down to six families:

• Design information for your scope. The details as issued, the revision the work was actually built to, and the reasoning behind the choices that carry risk: fire performance, structural fixings, interfaces with the packages either side of yours.
• Product and test evidence. Which system went in, which certificate or declaration of performance covers it, what the tested scope actually was, and the date. Any substitution needs the same treatment, including the justification for accepting it.
• Competence evidence for the people who did the work. Named individuals, on the dates they were on the job, against the scope they carried out. A company-wide training matrix on its own rarely answers this question.
• Installation and inspection evidence. Inspection and test plan sign-offs, hold points released, defects raised and closed, and photographs that can be tied to a location, a date and a person rather than sitting in a folder called "Site Photos".
• Decisions and changes. What changed, who agreed it, on what basis, and when. In practice this is often the hardest family to produce, and the one most likely to be pushed on.
• Transfer records. What information you handed over, to whom, and when. When the record moves between parties, the handover itself is part of the evidence.

Read that list back and notice what it has in common. Every item is a claim about a moment in time, and every item has to be tied to a part of the building. A request tests both. It is not enough to hold the certificate; you have to be able to show it was the certificate relied on for that element, on that date, by that person.

Why the Spreadsheet Version Fails

Plenty of contractors hold most of this somewhere, and still cannot put their hands on it quickly. The certificates are attached to an email from a supplier who has since changed account manager. The decision that matters was taken on a video call and survives as one line in a minute nobody indexed. The photographs are in a shared drive organised by month, so finding the fixing detail at level nine means scrolling through months of images. The competence matrix was accurate when it was built and describes a team that has since turned over. None of that is negligence, and it is worth saying so plainly. It is what happens when the record is a by-product of the work rather than part of it. The cost lands later, all at once: whatever window the request allows is spent on archaeology instead of answering, and the answer you eventually assemble is a reconstruction, which is the hardest thing to defend when someone asks how you know. A gap you can explain is a different problem from a record that cannot account for itself.

Keeping It Provable

The alternative is not more diligence at the end. It is moving the record into the work. When an inspection is signed off, the sign-off, the person, the date and the location are captured then, against the element of the building they describe. When a change is agreed, the decision and its basis go into the same record rather than into an inbox. When someone is put on a task, the competence evidence behind that is attached to the assignment, not to a separate matrix that ages quietly. Built that way, the record is a living one, anchored to the building, and a request stops being a project. You are exporting what you already hold rather than reconstructing what you once knew, and the difference is visible to the person reading it. A record built as the work happened tends to read like one. So does a record built the week before the deadline.

The Monday Checklist

1. Take one live higher-risk job and give yourself two hours to produce the full evidence set for a single element: one fixing detail, one fire-stopping penetration, one panel. How far you get is your real answer, and it is better to learn it now than under a deadline.
2. Write down who in your business would receive a request of this kind, and who actually assembles the answer. If those are the same overloaded person, that is a single point of failure worth naming.
3. Check your product and test evidence for the systems on live jobs: one register, with the tested scope and the date against each entry, and substitutions flagged.
4. Hold your competence records against the individuals named on current work, on the dates they worked, rather than against the company list.
5. Find where design and installation decisions are being recorded today. If the honest answer is email and meeting minutes, pick one place they will live from now on.
6. Agree with the main contractor what turnaround they will pass down when a request lands, and agree it before a request is on the table.
7. Confirm how long you keep this material after handover, and that it will still be readable and attributable when someone asks for it years later.

Where BrieXO Fits

BrieXO's FIELD bundle keeps daily site records, inspection and QA workflows, photo evidence, competence records and recorded decisions in one living record, anchored to the building, so the site-side evidence a "show me" request asks for accumulates as the work happens instead of being reassembled against a deadline. Design and commercial modules are on the roadmap. It supports your dutyholder duties; it doesn't discharge them, and nothing in it decides whether your evidence satisfies the Regulator. How that record maps to golden-thread information is set out on our golden thread software page.

Related reading:what the golden thread actually requires of specialist contractors, who evidences what, package by package, and the as-built record that survives handover.

George Sfica is a senior design manager at a specialist façade contractor, with 23 years in manufacturing and construction, eleven of them in façades and external envelopes, spanning fabrication, installation and design management, an MSc in Façade Engineering and an IFE Level 2 Certificate in Passive Fire Protection. He is the founder of BrieXO.