Construction ITP Inspection and Quality Records Register

Use this record for

Cross-trade register structure for identifying controlled requirements, ITP checkpoints, responsible and notified roles, actual inspection or test record references, open issues, evidence and separately documented completion, release and handover status. Each row is an index entry, not a substitute for the underlying evidence.

Outside this record: Creating project acceptance criteria, selecting standards or test methods, deciding whether an inspection passes, recording work that did not occur, approving a hold-point release, certifying compliance, or replacing the contract, approved ITP, test report, NCR, as-built drawing, certificate or O&M document.

Blank register. Populate it from the current controlled project documents and the project records actually created. Every status, date, result, role and document reference remains blank until evidenced. NCR closure, inspection result, contractual release and dossier/handover completeness are distinct fields and decisions. A complete index does not establish that indexed work complies.

Collect these project inputs first

Current contract, specification, approved drawings and ITPs

Use project-controlled sources to define the required checks, acceptance basis, notice rules, checkpoint type and release authority. This register supplies none of those requirements.

Project document numbering and retention rules

Confirm record IDs, revisions, status terms, file location, required metadata, retention period and dossier format from the contract and document control procedure.

Actual inspection, test and material evidence

Index source records that exist, including reports, certificates, photos or supplier records where required. An index row does not reproduce or verify its source document.

Issue, recheck and NCR references

Link unresolved findings and later evidence to the applicable NCR or corrective-action record. NCR closure does not itself close a separate ITP or contract release.

Separate release and handover requirements

Identify project-assigned release and handover roles, required decision records and outstanding conditions. Do not infer release or handover acceptance from a populated index.

How to use the record

1. Create the register from the current contract, approved quality plan, ITPs and document-control procedure. Record each source revision and its project owner.
2. Use a stable project record identifier for each requirement or checkpoint and retain its link to the controlling clause, drawing, ITP and applicable location or lot.
3. Record checkpoint type and notice arrangements exactly as assigned in project documents. Enter planned requirements separately from an actual inspection or test result.
4. Add actual events only after they occur. Link the result, inspector, date, evidence file and any NCR or recheck to the underlying record. Leave unknown, future and incomplete events blank or use the project-defined pending term.
5. Index source documents with their actual title, revision, date, author or issuer, status and controlled location. The index is a navigation aid; preserve each original report or evidence file.
6. Track action status, inspection result, NCR closure, contractual release and handover completeness in their own fields. Use only the authority and status definitions established by the project.
7. Reconcile the register against the contract handover schedule and project document-control process before a responsible project reviewer records completion.

Workflow stages and evidence to record

Use the controlled project procedure for assigned responsibilities, required decisions and record status. The fields below organise the actual evidence and decisions; the web page does not save, close or authorise project records.

When a check cannot be closed

Register and dossier review

Choose only the state evidenced by the project process. Index review does not establish compliance, approve an inspection result, close an NCR or make a contractual release decision.

Register review status options in the blank record:

• Records being compiled
• Project review or source record outstanding
• Index reviewed under the project process

Record the assigned roles: Register owner / role / revision; Source record reviewer / reference; NCR and action owner / status source; Release authority / separate record; Handover reviewer / decision and conditions.

Source notes and limits

• NSW Government, Quality management guidelines for construction

  Official NSW Government construction procurement guidance. The page describes NSW Government project scope and gives examples of quality-plan, ITP, nonconformity, document-control, register and handover record interfaces. Its sample GC21 clauses are not universal requirements and apply only when adopted by a project's actual contract. The linked Appendix D ITP DOCX was not readable in the source check, so no claim about its detailed contents is made. Read: Use the page headings “Scope and purpose” and “Contents of a quality management plan” for NSW Government context, quality-plan content and record management. Under the sample contract clauses, see the GC21 examples concerning quality records, conformity registers, nonconforming work and handover. These examples are NSW/GC21-specific and apply only when adopted by the project contract. Appendix D is linked on the page, but its DOCX body was not verified. Checked 2026-10-07.

Continue the work sequence

• Construction nonconformance report
• Quality management plan and ITP responsibilities
• Inspection register and handover dossier

This blank workflow record organises project information. It does not replace original evidence, technical decisions, contractual release or recipient acceptance.