Every inspection ends with proof attached

It replaces the paper checklist with one that runs on a phone, so every answer is stored with the photo, the reading, the time and the person who gave it. The difference from a forms app is what the answer is attached to: the inspection belongs to a specific asset, joins that asset’s history, and a failed check can raise work against it.

Yes. The builder is drag-and-drop, with sections you can reorder, and each check is set to what it actually needs — pass, fail or N/A, a numeric reading held between a minimum and a maximum, free text, a photo or a signature. Checklists belong to the organisation, so the same one runs at every site instead of being rebuilt team by team.

Upload the PDF your team inspects from and AI extracts a checklist out of it, which you review in a preview before anything is saved. You can also describe what you need in a sentence and generate from that, or build the checks by hand — and edit the result either way.

Checklists are stored on the device, so an inspection runs the same with or without coverage. Answers, photos and signatures queue on the phone and upload themselves when a connection returns, retrying on their own if it drops mid-upload. While the phone is online the count of answered checks updates as the technician works, so progress is visible without phoning anyone.

The failure is recorded against that specific check, with whatever photo or comment its rules require. From the failed answer you raise an action in one tap, and it arrives already carrying the inspection, the check, the asset, the site and the client. QAI does not fire that off by itself — a person still decides — but nobody re-types the context.

Give a checklist an interval in days and every asset it covers carries its own next-inspection date. Anything past that date shows in red in the asset list, and the technician finds it waiting on the home screen of the mobile app rather than having to go looking for it.

Checklist analytics ranks every check by how often it fails across a date range you choose, and counts skipped answers separately from failures, so a check nobody performs does not read as a check that passes. The filters are the date range and the checklist — there is no side-by-side comparison of one site against another yet.

Each completed inspection stores who ran it, when it started and finished, how long it took, the GPS coordinates it was completed at, every photo attached and the technician’s signature. Checklists that need a second pair of eyes can require an approval signature, stored with the approver’s name and the time they signed, and any inspection exports as a PDF.

Yes. A completed inspection can be shared as a link that opens without logging in, which is how most teams get a record to a client, a landlord or a contractor. They need no account, and it costs you no licence.

No. Every check on a checklist is shown to the technician; nothing is revealed or hidden based on an earlier answer. You can set rules per check instead — require a photo when it fails, a comment before it can be skipped, a numeric reading held to a range, or mark a check instant-fail so one bad answer fails the whole inspection. That covers most of what branching gets asked for, but if you need a checklist that genuinely changes shape mid-inspection, QAI is not there yet.

No. Inspections are part of QAI on one per-user subscription, with no separate module fee. Run inspections and nothing else if that is all you need — work orders, assets and analytics are there when you want them, not something to buy later.