Inspection and test plan (ITP)
An inspection and test plan where each hold point needs its evidence
- Rebar placement verified Pass
- Formwork dimensions checked Pass
An ITP lists every inspection and test for a scope of work, who performs it, and what happens when it fails. The weak point is always the hold point, so with RTI you write each hold point as a checklist that cannot be submitted without its evidence.
- Rebar placement verified Pass
- Formwork dimensions checked Pass
Where an inspection and test plan quietly gets skipped
The classic ITP is a table: activity, reference, inspection type, hold or witness point, responsible party, record. The rows below translate each part of that table into how it runs when the plan lives on the crew's phones instead of in a binder.
Today
With RTI
Today
Hold points get walked past because the concrete truck is already booked.
With RTI
Write the hold point as a checklist the crew cannot submit without its required answers and photos. The record carries when it was submitted and approved, so whether it came before the pour is on the record.
Today
Nobody can say afterwards who inspected the work or who signed it off.
With RTI
Every inspection carries the identity and timestamp of the person who submitted it, and the reviewer's approval is a separate signed record.
Today
The ITP references the spec, but the person on site has never read the spec.
With RTI
Each checklist item is written as an observable condition, what to look at and the photo that proves it, so the requirement travels with the work.
Today
ITP records are assembled into the turnover package by hand at the end of the job.
With RTI
Approved inspections roll directly into branded turnover packages with photos, timestamps and signatures attached, behind a tamper evident audit trail.
Before you buy anything
What an ITP must do beyond listing checks
Can the work proceed past a hold point without the record?
If yes, the ITP is documentation, not control. The gate has to be in the system the work flows through, and enforced server side so offline phones can't bypass it.
Is each inspection tied to a physical location?
ITPs fail at traceability: which of the forty identical risers was actually inspected? A QR tag at each inspection point makes the record physically anchored.
What does a failed inspection trigger?
A failure should open a deficiency with an owner and a due date, not just a red cell in a spreadsheet. Ask how the non-conformance loop closes.
Do the records survive a dispute?
If records can be edited after approval, an opposing party will argue they were. Look for hash chained or otherwise tamper evident records.
The template itself
Inspection and test plan (ITP)
This is the ITP as a working document: the rows a plan needs, with the hold and witness points written as evidence the work cannot pass without.
- 01Every ITP row defines5 items
- 02Hold and witness points3 items
- 03Records and closeout3 items
Activities, acceptance criteria, hold points and the record per row.
- Items
- 11
- Photos required
- 8
- Sections
- 3
Make your ITP enforce itself on the next pour
The RTI checklist library maps directly onto ITP rows, the rough-in, pre-cover, pre-pour and final inspections per trade, so a plan that starts as a template becomes an enforced workflow the day you load it.