E&I ITP Guide: Hold Points, Witness Points and Required Records

An Electrical and Instrumentation Inspection and Test Plan (E&I ITP) is a project-approved, stage-by-stage control plan that links each E&I activity to its verification method, inspection level, acceptance reference, responsible parties and retained record. It turns scope into auditable evidence from material receiving through installation, testing, FAT/SAT, loop checks, punch closure and final handover.

The ITP does not create technical requirements by itself. The contract, approved project specifications, drawings, procedures, applicable standard editions, manufacturer instructions and authorized project roles define the actual acceptance and release boundary. Any Hold, Witness, Review or Surveillance assignment in this guide is illustrative only and requires project approval.

For the wider lifecycle and discipline boundary, see NTIA’s complete E&I inspection guide. This article focuses on how inspectors and QA/QC teams build, review and audit the ITP as a control-and-evidence document.

Use NTIA’s E&I inspection checklist for lifecycle sequencing, the instrument loop check procedure for loop evidence, and the insulation resistance and continuity testing guide for electrical-test evidence.

E&I ITP vs Checklist, QCP, Method Statement, Test Procedure and Report

These documents work together, but they do not answer the same question. Confusing them produces either an oversized ITP that tries to contain every method or a vague plan that cannot support an acceptance decision.

A strong ITP points to the controlling checklist, method statement, test procedure or report form rather than copying all of their content. This keeps revisions controlled and makes the plan usable during execution.

Inputs Required Before Drafting an E&I ITP

Start with controlled inputs, not a blank template. The ITP can only be as specific as the scope and engineering information available when it is prepared.

• Contract, purchase order, client quality requirements and the agreed document-precedence rules.
• Approved E&I scope, system boundaries, equipment and tag lists, cable schedules, I/O lists and package-interface registers.
• Current approved drawings, including P&IDs, single-line diagrams, layouts, wiring and termination drawings, loop diagrams, hook-up drawings and area-classification documents where applicable.
• Approved project specifications, inspection procedures, installation methods, test procedures and manufacturer instructions.
• Risk or criticality classification, statutory or client-mandated points, supplier performance history and the ability to verify the work later.
• Project schedule, inspection notifications, responsibility matrix, release authority and rules for waiver, no-show or remote witnessing.
• Master document register, inspection forms, report templates, dossier index and required record-retention format.

Freeze the applicable revisions before approval. If the design is still changing, define how ITP rows and completed records will be reviewed when a drawing, procedure or equipment selection changes.

Hold, Witness, Review and Surveillance Points

H/W/R/S codes are contractual control points, not universal technical ratings. Clients may use different names or add codes such as monitoring, approval, verification or notification points. The approved ITP legend must define each code, the required notice, attendance or waiver rules, and who may release the work.

Inspection-Point Decision Logic

Assign the point only after considering the decision that the project must protect. The following matrix is a review aid, not an automatic code selector.

E&I Activity-to-Evidence Matrix

The master matrix should follow the actual lifecycle and system-completion sequence. Each row must identify the activity, verification method, acceptance source, point code, responsible parties, notification or sign-off rule and retain record. The examples below are intentionally bounded and do not prescribe universal points.

Pre-Start Document Approval and Scope Freeze

The approved ITP should exist before the affected work begins, but it must also remain connected to live engineering. Confirm that the activity list covers the actual systems, packages and interfaces rather than only repeating a corporate template. Record the document revisions and unresolved comments that could change inspection scope.

A revision after execution may affect completed records. The project should define how QA/QC assesses the change, identifies impacted tags or systems and decides whether review, additional evidence or retesting is required.

Material Receiving and Tag / Certificate Verification

Receiving is the first opportunity to protect traceability. The row should distinguish physical identity and condition from document review: tag or model, quantity, visible damage, storage requirements, certificate availability and match to the approved datasheet or purchase description.

Do not write only “material inspection.” Identify the receiving form, the required certificates and the route for shortages, substitutions, damaged items or certificate mismatches.

Cable Containment, Routing and Pulling

Containment and cable work often becomes difficult to inspect after covers, insulation or later trades restrict access. The ITP should identify which stages require surveillance, sampling or a pre-concealment witness, based on the project risk and inspection strategy.

Link the row to the approved route, segregation requirements, support details, cable schedule and manufacturer installation limits. Pulling evidence should identify the cable and route, not merely record that a crew completed a daily activity.

Glands, Terminations, Segregation and Earthing

Termination quality depends on correct identity, preparation, component selection, installation method and final arrangement. The ITP should separate the physical inspection from electrical test records where those are different activities.

Where torque, shield treatment, bonding or earthing continuity must be recorded, name the form or record. A generic visual tick cannot prove a measured or controlled requirement.

Panels, MCCs, Junction Boxes and Package Interfaces

For panels, MCCs, junction boxes and packaged equipment, the ITP should connect shop evidence to site acceptance. Verify that interface terminals, power and signal boundaries, environmental protection, spare entries, labeling and drawings align across vendor and site documents.

