Inspection and test plan (ITP)
An inspection and test plan that enforces its own hold points
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 — RTI makes hold points a gate the work cannot pass without evidence.
What gets in the way, and what RTI does about it
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
Hold points get walked past because the concrete truck is already booked.
With RTI
A hold point is a gate: the pre-pour inspection must be submitted — mandatory items answered, required photos attached — before the pour release exists as a record.
Today
Witness points are attended by whoever happened to be nearby, with no record of who actually showed up.
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
Questions worth asking any vendor, including us
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.
Put it on a real job.
The RTI checklist library maps directly onto ITP rows — 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.