Xactimate contents inventory: the complete 2026 workflow for adjusters and restoration teams

If you adjust property claims for a living, the contents portion of an Xactimate estimate is the part of the workflow most likely to swallow a full desk day. Structural lines are templated, repetitive, and fast — drop a roof, pull a few rooms, the system fills in the labor. Contents lines are different. Every item is unique, every replacement cost needs a defensible source, every depreciation decision is its own judgment call, and the carrier on the other side of the estimate is reading the schedule line by line.

This is a working guide to how contents inventories actually move through Xactimate in 2026 — the three workflow paths Verisk offers, the line-item format Xactimate expects from external tools, the errors that get schedules kicked back, and the AI-extraction shortcut that has reshaped the desk-time math in the last twelve months. We sell software in this category, so read what follows with that lens; we have tried to be specific enough that you can call the bias out when you see it.

Where contents fits in the Xactimate workflow

Xactimate is, first, a structural estimating tool. Contents arrived in the platform as a secondary discipline and has lived there as a module rather than a first-class workflow. The implication is practical: most of the friction adjusters and restoration estimators feel on contents claims comes from the fact that the contents schedule is being asked to live inside a tool whose center of gravity is roof pitches and drywall.

A contents schedule in Xactimate has to do four things. It has to name each item in language a desk adjuster recognizes. It has to apply a sourced replacement cost — ideally with a reference link or document trail back to a current retail price. It has to categorize the item against a depreciation table appropriate to its class. And it has to carry a condition grade that matches what the source photo shows.

When all four of those are present and consistent across the schedule, the contents portion of the estimate moves through carrier review in days. When one is missing — or, more often, when depreciation logic varies between similar items — the schedule comes back with line-level revision requests, and the time savings the team thought they were buying with Xactimate evaporate into supplements.

For a deeper look at the same four-check rubric from the public adjuster side, see the PA contents inventory field guide. For the carrier side, see the staff adjuster desk review guide.

The three workflow paths

Verisk supports three distinct paths for getting contents into an Xactimate estimate. Most adjusters know one or two of them; very few teams have used all three on the same kind of claim to compare. They are not interchangeable, and choosing the wrong path is one of the biggest predictors of how painful the contents desk day turns out to be.

Path 1: XactContents (in-platform)

XactContents is a contents module that lives inside the Xactimate desktop and cloud editions. Contents lines sit alongside structural lines in the same estimate, share the same export, and reference Xactware's pricing data for replacement costs. For carriers and IA firms that run their entire claims operation inside the Verisk stack, this is the default.

The strength of XactContents is integration depth. The contents schedule is part of the same document as the rest of the estimate, depreciation flows from the same pricing tables, and the export goes to the carrier in the format the desk adjuster opens every day. Nothing leaves the Xactimate environment.

The weakness is workflow ergonomics. Entering 200 contents lines through a UI built primarily for structural items is slow. The category and pricing pickers do not have the depth of a contents-specialist tool. And there is no AI extraction from photos — every line is hand-entered or imported from a CSV the estimator builds offline.

Path 2: ContentsTrack (separate Verisk platform)

ContentsTrack is a separate Verisk platform for contents-specialist workflows — pack-outs, cleaning codes, storage tracking, homeowner-facing portals, and large-scale contents claim management. It produces a finished contents schedule that can then be imported into an Xactimate estimate as a contents block.

The strength of ContentsTrack is depth of contents-specific functionality. If your operation handles pack-outs, manages contents in storage facilities, and runs cleaning codes against restoration jobs, no in-platform Xactimate module covers that ground. For restoration enterprises with dedicated contents divisions, ContentsTrack is built for the actual workflow.

The weakness is that ContentsTrack is heavy. It is enterprise software with enterprise procurement, deep training requirements, and a learning curve measured in weeks rather than days. Overkill for a public adjuster practice or a restoration shop where contents is one of several disciplines. See the restoration pack-out guide for where pack-out-grade contents tooling actually pays for itself.

Path 3: External tool with XLSX import

The third path — and the one most independent adjusters and mid-size restoration teams now use — is an external contents inventory tool that produces an Xactimate-compatible XLSX. The contents schedule is built outside Xactimate, exported in the column format Xactimate expects, and imported into the estimate as a contents block.

