The most common question we hear from claims teams is a fair one: "We already run Xactimate. Where does ContentsIQ fit, and are you asking us to rip anything out?" The answer is no. ContentsIQ is not an estimating platform and it is not a replacement for the tools your carriers and firm already standardize on. It solves a different, upstream problem: turning the messy pile of contents inputs into review-ready valuations with evidence, before that work reaches your estimating and claim systems.
What Xactimate and XactContents actually do
It helps to be precise about the tools, because they do different jobs. Xactimate is the industry-standard estimating platform, and its primary function is structural: the building, the repairs, the trades. Personal property is a separate discipline, which is why Verisk built XactContents to estimate replacement costs for personal property, applying actual cash value and replacement cost calculations and depreciation schedules to individual items.
Both are estimating and claim-ecosystem infrastructure. They assume you already have a clean, structured list of items to work from. The hard part on a large contents claim is not the estimating math. It is getting from a phone full of field photos and a half-finished spreadsheet to that clean, sourced list in the first place.
Where ContentsIQ fits: upstream of the estimate
ContentsIQ lives at the messy front end. You upload what you actually have, and the platform drafts the structured output your estimating workflow needs. The division of labor is clean.
| Stage | Tool | What happens |
|---|---|---|
| Messy inputs to review-ready list | ContentsIQ | Identify items, draft descriptions and replacement cost values, attach evidence, route to professional review |
| Structure estimate | Xactimate | Estimate the building and repairs |
| Personal property estimate | XactContents | Apply ACV, depreciation, and settlement math to the item list |
Read left to right, ContentsIQ produces the input the rest of the workflow has always assumed you would build by hand. It handles identification, valuation, and documentation on the contents side, then the reviewed output flows into your estimating and claim systems in whatever structured form you work in. This is the same complementary role covered in our guide to contents valuation support that complements restoration and packout workflows: keep your field and estimating tools, and add the valuation and evidence layer in front of them.
A large-loss example, end to end
Consider a total-loss fire with a 2,000-item inventory. The field team photographs and packs out. Today, someone then spends days turning those photos into a line-item list, researching prices one at a time, and pasting them into a spreadsheet before any estimating tool sees the data. That research bottleneck is exactly where ContentsIQ earns its place, and it is the core of processing large-loss and CAT contents claims.
With ContentsIQ in the flow, the team uploads the photos and any partial lists, the platform drafts a description and a replacement cost value for each item with a comparable listing behind it, and a professional reviews and approves each line. The finished, sourced item list is then ready to move into XactContents or your carrier's required format. The estimating tools do what they do best; ContentsIQ removes the manual research that used to gate them. The same pattern applies when documenting contents after a fire at smaller scale.
What changes for your team, and what does not
Adopting ContentsIQ does not ask your team to learn a new estimating system or your carriers to accept an unfamiliar format. The estimating tools, the claim files, and the review steps you already run stay in place. What changes is only the front of the contents process: instead of an estimator opening a blank spreadsheet and a dozen browser tabs, they upload the inputs they already have and review drafted, sourced values. The output is designed to leave the platform in the structured form your workflow expects, so the handoff into estimating is a copy of clean data rather than a re-entry job.
That is the whole design goal: additive, not disruptive. A tool that forced a workflow change would create the friction it is meant to remove, which is why ContentsIQ deliberately stops at the boundary of the estimate rather than trying to become one. The estimators keep their judgment and their systems; the platform absorbs the repetitive research that used to sit between the field and the estimate. For a firm running dozens of concurrent claims, that boundary is exactly where the time was being lost, and putting a drafting-and-review layer there is what frees the team to handle more volume without adding headcount.
What ContentsIQ does not do
Being clear about the boundaries is part of the answer. ContentsIQ does not estimate structure, does not replace Xactimate or XactContents, and does not submit claims for you. It is not a public adjuster, not a negotiation tool, and it makes no promise about payout amounts. It drafts contents valuations and evidence, and your licensed professionals make every final judgment on condition, match, and coverage. On the data side, teams handling sensitive claim files can review how ContentsIQ handles your claim data before uploading anything.
The result is additive. Your estimating stack stays exactly as it is, your carriers see the formats they expect, and the days of manual contents research turn into a review pass over drafted, sourced values. For more on the valuation approach and related workflows, the ContentsIQ blog covers the full contents-claim process, and you can talk to the ContentsIQ team about how it slots into your specific workflow.