Inspection Run

The Inspection Run page is a step-by-step checklist runner used for inspection-type tasks. It’s designed to be used while you’re physically inspecting equipment, capturing evidence, and recording results.

Platform

#Inspection Run

The Inspection Run page is a step-by-step checklist runner used for inspection-type tasks. It’s designed to be used while you’re physically inspecting equipment, capturing evidence, and recording results.

#How to get here

Common entry points:

  • From Tasks in Agenda view: tap an inspection task
  • From Task Details: open the inspection action (when available)

#What you see on this page

#1) Header card

Shows:

  • Inspection/template title and version (when available)
  • Current run status
  • Auto-save status (the run saves as you go)

#2) Step list

Each step is a card where you can:

  • Set the step result/status (pass/fail/needs work, depending on the template)
  • Add notes
  • Add attachments (photos/files)
  • Remove attachments (if not finalized)

While attachments are uploading, the step may show an uploading indicator.

#3) Finalize inspection

At the bottom, you may see Finalize inspection.

  • Finalizing locks the run as complete.
  • Once finalized, the run becomes read-only and a summary appears.

#Primary workflows

#Complete an inspection run

  1. Work through the steps top to bottom
  2. Mark each step’s result
  3. Add notes and attachments where helpful
  4. Tap Finalize inspection

#Attach evidence

  1. Open a step
  2. Tap Add attachment
  3. Choose camera/gallery/files (as prompted)
  4. Wait for upload to finish

#Leaving the page

When you go back, the inspection runner returns you to the previous screen and can trigger a refresh so task status updates are visible.

#Tips

  • If you see a read-only state, the inspection may already be finalized.
  • Keep an eye on upload indicators if you’re on a slow connection.

#Platform behavior

#iOS

  • The workflow and labels on iOS follow this page as written.
  • Controls (pickers, sheets, and permissions dialogs) use native iOS presentation.
  • Step attachments use iOS camera/photo/file pickers and iOS permission prompts.

#Android

  • The workflow and labels on Android follow this page as written.
  • Controls (pickers, sheets, and permissions dialogs) use native Android presentation.
  • Step attachments use Android camera/photo/file pickers and Android permission prompts.

#Web

  • No standalone inspection-run route is exposed on web.
  • Inspection/task execution workflows are integrated into maintenance contexts at /maintenance.
  • Use maintenance task detail actions for inspection-related steps.