The strength of this path is workflow flexibility. External tools include Encircle (for restoration field documentation), Contents.team (contents-specialist with AI extraction), iCat (restoration enterprises), and Adjust Square (contents specialist with subscription pricing). Each is optimized for the contents workflow itself, with photo-driven capture, AI-assisted item extraction, sourced replacement-cost pricing, and depreciation that is consistent within a category by design. The output drops into Xactimate as a contents schedule.

The weakness is the integration seam. The XLSX import is one-way — schedule corrections made inside Xactimate do not flow back into the source tool. If the carrier revises a line during desk review, the change lives in the Xactimate estimate; the source tool keeps the original. For most workflows this is fine; for round-trip estimating, it is the friction point. For an honest look at where Encircle fits in this picture, see the Encircle alternative comparison.

The Xactimate contents XLSX format

If you are importing a contents schedule from an external tool, the XLSX needs to match Xactimate's contents line-item template. The exact column names vary slightly between Xactimate versions, but the structure is consistent across releases.

A working contents line carries, at minimum:

• Description — item name in plain language. Keep it under the character limit (varies by version; 60 characters is a safe ceiling). "Living room sofa, three-cushion, microfiber" reads better than "couch" and survives carrier review more often.
• Category code — maps to Xactimate's contents depreciation tables. Furniture, electronics, kitchen, apparel, and so on. Category drives depreciation, so getting it right matters more than it looks.
• Quantity and unit — usually EA (each) for contents, occasionally LF or LS for bulk items.
• Age — the item's age at the date of loss, in years. Drives depreciation.
• Condition — typically a 1–5 or excellent/good/fair/poor grade. Should match the photo.
• Replacement cost (RCV) — current retail price. Ideally with a source reference (URL or retailer notation) carried in a notes column.
• Depreciation percent or ACV — the depreciation applied, either as a percent or as the computed ACV. Most teams carry both.

When the import fails, it is almost always one of four things: a category code Xactimate does not recognize, a depreciation column formatted as text instead of a number, a description that exceeds the character limit, or a quantity field with non-numeric content. Run the file through a validation step before the import — most external tools do this automatically; if you are building the XLSX by hand, build a small checker that flags any of the four failures before you waste the import session.

How AI extraction changed the math

The single largest workflow change in the contents-into-Xactimate path in the last twelve months is the maturation of AI item extraction. Two years ago, AI in this space meant photo tagging — the tool would label an item in a photo and leave everything else to the operator. In 2026, the leading contents-specialist tools do something different: AI extracts items from photos, classifies them against a category taxonomy, suggests a condition grade based on visible damage, pulls a sourced replacement cost from a live retail database, and applies a category-consistent depreciation rate, all before the operator sees the first line.

The desk-time math has shifted accordingly. A 250-item residential contents claim that took eight to twelve hours of manual XactContents entry in 2023 now runs forty minutes of review-and-edit time inside a tool like Contents.team or Adjust Square, followed by a five-minute XLSX import into Xactimate. The operator is not typing the schedule — they are auditing it.

This shift matters for an Xactimate workflow even if your team is committed to the Verisk stack. The bottleneck on contents claims is not the destination tool — it is the per-line price sourcing and depreciation decision. A tool that does both of those upstream of Xactimate saves the same time whether the final estimate is in XactContents, ContentsTrack, or external.

For a thorough look at how AI extraction differs from AI identification — and why most "AI-powered" tools sit at the identification end — see the 2026 contents inventory software buyer's guide.

What gets a contents schedule kicked back

Carrier desk review is the trial every Xactimate contents schedule goes through. In 2026 the bar has risen — carriers are faster at flagging schedules with documentation gaps, and the schedules that passed five years ago now come back with line-level revision requests.

The four most common reasons a contents schedule gets kicked back:

Unsourced replacement costs. A line with $187.99 in the RCV column and nothing in the notes to back it up is a documentation request waiting to happen. Carriers want to see where the price came from — retailer URL, screenshot, or pricing database reference. Tools that source pricing at line creation make this automatic; tools that ask the operator to look up prices externally guarantee that some lines will lack sources by the time the schedule is exported.

Inconsistent depreciation within a category. Two armchairs of similar age and condition with one depreciated at 20% and the other at 50% will trigger a revision request, even if the rest of the schedule is clean. Category-consistent depreciation is one of the strongest predictors of how fast the schedule moves through carrier review.

Condition that does not match the photo. Condition graded "good" on a chair the photo shows is visibly burned, or "excellent" on an item with smoke staining, will be caught on desk review. Condition grades have to be defensible against the source image.

