Inspections

Scheduling, conducting, submitting, and approving inspections — the core workflow in InspectAssets.

The inspection lifecycle

Every inspection moves through the same states. You'll see these as status labels in Inspection Management and on the Dashboard:

Status	Meaning
Scheduled	Created and assigned, not yet started.
In Progress	An inspector has started filling it out but hasn't submitted.
Completed	Submitted by the inspector.
Approved	Reviewed and signed off by an approver.
Rejected	Sent back by an approver; needs rework and resubmission.
Overdue	Past its due date without being completed.
Cancelled	Called off; no longer expected to be completed.

Finding your inspections

Inspection Management lists inspections with their site, asset, assigned inspector, due date, and status. Inspectors see the work assigned to them; managers and admins see the whole team's queue and can assign or reassign.

The My Approved Inspections view filters down to inspections that have completed the approval step — useful when you need to reference finished, signed-off work rather than active jobs.

Starting an inspection

There are three ways in, and they all end at the same screen:

• From the list — open Inspection Management and pick a scheduled inspection.
• By scanning — use Scan Asset and point the camera at the asset's QR code. If that asset has a scheduled inspection, InspectAssets opens it immediately ("Scheduled inspection found. Opening it now…"). If it doesn't, you'll land on the asset's passport instead.
• Direct link — inspection URLs are shareable, so a manager can send you straight to a specific job.

Once you're on the inspection, choose Start Conducting Inspection to begin filling it out.

Filling out the form

The form is generated from the inspection template assigned to that asset type, so the exact fields vary. The building blocks are always the same:

• Field types — text, number, dropdown/select, multi-select, date, and media fields (photo, image, file, attachment).
• Required fields — marked Required. You cannot submit while one is empty; you'll get "Please fill the required field: [field name]" naming the exact field.
• Units — numeric fields can carry a unit (for example, bar, °C, mm), displayed next to the input so readings are recorded consistently.
• Pass / Fail — individual fields can be marked pass or fail independently of their recorded value. A reading can be within tolerance but still fail on visual condition.
• Per-field photos — you can attach photos to a specific field rather than dumping them all at the end, which keeps evidence tied to the finding it supports.
• Asset Health — a template field named "Asset Health" is treated specially: its value feeds the asset's health trend over time. See Insights & Benchmarks.

Fields appear in the order the template defines, and the Previous Visits panel shows what was recorded for this asset last time — useful for spotting drift in a reading between visits.

Submitting

Choose Submit Inspection when the form is complete. The inspection moves to Completed and enters the approval queue if your organization requires sign-off.

Working offline

If you lose connectivity mid-visit, submissions are held locally in the Offline Queue rather than lost. Each queued item carries a status:

Status	Meaning	What to do
queued	Saved locally, waiting to upload.	Nothing — it syncs when you're back online.
synced	Successfully sent to the server.	Done. Safe to clear.
failed	Upload attempted and rejected.	Open it to read the error, then retry that item.

The Offline Queue screen shows whether you're currently online, counts of queued and failed items, and the time of the last successful sync. Failed items can be retried individually, so one bad submission doesn't block the rest.

Reviewing and approving

Opening a completed inspection shows the submitted values, per-field pass/fail results, and attached photos. Approvers can approve or reject from here, or work through the Approvals queue to handle several at once. Rejecting sends it back for rework rather than deleting it — the original submission stays in the record.

Editing templates

Users with manage_templates can change what inspectors are asked, via Customize Template: add, remove, and reorder fields, set which are required, attach units, and group related fields into sections.

Inspection Operations

Users with view_inspection_operations get a cross-portfolio operations view for coordinating inspection scheduling across multiple sites and teams at once — the inspection counterpart to Site Operations and Asset Operations.