When a new claim or exposure needs a field inspection, appraisal or other vendor work, the assignment is often created by hand from the claims system and sent by email or phone, so start times vary and the claim record does not show who has the work. On Verisk (estimating), the claim record already holds the context this work depends on: estimate totals and lines, revisions and supplements and supporting documents. Without a connection, that context is re-keyed into each downstream tool and drifts from the claim file.
A new or updated claim in the connected system starts the assignment workflow in VIP, and assignment status is kept against the claim so everyone works from the same record. With Verisk, VIP takes in estimate totals and lines, revisions and supplements and supporting documents and writes assignment context back to the claim. Confirm how estimate fields land on the claim, including the identifier used to match.
| Data | Direction | Detail |
|---|---|---|
| Estimate totals and lines | Verisk → VIP | Totals, categories and line detail attach to the claim so review does not start with a PDF. |
| Revisions and supplements | Verisk → VIP | Each revision is kept with its predecessor so movement in the estimate is visible. |
| Supporting documents | Verisk → VIP | Sketches, photos and reports are stored against the claim and tagged. |
| Assignment context | VIP → Verisk | Optional. Claim and assignment identifiers are sent so estimates return to the right file. |
Verisk has an existing integration with VIP. With Verisk, VIP takes in estimate totals and lines, revisions and supplements and supporting documents and writes assignment context back to the claim. Confirm how estimate fields land on the claim, including the identifier used to match.
Estimate totals and lines; Revisions and supplements; Supporting documents; Assignment context.
Assignment routing is built for carrier teams using Verisk, at the claims operations stage of the claim.