Inspection profiles
The applicable profile can connect an inspection type with configured questionnaire, photo, narrative, and workflow behavior.
Guided inspections
Guided insurance inspections from first section to report review
Follow a configured digital inspection workflow that keeps questions, required photos, evidence, progress, synchronization, narrative review, and report readiness connected to the claim.
Screenshots show the current product with synthetic demonstration data. Completion indicators guide human review; they do not make claim or compliance decisions.
Current workflow
Configured guidance without removing adjuster judgment
The inspection workflow presents applicable requirements and current status. The adjuster observes the property, decides what evidence is relevant, verifies accuracy, and remains responsible for the completed file.
Required sections
The inspection view distinguishes required, incomplete, recommended, and completed areas instead of presenting an unstructured form.
Configurable questionnaires
Applicable question templates and required-answer states guide what the adjuster records for the inspection.
Required photo categories
Configured photo categories show covered, missing, or exception states and link directly into evidence capture.
Progress and readiness
Visible section indicators and a weighted readiness display help locate unfinished work while a separate completion gate preserves hard blockers.
Offline field capture
Downloaded inspections support local answers, notes, damage items, photos, checklist decisions, and narrative text through connectivity gaps.
Inspection profile
One profile connects the requirements that apply
An inspection profile is the blueprint used to resolve relevant workflow configuration. It does not independently inspect the property or certify the resulting file.
Current configurable behavior
- Applicability by configured client, loss type, and inspection type
- Questionnaire template and required-answer states
- Required photo categories, minimums, ordering, and visibility
- Narrative template selection and current report behavior
Important configuration boundary
Requirements depend on the profile and templates that actually resolve for the inspection. Their presence does not prove that every client standard has been configured, integrated, or enforced. Firms should verify configuration during setup and adjusters should verify the runtime requirements before handoff.
Review current configuration capabilitiesStart to finish
The guided field inspection workflow
Each stage advances the same inspection record instead of creating separate notes, camera-roll evidence, and report inputs.
- STEP 01
Open the assigned inspection
Start from the claim and load the applicable inspection data before entering an area with unreliable connectivity.
- STEP 02
Review the guided sections
See the inspection modules, required states, recommended work, and current progress before beginning field capture.
- STEP 03
Answer the questionnaire
Complete the configured questions that apply to the inspection and review any required answers that remain missing.
- STEP 04
Document damage and evidence
Record damage items, notes, required photo categories, supplemental photos, and applicable signatures in the inspection.
- STEP 05
Review readiness and blockers
Use section indicators and the readiness display to locate unfinished work, then review the separate completion requirements before submission.
- STEP 06
Reconnect and synchronize
Return to the affected inspection with the app open, confirm queued work reaches the server, and resolve pending or failed items.
- STEP 07
Review the narrative draft
Generate an AI-assisted narrative from supported field evidence, then edit and approve the draft rather than treating it as a completed decision.
- STEP 08
Prepare the report
After synchronization, verify the documented evidence and reviewed narrative used by the current report and photo-sheet workflow.
Evidence collection
Questions, damage documentation, and photos stay in context
Guidance connects the required work, while the dedicated feature owners explain each capture and synchronization behavior in depth.
Questionnaire responses
Applicable questions appear inside the inspection. Required answers contribute to the configuration/completion state; the response remains the adjuster's documented observation.
Required and supplemental photos
Required categories show coverage and missing states. Adjusters can capture in context, add captions, organize the gallery, and record an exception where supported. A category state is not a guarantee that the image is sufficient.
Review the photo documentation workflow
Progress and completion
Readiness helps locate work; blockers control completion
The visible percentage is a weighted progress aid. Required-photo coverage, required questions, damage documentation, narratives, and signatures contribute differently, and non-applicable requirements are handled separately.
Section indicators
Required, incomplete, recommended, and completed states direct the adjuster to the part of the inspection needing attention.
Weighted readiness
Partial photo coverage can move the display incrementally, while other categories contribute when their applicable requirement is satisfied.
Completion gate
Hard blockers remain authoritative. A progress percentage does not certify compliance, guarantee evidence quality, or replace final review.
Offline to synchronized
The inspection can continue locally; the handoff cannot
Downloaded inspection data supports field capture without service, but local completion and server-confirmed synchronization are different states.
During the connectivity gap
Continue supported questionnaire answers, damage items, notes, photos, checklist decisions, and narrative text from data already downloaded to the device. Unsynced evidence remains dependent on local app storage.
After reconnecting
Reopen the affected inspection with the app in the foreground, allow queued work to synchronize, and verify pending, successful, or failed states. Do not rely on a report or server copy until the required evidence is confirmed uploaded.
Review exact offline and synchronization behaviorNarrative and report readiness
Captured evidence supports a draft and an assembled file
The final stages remain review steps, not automated claim decisions.
Draft, verify, then prepare the output
Supported inspection evidence can produce an editable narrative draft. The adjuster reviews the language, corrects the facts, and decides what belongs in the file. After required synchronization, current report and photo-sheet actions use the available server-confirmed evidence.
Understand AI narrative generation and human reviewapp.adjustercopilot.ai/claims/gs-26-3329
Product boundaries
Guided does not mean autonomous
Current responsibility model
- The workflow presents configured requirements and status.
- The adjuster observes, records, labels, and verifies evidence.
- The adjuster reviews AI drafts and the final inspection file.
Not represented as current
- Automated claim, coverage, causation, or severity decisions
- AI completing the inspection without the adjuster
- Computer-vision damage recognition or fraud detection
- Automatic compliance certification or enterprise QA scoring
- Carrier-system integrations or automatic carrier-rule enforcement
Expanded questionnaire libraries, report export formats, team roles, integrations, analytics, and advanced damage-detection AI remain in-development or roadmap items as identified on the Platform page.
Related workflows
See what the guided inspection connects
Independent adjusters
Follow the full assignment-to-report workflow around the guided inspection.
ExploreOffline inspections
Review local storage, connectivity boundaries, visible sync states, and recovery limits.
ExplorePhoto documentation
See required-category guidance, capture, organization, upload states, and photo-sheet use.
ExploreRoute planning
Organize the day’s mapped claims before beginning field inspections.
ExplorePlatform overview
See how guided field documentation connects to scheduling, synchronization, office review, and reporting.
ExploreBuyer questions
Questions about guided inspection workflows
Can inspections be completed offline?
Supported field documentation can continue after the inspection data has been downloaded. Final synchronization, server-confirmed uploads, and connected report actions still require connectivity.
Can inspection requirements differ by client?
The applicable inspection profile, questionnaire, and photo requirements can vary by configured client, loss type, and inspection type. This is configured behavior, not a carrier integration or automatic carrier enforcement claim.
How are required photos handled?
The checklist shows configured categories as covered, missing, or documented with an exception reason. The adjuster still reviews image relevance, clarity, labels, and upload status.
What happens if I lose connectivity?
Supported changes are stored locally and queued. When service returns, reopen the inspection, allow synchronization to run, and verify whether each item is pending, synced, or failed.
Are AI-generated narratives reviewed before submission?
Yes. The current AI capability produces an editable narrative draft from supported inspection evidence. The adjuster must review and correct it before file use.
Evaluate the workflow
Walk through a complete synthetic inspection
Tutorials will show profile resolution, sections, questionnaire and photo requirements, offline states, narrative review, and report preparation together.