About
Calm. Competent. Trusted.
The construction system that signs nothing for you.
Loadbearer exists because UK construction has tried to digitise the document for thirty years. It has not worked. The document is not the problem. The contract is the problem — and nobody put the contract on the working surface. We did.
The story
Why Loadbearer exists.
Construction software has spent three decades trying to digitise the document — the drawing, the form, the PDF, the report. Some of it works well. None of it digitises the contract. The contract is the rule book. It is the clock. It is the money. It is the law that governs who is liable when the programme slips and who was supposed to issue the notice that nobody issued. The contract lives in a drawer.
Loadbearer digitises the contract. Not the document that contains it — the logic inside it. Clause by clause, notice by notice, time-bar by time-bar. The contract becomes a queryable surface. Every event on site generates a recommendation that cites the clause behind it. A competent human reviews the recommendation and signs. That is the system.
The other half of the problem is the operative — the person whose hands build the job. Construction software has historically been written for the office. The operative was the recipient of a briefing, not the source of the system. Loadbearer inverts that. The safety record, the near-miss, the permit, the toolbox talk — they start on the operative's phone and flow upward. The CIO's view is downstream of that. If the operative does not pick up the phone, nothing else works.
The founder
Stephen Keogh
Twenty-plus years in UK construction delivery — hyperscale data centres, critical national infrastructure, and high-risk build environments. Programme director, project manager, delivery lead. The person who lived the failures this system fixes.
The missed time-bars. The contractor's narrative that arrived two months after the exposure. The operative who raised a near-miss and never heard what happened. The gateway evidence pack assembled at the wire. The QS who was on a different job the morning the Pay Less Notice window closed. These are not hypothetical. They are the list of things that Loadbearer exists to stop happening.
Founded Loadbearer in 2025. Building in collaboration with Innovate UK. The platform that is pitched will be the platform that is running — clickable, signed off, demonstrable end-to-end.
Cranebank — the demo world
A fictional site that holds the entire platform together.
Every workflow on every page in Loadbearer runs against the same fictional reference site: Cranebank — a £340M UK data centre delivered by main contractor Marauder Construction for client Phoenix Digital (CIO: Krupa). Three halls, three storeys per hall, six pods per storey: fifty-four pods total. CxA: Donnelly · Sentinel. Subcontractors: Apex Mechanical, Verdant Scaffolding, Halloran Electrical, Shankar Civils, Vasquez Drylining.
Cranebank exists to keep the demo coherent and honest. Every notice references the same contract. Every onboarding cascade pre-populates the same WBS. Every delay event is logged against the same baseline. When you see a number, it came from the same fictional record as every other number on the site.
There is no name in this universe that maps to a real person, project, or organisation. Where surnames appear in the persona dashboards, they are fictional placeholders for the disciplines, not for any individual. This honest framing matters because the platform is built for an industry where the names on sign-offs carry legal weight. We will not blur that line, even in a demo.
Four pillars
The principles that survive every product debate.
Recommendation-Only
Every output from Loadbearer is a recommendation. A suggestion. A draft. It carries no legal or contractual effect until a competent human reviews it, decides on it, and signs it. The system cannot decide. It can only surface.
AI Never Decides
Artificial intelligence is used to extract, classify, draft, and surface. It does not decide, certify, approve, or assume liability. Those acts belong to the named competent person whose signature is on the record.
Law First
Current UK legislation takes absolute and total priority over any contract clause, any system recommendation, and any user instruction. CDM 2015. Building Safety Act 2022. HSAW 1974. Where a contract clause conflicts with statute, the statute wins and the conflict is flagged.
One Record
Every persona — operative, PM, safety lead, QS, CIO, CxA — works from the same record, filtered to their role. There is no contractor's version and client's version. There is one record. Reconciliation is automatic, not a meeting.
Innovate UK
Co-developed under Innovate UK funding.
Loadbearer is being built in collaboration with Innovate UK's construction productivity programme. Innovate UK's remit is to fund and accelerate solutions to the productivity gap in critical sectors. UK construction sits at the top of the list — chronically under-digitised, perennially over-papered, and uniquely exposed to the post-Grenfell statutory reset.
The platform is aligned to the Building Safety Act 2022, the Higher-Risk Building (HRB) regime, the golden thread requirement, and the gateway sequence under BSA Part 3. The Cx Spine is designed around the chain-of-custody requirements that HRB gateways demand. The Contract-Aware Engine flags where contract clauses conflict with or fall short of statutory obligations under CDM 2015 and the BSA.
The platform that is pitched to Innovate UK will be the platform that is running — clickable, signed off, and demonstrable end-to-end. Not a slide deck. Not a prototype. The thing itself.