How do I stop hold points from getting skipped in the field?

You bind the hold-point checklist to a QR tag on the actual location. A scan opens that tag, one tap from exactly that checklist, and the submit button stays locked until every mandatory item is answered and every required photo is attached. The gate is enforced by the database, not left to whether the crew remembered your plan. RTI can't make anyone scan, but the tag shows not inspected until it is.

How are NCRs handled?

Work that falls short is sent back with its reason, and it moves to Sent back instead of passing. A defect that needs tracking becomes an NCR with a severity, an owner and a due date, and it can only close on an approved re-inspection. Every NCR step is written to the activity log.

How do I prove to an owner or an auditor that the plan was actually followed?

Every submission, decision, NCR step and sign-off is written to an activity log that hashes each entry over the previous one with SHA-256, so an edited entry no longer matches its hash and a removed one breaks the next link. Export any inspection, or a project's approved inspections, as a PDF with answers, photos, signatures and the audit trail, and hand an auditor the verification package to check independently.

For QA/QC managers

The quality plan, enforced on the phone.

You wrote the QC plan, the hold points and the NCR process. RTI turns that plan into the checklist a crew has to complete before they can submit anything, and writes each submission, decision and NCR step to a tamper evident record.

Start free Browse the checklist library

The RTI home screen: what needs you, with inspections awaiting review, awaiting client sign off and needing rework, then recent activity

The RTI mobile app's home screen: start an inspection by scanning a tag, seven inspections waiting on a decision, and the week in numbers

The RTI review board with submitted, in review, approved and rejected lanes of inspection cards tagged by unit, trade and pass count

An electrical rough-in inspection under review in the RTI mobile app: six jobsite photos of wiring, boxes and the panel, with send back and approve

The RTI activity log where every action is chained by SHA-256 fingerprint, with a verify chain control and absolute UTC timestamps

The activity log in the RTI mobile app: the audit chain check passed with a verify now control, then today's submissions by person, tag and time

The challenge

What gets in the way, and what RTI does about it

Today
The QC plan lives in a binder and a shared drive, and whether a hold point actually gets inspected comes down to whether the crew on shift felt like following it that day.
With RTI
The plan becomes the checklist bound to the tag, and the phone won't submit until the mandatory items and photos are complete. The evidence is required at the point of work, not left to memory or goodwill.
Today
NCRs get tracked in a spreadsheet that shows they were opened but never really proves they were closed, and re-work happens off to the side with no photos.
With RTI
Work that falls short is sent back with its reason, and a defect that needs tracking becomes an NCR with an owner and a due date. It closes only on an approved re-inspection with its own photos and answers, and every NCR step is on the activity log, so closure is proven, not assumed.
Today
When an owner or auditor asks you to prove the plan was followed, you're assembling evidence that anyone could have edited, and you can't show it wasn't.
With RTI
The record is a SHA-256 hash chain: change one entry and the check fails from there. You export the project with photos, signatures and the trail, and the verification package lets anyone confirm the answers and decisions weren't altered.

A real inspection point

What this looks like on your job

One tag, one checklist, and the photos that have to come with it.

Tag

Level 5 Riser, Firestop Verification

HSP-L5-RSR-03

Sticker location: Mechanical riser at the north shaft wall
Assigned checklist: Firestop verification, QC hold point

Penetration cleaned and correct sleeve or backing confirmed2 photos required
Listed firestop system matched to the penetration type2 photos required
Installation depth and detail per the manufacturer listing2 photos required
System labeled with product and installer1 photo required

Checklists for your work

Start from a checklist that already knows the walk

Real guides from the RTI library. Sections in build order, what to look for on each item, and the photos that prove it. Free to read, one click to run on a tag.

Browse the full library

Questions QA/QC managers ask

3 answers

How do I stop hold points from getting skipped in the field?: You bind the hold-point checklist to a QR tag on the actual location. A scan opens that tag, one tap from exactly that checklist, and the submit button stays locked until every mandatory item is answered and every required photo is attached. The gate is enforced by the database, not left to whether the crew remembered your plan. RTI can't make anyone scan, but the tag shows not inspected until it is.
How are NCRs handled?: Work that falls short is sent back with its reason, and it moves to Sent back instead of passing. A defect that needs tracking becomes an NCR with a severity, an owner and a due date, and it can only close on an approved re-inspection. Every NCR step is written to the activity log.
How do I prove to an owner or an auditor that the plan was actually followed?: Every submission, decision, NCR step and sign-off is written to an activity log that hashes each entry over the previous one with SHA-256, so an edited entry no longer matches its hash and a removed one breaks the next link. Export any inspection, or a project's approved inspections, as a PDF with answers, photos, signatures and the audit trail, and hand an auditor the verification package to check independently.

Put it on a real job.

Tag one area, run one walk, and see the record it leaves behind.

Start free See how it works

30-day trial · No card required