Inspection and Test Plans (ITPs): A Practical Primer

What an ITP is

An Inspection and Test Plan (ITP) is a document that lists, in the order the work happens, every inspection and test required for a work package — along with who performs each one, who witnesses or signs off, what standard or specification it is checked against, and what record gets generated. It is the quality roadmap for a defined scope of work.

Think of the ITP as the plan that turns a vague intention to "do quality control" into a specific, sequenced set of checkpoints. Instead of hoping the right inspections happen, the ITP says: before you pour, the rebar gets inspected and signed off here; the concrete gets sampled there; the strength results get reviewed at this point. Everyone — your crew, the inspector, the owner — knows in advance what gets checked and when.

Hold points, witness points, and review points

The heart of an ITP is the type of checkpoint assigned to each activity. Three types matter, and the distinction controls whether work can proceed:

• •Hold point: a mandatory stop. Work cannot continue past this point until the required party inspects and releases it. A rebar inspection before a concrete pour is the classic example — once you pour, the rebar is buried and unverifiable, so the inspection has to happen first and the work is held until it is signed off.
• •Witness point: a scheduled inspection or test that a party is given notice to attend, but if they do not show, the work can proceed. The activity is observed if the witness is present; their absence does not stop the job. Used when verification is valuable but not so critical that it must halt progress.
• •Review point (or surveillance/monitor point): a document or record check rather than a physical observation — for example, reviewing mill certs, calibration records, or test reports. No work is held; the check confirms the paperwork supports the work.

Who signs off

An ITP only works if each checkpoint names who is responsible, because a checkpoint with no owner gets skipped. Typical sign-off parties include your own QA/QC inspector or foreman for in-house checks, the general contractor's quality staff, the owner's representative or commissioning agent, the engineer of record for engineered elements, third-party special inspectors for code-required inspections, and authorities having jurisdiction for code inspections.

Hold points in particular need a clearly identified releasing party and a notification lead time, so the inspector can be there before the work is ready to proceed. Many disputes on site come down to a missed notification — the crew was ready to pour and the inspector had not been called. The ITP should make the lead times explicit so nobody is surprised.

Tie the ITP to specs and code

An ITP is not invented from scratch; it is assembled from requirements that already exist. Every checkpoint should trace back to a source: a project specification section, a referenced industry standard, a building-code provision, or the contract. The acceptance criteria — what counts as passing — come from those same sources, not from opinion.

Building codes drive a lot of this through special inspection requirements: structural concrete, structural steel and welding, masonry, soils and foundations, and similar high-consequence work typically require code-mandated special inspections by qualified inspectors. Those requirements belong in the ITP as hold or witness points with the right inspector named. When every line of the ITP cites its source spec or code clause, the plan is defensible and the inspector knows exactly what standard they are checking against.

Building one for a work package

Start by defining the work package narrowly — "cast-in-place concrete for the foundations," "structural steel erection for the north building," "underground process piping," or "field welding of the spool assemblies." A tight scope keeps the ITP usable. Then walk the work in sequence and build the table:

• •List each activity in the order it is performed, from material receipt through final acceptance.
• •For each activity, identify the inspection or test required, pulled from the spec and code.
• •Assign the checkpoint type — hold, witness, or review — based on consequence and reversibility.
• •Name the responsible and sign-off parties, and the notification lead time for hold and witness points.
• •State the acceptance criteria and the reference document, and name the record that gets produced.

From spreadsheet to a plan people follow

Trades that almost always need a formal ITP include concrete, structural steel and welding, piping and pressure systems, masonry, earthwork and foundations, and any work subject to code special inspections or third-party testing. The plan itself is straightforward; the hard part is making sure it is actually executed instead of filed and forgotten.

In Field PM, the QA/QC module supports inspection logs, hold points, and NCRs, so the ITP stops being a static spreadsheet — each checkpoint becomes a tracked inspection with its sign-off and records attached, hold points are flagged so the work genuinely waits for release, and any failure rolls straight into an NCR. The plan and the execution live in one place, which is the whole point: an ITP nobody follows is just a document.