Client-specific standards
Configuration can vary by client, loss type, and inspection profile from the desktop web app.
Configure what a complete inspection means for each client, carry those requirements to the property, and review the synchronized record from the office.
Current product shown with synthetic demonstration data.

Define a repeatable inspection approach instead of relying on memory.
See claim and inspection status, then open the underlying record when follow-up is needed.
Review a structured file built from required questions, photo categories, notes, and adjuster-approved narrative text.
Carry the configured requirements into the property, including through supported connectivity gaps.
Connect the applicable questionnaire, photo set, narrative template, and current report behavior in an inspection profile.
The adjuster opens the assignment and follows the visible questions, required items, and photo categories.
Queued field work uploads when connectivity returns, with pending, successful, and failed states available for review.
Authorized users open the synchronized record while the adjuster verifies the narrative and assembled inspection output.
Configuration can vary by client, loss type, and inspection profile from the desktop web app.
Questionnaires, required photos, progress, offline documentation, and supported signatures stay in one inspection.
The desktop workspace shows claim and inspection states with search, filters, and access to the underlying record.
Search the claim list, review its status, and open synchronized photos, notes, messages, documents, and generated reports. Follow-up starts from the record instead of a phone call.

Configuration Studio is authored from the desktop web app. Walk through the required behavior during setup rather than assuming an automatic carrier integration.
Illustrative example: a wind client could connect its question set, elevation and roof photo requirements, narrative template, and report behavior in one applicable profile. A different client can load a different standard. Configuration varies by client and inspection profile.
Adjusters can use a temporary deployment address as routing origin, a higher same-day cluster cap, and a user-set 5–100 mile clustering radius. Workforce dispatch, SLA enforcement, crew management, and the CAT operations console are not represented as current capabilities.
See what you can use today and what is coming before relying on a capability in a rollout decision.
Talk through your requirements, or start a trial and evaluate the current configuration yourself.