Package interfaces are a common source of late NCRs because each party assumes the other owns the check. The responsibility column should identify who verifies the vendor boundary, who verifies the site boundary and who accepts the integrated result.

Instrument Installation, Hook-Up and Calibration Evidence

Installation and calibration are related but separate. A valid calibration record does not prove that the instrument is correctly installed, accessible, connected, supported or protected. Likewise, a visually correct installation does not prove range performance.

Use separate rows or clearly separated evidence requirements where the project needs independent installation inspection, hook-up or tubing checks, calibration review and final readiness.

Insulation Resistance, Continuity and Pre-Energization Readiness

The ITP should state when IR and continuity evidence becomes available, what assets or cable cores it covers and which document defines the method and acceptance criteria. It should not reproduce universal test voltages or pass values.

Pre-energization release is broader than a passed electrical test. The designated authority should also consider completion status, terminations, protection settings, earthing, open items, system condition and approved energization controls.

Loop Check, Functional Test and Alarm / Interlock Interfaces

Loop checking should appear after its prerequisites and before the relevant commissioning release. The ITP row should identify the approved loop sheet or procedure, required participants, record and treatment of failures.

Alarm, interlock, permissive, trip and safety-instrumented functions may require separate test procedures and authorization. Do not let one broad “functional test” row hide multiple systems, roles or acceptance sources.

FAT, FIT, SAT and Site Integration Activities

Factory and site tests need project-specific plans that define scope, responsibilities, prerequisites, test cases, deviations, restoration and release. The ITP should show which plan controls each event and whether acceptance releases manufacturing, shipment, installation or system handover.

A signed attendance sheet is not sufficient evidence. Retain the executed protocol, actual results, deviations, punch items, retests and the formal release decision.

Hazardous-Area Initial Inspection and Specialist Escalation

Hazardous-area rows must respect competence and authorization boundaries. The ITP can identify required documentation, initial inspection and records, but it should not turn a general E&I inspector into the project’s Ex authority.

Link the activity to the approved area classification, equipment register, certificates, installation requirements and the applicable project-specified edition. Define how unclear marking, certificate scope or installation defects are escalated.

Punch, NCR, Correction, Retest and Closure

The ITP should not treat a failed activity as complete simply because a later record says “retested.” Preserve the original finding, approved disposition, correction evidence, affected scope and retest result.

Where a correction could influence adjacent circuits, configuration, logic or interfaces, expand the retest boundary under the approved change and quality process. Release status must remain visible until the authorized closure is complete.

As-Built Documentation, Dossier Index and Final Handover

Final handover should be traceable to the approved ITP, not assembled as an unrelated document dump. Every completed row should point to the retained form, report, certificate or controlled record, including linked findings and retests.

The dossier index should show revision and status. Missing signatures, superseded drawings, duplicated reports and unclosed punch items are completeness failures even when field work appears finished.

From Matrix Structure to Inspection Judgment

A matrix is useful only when the inspector can interpret drawings, procedures, test evidence and field conditions well enough to challenge a weak row. NTIA’s Electrical & Instrumentation (E&I) Inspection Training Course supports structured learning in E&I inspection, testing methods, documentation and reporting. Training develops knowledge; it does not replace project authorization, employer competence assessment, specialist Ex or functional-safety qualifications, or the approved project procedures.

How to Write Defensible Acceptance References

The acceptance column should tell the inspector exactly where the requirement comes from. Phrases such as “as per specification,” “as applicable” or “client requirement” are not adequate unless the specific document and revision can be identified.

The contract or project quality plan should define document precedence. When two approved sources conflict, the inspector should not invent a compromise: record the conflict and obtain an authorized clarification before release.

Required Records and the E&I Dossier

A required record is the evidence that allows another competent reviewer to understand what was inspected or tested, against which revision, with what result and under whose authority. “Signed ITP” is not a substitute for the underlying evidence.

Roles, Notification, Waiver and Sign-Off

The ITP should separate who performs the work, who checks it, who witnesses or reviews it and who releases the next stage. One signature box labelled “Inspector” is rarely enough for complex package or commissioning interfaces.

Notification periods and waiver rules belong in the approved ITP legend or referenced procedure. Define how notice is issued, how attendance is confirmed, what happens if the witness does not attend, who may waive a point and how that decision is recorded. Never treat an unconfirmed email or verbal message as automatic release unless the contract explicitly permits it.

Failed Activity, NCR, Retest and Inspection Release

A failed inspection or test interrupts the evidence chain. The ITP should direct the team into the approved punch or NCR process without hiding the first result or allowing uncontrolled rework.

