What should I do first if the app misbehaves mid-inspection?

Protect unsynchronised work. Reconnect, keep the application open and let pending inspections upload before signing out, reinstalling or restarting — those actions risk the only copy of work that has not yet reached the workspace.

What information makes a support request actionable?

The workspace, the approximate time, the device and app version, the connectivity state, and what was expected against what happened. Timing is the most valuable single detail because it allows the event to be located.

How do I tell a fault from a configuration problem?

By consistency. Configuration issues behave identically every time — a missing question is always missing. Faults tend to be intermittent or context-dependent. Checking workspace configuration first resolves a large share of reported problems.

Support

Get an inspection workflow moving again

Start with the relevant guide, protect any unsynchronised mobile work and send the support team enough context to investigate the underlying issue.

Start free Talk to sales

MeetInspect support team reviewing an inspection record

What it covers

Resolve the most common issues safely

Do not sign out, uninstall the mobile app or delete local data while an inspection is waiting to synchronise.

Sign-in and access

Confirm the correct email and workspace, check the invitation and ask an administrator to verify the member role.

Correct account
Active invitation
Appropriate role

Offline and sync

Reconnect to a stable network, keep the app active and confirm uploads finish before closing the inspection.

Protect pending data
Check device storage
Record inspection ID

Templates and reports

Verify required items, synchronisation status and workspace configuration before regenerating or escalating.

Required evidence
Review status
Report configuration

In practice

Contact support with useful context

Identify the workspace

Include the workspace and, when safe to share, the inspection identifier—not unnecessary customer data.

Describe what happened

Provide the approximate time, expected outcome, actual outcome and steps already attempted.

Include the environment

Share the app or browser version, device type and connectivity state relevant to the issue.

In depth

Resolving field problems without losing work

Protect unsynchronised work first

When something goes wrong mid-inspection, the instinct is to restart the application, sign out and back in, or reinstall. Each of those risks the one thing that cannot be recovered: inspection work that has been captured on the device but not yet transferred to the workspace.

The correct first step is almost always the opposite of the instinct. Re-establish connectivity, keep the application open, and allow pending work to synchronise before attempting anything else. Only once the record is safe are the usual remedies appropriate.

Do not sign out while an inspection is pending synchronisation
Do not remove or reinstall the application with unsynchronised work
Reconnect and keep the app open until uploads complete
Note the inspection identifier before attempting any other fix

Describing a problem so it can be investigated

Support requests that identify the workspace, the approximate time, the device, the connectivity state and what was expected versus what happened are resolvable. Requests describing a symptom without context usually generate a round of questions before anything can begin.

The most valuable single detail is usually timing. Knowing when something occurred allows the event to be located; knowing only that it happened recently does not.

Distinguishing configuration from malfunction

A significant share of reported problems are configuration rather than faults: a template that does not include the expected question, a member without the role required for an action, a report missing a section that was never configured into it.

Checking the workspace configuration before escalating resolves these faster, and the distinction is usually straightforward — a fault behaves inconsistently, while a configuration issue behaves the same way every time.

Common questions

What should I do first if the app misbehaves mid-inspection?: Protect unsynchronised work. Reconnect, keep the application open and let pending inspections upload before signing out, reinstalling or restarting — those actions risk the only copy of work that has not yet reached the workspace.
What information makes a support request actionable?: The workspace, the approximate time, the device and app version, the connectivity state, and what was expected against what happened. Timing is the most valuable single detail because it allows the event to be located.
How do I tell a fault from a configuration problem?: By consistency. Configuration issues behave identically every time — a missing question is always missing. Faults tend to be intermittent or context-dependent. Checking workspace configuration first resolves a large share of reported problems.