The right standard
The applicable profile connects the client, loss type, questionnaire, photo requirements, narrative template, and report behavior.
Questions, required photos, progress, offline capture, and report readiness stay connected to the assigned inspection—so the standard is visible while the work is happening.
Current product shown with synthetic demonstration data.

The product guides the documentation sequence; the adjuster still observes, decides, and reviews.
The applicable profile connects the client, loss type, questionnaire, photo requirements, narrative template, and report behavior.
Required, incomplete, recommended, and completed states keep the inspection readable without replacing adjuster judgment.
Answers, damage items, photos, notes, and supported signatures remain attached to the same inspection record.
The long checklist becomes a short path. Detail appears inside the inspection when it is relevant.
Load the assigned claim and applicable inspection data before entering unreliable coverage.
Work through configured questions, damage items, required photo categories, notes, and signatures.
Use progress and readiness states to find missing required work before leaving the property.
Reconnect, confirm synchronization, then review the editable narrative draft and assembled inspection output.
Supported inspection evidence can produce an editable narrative draft. The adjuster reviews and corrects it before file use; guidance is not autopilot.
Supported field documentation can continue after the inspection data has been downloaded. Final synchronization, server-confirmed uploads, and connected report actions require connectivity.
Yes. The applicable profile, questionnaire, and photo requirements can vary by configured client, loss type, and inspection type. This is configured behavior—not a carrier integration claim.
No. Readiness surfaces configured requirements and unfinished work. The adjuster still reviews relevance, accuracy, image quality, and the final file.
See what you can use today, and the AI Usage & Disclaimer for the human-review boundary.
Use a real claim type and see how requirements, evidence, readiness, and review stay connected.