For UK main contractors

Construction assurance that is ready before the work starts.

BuildAssure gives every work package a trade-specific inspection plan, structured sign-off and connected project controls — without weeks of manual setup.

Book a walkthroughExplore the platform

Built for main contractors managing quality, evidence, risk and accountability across live projects.

Construction content already built in

104
Uniclass-coded package types
430
Seeded inspection stages
370
Stage checklists
2,934
Checklist items
2,612
Items with acceptance criteria
2,331
Items with evidence requirements

Counts describe the seeded content library, not customer usage — the 430 stages include 149 hold points and 21 trade handovers. Package content can be adapted to project requirements.

How it works

From package name to project-specific inspection plan

One workflow takes a package from a name to a controlled, specification-aligned inspection plan — with a human decision at every change.

  1. Step 01

    Create the package

    Name the package — Drylining, Curtain Walling, Fire Stopping, Mechanical Services. BuildAssure infers the trade from the package name and creates an appropriate starting inspection plan.

  2. Step 02

    Start with structured construction content

    Stage sequences, gate types, checklists, acceptance criteria and evidence requirements are linked automatically. If the name matches no known trade, the package still lands with a generic stage sequence and checklists — a package is never created empty.

  3. Step 03

    Review the project specification

    Upload the project specification. BuildAssure analyses it against the existing checklists and proposes clause-referenced amendments — additions, edits and removals tied to the clauses that require them.

  4. Step 04

    Keep humans in control

    Every amendment stays pending until an authorised reviewer accepts it, and reviewers can accept individual operations rather than the whole suggestion. Once a checklist has been specialised for a package, later updates to the built-in library leave it alone.

  1. Package name
  2. Trade classification
  3. Seeded stages and checklists
  4. Specification review
  5. Human approval
  6. Controlled inspection plan

Why it matters

Less setup. Stronger evidence. Fewer gaps between site and assurance.

01
Start without rebuilding every ITP structure
Packages open with stage sequences, checklists and evidence requirements in place, ready to adapt rather than author from scratch.
02
Make inspection requirements visible before sign-off
Acceptance criteria and evidence requirements sit on the checklist item, in front of the person doing the work.
03
Preserve who reviewed, signed, rejected or changed a record
Signatures, rejections and corrections are kept on the record in append-only histories.
04
Carry site information into meetings, risks and reports
Records raised on site feed agendas, registers and reports without being retyped into separate documents.

Capabilities

Four modules working on the same project record

Field, Assurance, Management and Location each handle a distinct part of delivery. Every record they create lands in the same structured project data.

Field

Control package readiness, inspection and evidence from pre-start through completion.

Work packages carry their inspection stages, zone-by-stage matrix and checklists. Hold points and trade handovers gate stage completion until the required sign-off is present, and open inspections or unresolved QA failures can block a stage from closing.

  • Work packages with trade-specific inspection stages
  • Zone-by-stage inspection matrix and checklists
  • Evidence capture against checklist items
  • Hold points, NCRs and permits
  • ITP and RAMS review
  • Site logs, tasks and trade handovers
Explore Field

Assurance

Turn assurance activity into managed findings, actions, risks and leadership reporting.

Audits run against structured templates, findings become owned actions, and lessons and risks stay linked to the audit that raised them. Red and Amber audit answers require an evidence note — enforced in the database, not just the form.

  • Audits and structured templates
  • Findings and tracked actions
  • Lessons and risk linkage
  • External response portals
  • Board and insight reports
Explore Assurance

Management

Connect live project records to the meetings and decisions that manage the work.

Meeting agendas can prefill from live project sources and carry previous open actions forward, so meetings start from the current record rather than a retyped pack.

  • Meetings with agenda prefill from live records
  • Actions carried forward between meetings
  • Daily briefings
  • Management plans and design issues
  • Project risks, lessons and reports
Explore Management

Location

Link inspections, issues and project records to where the work actually happens.

Upload and calibrate drawings, draw zones, mark up site plans and pin records to IFC models — so a record like “Level 03 – East Zone” means the same place to everyone.

  • Drawing upload and calibration
  • Zones and site plan markup
  • IFC models with record pins
  • Measurements and saved viewpoints
  • QR anchors on site
Explore Location

Site to meeting

Capture it once on site. Discuss it with the right people.

