FAQ

Questions inspection teams ask before getting started

Direct answers about workflows, offline fieldwork, templates, reports, access and subscriptions.

MeetInspect specialist answering questions about inspection workflows

What it covers

Product and workflow

Open each question for a concise answer, then follow the related documentation when you need operating detail.

Can inspectors work without signal?

Yes. MeetInspect supports guided offline field capture. Saved work synchronises after the device reconnects; inspectors should not sign out or remove the app while work is pending.

Can we create our own templates?

Workspace administrators can configure templates around the sections, questions and evidence required by their inspection process. Available capabilities depend on the workspace plan.

What evidence can an inspection include?

A workflow can include structured answers, notes, photographs, annotations and signatures where the template and device permissions support them.

How are reports created?

After the record has synchronised and been reviewed, authorised users can generate a PDF from the completed inspection content and workspace report configuration.

What roles are available?

The documented workspace roles are Admin, Inspector and Viewer. Billing ownership is separate from an ordinary invitation.

Is MeetInspect suitable for multiple inspection types?

Yes. Separate templates can represent different property, safety, quality, handover or operational workflows inside the same workspace.

In practice

Account, support and privacy

How do we start?

Create a workspace, configure one representative template and complete a test inspection before a wider rollout.

Where can I get help?

Use the documentation first, then email support@meetinspect.com with the workspace, approximate time, device and concise issue description.

How is personal information handled?

The Privacy Policy explains account, workspace, inspection, billing and diagnostic information, service providers, retention and available choices.

In depth

Beyond the common questions

What inspection software can and cannot decide

Inspection software structures and records professional judgement; it does not replace it. A template can require that a question is answered and that a photograph accompanies the answer, but it cannot determine whether a crack is structural or whether damp is condensation. Those remain the inspector's assessment.

This matters when evaluating any automated or generated capability. MeetInspect includes functionality for generating inspection workflows from prompts, which produces a structure to review and adjust — not a judgement that can be accepted without checking. Generated inspection content should always be reviewed before use.

Where data lives during an inspection

During a visit, particularly one conducted without connectivity, the inspection exists on the device. It becomes shared once synchronised. Understanding this sequence explains most of the operational advice around field work: do not sign out mid-inspection, do not remove the application with work pending, and confirm synchronisation before considering a visit closed.

These are not arbitrary cautions. They follow directly from the fact that captured-but-unsynchronised work has exactly one copy.

Adapting to different inspection types

Organisations rarely perform one kind of inspection. Separate templates can represent different property, safety, quality, handover or operational workflows inside the same workspace, which is what allows a single programme to cover genuinely different work without forcing it into one shape.

The judgement is about where to draw the line between templates. Inspections that support the same decision belong together; inspections that answer different questions are better separated even when they cover the same building.