Gateway 2 is where the paper promises of the Golden Thread meet the realities of design risk, procurement slippage and regulator scrutiny. Choosing software to carry your evidence from design freeze to approval is no longer a nice-to-have; it determines whether your principal designer, principal contractor and client can prove control of fire and structural safety information in a way a building control approver can follow without guesswork.
TL;DR
/>
– Treat Golden Thread software as a control system for evidence, not just a document store or BIM viewer.
– Write a spec that ties workflows, approvals and exports directly to Gateway 2 information requirements.
– Map roles for principal designer, principal contractor and supply chain, and lock down data ownership and retention in contracts.
– Test the export and audit trail on a real package before committing across the project.
– Measure value by regulator query turnaround time, audit completeness and substitution traceability, not by licence counts.
Writing a usable spec for Golden Thread platforms at Gateway 2
/> Procurement starts with being precise about the job to be done. For Gateway 2, that means setting out exactly which information must be structured, who approves it, and how it’s frozen and exported when the submission window opens. A workable spec clarifies the relationship between your existing common data environment and the Golden Thread tool: what lives where, how revisions flow, and which platform holds the “single source of truth” at the point of submission.
Translate your project’s information requirements into fields and workflows. If you expect product declarations, fire stopping details, structural assumptions and installation methods to be traceable, require the platform to capture those as structured attributes aligned to your classification (for example, Uniclass) and to maintain a visible audit trail from design decision to evidence. Insist on role-based approvals tied to dutyholder responsibilities, so a principal designer sign-off is not just a digital stamp but a permissioned action with a record of dates, comments and attachments.
Interfaces matter. The Golden Thread platform must pull information from models, drawings, RFIs, TQs and QA records, but also cope with site realities: patchy connectivity, photo capture by supervisors, and late manufacturer data that arrives as PDFs. Require offline capture and delayed sync, email-to-record ingestion, and the ability to link a field observation or product substitution to the design rationale that justified it. Don’t overlook competence: ask for a way to tie evidence to named people, their role and, where relevant, verification of competency.
Your export is your reputation. Beyond pretty dashboards, require a submission pack generator that outputs a coherent, bookmarked evidence set with cross-references, version identifiers and status states that a regulator can follow without needing your platform log-in. The spec should require open export formats, not a proprietary lock-in. Put time-boxed service levels for support and configuration into the contract; Gateway windows are unforgiving when a workflow needs tweaking the week before submission.
Interfaces, roles and risk you need to manage
/> There are moving parts across design, procurement and site delivery that determine whether the Golden Thread feels like governance or grief. The principal designer needs clear authority to set the information standard. The principal contractor needs a predictable path to collect, verify and freeze evidence from packages without stopping site progress. The fire engineer, structural engineer and building control approver need traceability without wading through duplicate uploads.
Scenario: A regional city centre high‑rise residential scheme is sprinting for Gateway 2. The cladding package is out to tender, the MEP coordination model is stable, but the fire strategy has just been updated after a late RFI on service penetrations. The principal designer wants to lock the design, yet the façade team warns that a preferred product may have a longer lead time, triggering a substitution. The site team is juggling delivery windows for the tower crane, while the digital lead tries to collate product data sheets that arrive as stitched PDFs from different suppliers. Building control has asked for a clear chain showing how each high‑risk element meets the strategy, with evidence of competent review. The Golden Thread platform is online, but permissions are too open, and a subcontractor has uploaded a draft datasheet that looks final. With two weeks left, the team needs the software to surface what’s missing, prove who approved what, and generate an evidence pack that matches the regulator’s logic.
Design the interfaces to avoid this pile‑up. Set a RACI for every evidence class and lock permissions accordingly. Demand configuration that highlights “near‑final” vs “approved for Gateway” states and prevents accidental overwrites. Tie product data to the model element or package, and force a substitution workflow that records the reason, impacts, approvals and re‑checks against the fire and structural strategies. Agree up front how decisions are captured when the regulator queries an assumption, and ensure your platform logs the response as part of the same thread.
Clarify ownership and retention. Contracts should state who owns the configured environment, how data is handed over at completion, and how long it remains accessible if the vendor relationship changes. Seek step‑in rights for the client, and specify that all structured data and files are exportable in non‑proprietary forms. Finally, recognise training as risk control: brief the supervisors and package managers who will actually upload and tag evidence, not just the BIM team.
# Common mistakes
/>
– Treating the Golden Thread as a filing cabinet and ignoring structured fields, which cripples your ability to show traceability at Gateway 2.
– Leaving permissions wide open so drafts appear “final”, creating confusion and rework when the submission pack is assembled.
– Assuming the CDE covers everything and discovering too late that approvals and audit trails don’t map to dutyholder roles.
– Setting the export format last, only to find the regulator-facing evidence needs reformatting under time pressure.
Proving value: measures that actually matter
/> You don’t measure Golden Thread software by the number of licences; you measure it by avoided delay and clarity under scrutiny. Start by baselining how long it currently takes to assemble a submission pack, and track whether the platform reduces that time without degrading quality. Monitor regulator query turnaround: how quickly can you trace a decision, surface the evidence and produce a clean response? Check substitution traceability: is every change discoverable with impacts and approvals in one thread?
Look at data cleanliness rather than terabytes stored. Sample packages for duplicate uploads, missing attributes and mismatched version states between model, drawings and evidence. Track training coverage for the roles that actually generate content: supervisors, package managers and design coordinators. Above all, test the export early by running a rehearsal submission for one high‑risk package and sitting a building control professional down to navigate it cold.
# Gateway 2 Golden Thread procurement checklist
/>
– Define the information classes you need (design decisions, product data, test certificates, installation methods) and map them to structured fields and approvals.
– Specify role‑based permissions tied to dutyholder responsibilities, with states that distinguish draft, for review, approved for Gateway and frozen.
– Require integrations for model metadata, email capture and site photo/video uploads, including offline sync for low‑connectivity areas.
– Mandate a substitution workflow that forces recording of reason, impacts, competence checks and re‑approval against fire/structural strategies.
– Insist on exportable, regulator‑readable packs with cross‑references, bookmarks, version IDs and open formats.
– Put data ownership, retention, step‑in rights and configuration IP into your contracts so the client isn’t stranded at close‑out.
Bottom line: pick a platform that enforces process discipline, makes evidence easy to find, and produces a clean submission pack without heroics. Watch for how quickly vendors adapt to evolving regulator expectations and whether manufacturer data becomes easier to import as standardised product information matures.
FAQ
/>
Do we need a separate Golden Thread platform, or can our current CDE handle Gateway 2?
Some CDEs can be configured to meet Gateway 2 needs, but many teams find they need additional workflow, audit and structured data capabilities. The key is whether your environment supports dutyholder approvals, substitution workflows and a regulator‑ready export without manual patchwork. If your CDE can do that reliably, you may not need a separate tool; if not, add a layer that fills the gaps.
# How should subcontractors interact with the platform, and who pays for access?
/> Subcontractors should contribute structured product data, installation evidence and sign‑offs within a defined workflow and permission set. Licencing models vary, so decide early whether to grant named access to key suppliers or to route uploads through the principal contractor’s coordinators. Build access expectations and data quality rules into package orders so commercial leverage supports compliance.
# What happens if a product substitution is proposed after Gateway 2?
/> Substitutions aren’t unusual, but they must run through a controlled process that re‑checks the fire and structural strategies. Your platform should capture the reason, impacted elements, competence of reviewers and new evidence, then flag the change clearly in the audit trail. Expect to communicate the change to building control and preserve both the original and revised decision records.
# How do we handle data ownership and retention at project close?
/> Set it out in the appointments and main contract: who owns the configured environment, who funds hosting, and how long the data remains accessible. Require a full export of structured data and files in open formats so the client can migrate to an asset information platform or archive as needed. Include step‑in rights so the client retains access if a vendor or party exits.
# What evidence formats work best for regulators, and how do we export them?
/> Regulators generally expect clear, legible evidence they can navigate without special software. Aim for a bookmarked, linked pack that cross‑references decisions, drawings, product data and approvals, preferably in open or widely readable formats. Test your export early and adjust your configuration so the pack reads logically to someone outside the project team.
