Sealing the consent.
Everything begins the instant the Regulator's Gateway 2 Consent Notice arrives. STRAND recognises it, asks a named human to confirm it, and — on that confirmation — seals the consented design as a read-only baseline and flips the whole project from assessment into continuous construction oversight.
A documented trigger
The transition fires only on the arrival of the Consent Notice itself — never a button someone presses. It's an observable, timestamped, document-evidenced event, exactly as the whole regime demands.
Confirmed by a human
STRAND recognises the notice automatically, then puts a confirmation in front of the competent person. A moment this consequential is never decided by the machine alone.
The design becomes read-only
At confirmation, every consented artefact is locked. From here nothing is edited into the design — changes are recorded as deviations against the sealed baseline, never as edits to it.
The team is told
STRAND notifies every relevant stakeholder that the baseline is sealed and construction oversight is live — warmly acknowledging the milestone, then getting to work.
From this instant, the consented design is the fixed point everything else is measured against.
Pre-construction.
Protecting the procurement.
Between consent and the first spade in the ground sits the phase that quietly drives the second-largest cause of cost overruns: procurement. STRAND compiles the pre-construction programme itself — reading the sealed design, the assets, the specification and real lead-times — and supports the contractor's commercial team all the way to a placed contract.
It compiles the programme
Not received from anyone — computed. STRAND reads the baseline, the specification and the lead-time information and builds the lead-time-aware, critical-path programme, then presents it for adoption.
Lead-times, chased at source
Non-standard components are identified and the specifiers who owe lead-time and interface information are chased directly — before a missing answer becomes a delay on site.
A mentoring posture
STRAND doesn't run the procurement and doesn't seize it. It holds the discipline, surfaces what should be considered, and stays present — the commercial team owns the decisions.
Contract language, tightened
It analyses contract wording for the ambiguity a contractor could later exploit — and won't wave through scope that carries known gaps. Ambiguity is closed before it's signed, not argued after.
Trust is extended at submission — then quietly verified, with consequence that escalates only as far as behaviour demands: supportive, then firm, then contractual.
The evidence ledger.
Once works begin, the building's evidence stops being something you gather at the end and becomes something that assembles itself as it happens. Every asset is a node in a living ledger; deliveries, materials, inspections and site records attach to it the moment they arrive — captured at source, never reconstructed.
Evidence, captured at source
Each component carries the evidence its type requires — data sheets, certificates, conformity, batch traceability — and its status is computed from what's actually arrived, never ticked off by hand.
Strict spec match on materials
Every delivery is matched against the specification. There is no "close enough" state — material can't be marked installed unless the match is clean or a substitution has been properly approved.
COSHH kept current, live
The COSHH register fills from deliveries as they land; a substance arriving without a current safety data sheet raises an RFI to whoever delivered it, automatically.
The daily diary drives the site
Absorbed daily-diary content updates the materials inventory, the programme, the risk picture and the COSHH register — and even regenerates worker-tailored induction and toolbox-talk prompts from what's actually happening on site.
The exhaustive, evidence-grade record isn't a by-product of the work. It is the primary deliverable.
Continuous ingestion.
A live site generates a torrent of paper — delivery tickets, inspection records, clash notifications, programme updates, change requests, regulatory correspondence. STRAND takes it all in by email, recognises each document for what it is, authenticates where it matters, and routes it to exactly the right place. Nothing is ever silently dropped.
Email-in, at volume
The way the industry already communicates — extended for construction-phase volume and variety, handling batches and multi-record attachments as batches, not one lost message at a time.
Authenticated where it counts
High-stakes document types require the sender to be who they say they are — up to a named individual with a valid signature. Authentication failure means quarantine, never silent acceptance.
Quarantine, not rejection
When a document can't be confidently classified, it isn't thrown away — it's quarantined and the sender is told. There is no "miscellaneous" folder where things quietly disappear.
Read without OCR
STRAND's own reader handles every PDF — with or without a text layer — and judges a document on its content, not its file format. Acceptance is about what's inside, not how it was made.
Every document received at STRAND's address is preserved and processed — whether the platform was up at that instant or not.
The oversight engines.
This is the continuous watch. As events arrive, STRAND's engines classify every change against the sealed baseline, price it, programme it, detect what must be reported, and — crucially — read the cumulative picture, catching the drift that no single change ever crossed. Every output is traceable to the event that caused it.
Change, classified against the baseline
Every change is measured against the protected design — its regulatory significance, its cost, its programme impact — and put in front of the right people with the reasoning attached.
The cumulative picture
Alongside each individual change, STRAND re-reads all prior deviations affecting the same subject. A dozen "minor" changes that together cross a line are caught — the failure mode that slips past everyone else.
Occurrences & incidents detected
Mandatory occurrence and reportable-incident conditions are surfaced the moment the evidence appears — flagged for the human decision the law requires, never actioned autonomously.
The cost of friction, made visible
Late answers and open questions carry a real, quantifiable cost — and STRAND surfaces it continuously, so information friction stops being invisible and starts being managed.
Success isn't measured in activity. It's measured in exceptions — and a well-run project produces very few.
Ask it anything.
One data spine — and no dashboards. Any stakeholder simply emails STRAND a question, in plain language, exactly as they'd email a colleague: how is the fire-stopping package progressing, where does the programme stand, what's outstanding on level six. A complete, tailored report comes straight back — in minutes. And the regulatory dossiers assemble themselves continuously in the background, so they're never scrambled together at the end.
A report for any question
No fixed screens to learn. Ask what you actually need to know and STRAND writes the report to answer it — tailored to the exact question, with every figure traceable back to the source document and the reasoning behind it.
Answered in minutes
Because STRAND has already done the work, the reply comes back in minutes, not days. Stakeholders correspond with STRAND directly — like a tireless colleague who has read everything and forgotten nothing.
Exceptions, not busywork
Reports lead with what needs attention, not raw volume — how many things are exceptions, measured against the project's own baseline. Few exceptions is the mark of a well-run job.
Dossiers, assembling themselves
The Gateway 3 application, the Reg 38 fire-safety pack, the FM handover and the safety case foundation build continuously from day one — request any of them at any moment and you get the current-state snapshot.
No screen to check, nothing to log into. You ask; STRAND answers — completely, in minutes, whenever you need it.