How does RTI help me close out submittals and ITP line items?

The proof for each item is captured against the checklist item it supports and stored on the tag, with a timestamp and the person who took it. When you go to close the submittal or the ITP line, the photos and answers are already there and attributable, so you stop emailing the field for a shot that should exist.

Can I enforce a hold point so work doesn't proceed without the inspection?

Yes. Build the hold-point checklist, bind it to the tag on the physical location, and the required photos and answers must be submitted before it can be marked complete. It lands on the review board for you to accept or reject, so the record of the hold point exists before anyone covers or pours over it.

How do I match what was installed to the approved submittal?

The checklist item asks the crew to verify the installation against the approved shop drawing and photograph it. The photo, the answer and the location tag stay together, so reconciling installed work to the approved set is reading one record instead of cross-referencing a camera roll against a document.

For project engineers

Evidence captured as it's built, not chased after.

You run the submittals, the RFIs and the ITPs, and most of your week goes to chasing the photo or the signature that proves an approved detail actually got built. RTI captures that proof at the point of work, tagged to the location, so the record is already assembled when it's time to close the item.

Start free Browse the checklist library

The RTI home screen showing setup progress, review queue counts, and first pass yield for the week

The same home screen on a phone, with the review queue and setup steps stacked for use with one hand

The RTI inspections board with submitted, in review, approved, and rejected lanes of cards tagged by unit

The inspections list on a phone, showing status tabs and cards tagged by unit with the scan button in the bottom bar

RTI checklist templates tagged by trade, showing item counts and photo gate minimums

Checklist templates on a phone, with your templates and the RTI library filtered by category

RTI reports and analytics showing total inspections, first pass approval rate, and review turnaround

Reports on a phone, with period filters and headline quality metrics stacked in one column

The RTI activity log where every action is cryptographically chained, with absolute UTC timestamps

The activity log on a phone, with the verify chain, filters, and chained events in one column

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

Grid C4-C6, Slab Pre-Pour Hold Point

PDK-L2-CP-C4

Sticker location: Formwork edge at column line C4
Bound checklist: Slab pre-pour, ITP hold point

Rebar size and spacing verified against approved shop drawings3 photos required
Embeds and sleeves located per the coordination set2 photos required
Formwork dimensions and elevations checked2 photos required
Third-party inspection witnessed and released1 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

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

Today

You can't close the submittal because the one photo that proves the detail was installed is on someone's phone, or was never taken, and the crew has moved to another floor.

With RTI

The photo is captured against the checklist item at the moment of work and stored on the tag. By the time you go to close the item, the evidence is already filed, timestamped and attributed, not something you have to reconstruct.

Today

A hold point gets skipped, the pour or the cover goes ahead, and now you're writing an RFI to document work no one inspected before it was buried.

With RTI

The hold-point checklist must be submitted with its photos before the tag can be marked complete, and it sits on the review board for release. The inspection is on the record before the concrete is, not reconstructed afterward.

Today

Reconciling installed work to the approved submittal means cross-referencing a folder of undated photos against a stack of drawings, hoping they line up.

With RTI

Each verification photo lives on the checklist item and the location tag that produced it. The installed condition and the item it answers stay together, so the reconciliation is a record you read, not a puzzle you assemble.

Questions project engineers ask

How does RTI help me close out submittals and ITP line items?: The proof for each item is captured against the checklist item it supports and stored on the tag, with a timestamp and the person who took it. When you go to close the submittal or the ITP line, the photos and answers are already there and attributable, so you stop emailing the field for a shot that should exist.
Can I enforce a hold point so work doesn't proceed without the inspection?: Yes. Build the hold-point checklist, bind it to the tag on the physical location, and the required photos and answers must be submitted before it can be marked complete. It lands on the review board for you to accept or reject, so the record of the hold point exists before anyone covers or pours over it.
How do I match what was installed to the approved submittal?: The checklist item asks the crew to verify the installation against the approved shop drawing and photograph it. The photo, the answer and the location tag stay together, so reconciling installed work to the approved set is reading one record instead of cross-referencing a camera roll against a document.

Put it on a real job.

Tag one area, run one walk, and see the record it leaves behind. Start free. 30 days, no card required.

Start free See how it works