Features — COMP³ Compliance Engine for BRPDs

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

Interface Management

Design Interface Management

Structural depths shape ceiling voids. Voids shape M&E routing. Routing shapes fire compartmentation penetrations. COMP³ tracks every interface — a Part can't be confirmed while a linked interface is unresolved. The single biggest driver of Gateway 2 rejections.

Interface typeStructural ↔ Fire

Parts affectedA, B

DesignersStructural Eng · Fire Eng

StatusResolution Proposed

★ 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.

⚠ 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

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

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 is one of the most common Gateway 2 rejection causes.

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

See everything you owe. Free. Forever.

Create a project. Run the reasoning engine. See your full duty register and read the Why? drawer for every one of them. Free, forever.

When you're ready to act — assign Parts, track compliance, upload evidence, generate your BRCS — that's where the subscription starts.

Always Free

Understand

£0

✓Create a project and run the reasoning engine
✓AI-assisted project setup: upload a PCI or brief, fields pre-populated
✓Full obligation register with regulatory citations
✓Why? drawer for every duty: plain-language explanation, statutory basis, evidence requirements, criminal sanctions
✓See which Building Regulation Parts apply
✓Gateway 2 readiness headline score (HRB)
✓Red-flag compliance risk alerts

Unlocked on Subscription

Discharge & prove

Act

✓Action any compliance item — assign, track, evidence
✓Assign designers to Building Regulation Parts
✓Track Part-by-Part compliance with submissions and reviews
✓Upload and link evidence to duties
✓AI evidence QA: per-upload checks and cross-Part consistency flagging
✓Design change compliance impact assessment
✓Generate BRCS (HRB) or Full Plans Compliance Summary
✓Gateway 2 prescribed document tracking
✓Export reports and audit trail

The real objections, addressed.

Is this just another compliance checklist?+

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.

AIHow does the AI work? Is this AI-generated compliance advice?+

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.

Can I trust the regulatory accuracy?+

The reasoning engine is built on a structured regulatory model where every duty is mapped to its primary statutory source (Building Regulations 2010 as amended, Building Safety Act 2022, CDM 2015) and citation-verified against government legislation and reviewed by an independent subject matter expert. COMP³ does not replace professional judgement or legal advice. It gives you a structured starting point that's better than a blank spreadsheet.

What happens when my project changes mid-design?+

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. 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.

I'm already using the RIBA templates / a practice management tool / a consultant. Why do I need this?+

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.

Does this work for non-HRB projects too?+

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.

I hold both CDM PD and BRPD on the same project. Does COMP³ handle that?+

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. The confusion between these two roles is one of the most common Gateway 2 rejection causes. COMP³ makes the boundary visible.

Is my project data secure?+

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.

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.

A reasoning engine, not a checklist. Modelled from statute.