COMP3 Book a walkthrough →
Features

Building Regulations Principal Designer software, modelled from statute.

Each feature below is a modelled capability in the MVP, not a concept drawing. Every status, every interface, every flag connects back to a statutory duty with its verification status on record.

Compliance Map

Parts A–T Compliance Map

The engine determines which Building Regulation Parts apply to your project. You assign each Part to the responsible designer. They submit evidence. You review, raise queries, confirm compliance. The review trail becomes your evidence. If a Part has linked design interfaces that haven't been resolved, it's blocked from confirmation.

Confirmed Under review Query raised Not assigned

Parts shown are those in force in England. Part N was revoked and its provisions consolidated into Part K.

Interface Management

Design Interface Management

Structural depths shape ceiling voids. Voids shape M&E routing. Routing shapes fire compartmentation penetrations. COMP³ tracks every interface, and a Part can't be confirmed while a linked interface is unresolved. A recurring theme in BSR commentary on Gateway 2 outcomes.

Interface typeStructural ↔ Fire
Parts affectedA, B
DesignersStructural Eng · Fire Eng
StatusResolution Proposed
Zero-friction coordination

Your designers don't need accounts.

Every designer you assign gets a secure link to their Parts: submit evidence, respond to queries, resolve interfaces. No licences or logins, and nothing for your design team to install. You get the coordinated record either way.

portal.comp3.co.uk/…f8a2
DesignerStructural Eng
AssignedParts A, B
Status2 submissions pending
★ Differentiator AI-Assisted Evidence Intelligence

It doesn't just store your evidence. It reads it.

Three checks fire on every upload. All advisory. None blocking.

01Per-document QA
A fire strategy on Part B is checked for means of escape, compartmentation, external fire spread, and firefighter access. Missing items get flagged.
02Cross-Part consistency
Compares assumptions across designers — Part A's slab depth vs Part L's ceiling void vs Part B's compartmentation — and flags where the design doesn't add up.
03Competence matching
A designer assigned Part B without a fire-safety competence record? Flagged. You decide what to do.
We haven't seen another tool that does this. Document checkers read one file at a time. Form-fillers don't read content at all.

We test the checker against fixture documents with deliberately seeded errors before we trust it with yours.

⚠ Cross-Part inconsistency · Riverside Tower
Part A structural submission assumes a 300mm floor slab. Part L energy submission assumes a 200mm ceiling void. At the stated 2.7m floor-to-floor height, these may not be compatible with Part B compartmentation locations.
Escalate to designers Dismiss with justification View linked evidence
Advisory only Doesn't block uploads Doesn't override judgement Never authors documents Every check audit-logged
HRB · Gateway 2

Gateway 2 Readiness

A dedicated view tracks BRCS, Fire & Emergency File, Change Control, Mandatory Occurrence Reporting procedures, competence evidence and drawings. Validation readiness (is it present?) is shown separately from approval readiness (is it internally consistent?).

BRCS82%
Fire & Emergency File64%
Change Control Plan48%
Competence evidence91%
Mandatory Occurrence Reporting22%
Non-HRB

Full Plans Support

