ITP - inspection test plan

I. What is an ITP?

ITP – Inspection and Test Plan is an inspection and testing plan used to control the quality of a work activity, item, or system throughout construction. An ITP clearly defines what must be inspected, which documents provide the reference basis, the inspection or test method, acceptance criteria, frequency, control-point type, participating parties, and records to be retained.

In short: Method Statement answers “how to build?”, while an ITP answers “what to inspect – when – against which criteria – who verifies it – what evidence must be retained?”.

An ITP is the quality-control map of the work: when the map is clear, the site team knows when work must stop, when witnessing is required, and what conditions must be satisfied before moving to the next step.

ITP Inspection and Test Plan – construction quality control system — **Figure 1.** ITP connects planning – inspection – testing – acceptance – quality records into a traceable control chain.

II. Why is an ITP the “quality-control map” of a construction site?

Inspect at the right time

Do not wait until the end of the work to discover errors; inspection points are placed immediately before steps that may conceal the work or make correction difficult.

Prevent error propagation

A small error in reinforcement, materials, welds, or installation parameters can significantly reduce rework cost and schedule delay when detected early.

Trace responsibilities

The ITP clarifies who prepares, who inspects, who witnesses, who approves/releases, and what evidence proves that the work has been accepted.

An effective ITP does not slow down site work. On the contrary, it helps the work progress through controlled stages, reduces subjective disputes, and creates a common language among contractors, consultants, clients/owners, laboratories, and third parties.

III. What does an ITP include?

1. Activity / Work Step

Describes each work step that requires inspection or testing.

2. Reference Document

Contract, specification, drawing, shop drawing, applicable standards, and approved Method Statement.

3. Inspection / Test Method

Visual inspection, measurement, field test, laboratory test, NDT, functional test, or document review.

4. Acceptance Criteria

Specific pass/fail conditions used to determine whether the work is acceptable.

5. Frequency

By component, lot, batch, shift, length, quantity, or defined milestone.

6. H / W / R Point

Defines Hold, Witness, Review, or other checkpoint types in accordance with project requirements.

7. Responsibility

Defines who prepares, inspects, witnesses, reviews, approves/releases, and retains the records.

8. Quality Record

Checklist, inspection request, acceptance record, test report, certificate, photographs, and close-out records.

Structure of a professional Inspection and Test Plan — **Figure 2.** Anatomy of an ITP: **What → How → Standard → Who → When → Record**.

IV. What are Hold Point, Witness Point, and Review Point?

Hold Point (H)

A mandatory stop point. The work must not continue until the checkpoint has been inspected and properly released by the authorized party in accordance with the approved ITP.

STOPAPPROVERELEASE

Witness Point (W)

A point at which the invited party has the right to attend and witness the activity. Continuing the work when that party is absent must comply with the ITP, contract, specification, and notification procedure of the project.

NOTIFYWITNESSRECORD

Review Point (R)

A point for reviewing documents/records such as certificates, test reports, material approvals, calibration records, inspection records, or other relevant documentation.

DOCUMENTVERIFYRECORD

H/W/R points should not be assigned by habit. The control-point type must reflect technical risk, contractual requirements, and the actual approval authority defined for the project.

Comparison of Hold Point, Witness Point, and Review Point in an ITP — **Figure 4.** H – W – R differ mainly in **stop authority, witnessing rights, and the form of document control**.

V. How is an ITP different from a Method Statement, Checklist, and Inspection Request?

Document	Main question answered	Role
Method Statement	How is the work performed?	Describes the method, sequence, resources, safety controls, and construction organization.
ITP	What is inspected, when, and against which criteria?	Coordinates inspection/test activities, H/W/R, Acceptance Criteria, Frequency, and Records.
Checklist	Which specific items must be checked?	A detailed list of field/document checks for a specific work step.
IR / WIR	When should inspection be requested?	Requests the authorized party to attend for inspection, witnessing, or acceptance.
Test Report	What is the test result?	Provides evidence through data, measurements, or test results.
NCR	What should be done when a nonconformity occurs?	Records the issue and governs disposition, corrective action, re-inspection, and close-out.

Quality document ecosystem: Method Statement, ITP, Inspection Request, Quality Record — **Figure 5.** ITP sits between **the construction method** and **quality evidence**, linking drawing – checklist – IR/WIR – test report – NCR – close-out.

VI. How to prepare an ITP in 7 steps

Define the scope of work.
Break the scope into sufficiently clear work steps so that each step can be inspected, tested, or verified before proceeding.

Collect applicable documents.
Contract, specification, IFC/approved drawing, shop drawing, Method Statement, material approval, and manufacturer requirements where applicable.

Define the Acceptance Criteria.
Convert technical requirements into verifiable pass/fail criteria.

Select the Inspection / Test Method.
Visual, measurement, laboratory test, field test, NDT, functional test, or document review.

