Photo documentation

Claim photos that stay tied to the inspection

Required-photo guidance, capture, categories, captions, ordering, upload state, and inspection output remain part of one claim workflow.

Categories, captions, image quality, and completeness remain subject to adjuster review.

Adjuster Copilot — inspection photos captured and labeled by area
One guided photo set

Capture, label, and verify while the property is in front of you

The checklist can vary with the configured client, loss type, and inspection profile.

Capture against the checklist

Start from a missing category, take or choose the image, and confirm its category before saving.

Keep the meaning attached

Categories, optional adjuster-entered captions, saved order, and upload state remain visible in the inspection gallery.

Know what reached the server

Offline, waiting, uploading, uploaded, and failed states distinguish local evidence from confirmed handoff.

Capture to output

Four milestones replace a camera-roll cleanup project

  1. STEP 01

    Review

    See which configured categories are covered, missing, or documented with an exception reason.

  2. STEP 02

    Capture

    Take a photo or choose one from the library, then confirm its category and optional caption.

  3. STEP 03

    Organize

    Review the gallery, edit labels when needed, and save the intended display order.

  4. STEP 04

    Confirm

    Reconnect, resolve pending or failed uploads, and use server-confirmed photos in the current output workflow.

Adjuster Copilot — assembled inspection photo sheet report
Current assembled inspection photo sheet using demonstration data
Details and limits

Open the operational detail only when you need it

What do the upload states mean?Five labels separate device-saved work from server-confirmed evidence.
  • Saved offline: The compressed photo is retained locally but has not reached the server.
  • Waiting to sync: Photo metadata or the binary upload is queued for the inspection.
  • Uploading: The app is actively sending the photo file.
  • Uploaded: The server has confirmed the binary upload.
  • Upload failed: The file needs retry or user attention before handoff.
How is the photo sheet ordered?Configured profile order when available; saved photo order otherwise.

When the applicable inspection profile defines photo-sheet categories and display order, the generated sheet follows that sequence. Categories configured not to appear are omitted, and unmatched photos move to a miscellaneous group. Without applicable profile ordering, output keeps the saved photo sequence.

What should be reviewed before handoff?The checklist is guidance, not a guarantee of sufficiency.
  • Required categories and supported exception reasons.
  • Image relevance, clarity, category, caption, and saved order.
  • Pending or failed uploads before relying on the server copy.
Review offline synchronization →
Capture and file behaviorPractical file details, kept out of the primary story.

Take a photo in the mobile app or choose one from the device library. On the web app, attach files instead of shooting directly. Photos are converted to JPEG and sized by type for the current output workflow; the photo sheet builds from server-confirmed uploads.

Photograph one practice inspection end to end

See the required set, capture flow, upload states, and assembled output together.