BRPD applies to every project with more than one contractor (or where that's reasonably foreseeable) — not just HRBs. For non-HRBs, COMP³ generates a Full Plans Compliance Summary for Building Control. Different output, same reasoning engine.

Full Plans Compliance Summary v2 · Birch Mews
Generated
Change Management

Design Change Management

Design changes don't stop at first submission. Log a change — COMP³ flags the affected Parts, the designers who need to respond, and the evidence that needs updating. For HRBs, this feeds straight into your Change Control Plan.

CHG-014 · Facade buildup revisionParts B, L · 3 designers
CHG-015 · Refuge dimensionsPart M · 1 designer
CHG-016 · MEP riser relocationParts B, F, J · 4 designers
Live register

The register that re-reasons.

Projects change. When the context changes, the engine re-runs: newly triggered duties activate, evidence that no longer holds is flagged, and the affected Parts and designers are identified. A static tracker is wrong the day after the first design change.

Storeys6 → 9
HRB statusRe-derived
Duties4 activated
Evidence2 items flagged stale
Recurring Duties

Recurring Duty Management

Some BRPD duties are processes, not documents — fortnightly coordination reviews, RIBA stage-gate reviews, designer monitoring. COMP³ models them as recurring actions with configurable cadence. Every log entry becomes timestamped evidence. The trail builds itself.

Dual Role Clarity

CDM PD / BRPD Dual Role

Hold both CDM PD and BRPD on one project? COMP³ shows CDM duties separately from Building Regs duties. Role confusion between the two appointments is a recurring theme in Gateway 2 feedback.

CDM 2015 · Health & Safety
PCI compilation
Designer risk coordination
Pre-construction info pack
BSA · Building Regs
Parts A–T coordination
Design interface management
BRCS / Gateway 2
Handover

BRPD → BRPC Handover

At design sign-off, COMP³ auto-generates a draft handover pack from your Part-by-Part records, interface resolutions, and fire strategy coordination. The BRPC sees what's approved, which Parts apply, what evidence is still needed, and the assumptions underpinning the design. No more inferring from drawings.

Design Compliance Handover Pack · v1 draft
Auto-generated
Reporting

Export & Reporting

Compliance status reports, Gateway 2 submission index, pre-populated BRCS template, audit trail export. The outputs BRPDs share with clients, Building Control, and the BSR.

BRCS_RiversideTower_v1.pdfExport
Gateway 2 Submission Index.xlsxExport
Audit_Trail_Q2_2026.csvExport
Compliance_Status_Report.pdfExport
Getting COMP³

Access is by walkthrough.

COMP³ is in validation with founding users ahead of production release. The way in is a 20-minute walkthrough on a realistic project scenario for your role. If it earns a place in how you work, you can reserve a founding-user position for the production cohort.

Pricing is per BRPD appointment, tiered by project complexity, with a light annual platform fee per organisation. We will take you through the numbers on the call.

Common questions

The real objections, addressed.

No. Checklists assume you already know what applies to your project. COMP³ is a reasoning engine. It determines which obligations apply based on your project's specific context (building type, height, use class, HRB status, contract type) and generates a personalised register. Change your project context, and the obligations change with it. Templates can't do that.
No. The compliance logic is deterministic. Given the same project inputs, COMP³ always produces the same obligations. The AI layer does three things: it extracts project data from uploaded documents (so you don't have to type it all in manually), it checks whether uploaded evidence appears to address expected requirements for each duty, and it cross-references evidence across Parts to flag potential contradictions between designers' submissions. The AI never creates duties, never classifies your project, and never makes compliance determinations. It reads and compares. You decide what to do with what it finds.
The reasoning engine is built on a structured regulatory model. Every duty is mapped to its primary statutory source (Building Regulations 2010 as amended, Building Safety Act 2022) and verified against legislation.gov.uk under a documented methodology, with verification status recorded per duty. Independent review by a chartered subject matter expert is a release gate: no production version ships without it. COMP³ does not replace professional judgement or legal advice. It gives you a structured starting point that is better than a blank spreadsheet. How we verify.
The engine reassesses. When project context changes (a new designer, a scope alteration, a change of use), COMP³ re-runs the reasoning and flags every affected duty, every impacted Part, and every piece of evidence that needs updating. See how re-reasoning works. Design changes are logged with structured fields showing which Parts and designers are affected, and the system generates the compliance impact assessment. For HRB projects, this feeds directly into your Change Control Plan contribution.
Those tools work downstream. Templates give you a document to fill in but don't tell you which ones apply to your project. Practice management tools digitise your existing process but don't reason about obligations. Consultants give you expert advice but charge by the hour and don't build your evidence trail. COMP³ operates upstream of all three. It tells you what your obligations are before you create the documents, and builds the evidence as you work.
Yes. The BRPD obligation applies to every project requiring Building Regulations approval with more than one contractor (or where that's reasonably foreseeable) — not just higher-risk buildings. For non-HRB projects, COMP³ generates a Full Plans Compliance Summary instead of an HRB BRCS, and the Gateway 2 features are suppressed. The Parts A–T compliance map, designer coordination, design change management, and evidence trail work identically. What a BRPD is and when the role applies.
Yes, explicitly. When you confirm both roles in the project wizard, COMP³ shows your CDM obligations and Building Regulations obligations as separate, clearly distinguished sets. CDM PCI focuses on health and safety risk information. BRPD coordination focuses on Building Regulations design compliance. Role confusion between the two appointments is a recurring theme in Gateway 2 feedback. COMP³ makes the boundary visible.
COMP³ covers England and Wales, including Wales's higher-risk building regime introduced in July 2026. Scotland and Northern Ireland operate separate building standards frameworks and are on the roadmap.
COMP³ is UK-hosted. Your project data is yours. We don't use it to train AI models. During the current demo and validation phase, sessions use realistic mock data scenarios. No live project data is required.
Book a Walkthrough

See COMP³ on a project like yours.

A short walkthrough on a realistic project scenario — HRB or non-HRB. See the reasoning engine in action. Tell us where it gets it right, and where it doesn't.

20 minutes. No commitment. No sales pitch.

Book Your Walkthrough → info@comp3.co.uk
Prefer email? info@comp3.co.uk