One product for every inspection workflow

Two halves, doing different jobs

MeetInspect is a SaaS inspection platform made of a native iOS application and a web administration environment. That division is not incidental — the two halves have genuinely different users, contexts and constraints, and treating them as one product with two skins is where inspection tooling usually goes wrong.

The dashboard is used sitting down, with a keyboard, by someone configuring how inspections should work. The application is used standing up, one-handed, by someone with fifteen minutes and a resident waiting. Optimising both for the same interaction model compromises each.

The Inspection Runner

The Inspection Runner is the part of the iOS application that carries an inspector through a workflow: the fields and checks to complete, navigation between steps, evidence capture, and the persistence that keeps all of it intact as the inspection proceeds.

It is built around completing inspections efficiently in real working conditions rather than around demonstrating features. Photo capture happens inside the runner rather than as a separate step, so each image belongs to the check that required it, and the application is engineered specifically around retaining captured photos as the inspector continues through the workflow.

• ✓Inspection fields and checks completed in sequence
• ✓Photo capture integrated into the workflow rather than bolted on
• ✓Navigation between inspection steps, with state preserved
• ✓Offline handling, with loading and recovery states

The administration environment

The web dashboard is the management side of the platform: where inspections are created and managed, and where the structure that field teams receive is defined. It is the point at which one organisation's standard becomes the thing every inspector is actually handed.

MeetInspect also includes functionality for generating inspection workflows from prompts, producing a structure that can be reviewed and adjusted before use. Generated content is a starting point for a person to check, not an output to accept unexamined.

Records, evidence and output

An inspection record holds the answers, notes, photographs and signatures captured during a visit, connected to the property and the template that produced it. A PDF report is generated from that record once it is complete.

Keeping the report as a rendering of the record rather than a separate document is what stops the two diverging. There is one account of what was observed, and the document people read is a view of it.