Scope of this guide
For organising contractor-side construction quality evidence for a defined work package. The recipient and contract control required files, status, exceptions and acceptance. This is an indexing workflow, not a completion certificate, a substitute for original reports or approval of the work.
Agree the boundary and required record list
Identify the trade, area, system, element or chainage/lot being transferred and the recipient. Use the contract, QMP, ITP, drawing schedule and closeout instructions to list what must be supplied. Separate documents needed for this handover from records belonging to an adjoining trade or a later commissioning stage.
Depending on the adopted project requirements, the list may include the controlled ITP, completed inspection records, supplier certificates, original test reports, release notices, NCR dispositions, as-built drawings, product information and O&M material. Do not label every category mandatory for every package.
Use the live register to assemble the final index
The live ITP register follows changing documents and inspection events while work proceeds. The handover index is a dated submission view for one recipient and scope. Reuse the same record IDs and evidence locations, record the submission revision, and preserve later changes as another issue rather than silently changing what was transmitted.
In the blank register, use the event log for repeated inspection/report entries and the issues and handover sheet for outstanding items and the submission decision. Create a project-specific cover/index from the agreed required list. The register is an index; it does not store the original photographs, laboratory reports or authority responses.
Make each item retrievable
| Index field | What it resolves |
|---|---|
| Package and location/lot | Which work the evidence actually covers |
| Document or record ID and title | Which ITP row, inspection, test, NCR or completion document is referenced |
| Revision, status and date | Which controlled issue was submitted and whether it remains current |
| File or evidence location | Where the recipient can open the original evidence |
| Required category and related IDs | Which planned requirement is covered and how tests, lots and releases connect |
| Open item and assigned decision reference | What remains incomplete and which written instruction governs an exception |
| Transmittal and recipient response | What was sent, to whom, and what response or further issue followed |
Reconcile planned checks with actual evidence
For each applicable ITP row, identify the relevant inspections and lots, locate the original evidence and confirm that it covers the specified area or system. A record labelled complete is insufficient if its laboratory report belongs to a different sample or its drawing revision is superseded.
Keep document status, actual inspection result, contractual release and handover acceptance separate. A passing test does not automatically close an NCR or release another point. A dossier sent for review is not an accepted handover; retain the recipient response and any required resubmission.
Show outstanding items and permitted exceptions
List missing reports, unresolved results, incomplete as-builts and NCRs with the affected work, owner, next action and evidence reference. Distinguish work awaiting a decision from an exception specifically accepted by the authorised recipient. Do not make an exception appear approved by entering a due date or marking a checklist tick.
If the project permits staged handover, define the transferred boundary, outstanding dependencies and the authorised conditions. Keep the instruction with the index. Update the register and issue a new submission when later evidence arrives.
Check the links before transmitting
Confirm filenames, revisions, package IDs and access permissions through the project document-control route. Include a concise transmittal identifying scope, purpose, attachments and known open items. Follow the project retention and privacy procedure for records and personal information.
ITP drafting provides the plan and matching blank records. Original field results, test reports, statutory certificates and the recipient’s acceptance must come from the parties performing and authorising those activities; an unpopulated public download cannot supply that evidence.
Fictional staged handover with a pending report
Illustrative record identifiers only. No result, release or acceptance is represented.
- Index the fictional pipe package by floor and zone, with its ITP revision and the inspection record IDs for that boundary.
- Link the original test report required by the project. If it has not arrived, keep its index entry pending and name the affected event and responsible route.
- Add the separate release reference only after the project authority provides it; do not copy the inspector name into the release field.
- If staged submission is permitted, include the authorised conditions and the pending item in the transmittal, then issue an updated index when the report arrives.
Before issuing the plan
- Use the agreed contract and recipient record list.
- Reconcile evidence to the correct area, system, lot and ITP revision.
- Keep original reports retrievable rather than replacing them with ticks.
- List unresolved items and written exception decisions.
- Retain the submission issue, transmittal and recipient response.
Sources and their limits
Public sources explain the planning topics below. Confirm their jurisdiction, contract context and applicable edition; use controlled project documents for the actual requirements.
- NSW Government Quality management guidelines for construction
Webpage updated 1 December 2019: scope and purpose; typical QMP contents; client records; example GC21 clauses on ITPs, nonconforming work and conformity records register. Appendix D is listed but its DOCX contents were not inspected.
NSW Government construction procurement guidance. The example clauses apply only where the contract adopts them. Used for document relationships and records, not universal acceptance criteria or project approval rights.
Source reviewed: 2026-10-07