Camera and library capture
Take a photo in the mobile app or choose an existing image from the device library.
Photo documentation
Claim photos that stay tied to the inspection
Adjuster Copilot keeps required-photo guidance, capture, categories, captions, ordering, upload status, and report use inside the same claim inspection workflow.
Product screenshots use approved demonstration data. Categories and captions remain subject to adjuster review.
Current product
What photo documentation supports today
The current workflow organizes human-captured evidence. It does not analyze image content or make claim decisions.
Required-category tracking
See covered and missing categories, capture from a missing item, or record why a required view cannot be photographed.
Category and caption review
Choose a category before saving, add an optional caption, and edit either value from photo details.
Saved display order
Review the gallery order and explicitly save a new sequence for the inspection.
Local offline evidence
Keep captured photos in local device storage and queue them with the inspection when connectivity is unavailable.
Photo-sheet and report use
Use server-confirmed photos in the inspection photo sheet and full inspection report.
Required-photo guidance
The checklist follows the inspection’s configured requirements
Required-photo behavior is resolved for the inspection rather than assumed to be identical for every claim.
Configured behavior
Required categories can be resolved from the applicable inspection profile, client, and loss-type configuration. The picker places those categories first and also offers supplemental types.
What the adjuster sees
Each required category shows whether it is covered, missing, or accompanied by an exception reason. Tapping an uncovered category opens capture with that category preselected for review.
Not a completeness guarantee
A covered category confirms that a categorized photo exists or an exception was recorded. It does not prove the image is clear, relevant, sufficient, or correct.
Capture to report
The photo workflow, step by step
Each stage preserves the difference between locally saved evidence and a server-confirmed upload.
- STEP 01
Review required photo guidance
See which configured categories are covered, missing, or documented with an exception reason.
- STEP 02
Capture or choose an image
Use the device camera or photo library. Starting from a missing category carries it into capture for review.
- STEP 03
Confirm category and caption
Choose the required category, add an optional caption, and verify both before saving.
- STEP 04
Review and organize
Edit the category or caption from photo details and set the intended gallery order.
- STEP 05
Confirm upload status
Distinguish Saved offline, Waiting to sync, Uploading, Uploaded, and Upload failed.
- STEP 06
Use uploaded photos in output
Generate the photo sheet or inspection report after synchronization.
Review in context
Category, caption, order, and status stay visible together
The current gallery displays each photo with its human-readable category, optional adjuster-entered caption, and upload status. Adjusters can open a photo for closer review and edit its category or caption.
Saving a new gallery order requires a connection. Do not assume a local move reached the server until the save succeeds.
Offline and upload behavior
A local photo is not yet an uploaded photo
The status label is the evidence for where each file is in the handoff.
The compressed photo is retained locally but has not reached the server.
Photo metadata or binary upload is queued for the inspection.
The app is actively sending the photo file.
The server has confirmed the binary upload.
The file needs retry or user attention before handoff.
Before leaving or handing off the file
- Review required categories and any exception reasons.
- Review photo category and caption accuracy.
- Reconnect with the inspection open so queued uploads can run.
- Resolve pending or failed items before relying on the server copy.
Photo-sheet output
Uploaded evidence can move into the inspection deliverable
Photo-sheet generation is a connected server action and uses uploaded—not merely local—photo files.
How ordering reaches the photo sheet
When an applicable inspection profile defines photo-sheet categories and display order, the generated sheet uses that sequence. Categories configured not to appear are omitted, and unmatched photos move to a final miscellaneous group.
Without applicable profile ordering, output keeps the saved photo sequence. Optional empty categories are skipped; configured required categories can remain visible as missing.
See how documented evidence informs narrative drafting
Practical constraints
Permissions, storage, file handling, and review
These operational limits are part of a reliable photo workflow.
Camera and library permission
The mobile app needs camera permission to take a photo and photo-library permission to choose an image. Denied access blocks that action.
JPEG-normalized output
Selected images are compressed and converted to JPEG. The longest edge is limited by photo type to 900, 1600, or 1920 pixels.
Local-storage dependence
Before upload confirmation, the photo depends on local app storage. Clearing or removing the app, signing out, or losing or changing the device puts unsynced evidence at risk.
Connectivity for handoff
Photo metadata and files need connectivity to reach the server. Photo-sheet generation and final report use require uploaded photos.
Web capture difference
Direct camera capture is not offered in the web app. The web workflow uses file selection instead. No broader device-support promise is made.
Human review remains required
Categories, captions, ordering, image quality, checklist coverage, exception reasons, and upload status all require user review.
Captions are optional and currently limited to 2,000 characters. A category must be selected before a new photo is saved.
Unsupported and planned behavior
Photo organization is not image analysis
The current product does not claim to:
- Recognize damage automatically from image pixels.
- Detect fraud or image manipulation.
- Make coverage, causation, or severity decisions.
- Guarantee that a required photo is usable or complete.
- Generate captions through AI image analysis.
- Create unsupported carrier or estimating-system outputs.
Related workflows
See photo documentation in the larger inspection
All current features
Review the complete capability inventory and availability.
ExploreField-to-office platform
See where photos, narratives, reporting, and office review connect.
ExploreOffline inspections
Understand local storage, queued work, synchronization, and failure states.
ExploreFor independent adjusters
Follow the complete assignment-to-report workflow for field adjusters.
ExploreFor independent adjusting firms
See how configured photo requirements support repeatable field documentation.
ExploreEvaluate the workflow
See required photos, capture, upload states, and output together
Tutorials will use synthetic inspection data to show the current photo workflow without implying image-analysis capabilities.