Define the Frequency.
Avoid vague wording such as “as required” when frequency can be quantified by lot, batch, component, quantity, length, or work shift.

Classify H/W/R and Responsibility.
Define who inspects, witnesses, approves/releases, and the required advance-notification conditions.

Assign Records and a close-out mechanism.
Each checkpoint must have corresponding evidence that can be traced during acceptance, handover, or audit.

ITP workflow from drawing/specification to inspection, acceptance, and quality records — **Figure 3.** Workflow ITP: **Approved Documents → ITP → Inspection/Test → Accept/Reject → Quality Record**; when rejected, a corrective-action and re-inspection loop is required.

VII. Where do Acceptance Criteria and standards in an ITP come from?

An ITP does not create its own acceptance criteria. Acceptance Criteria must be traceable to approved technical and contractual sources.

Typical traceability hierarchy

Contract → Specification → Approved Drawing → Applicable Standard → Approved Method Statement → Manufacturer Requirement.

Common standards systems

TCVN, ISO, ASTM, ACI, AWS, ASME, IEC, NFPA, or other standards depending on the project scope and contract.

When documents contain different requirements, do not simply select the more convenient criterion. Follow the project’s document-precedence rules, RFI/TQ/technical clarification process, or approved deviation procedure.

VIII. Complete example of an ITP for concrete works

The table below illustrates how a concrete ITP can be organized. Specific values must be adjusted to suit the design, specification, applicable standards, and approvals of each project.

Activity	Inspection / Test	Reference / Criteria	Frequency	H/W/R	Responsibility	Record
Formwork	Location, dimensions, elevation, tightness, stability	Approved drawing / Method Statement / project spec	Each area/component before pouring	W	Site + QA/QC + Supervision	Checklist / IR / photos
Reinforcement	Diameter, spacing, lap, anchorage, inserts, starter bars	Approved drawing / rebar schedule / project spec	Each component before concealment	H	Site + QA/QC + Supervision	Checklist / IR / acceptance record
Concrete cover	Spacers, cover thickness, stability before pouring	Approved drawing / project spec	Each component	H	QA/QC + Supervision	Checklist / photos
Concrete delivery	Delivery ticket, mix, delivery/receipt time, traceability	Approved mix design / project spec	Each truck/batch as required by the project	R	QA/QC + Supplier	Delivery ticket / batch record
Slump / field test	Field test in accordance with the specified method	Approved mix / applicable standard	By batch/volume/project-defined frequency	W	QA/QC + Lab + Supervision	Field test report
Sample casting	Sampling, specimen casting, identification, curing, traceability	Applicable standard / project spec	At the required frequency	W	QA/QC + Lab	Sample log / test report
Concrete pouring	Sequence, compaction, joints, timing, construction conditions	Method Statement / project spec	Continuously during the concrete pour	W	Construction + QA/QC + Supervision	Daily report / pour record / photos
Curing	Curing method, duration, and conditions	Method Statement / project spec	According to the curing plan	W/R	Site + QA/QC	Curing log / inspection record

Example ITP for reinforced concrete works — **Figure 6.** A good concrete ITP should not merely state “inspect reinforcement”; it must clearly define **Reference – Criteria – Frequency – H/W/R – Responsibility – Record**.

IX. Inspection – Acceptance – NCR – Reinspection process

An ITP does not only describe the path when everything passes. A robust quality system must clearly define how to respond when an inspection or test fails.

PASS path

Inspection/Test → Acceptance → Record → Next Activity.

FAIL path

Nonconformity → NCR/Observation → Root Cause → Corrective Action → Repair/Rework → Re-inspection → Close-out.

An NCR should not be closed simply because the work “has been repaired.” There must be evidence that the cause and corrective actions were addressed, the work was appropriately re-inspected, and the records were closed out by the proper authority.

Inspection fail NCR corrective action reinspection close out — **Figure 7.** FAIL is not the end point; quality depends on the ability to **detect – correct – re-inspect – close out in a controlled manner**.

X. Who prepares, reviews, and approves an ITP?

There is no single responsibility matrix that applies to every project. Roles must follow the contract, project organization, quality plan, and approved ITP. However, responsibilities typically revolve around the following functions:

Prepare

Site Engineer / QA/QC Engineer prepares the technical and control content.

Review

QA/QC Manager, Construction Manager, or discipline lead reviews completeness.

Approve / Accept

Depending on the contract: Consultant, Client/Owner, or the corresponding authorized person.

Inspect

Site + QA/QC + discipline inspector performs inspections in accordance with the ITP.

Witness / Release

The party designated at the H/W checkpoint and under the project procedure.

Record / Close-out

QA/QC / Document Control coordinates record retention, traceability, and turnover.

