Field

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

Every work package carries its inspection stages, its zone-by-stage matrix and its checklists. The controls that matter — hold points, sign-offs, open failures — sit on the record, not in a separate tracker.

Watch it run

One fire cavity barrier, specification to closed record.

A single inspection followed the whole way: the specification clause becomes a checklist, the checklist meets the drawing and the zone matrix, the subcontractor works it at the slab edge, the main contractor rejects it, and it closes on the second pass with the signature history intact.

Play the walkthrough1:31
0:03 / 1:311. Opener

Who works here

Quality manager

Needs to know which stages are closed, which are stuck at a hold point and which failures are still open — across every package.

The matrix answers it per zone, without chasing spreadsheets.

Package manager

Runs the subcontractor day to day and needs pre-start requirements, ITP and RAMS review in one place.

Package readiness and review sit on the package itself.

Site supervisor

Signs off work at the workface and needs the checklist, acceptance criteria and evidence requirements in hand.

The checklist item says what good looks like and what to photograph.

Packages and inspection plans

Packages start with a trade-specific stage sequence and linked checklists, then adapt to the project specification. An unrecognised package name still lands with a generic sequence — a package is never created empty.

  • Work packages with seeded inspection stages
  • Four gate types: hold point, trade handover, standard, milestone
  • Zone-by-stage inspection matrix
  • Checklists with acceptance criteria
  • Evidence requirements on checklist items

ITP and RAMS as controlled documents

The two documents a main contractor reviews before a subcontractor starts get a document-control workflow rather than an inbox — including supersede and expire, so a newer revision replaces its predecessor and a time-limited RAMS lapses rather than sitting approved forever.

  • Six-state review workflow with submitter and reviewer signatures
  • Five-working-day review deadline
  • Escalation to project administrators two days past deadline
  • AI pre-review reporting good practice as well as deficiencies

Controls on site

Hold points and trade handovers gate stage completion until the required sign-off is present. Open inspections and unresolved QA failures can block a stage from closing.

  • Hold points with witnessed release
  • NCRs raised against packages and locations
  • Permits to work
  • Trade handovers with sign and witness

Daily running of the job

Site logs, tasks and photo evidence keep the day-to-day record beside the packages it relates to.

  • Site logs with weather capture
  • Tasks with a controlled lifecycle
  • Photo evidence pinned to plans

An inspection, end to end

  1. 01

    Plan

    A zone assignment creates the inspection record against the right stage and checklist.

  2. 02

    Inspect

    The subcontractor works the checklist, attaches evidence and signs the result as available for inspection.

  3. 03

    Review

    The main contractor reviews, marks failed items and signs off — or rejects with the failures assigned for rework.

  4. 04

    Close

    Rework is re-attested and the record closes with the full signature history preserved.

Hold points and sign-off gate completion of the relevant stage; they do not lock successor stages from starting.

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.

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.