Inspection and test plan (ITP): how to build one and run it on site

An inspection and test plan (ITP) is the document that says, for a defined scope of work, which inspections and tests will be done, at what stage, against which acceptance criteria, and who has to be present or sign off before work continues. It is used across construction, fabrication and manufacturing, usually agreed with the client before the work starts. A good ITP turns the specification into a sequence of checks; a poor one is a copy of last project's table with the project name changed.

What an inspection and test plan contains

• Scope: the work package, drawings and specification sections the plan covers.
• Activity sequence: each inspection or test in the order it happens on site or in the shop.
• Reference documents: the standard, clause or drawing that defines what "acceptable" means.
• Acceptance criteria: tolerances, test values or visual criteria, written so an inspector can apply them.
• Inspection type: hold, witness, review or surveillance point for each party.
• Responsibility: who performs the check — contractor, subcontractor, third-party inspector, client.
• Records produced: the test certificate, checklist or report that proves the check was done.

Hold points, witness points and review points

The inspection type column is what gives an ITP its force. A hold point means work must stop until the named party has inspected and released it — pouring concrete before the reinforcement is inspected is the classic example. A witness point means the party is given notice and may attend, but work can continue if they do not. A review point means the records are checked afterwards rather than the activity itself. Agree the notice period for hold and witness points up front, or the plan will stall the programme.

Keep hold points for checks that cannot be verified later. If a defect would be buried, covered or impossible to test once the next activity starts, it belongs at a hold point; everything else can usually be a witness or review point.

How to run an ITP through the job

1. Draft the ITP from the specification for each work package and submit it for client approval before work starts.
2. Give every line a unique reference so inspection records can point back to it.
3. Before each hold or witness point, issue the notice to the named parties with the planned date.
4. Record the result for each line: passed, failed, released with comment — with the date, inspector and evidence attached.
5. Raise a non-conformance report for any failed line and link it, so the ITP shows the line as open until the NCR is closed.
6. At handover, compile the completed ITP with its records into the quality dossier.

Ettex Records works well as the live version of the plan: one row per ITP line with its reference, inspection type, responsible party, status and attached certificates. Filtering by open hold points shows what is blocking the programme this week. The same register can sit alongside your submittal log and your quality control checklist, so approvals, inspections and defects are tracked in one place.

Common ITP mistakes

• Acceptance criteria that say "as per specification" without the actual value.
• Too many hold points, so inspectors cannot attend and the job stops waiting.
• No link between a failed inspection and the corrective action that closed it.
• Records collected at the end rather than when the inspection happened.
• One generic ITP reused across different work packages.