ITP Responsibility Matrix and Project Quality Dashboard — **Figure 8.** The Responsibility Matrix clearly shows who **prepare – inspect – witness – release – record – close-out** at each checkpoint.

XI. ITP for Civil – MEP – Industrial/MRO

Civil / Structural

Earthwork, piling, reinforcement, formwork, concrete, waterproofing, structural steel, finishing.

MEP

HVAC, electrical, plumbing, fire fighting, ELV/BMS, pressure testing, insulation, functional testing, and commissioning.

Industrial / MRO

Piping, welding, NDT, alignment, equipment installation, pressure testing, coating, repair, and post-maintenance inspection.

The logical structure of the ITP remains the same, but inspection method, Acceptance Criteria, Frequency, H/W/R, and Records must be designed around the risks and characteristics of each discipline.

XII. 10 common mistakes when preparing and using an ITP

1. Copying an ITP from an old project and changing the name without reviewing the specification and drawings.
2. Using no clear Acceptance Criteria and writing only “as per specification”.
3. Using vague Frequency requirements that cannot be quantified.
4. Assigning H/W/R by habit instead of based on risk and contractual requirements.
5. Failing to define the release conditions for a Hold Point.
6. Failing to define notification timing/procedure for a Witness Point.
7. Allowing the Method Statement and ITP sequences to become inconsistent.
8. Keeping records that are insufficient to trace a lot, batch, component, or construction location.
9. Having an inspection failure without a clearly defined corrective-action and re-inspection loop.
10. Approving the ITP but failing to brief the site team and subcontractors.

XIII. Checklist for reviewing an ITP before issue

✓Are the scope of work and work steps sufficiently clear?

✓Are the reference documents at the correct approved revision?

✓Does every inspection/test have defined Acceptance Criteria?

✓Can the Frequency be measured or quantified?

✓Are H/W/R points aligned with the contract and project procedure?

✓Are Responsibility and release authority clearly defined?

✓Are the Records sufficient for traceability and turnover?

✓Is the ITP aligned with the Method Statement and Checklist?

✓Has the FAIL/NCR/Re-inspection path been defined?

✓Have the parties directly involved in construction and inspection been briefed?

XIV. FAQ – Frequently Asked Questions about ITP

What is an ITP in construction?

ITP stands for Inspection and Test Plan – a plan that defines work steps, references, methods, Acceptance Criteria, frequency, H/W/R, responsibility, and quality records.

Who prepares an ITP?

Typically, the contractor/subcontractor prepares the ITP through the Site/QA/QC team; the reviewer and approver depend on the project organization and contract.

How is an ITP different from a Method Statement?

The Method Statement describes how the work is carried out. The ITP describes how the quality of that work is controlled: what is inspected, when, against which criteria, who participates, and what records are retained.

Are an ITP and a Checklist the same?

No. An ITP is a control plan at activity/process level; a checklist is a detailed list of items to be checked at a specific work step.

Can work continue past a Hold Point?

No. Work must not continue until it has been properly released by the authorized party in accordance with the approved ITP and project procedure.

What happens at a Witness Point if the consultant/client is absent?

Follow the ITP, contract, and project notification procedure. It should not be assumed that the contractor may automatically proceed simply because the invited party is absent.

What is a Review Point?

It is a checkpoint focused on reviewing documents/records such as material certificates, test reports, calibration records, approvals, or other records.

Where do Acceptance Criteria come from?

From the contract, specification, approved drawing, applicable standard, approved Method Statement, and manufacturer requirements where applicable.

Does every work item need a separate ITP?

Not necessarily. Smaller work items may be grouped where they share the same control logic, provided the scope is clear and no important checkpoints are omitted.

Does ITP apply to MEP and MRO?

Yes. ITP is highly effective for installation, pressure testing, NDT, alignment, functional testing, commissioning, repair, and many industrial/MRO activities.

What should be done when an inspection fails?

Record the nonconformity in accordance with the project procedure; raise an NCR/observation where required; perform root-cause analysis, corrective action, repair/rework, re-inspection, and documented close-out.

Does an ITP replace acceptance/inspection approval?

No. The ITP organizes how inspections and tests are performed; acceptance is the confirmation outcome at checkpoints in accordance with project requirements.

XV. Conclusion

An ITP is not a QA/QC form created merely to “complete the paperwork.” A good Inspection and Test Plan converts technical requirements into control points with defined timing, criteria, accountable persons, and clear evidence.

When the ITP is properly linked to drawings, specifications, Method Statements, checklists, IR/WIR, test reports, and NCRs, quality no longer depends on the memory or experience of an individual; it becomes an operating discipline for the entire project.

The ultimate objective is not merely to “have an ITP,” but to ensure that every construction step is properly inspected, properly released, and traceable when required.

This content is provided for technical and management reference. Actual standards, responsibilities, checkpoint types, and acceptance procedures must comply with the contract, approved documents, and requirements of each project.