COMP3 Book a walkthrough →
Introducing COMP³

The compliance engine for Building Regulations Principal Designers.

COMP³ tells you what you owe, why, and the evidence that proves it.

Describe your project in two minutes. The reasoning engine returns your obligation register: every duty, the actions it requires, and the evidence that proves it, mapped to Building Regulations Parts A–T.

Book a walkthrough → See how it works ↓
See COMP³ on a realistic project scenario for your role. 20 minutes. No commitment.
In validation with founding users. Production release follows independent SME review.
COMP³ BRPD Obligation Dashboard interface, showing Riverside Tower project with Parts A–T compliance tracking and a Why? drawer open on a duty.
Building Regulations 2010 (as amended) Building Safety Act 2022 PAS 8671:2022
The Problem

You accepted the BRPD appointment.
Now what?

The gap isn't knowledge. Most BRPDs understand their obligations in principle. The gap is execution.

The Building Safety Act 2022 introduced the BRPD role, with duties taking effect in October 2023 through the Building Regulations etc. (Amendment) (England) Regulations 2023. Breach of building regulations carries an unlimited fine and up to two years' custody on conviction on indictment. Regulations are scattered across statutory instruments. PAS 8671 reads like it was written to intimidate. The RIBA guide helps, but doesn't tell you what applies to your specific project.

You coordinate designers across the Parts in force with spreadsheets, email chains, and Word documents. Reinventing the tracker every project. Building competence statements from scratch. Whether you hold the appointment in-house or deliver it for clients, the process is manual and the record is fragile.

And it isn't defensible. If Building Control or the BSR asks how you discharged your duties, your evidence sits in inboxes, shared drives, and half-finished spreadsheets. The compliance trail you'd need doesn't exist as a coherent record.

How it works

From project context to a defensible compliance position in three steps.

The Why? Drawer

What you owe. Why you owe it. What happens if you don't.

Every duty has a plain-language drawer: what, why, who, when, what evidence, and what happens if it's missing, including criminal sanctions. Built into every duty. This is how COMP³ shows its reasoning instead of asking you to trust it.

Live example · From the BRPD duty model
Identify and manage design interfaces affecting Building Regulations compliance
NEW-BRPD-017
What
Identify where one designer's work affects another's ability to demonstrate Part compliance. Record, notify, and monitor resolution through design development.
↗
Why
Compliance depends on integrated design, not isolated discipline compliance. Fire compartmentation, fire protection, escape, ventilation, acoustics, energy, accessibility: all create dependencies between designers. Unmanaged interfaces are a recurring theme in why submissions fail.
◆
Who
The BRPD identifies and coordinates. The affected designers resolve the technical interface.
◷
When
After Part assignment, at each coordination review and stage-gate, and on any change touching multiple Parts.
▤
Evidence
Design Interface Register. Interface Resolution Records.
!
Consequence
Evidence that looks complete in isolation, but is internally inconsistent. A pattern repeatedly highlighted in Gateway 2 refusals.
Positioning

COMP³ doesn't digitise your paperwork.
It tells you what paperwork you need before you create it.

COMP³ answers the question nobody else addresses: based on your specific project — height, use class, building control route, design team structure — what does the law require you to do, why, and what evidence do you need?

And when that evidence arrives from multiple designers, COMP³ cross-checks it. It checks each document against its own Part requirements, and it checks whether the assumptions across Parts agree with each other.

The reasoning engine is built on a regulatory model verified against primary legislation, duty by duty: frameworks, duties, actions, evidence, and triggers, running deterministically. It reasons from statute.

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