Hold points vs witness points explained

Hold points and witness points are inspection gates built into construction projects. They appear in Inspection and Test Plans (ITPs), consent conditions, and contract specifications. Both require someone to verify work before it proceeds — but the consequences of missing them are very different.

On Australian infrastructure projects, these terms get used interchangeably. They shouldn't be. The distinction matters because one can stop your project dead and the other can't.

What is a hold point?

A hold point is a mandatory inspection gate. Work cannot proceed past this point until the designated person has inspected and formally released it. If you pour concrete over reinforcement that hasn't been released at a hold point, you've committed a non-conformance — regardless of whether the reinforcement was actually correct.

Hold points typically require:

• Formal notification to the inspector (usually 24-48 hours in advance)
• The inspector physically attends and signs off
• A written release before the next stage of work begins
• Documentation retained as quality evidence

Common hold points include: structural steel connections, reinforcement pre-pour, pile depths, subgrade preparation, waterproofing before backfill, and fire-rated penetrations.

What is a witness point?

A witness point is an optional inspection gate. The designated person is invited to attend and observe the work, but if they don't show up (or decline to attend), work can proceed without their sign-off.

The key difference: the contractor must still give notice and offer the opportunity to inspect. If the inspector chooses not to attend, the contractor documents that notice was given and proceeds. The work is not held.

Witness points are used for activities where the client or certifier wants visibility but where stopping work would be disproportionate. Examples include: concrete placement (after rebar hold point is released), formwork checks, backfill operations, and landscape installations.

Side-by-side comparison

Where they appear in your project

Inspection and Test Plans (ITPs)

ITPs are the primary source. They list every inspection activity for a scope of work with a column indicating whether each is a hold point (H), witness point (W), or review point (R). The ITP is usually a contractual document — either submitted by the contractor for approval or prescribed by the client's specification.

Consent conditions

Development consents and conditions of approval sometimes create hold points directly. A condition saying "no excavation shall commence until the geotechnical report is approved by the certifier" is functionally a hold point — even if it doesn't use that term. When you're reading your development consent, look for language like "prior to", "not until", or "before commencement of" — these create timing gates that function as hold points.

Contract specifications

Technical specifications (particularly in government contracts) prescribe hold points for critical activities. Transport for NSW, for instance, specifies hold points for pavement layer thickness, structural concrete, and drainage installations. These are contractual, not just quality management tools.

Common problems in practice

1. Notification failures

The most common issue. The subbie forgets to notify, or notifies too late. The inspector can't attend in time, and the work either proceeds without release (non-conformance) or the program takes a hit waiting for the next available slot. Build notification lead times into your program — don't treat them as same-day requests.

2. Confusion about which is which

Teams treat witness points as hold points (unnecessarily delaying work) or treat hold points as witness points (proceeding without release). Both are costly. The ITP should be unambiguous — if it's not, clarify with the superintendent before work starts.

3. Missing the hold point entirely

On large projects with hundreds of conditions, hold points embedded in consent conditions get missed because they're not in the ITP. The consent says "prior to any works within 5m of the heritage item, an archival recording must be completed and approved." That's a hold point. If it's not in your register, you'll miss it. This is one of the most commonly missed condition types.

4. No evidence trail

The hold point was released verbally on site but nobody signed the form, took the photo, or updated the register. Three months later when the auditor asks, there's no evidence of release. A hold point without documented release is the same as a hold point that was never released.

How to manage them effectively

• Map every hold point before work starts — extract them from the ITP, consent conditions, and specifications into a single register
• Set notification lead times in your program — if the hold point needs 48 hours notice, your program should flag the notification date, not just the inspection date
• Document every release — photo, sign-off, timestamp, who released it. This is your audit trail.
• Don't rely on email — notification by email is fine, but the release should be recorded in a system that the whole team can see. Emails get buried.
• Brief your subcontractors — they're usually the ones doing the work, and they need to know which activities have hold points before they mobilise to site