Connect inspection records to the approved ITP

An inspection and test plan identifies the activities, checks, acceptance references, responsibilities and intervention points applicable to the work. Its approval and revision status should be controlled through the project's quality process.

For each inspection request, identify the work package, location, item or lot, activity and applicable ITP step. Record the drawing, specification or procedure references needed for the check. The inspector should not have to guess which requirement a generic form is intended to demonstrate.

The works manual's quality provisions discuss quality planning and inspection records in section 7.3.4. The actual project ITP and technical requirements determine the checks and release authority for the work at hand.

The planned requirement states what should be inspected or witnessed. The completed record states what was actually checked, by whom, when and with what result. The release decision states whether the work may proceed under the applicable procedure.

These may appear on one form, but they remain distinct. A scheduled inspection is not evidence that it occurred. A completed measurement is not automatically a release if required review or witnessing remains unresolved. A signature needs a defined role and meaning.

Record the relevant inspection or test equipment identity where required by the approved procedure. Link calibration or verification evidence according to that procedure. Do not assume that attaching any calibration certificate makes every measurement valid; the qualified reviewer must assess applicability when a concern arises.

Consider a synthetic installation inspected using a form linked to ITP revision 2 when revision 3 was applicable. Quality compares the requirements and finds that revision 3 added a documented check before covering the work.

The outcome depends on the facts and the authorised technical assessment. If the check was performed and reliable evidence exists, the team may be able to resolve the documentation issue through its procedure. If evidence is absent, additional action may be necessary. The register should capture the decision rather than prescribe a universal result.

A hold point, witness point or review point has the meaning assigned by the project documents. Record notification requirements, attendance or waiver evidence, and the authority needed to proceed. Do not rely on informal assumptions about what an absent witness implies.

Where a required party does not attend, follow the applicable procedure and retain the notification and decision records. A missed email or an expired meeting invitation is not automatically permission to continue. The responsible quality or contractual owner should resolve the situation.

If work proceeds past a required intervention point without the necessary release, record the event promptly and route it for assessment. Preserve the actual sequence of events. Backdating a signature to make the record appear complete destroys the evidence needed to decide the appropriate response.

An unsuccessful inspection may lead to correction, retest, an NCR or another controlled action under the quality system. Link that record to the original inspection and identify what must be verified before release.

Retain failed results alongside later passing results. The passing retest does not erase the earlier failure or the corrective work that made it possible. The sequence helps reviewers understand the condition of the work and whether the required disposition was completed.

For partial acceptance, identify the accepted and unresolved scope precisely. A broad package-level pass should not conceal a failed location or item. Use physical identifiers that the execution team can recognise at the work front.

The inspection record should be retrievable by asset, system, location or package in the eventual handover structure. Link the accepted drawing revision, test reports and related nonconformance closures where relevant.

Agree mandatory fields and attachments before inspection begins. Missing signatures, unclear locations and unidentified test reports are much harder to resolve after the crew has demobilised or the work is covered. A short completeness check at the time of release can prevent substantial later rework.

Keep the document history available. If an inspection record is corrected, preserve the original entry and the reason for amendment through the approved record-control process. The correction should improve accuracy without obscuring who recorded what and when.

Use a sample inspection with a superseded ITP reference, a failed check and a subsequent retest. Confirm that the system identifies the mismatch, preserves both results and requires the appropriate release decision.

Then try to close the package while a linked inspection remains unresolved. The process should either prevent closure or show the authorised exception explicitly, depending on project rules. A dashboard that reports complete merely because every form has a file attached is not testing inspection completion.

Review recurring causes of incomplete records with execution and quality teams. Simplify forms that collect unused information, while retaining the fields that establish identity, requirement, result and authority.

A trustworthy record shows why the work was permitted to proceed. It connects the approved requirement to the actual check and the authorised decision, including any exception.

1. Link inspection requests to the applicable ITP step and revision.
2. Record actual checks and results separately from planned requirements.
3. Escalate missed intervention points and revision mismatches promptly.
4. Preserve failures, corrective actions and retests in one traceable history.
5. Verify record completeness before work is covered or handed over.