An ITP is only as good as its sign-off chain. The document itself defines what gets inspected, but the sign-off workflow determines whether those inspections actually happen, who verifies them, and whether the record will hold up in an audit.
Most sign-off failures aren't technical — they're process failures. The inspection was done but never signed. The superintendent signed but the contractor didn't countersign. The document was signed off after the work had already proceeded. These are the gaps that a well-designed sign-off workflow eliminates.
This guide covers how ITP sign-off works from the inspector through to the principal contractor, what each party's role is, and how to avoid the common failure points.
The sign-off chain
On a typical Australian construction project, an ITP sign-off involves three to four parties:
1. The subcontractor (originator)
The subcontractor creates and owns the ITP. They perform the initial self-inspection, fill in the inspection results, and initiate the sign-off request.
Their role:
- Complete every inspection item in the ITP before requesting sign-off
- Attach any required evidence (test certificates, photos, measurement records)
- Confirm that all hold point prerequisites have been met
- Submit the document to the next party in the chain
2. The site inspector or quality manager
On larger projects, a dedicated quality manager or site inspector verifies the subcontractor's work before it reaches the superintendent. On smaller projects, this role is often filled by the subcontractor's own site supervisor.
Their role:
- Independently verify the inspection items against the acceptance criteria
- Confirm that hold point requirements have been met (not just checking a box — physically attending the hold point inspection)
- Record any non-conformances and require rectification before sign-off
- Sign off their section of the ITP
3. The superintendent or principal contractor's representative
The superintendent represents the principal contractor's interests on site. Their sign-off confirms that the work meets the project specification and contract requirements.
Their role:
- Review the completed ITP and any attached evidence
- Attend hold point inspections where nominated
- Approve or reject the document
- Record any conditions or observations
4. The principal contractor (final acceptance)
On some projects, the principal contractor requires a final sign-off above the superintendent level — particularly for high-risk elements or at project milestones like level handovers.
Their role:
- Review the signed ITP as part of the area or level sign-off pack
- Confirm that the document chain is complete and unbroken
- Accept the work as meeting contractual quality requirements
Hold points vs witness points in the workflow
The sign-off workflow changes depending on the inspection type:
Hold points require the nominated party to physically attend, inspect, and sign before work can continue. If the superintendent is nominated for a hold point and they don't attend, the work must stop. There is no "sign later" option — at least not one that will survive an audit.
Witness points give the nominated party the right to attend, but work can proceed if they choose not to. The subcontractor must give adequate notice (typically 24 hours), and if the witness party doesn't attend, the inspection item is recorded as "offered, not attended."
The critical difference in the workflow: a hold point creates a hard dependency on another party's availability. This has real scheduling implications, which is why over-classifying inspection items as hold points (a common mistake) can delay the entire program.
The sign-off sequence
A properly managed sign-off follows this sequence:
- Subcontractor completes the ITP — all inspection items filled in, evidence attached, self-inspection confirmed
- Hold point notice — the subcontractor notifies the nominated party (typically the superintendent) that a hold point inspection is ready, giving the required notice period
- Hold point inspection — the nominated party attends, inspects, and signs off (or raises a non-conformance)
- Document submitted for sign-off — the completed ITP is sent to the superintendent or principal contractor's representative for review and approval
- Final sign-off or rejection — the reviewing party approves the document (locking it) or returns it with comments requiring rectification
- PDF generation and filing — the signed document is produced as a PDF and filed in the project quality register
Common failure points
Sign-off after the fact
The most frequent sign-off failure is retrospective signing. The pour happened on Monday, the superintendent signs on Thursday. In between, the conditions may have changed, the inspection was not actually witnessed, and the sign-off is effectively a rubber stamp.
Digital platforms with timestamp enforcement solve this by recording the exact time of sign-off and making it visible in the audit trail. If the sign-off timestamp is days after the pour date, the discrepancy is immediately obvious.
Missing the chain
A sign-off chain with gaps is a compliance failure. If the subcontractor signed off but the superintendent's signature is missing, the ITP is incomplete. In an audit, incomplete ITPs are treated the same as missing ITPs.
The fix is systematic tracking of sign-off status. Every ITP should have a visible status — draft, in progress, pending sign-off, approved — so that anyone can see at a glance which documents are incomplete.
Email chains as sign-off
Some teams use email approval as a proxy for sign-off. The superintendent emails "approved" and the project administrator records it against the document. This is fragile: the email can be lost, the thread can be ambiguous, and there's no binding connection between the email and the specific document revision.
A proper sign-off requires the signer to see the document in its current state and sign it — not a detached email that may refer to an earlier version.
No single source of truth
When ITPs are scattered across shared drives, inboxes, and site folders, there is no definitive answer to "is this document signed off?" Someone has to check the file, open it, look for signatures, and hope they're looking at the latest version.
A centralised document register with live status tracking eliminates this entirely. Every document has one canonical state, visible to everyone with access.
How HoldPoint manages the workflow
HoldPoint enforces the sign-off chain digitally:
- The subcontractor completes the ITP in the system and marks it as ready for sign-off
- Hold points are enforced — the document cannot be marked complete until all hold point items have been signed by the nominated party
- The document is sent for external sign-off via a secure email link — the signer reviews the document and signs electronically without creating an account
- The signed document is automatically locked, timestamped, and converted to a branded PDF
- For area-based projects, all signed ITPs for a floor or lot can be bundled into a single sign-off pack and sent for final approval
The result is a complete, unbroken sign-off chain for every document on every project — with no manual filing, no email chains, and no gaps.
Getting the workflow right
The sign-off workflow is not a technology problem — it's a process problem. Digital tools enforce the process, but the process has to be designed correctly first:
- Define the sign-off chain for each ITP at the project start, not on the fly during inspections
- Classify inspection types carefully — use hold points only where work is genuinely irreversible
- Give adequate notice for hold point inspections — a 24-hour minimum is standard, but check the contract
- Track document status in real time — don't discover missing sign-offs at handover
- Produce the audit trail as you go — signed PDFs generated at the time of approval, not reconstructed months later
If your current workflow has gaps in any of these areas, closing them will improve your quality documentation more than any individual technology change. To start with a single ITP and see what a structured sign-off chain looks like, try the free AI ITP generator — it produces a hold-point-ready document in seconds.