How this works
Capture an inspection once — building, unit data plate, A17.2-ordered checklist, photos — and the record exports as structured JSON. The client PDF, state submission, certificate and invoice all generate from that single record downstream. Everything saves to this device automatically; with cloud sync on, it also lands in the shared team database the moment you're back in signal.
Building & Contact
Unit Data Plate
Inspection
Your name, state license and QEI number are remembered on this device and pre-filled into every new inspection — check them if you're borrowing someone else's tablet. They stay on the device; they're written into a record only when you save one.
Inspection Result
—Two-way communication test · A17.1 8.6.11.2
Immediate hazard — is this unit safe to operate?
You marked at least one finding as a Severity 1 immediate hazard. That is not a note; it is a decision. Answer it here, before the record is approved.
Missouri's own public inspection records carry a red-tag column, so the state already treats this as a separate fact from the deficiency itself. Whichever you choose prints across the top of the report.
Deficiencies
Photos
Photos are compressed on-device and travel inside the inspection record.
General Notes
On-site signature
Who was there when you delivered the findings. Capture it before you leave the site — this is the part that answers “nobody told us” a year from now. Your own QEI signature is captured later, when you approve the record for filing.
Pre-flight
Everything the app knows about this record, in one place, ranked by what it would actually cost you. Read it before you seal.
Saving stores the record on this device and queues it for cloud sync. The JSON record is the master copy — every downstream output (client PDF, state submission, certificate, invoice) generates from it.
New job
Records live on this device (they survive closing the app). With cloud sync signed in, they also upsert into the shared inspections table. Export all writes every record and job to one JSON file — do it at the end of a route day. Restore reads that file back on any device; it merges rather than replaces, and it will never overwrite a sealed record.