The Golden Thread, Assembled As You Go
Applications do not usually fail because the building is wrong. They fail because the documentation is generic, and documentation is generic when it gets assembled at the end by someone reconstructing decisions they were not there for. ScopeKit structures the golden thread across twelve information categories while the work is happening, gates Gateway 2 packs on evidenced competence, and records duty holder and Accountable Person acceptance.
15-minute walkthrough. No credit card required.
What the regime asks for, structured
Gateway 2 and Gateway 3 both require the golden thread. These are the parts of that ScopeKit holds, and the points at which it refuses to let you move on without the evidence.
Twelve information categories, none of them silently blank
The Gateway 3 manifest always carries all twelve categories: competence declaration, construction control plan, change control log, mandatory occurrence reporting, health and safety file, drawings and plans, fire strategy, structural information, commissioning and testing, O&M information, as-built, and materials and products.
Every entry is sourced, or explicitly not applicable
Each category is linked to a real record, marked as external, or marked not applicable. There is no fourth state, so you cannot arrive at handover with a gap nobody chose. A gap has to be somebody's decision.
Competence evidenced before the pack exists
ScopeKit will not generate a Gateway 2 pack until the Principal Designer and Principal Contractor are both confirmed competent and carry an evidence document. Not a tick box. A document. Expiring evidence raises a warning so it is dealt with before it lapses.
Duty holder signatures against the current declaration
Duty holders sign with a drawn signature and typed name, recorded against the declaration text as it stood at the time. If the declaration changes later, you can still see what was actually agreed to.
External duty holders sign by secure link
Duty holders outside your organisation sign by secure emailed link. They do not need a ScopeKit account, which matters when your Principal Designer sits at another firm entirely.
Accountable Person acceptance
The Accountable Person reviews the manifest and accepts it by secure emailed link, so handover is a recorded event with a name attached rather than an email with a zip file on it.
Re-handover is versioned, with a reason
Buildings change hands and Accountable Persons change with them. Each handover version records why it happened: initial, sale, change of Accountable Person, or other. You reissue rather than starting again.
Built up over the job, not reconstructed at the end
The reason golden thread documentation reads as generic is that it usually gets assembled at the end, by someone reconstructing decisions they were not present for. Assembling it against a fixed structure as the work happens is what makes it specific.
Whose golden thread is it?
Worth being precise about, because a lot of software is sold to people on the wrong side of this line. Where you sit changes what you actually need.
The client
Initiates the golden thread before the design stage begins and sets up the system that holds it. At Gateway 3 they demonstrate they have shared it with the Principal Accountable Person.
The principal contractor
Manages the golden thread relevant to their building work, using the system the client set up. They hand over their part and are judged on whether it is accepted.
Everyone else in the chain
Contributes. Most specialist and tier-2 contractors are here: producing competence declarations, commissioning records, as-builts and materials evidence for somebody else's thread.
If you are a contributor, your problem is not managing a thread. It is being asked for something from four months ago, urgently, in a format nobody specified at the time. That is the problem ScopeKit solves for you.
Questions contractors usually ask
What buyers ask before signing up — answered straight.
01
Does ScopeKit make us compliant with the Building Safety Act?
No, and be wary of anyone who says otherwise. Compliance is determined by the Building Safety Regulator, and no software product is accredited, endorsed or approved by them. ScopeKit is readiness tooling: it structures the information you have to produce and keeps it traceable, so what you submit was built up over the job rather than assembled in a hurry. The judgement remains the Regulator's.
02
We are a subcontractor. The golden thread is not ours, so is this relevant?
Yes, and this is the part most software gets wrong. Under the regime the client initiates the golden thread and sets up the system that holds it, and the principal contractor manages the part relevant to their building work within that system. If you are a tier-2 mechanical or electrical contractor, you are a contributor, not the owner. Your problem is being asked for competence declarations, commissioning records, as-builts or materials evidence from four months ago, in a format nobody specified at the time. ScopeKit keeps your part structured from the start so answering takes an afternoon rather than a fortnight.
03
What actually stops us generating a Gateway 2 pack?
Two things, both about competence. The pack will not generate if the Principal Designer or Principal Contractor has not been confirmed competent, or if either is confirmed but has no evidence document attached. Evidence that has expired raises a warning rather than blocking, on the basis that competence was genuinely recorded at the time and the right response is to chase the renewal, not to freeze the submission.
04
Is this a full golden thread solution?
The golden thread is a regulatory regime, not a feature, so no product is the whole of it. What ScopeKit provides is the manifest across twelve information categories, sourcing for every entry, competence gating on Gateway 2, duty holder and Accountable Person signature capture, and versioned handover. How you run the buildings afterwards, and the obligations that sit with the Principal Accountable Person, extend well past any software.
05
What happens when the building is sold?
You create a new handover version and record the reason, which can be a sale, a change of Accountable Person, or something else. The previous version stays intact, so the chain of who accepted what, and when, survives the change of ownership.
06
Does this only apply to higher-risk buildings?
The Gateway regime applies to higher-risk buildings, so that is where the Gateway 2 and Gateway 3 tooling is relevant. The underlying capabilities are not exclusive to them: competence evidence, duty holder signatures and structured handover information are useful on any project where somebody will later ask you to prove what was done and who agreed to it.
Building Safety Act tooling sits alongside the wider compliance toolset. See pricing to compare what each tier includes.
Related features
Hand over something that was built up, not assembled
See how the golden thread manifest, competence gating and duty holder signatures work on a real project.
15-minute walkthrough. No credit card required.