Hold Points That Actually Hold: Digitizing Alberta's Mandatory Inspection Gates

A hold point is not a reminder. It is a legal stop in the work sequence. Under Alberta's regulatory framework, specific construction activities — pressure welds, certain mechanical connections, safety-critical tests — cannot proceed until an authorized inspector has physically attended and signed off. Nothing moves forward without that signature. The paper version of this gate leaks. The digital version does not have to.

What hold points and witness points actually are

Every ITP (Inspection Test Plan) contains steps. Each step carries an intervention type: Hold (H), Witness (W), Review (R), or, in some frameworks, Surveillance (S).

Hold is the most strict. Work cannot proceed until the relevant party — the client, a third-party inspector, or a regulatory authority — has attended and signed off. If the inspector does not show, the work does not happen.

Witness is softer. The relevant party must be notified and given the opportunity to attend. If they do not attend within the required window, work can proceed — but the notification and the timeline must be on record.

Review requires document submission and sign-off before the next phase begins. No physical attendance required.

The distinction matters because the consequences of getting it wrong are significant: rework orders, regulatory non-compliance, project delays, and in pressure-rated work, safety implications.

Why paper breaks down

On a typical Alberta construction site, hold point management works like this: the QC coordinator keeps a log, sends notification emails, and hopes the right person shows up at the right time. If they do not, the site sometimes proceeds anyway — and the coordinator logs a waiver they may or may not be authorized to grant.

The information lives in emails, a shared spreadsheet, and the coordinator's memory. There is no system enforcing the gate. The hold point is advisory.

How we encoded the gate

In AIMQC, hold points and witness points are structural. They are not a separate checklist on top of the inspection workflow — they are built into the ITP step model.

ITPStep
  └── interventionType: Hold | Witness | Review | Surveillance
  └── notificationHoursRequired: number
  └── responsibleParties: string[]

HoldWitnessRegister
  └── status: pendingNotification | notificationSent | completed | waived | onHold
  └── notificationSentDate
  └── plannedDate
  └── releasedBy
  └── releaseDate
  └── waivedReason

When an Inspection Request (IR) is raised against an ITP step that carries a Hold or Witness type, the system does two things: it records the notification timestamp, and it blocks state advancement until the required condition is met.

The Hold/Witness Register is auto-generated from ITP steps. Every step flagged H or W across every ITP on the project appears in the register. The QC manager has a live view of every gate on the project — notified, pending, completed, waived — without maintaining a separate log.

The waiver path

Sometimes a hold must be waived. A regulatory inspector is unavailable; a client representative provides written authorization to proceed. The waiver path exists — but it requires a reason, an authorizing party, and a timestamp. It leaves a record. The system enforces that a waiver is a deliberate, documented act — not a quiet decision to move forward without telling anyone.

Why this matters beyond compliance

The hold point register is one of the most-referenced documents during turnover audits. Auditors want to see evidence that every mandatory gate was honored — or that exceptions were properly authorized. When that record lives in a spreadsheet, reconstructing it is hours of work. When it is a live register built from the ITP itself, the audit trail exists automatically.

David Olsson is CTO at AIMQC. Contact: dolsson@aimqc.com