1. Record the observed condition, affected asset or system, document revisions and the ITP row that was not accepted.
2. Control progression beyond the relevant point according to the ITP, system-completion status and authorized release rules.
3. Classify and route the issue through the project punch, nonconformance or technical-query process.
4. Obtain the required disposition, concession or corrective instruction from the authorized role before changing the work.
5. Complete the correction under an approved method and preserve evidence of what changed.
6. Define the retest boundary, including connected circuits, functions, configuration or interfaces that may have been affected.
7. Link the retest to the original finding, record the actual result and obtain the required closure and release signatures.

Inspection release is the authorized decision that the defined activity or stage may proceed. It is not the same as overall system readiness, energization authorization or startup approval unless the project documents explicitly combine those decisions.

Dossier Traceability Audit

Audit the dossier in both directions. Forward traceability asks whether every applicable ITP row has complete evidence. Reverse traceability asks whether a selected record can be traced back to the correct ITP activity, asset, controlling revision and release decision.

• Select each applicable ITP row and confirm the required record exists, is legible, complete, signed and at the correct revision.
• Check that the record identifies the actual tag, cable, core, loop, panel, package or system boundary.
• Confirm that measured or observed results are recorded where the activity requires them; a tick alone may not be enough.
• Trace every failed result, punch or NCR to its disposition, correction, retest and authorized closure.
• Sample records in reverse and confirm they point to an approved ITP row and acceptance source.
• Check that superseded or duplicate records are controlled and that the dossier index reflects final status.
• Confirm remaining open items are explicitly accepted, categorized and controlled under the handover procedure.

Common E&I ITP Failures and Corrective Actions

E&I ITP Review Checklist

Use this checklist before approval and again before execution starts. A “yes” should be supported by the plan and its referenced documents, not by assumption.

FAQ

What is an E&I Inspection and Test Plan?

It is a project-approved control plan that sequences electrical and instrumentation activities and links each one to a verification method, inspection point, acceptance reference, responsible parties and retained record.

What is the difference between an ITP and an inspection checklist?

The ITP controls when an activity is inspected or tested, who participates, what source defines acceptance and what evidence is retained. The checklist guides the detailed items checked during one activity.

What is the difference between an ITP, QCP, method statement and test procedure?

The ITP controls inspection stages and evidence. The QCP describes the wider quality system. A method statement explains how work is performed. A test procedure defines the detailed test boundary, setup, steps, acceptance and restoration.

What do Hold, Witness, Review and Surveillance points mean?

A Hold Point blocks progression until authorized release. A Witness Point gives an authorized party the opportunity to attend under defined notice rules. A Review Point requires document or record review. Surveillance monitors selected work. Exact definitions come from the approved project legend.

Who decides whether an E&I activity is a Hold or Witness Point?

The decision is made through the contract and project approval process, using risk, irreversibility, later verifiability, statutory/client requirements, supplier performance and evidence quality. An inspector should not unilaterally rewrite the approved point.

What documents are needed before preparing an E&I ITP?

Typical inputs include the contract or PO, scope, specifications, current drawings, equipment/tag and cable registers, procedures, risk/criticality data, schedule, responsibility matrix, notification rules, forms and dossier requirements.

Which electrical and instrumentation activities should be included?

Include the activities that apply to the project lifecycle: receiving, containment and cable work, terminations and earthing, panels/JBs, instrument installation and calibration, IR/continuity, loop and functional tests, FAT/SAT, hazardous-area initial inspection, punch/NCR closure and handover.

What should be written in the acceptance criteria column?

Identify the exact approved source—such as a specification, drawing, test procedure, applicable standard edition, datasheet or manufacturer instruction—and the relevant revision or reference. Avoid vague wording by itself.

What records are required for IR, continuity, calibration and loop checks?

The project defines the forms, but records should identify the asset or endpoints, controlling revisions, test method and equipment, actual results, acceptance source, participants, deviations, retests, restoration and signatures.

How should FAT, SAT and site integration activities appear in the ITP?

Use separate rows or a clearly controlled test stage linked to the approved FAT/FIT/SAT/SIT plan. Identify prerequisites, roles, point type, executed protocol, deviations, retest and the release decision.

How are punch items, NCRs and retests controlled through the ITP?

A failed activity is linked to the project finding process. Progression is controlled, an authorized disposition is obtained, correction is documented, the affected boundary is retested and the closure evidence is linked to the original row.

How do you audit an E&I final dossier against the approved ITP?

Check every applicable ITP row forward to its required records, then sample records in reverse back to the row, asset, acceptance source and revision. Confirm findings, retests, signatures, as-built status and open items are controlled.

Final Next Step

Before approving an E&I ITP, ask five questions for every row: What exact activity is controlled? Which approved requirement defines acceptance? Who performs, verifies and releases it? Which H/W/R/S rule applies under the contract? What record will prove the result in the final dossier? If any answer is vague, the row is not ready for execution.

Use the complete NTIA E&I inspection guide for the wider discipline lifecycle and the NTIA Electrical & Instrumentation Inspection Training Course for structured learning in inspection, testing, documentation and reporting. Project documents, authorized roles and competent specialist review remain the governing authority for live work.