ITP Revision, Review and Approval: Keep Changes Traceable

Decide whether a change affects the ITP

Trigger a review when a referenced drawing, specification, product instruction, test method, method statement, scope boundary, inspection frequency or responsibility changes. Also review after a nonconformance, approved clarification or field condition exposes a gap in the plan.

Compare old and new source revisions and record which ITP rows, checklists and handover evidence are affected. Do not revise a controlled criterion based on an informal conversation; capture the project-authorised decision first.

Use a review and release sequence

Prepare a marked change or revision summary, identify the reason and source, and route the document to reviewers and approvers identified in the project procedure. Reviewers should focus on their assigned responsibilities; the drafter should not assign technical approval authority.

After formal issue, distribute the current revision to affected teams and linked forms. Remove or clearly mark superseded copies according to the document-control procedure. Record acknowledgements or briefing where the project requires it.

Respond to comments without losing the record

Keep a comment log that links each comment to the affected section or row, response, source/decision and close-out status. If a comment requests a project decision, send it to the designated owner and leave the matter open until an authorised resolution is received.

If the planned inspection has already occurred under an older issue, preserve the record made at the time and assess it under the project’s nonconformance or document-control route. Do not silently rewrite a historical record to look as if the new revision was used.

Confirm approval is distinct from authorship

The ITP’s author, reviewer, approver and release authority can be different people. Their roles come from the contract and project procedures. A completed review, signature or portal status has only the effect assigned by that process.

A document being issued does not by itself establish that the underlying work complies, that an inspection occurred or that a statutory certificate was issued. Keep field results, test reports and certification records in their designated forms.

Fictional example: product instruction revision before installation

Fictional teaching example only. A membrane supplier issues a revised product instruction before a hypothetical work area starts. The scenario has no real project, acceptance value or approval authority.

1. Log the newly received instruction and verify whether it is approved for use on the project.
2. Compare the revision and ask the designated project contact whether the specified system or compliance route changes.
3. Identify affected ITP rows, blank field records and method statement references; do not alter acceptance criteria until the project decision is recorded.
4. Route the revised ITP to the assigned reviewers and approver under project document control.
5. Issue the approved revision, brief affected users as required and withdraw obsolete field copies.