The Photo Gate
A rule, not a reminder.
Most inspection apps ask for photos. RTI refuses the submission without them — and it refuses on the server, where the field crew’s browser cannot argue with it.
The Photo Gate
The submit button does not care how busy you are.
This is the real field screen. Answer the items, attach the required photos, and watch the gate release. Skip one and the record never gets written.
RIV-A-F3-305
Riverside Commons / Building A / Level 3 / Unit 305
Electrical Rough-In Checklist · v1
Checklist progress
0/4
Mandatory items
0/3
Required photos
0/2
Wire pulled and secured*
Boxes at correct height*
Grounding continuous*
Circuit schedule matches drawings
Locked
0 / 2Photos
- 3 mandatory items are unanswered
- 2 photo-flagged items still need a photo
- Add 2 more photos — this checklist requires 2
- 3 mandatory items are unanswered
- 2 photo-flagged items still need a photo
- Add 2 more photos — this checklist requires 2
All records are tamper-evident
Photo gate · server-enforced
Where it is enforced
Browser
Button disabled. Helpful, not sufficient.
The crew sees exactly what is missing — unanswered items, 1 of 3 photos — and the submit control stays locked.
Server
Request rejected. This is the gate.
Submission runs through a single server routine that re-counts mandatory answers and attached photos. Short by one photo, the call fails and nothing is promoted.
Database
Constraint holds the line.
Row-level security only accepts an inspection as a draft, so nothing can be written as submitted directly. A check constraint keeps every checklist's photo minimum at one or more.
A UI check is a suggestion. RTI’s check runs where the record is written.
Try it on a real walk.
Build a checklist, print a sticker, and see what happens when the photos aren’t there.
Start free