Vague descriptions. "Lamp" tells the carrier nothing. "Brushed nickel table lamp with white linen shade, approx. 18 inches tall" is the same line written in a way that survives review. Most desk-time gains come from getting the description and category right at line creation rather than fixing them in revision cycles.

For the carrier-and-TPA side of these same considerations — what a TPA actually does to compress cycle time on contents claims — see the TPA contents cycle-time guide.

Picking the right path for your role

The three Xactimate paths suit different teams, and picking by role rather than by habit produces the best result.

Public adjusters. Use an external contents-specialist tool with XLSX export into Xactimate. PAs need a defensible per-line schedule and most do not need the rest of the structural estimating workflow. The PA fee is the schedule. A contents-specialist tool produces a stronger schedule than XactContents because contents is the only thing the tool is built for.

Staff adjusters at carriers. XactContents is the default and works for the volume profile of most staff workloads. Where contents claims are particularly photo-heavy or volume-heavy, an external tool with AI extraction can compress per-claim desk time meaningfully — the import seam is worth the gain. See the desk review guide for the staff-side review criteria.

Restoration contractors doing mitigation. Encircle for the field walk and Xactimate (or its restoration variant Xactimate Cleaning) for the estimate. If your contents volume is high enough to justify a dedicated contents division, layer a contents-specialist on top of Encircle for the schedule-only piece.

Restoration enterprises with contents divisions. ContentsTrack is built for this. If you have pack-outs, storage facilities, cleaning codes, and a homeowner portal in scope, no other tool covers the same ground. The procurement cost is worth it at scale.

TPAs and carriers managing claims volume. XactContents for in-platform claims, ContentsTrack for outsourced contents specialist work, and an external tool when cycle-time compression is the goal. Most large operations end up with all three paths in production at the same time.

Policyholders. None of the three paths above. Policyholders documenting a loss should hand the photo set to a public adjuster, contractor, or carrier-side staff adjuster, who will run the contents schedule through one of the three paths. Policyholder-facing apps like Sortly or Scanlily are built for pre-loss inventory, not for producing an Xactimate contents schedule after a claim.

A two-week test plan

If you are evaluating a change to your Xactimate contents workflow — whether moving from manual XactContents entry to an external tool, or comparing two external tools — the fairest evaluation is two weeks of parallel running.

Pick three contents claims that have not yet been written. For each claim, run the schedule both ways: through your current workflow, and through the tool you are evaluating. Track three numbers per claim per tool: total desk time to produce a complete schedule ready for Xactimate import, number of lines that required manual price-sourcing or depreciation correction, and whether the carrier-facing export passed your desk-adjuster eye test on the first pass.

At the end of the two weeks, you will have nine data points per tool. Multiplied by your monthly claim volume, that is the actual decision input. The marketing pages are not.

Three claims is enough to expose the workflow differences without being a research project. The trap to avoid is evaluating a new tool on one easy claim — every tool wins on the easy ones. Pick at least one claim that is genuinely hard, with a large item count or significant damage variation across rooms.

Where Contents.team fits in this picture

The product behind this guide sits in the third path — an external contents-specialist tool that produces an Xactimate-compatible XLSX. AI extraction runs at the photo upload step, every line lands with a sourced replacement cost and a category-consistent depreciation suggestion, condition grades come from the visible damage in the photo, and the export drops into Xactimate as a contents block.

The pricing is per-item with a per-seat allowance — $0 base, 500 items included per cycle, $0.80 per item after that — which suits teams whose contents volume is variable. There is no annual commitment, the trial is direct (no waitlist, no demo gate, no card), and the XLSX export is the standard Xactimate contents column format.

The honest framing: this is the right tool for public adjusters, contents-focused restoration divisions, staff adjusters who want to compress per-claim desk time, and TPAs measuring cycle time on contents specifically. It is not a structural estimating tool, it does not replace Xactimate, and it does not cover pack-outs or restoration field documentation the way Encircle does. It does one thing — produce a defensible contents schedule from photos — and is built to be measured against that one thing.

Try it on one claim

The honest invitation: pick one residential contents claim you are about to write in Xactimate, run it through Contents.team alongside your normal workflow, and time both. If the AI-extracted schedule survives your desk-adjuster eye test and imports cleanly into Xactimate, the math will speak for itself.

Start a Contents.team account →

Or email sales@contents.team to run a working session on one of your real claims.

---

Last updated: May 19, 2026. Xactimate version-specific details vary across releases; verify column mapping against your current Xactimate edition before a production import.