Hold Point vs Witness Point in an ITP: Choose and Run Each Clearly

The distinction is about the next action

In TfNSW G2, a Hold Point is a point beyond which the work process must not proceed without the Principal’s express written authorisation. Its Witness Point definition requires prior notice and gives the Principal the option to attend. These are useful examples, not universal definitions: other contracts can define control points differently.

Choose the control from the contract and risk

Start with explicit contract points and regulatory inspection requirements. Do not weaken a specified hold point by relabelling it as a witness point. If a control is not specified, propose the point to the responsible project authority for agreement rather than creating approval powers for a party that does not hold them.

For each proposed point, identify what will become inaccessible or materially harder to verify, what evidence is required before covering or proceeding, and who has authority to release the next step. A project may assign internal contractor checks separately from client or certifier points.

• Use H only when the project documents establish a stop and identify the release authority or approval route.
• Use W only after verifying the notice recipient, notice method and whether the contract permits work to proceed if the party does not attend.
• Keep surveillance, routine inspection and document review distinct where the project legend distinguishes them.

Make the point operable in the ITP

A usable control-point row names the exact work boundary, readiness condition, inspection or document evidence, notice recipient, notice lead time as stated in the contract, and the outcome that allows work to move on. Link it to the next activity so a supervisor can see the consequence.

Keep required approval separate from attendance. A person’s presence, silence, email receipt or inspection record is not automatically a release unless the contract says it is.

Plan the field record before issuing the row

The matching field record should let the team prove which location or lot was checked, which drawing/specification revision governed it, what was observed or tested, where supporting evidence is filed, and what happened to any discrepancy. A signature box cannot create delegated authority; use the role and approval route assigned by the project.

Fictional example: bathroom membrane before tile installation

Fictional teaching scenario only. A contractor’s approved project quality plan assigns the builder’s quality lead a hold point before tiling, while the contract gives the client representative a witness opportunity for the pre-cover inspection. No real project, legal rule, membrane value or inspection result is represented.

1. Identify the room/zone and approved drawing and membrane-system documents in the row.
2. The subcontractor submits a readiness notice and records the substrate, junction, penetration and membrane evidence required by the approved project documents.
3. The contractor’s assigned quality lead reviews the evidence and records the hold release using the project’s approved process. Tiling remains stopped until that release.
4. The client representative receives the contract-specified witness notice. Record attendance or non-attendance; apply the contract’s stated next step.
5. File the completed record and any issue/reinspection reference against the same room/zone.