Skip to main content
An inspection was created on the web but the inspector cannot find it in Assigned Inspections on mobile. This is the single most common first-run problem and almost always comes down to one of the causes below. Walk this page top to bottom.

1. The real reasons a job doesn’t appear on the phone

Two conditions hide a job from the Assigned Inspections list on mobile. An unsigned or unsent agreement doesn’t hide it. Check them in order:
  • The inspection is more than 30 days in the future. The Assigned Inspections list only shows jobs within a 30-day window. A booking two months out stays hidden until it enters the window.
  • The inspector’s display name doesn’t exactly match the assigned name on the inspection. The match is case- and whitespace-sensitive. If the inspector’s user profile has “Jane Smith” but the inspection says “Jane Smith” (two spaces) or “jane smith”, the job is hidden.
Fix any of these and the job appears on the next pull-to-refresh in Assigned Inspections. A missing template does not hide the job; it shows a “Setup Required” card on the inspection. Confirm the inspection has a template and a narrative collection assigned; the caption library is optional (missing it means an empty autocomplete, not a block).

2. No narrative collection is set

A narrative collection is needed to start the inspection (it does not hide the job). Libraries are set per inspection on Inspection Details, with company defaults in Business Ops › Company Info › Inspection Defaults. The template association in the Narrative Library is only a fallback. A missing caption library is not a block; the caption autocomplete is just empty.

3. The inspector isn’t marked as an Inspector

The Inspector toggle affects the booking roster (who can be booked), not what appears on mobile. If the inspector is missing from the booking form or scheduling, check the toggle:
  • Open Business Ops › Users tab
  • Edit the inspector
  • Confirm the Inspector toggle is on

4. The agreement is unsigned (blocks starting, not syncing)

If the job is grayed out with an Agreement Required label, it’s waiting on the agreement. The sync works; the start check is separate. Whether an unsigned job can be started depends on your Signed agreement policy:
  • Signed before the client can view the report or Handled outside the app: the agreement never blocks Start.
  • Signed before the inspection starts: Start needs the client’s signature in 1nspecT, a recorded outside agreement (Signed by and Date signed), or an exemption. Ticking Client already contracted externally without filling in who signed and when isn’t enough. A blocked job is grayed out with an Agreement Required label, and tapping Start shows Signed Agreement Required.
A reinspection with no agreement of its own counts as signed when the original inspection’s agreement is signed. To unblock it, have the client sign in their portal, or record an outside agreement on Inspection Details (Record outside agreement). Then the inspector pulls to refresh.

Mobile-side verification

On the phone:
  • Pull down to refresh on Assigned Inspections
  • Confirm the inspector is signed in as the right user (Config does not show the account, so check the sign-in email)
  • Confirm the inspection is scheduled within the next 30 days (older or far-future jobs don’t appear in Assigned Inspections)

Still not working

Email support@mymavtech.com with:
  • The order number
  • The expected inspector’s email
  • Confirmation of the assigned inspector’s exact display name, the template and the narrative collection