A site note taken at the workface can reach the meeting that resolves it without being retyped along the way.

  1. Voice note

    Supervisors dictate site notes as they walk the job.

  2. Automatic categorisation

    Rules-based, construction-specific tagging sorts the entry — no black-box classification.

  3. Company mention

    People and companies can be mentioned, so accountability is on the record.

  4. Evidence prompt

    Entries prompt for the photo or record that supports them.

  5. Flag for minutes

    Anything that needs discussing is flagged in one tap.

  6. Meeting agenda

    Flagged records and open follow-ups populate the meeting agenda.

Risk

A risk register built around treatment recording.

Not a list of worries — a record of what the exposure is, what is being done about it, and what the score should be once the treatment lands.

  • Threats and opportunities in one register
  • Current and target 5×5 scoring
  • Controls with recorded effectiveness
  • Mitigation actions with owners
  • Cost and time impact ranges
  • Evidence, score history and closure records
  • Links to audit findings
  • AI-assisted drafting from findings, reviewed before saving

Sign-off

Workflows with authority built in

Ready-made workflows for the sign-offs a main contractor already runs. Roles govern who can sign or reject, signatures drive status, and every decision lands in an append-only history.

  • Inspection sign-off
  • Hold-point release
  • NCR escalation
  • Trade handover
  • Permit to work
  • Builders’ work requests
  • Task lifecycle
  • Deliverable approval

Roles decide who signs

Each step names the responsible role. A subcontractor signs their work up to the main contractor’s review; the reviewer signs it closed or sends it back. The hold-point witness must be different from the releaser.

Signatures drive status

Status changes because someone signed or rejected — not because someone edited a field. Rejection preserves the entered work and invalidates the signature, so corrections are re-attested rather than redone.

Histories are append-only

Direct signature insertion is restricted and audit histories cannot be edited or deleted. Corrections happen as new recorded events, never as silent changes.

For assurance and IT teams — how the workflows are enforced

These are preset workflows, not a configurable workflow designer. Each one is a fixed state machine: the runtime canonicalises every advance to a sign or a reject, and the role required at each step is resolved per project.

Status is derived from the signature set rather than written directly, and a signature can only be created through a database routine that stamps the signer and the timestamp server-side — direct insertion is revoked, so a signer supplied by the client is ignored in favour of the authenticated session. A separate database trigger independently re-checks that the signer holds the required authority.

Record histories are append-only: updates and deletes are refused by the database across nine record types, so corrections are new events rather than edits. Rejecting a submission returns the record to the responsible party with field data preserved and signatures cleared.

Security and controls

Controls that do not disappear when someone bypasses the screen

Key controls are enforced beneath the interface, in the database, for user-originated writes. The screen is a convenience; the control is the constraint.

Row-level security throughout

Every application table in the public schema has row-level security enabled, backed by 890 policies scoping data to the organisations and projects that own it.

Append-only histories

Key record types keep append-only histories. Corrections are new events with a named author, never edits to what was recorded.

Authority checks in the database

Who can sign, reject or release is checked in the database for user-originated writes — not only in the interface.

Evidence rules enforced

Rules like “Red and Amber audit answers require an evidence note” are database constraints, so they hold however the record is written.

Immutable published reports

Completed insight reports are published as immutable snapshots. The pack the board saw stays the pack the board saw.

Read the full security and controls overview →

AI assistance

AI proposes. Your team decides.

BuildAssure uses AI for defined tasks with a review step, not as a layer over the whole product.

  • Specification-to-checklist amendment suggestions
  • ITP and RAMS pre-review
  • Drafting risks from audit findings
  • Meeting-template amendments
  • Report narrative assistance

The boundaries are deliberate

  • Suggestions are reviewable. Proposals sit in a pending state until a person accepts or rejects them, with the confidence, rationale and source pages shown alongside.
  • Sources are retained. Every proposed checklist change carries a clause reference back to the document that prompted it. Changes without one are dropped, not applied.
  • Approvals stay human. A specification amendment can only add, edit or remove a checklist item — there is no signature field in that vocabulary. A specification can change what gets checked; it cannot change who signs, in what order, or what signing does to the record.

See how BuildAssure would structure one of your live work packages.

Bring a package name, an ITP or a project specification. We will show how BuildAssure turns it into a controlled project workflow.

Book a walkthroughContact BuildAssure

BuildAssure

Construction assurance for main contractors.

Build Assure Limited, trading as BuildAssure · Company No. 16843792 · Registered in England & Wales · 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ.

© 2025 Build Assure Limited