iCat resource
How Packout Works With Insurance Claims

A packout is not only a move. For a contents restoration contractor, how packout works with insurance claims is a file problem. The claim record starts when the crew photographs an item in place. It changes again at the truck, the warehouse, the exception desk, and pack-back. If those handoffs live in separate notes, the operations manager spends unpaid hours rebuilding the file before anyone can bill or answer an adjuster.
Call (888) 494-4228 to review your packout claim file
This guide is for the project manager and warehouse lead who already know how to pack a house. It shows which claim record each stage should create or update, and which records should stay out of the general inventory. The physical step sequence lives in the contents pack-out steps for contractors. Use this page to keep the claim file attached to that work.
How packout works with insurance claims
Packout works with an insurance claim when every item and box keeps one identity from the property to return. The contractor does not decide coverage. The contractor does decide whether the file can show what left the home, where it went, and what changed.
A useful claim file has four layers. Do not collapse them into one spreadsheet.
Identity. Photo, description, room, and item or box ID. Condition and status. What the team saw, so a person can decide the next handling step. Custody. Who had the item, and which location holds it now. Exception branch. Non-salvage, high-value, or owner items that need a separate record.
The ANSI/IICRC S700 standard covers fire and smoke damage restoration. Its scope includes contents restoration and documentation of project-related events. It is a fire standard, not a packout checklist for every loss. The working rule still travels. Write the event down when it happens. Do not rebuild the file from memory after the house is empty.
Which claim records start on site?
The claim record starts before the first box is taped. A field supervisor should be able to answer three questions from the file: what was there, what condition was visible, and which container it entered.
Photograph the item in place, then photograph it as its own record. In-place photos show context. Item photos support later identification. Tie both to a room and to the box or item ID the crew will scan at the warehouse. Photo method, folder structure, and metadata belong in the photo evidence guide for contents claims. This page only needs the link between the photo and the packout ID.
Keep the first record short. A contents inventory needs identity, photos, location, box or item ID, condition or status, and movement. It does not need replacement cost, age, depreciation, or actual cash value on every line. Those fields belong on a non-salvage or valuation branch, after a person separates that item.
iCat starts that record from a photo on an iPhone, including when the technician is offline. AI can draft a description from the image. A qualified person still reviews that draft before the line is treated as final. The software reports condition. It does not decide whether the item is salvageable, and it does not auto-categorize the contents.
Give the field supervisor a short gate before anyone tapes a box. Each item needs a photo, a room, and an ID that will still make sense at receiving. If any of those three are missing, the item stays in place until the record is fixed. That pause is cheaper than a warehouse search two days later.
What should move with the truck?
The claim file breaks most often between the front door and receiving. A box list that never left the house cannot prove custody. A warehouse count that starts from scratch cannot prove the load was complete.
Before the truck rolls, the project manager should confirm four facts for each container:
- The box or item ID matches the field inventory.
- The room of origin is still attached.
- The load is assigned to this job, not a shared truck note.
- Exceptions are marked and not buried in a general box.
If a third party hauls the load, name that handoff in the file. Custody is only as clear as the weakest transfer. "Left with the mover" is not a location.
This is also where unpaid labor hides. Teams retype box counts because the field list and the warehouse list were never the same record. A connected packout keeps the ID and adds the next location. It does not start a second inventory.
Name a single owner for the load record. On a small crew that is often the project manager. On a larger loss it may be the field supervisor who stays until the truck door closes. The owner confirms the box count against the field list, notes any item that stayed in the home, and records the handoff time. A count with no owner is a number nobody will defend later.
How should the warehouse update the claim file?
Receiving is a claim event, not a storage chore. The warehouse lead should scan or confirm each box against the field list and record the location. A missing box is an open exception. An extra box is an open exception. Neither should wait for pack-back.
Separate three statuses that crews often mash together:
Received. The container is in the building and tied to a location. In production. Cleaning or specialty work is underway. Billing codes can be assigned here. They are not the same as the inventory line. Stored.* The item has a stable location and is waiting for the next decision or for pack-back.
Cleaning choices happen at the facility, not during the packout at the house. Do not write a cleaning code on the field sheet and treat it as settled. If AI suggests a billing code, a billing lead still reviews it. The inventory record supports the estimate by showing quantities and services. It is not the estimate.
For the broader inventory structure, use how to streamline contents inventory for insurance claims. Keep this section limited to the warehouse handoff.
Set a same-day receiving rule. Boxes that arrive before noon are checked before the crew goes home. Boxes that arrive later are checked at the start of the next shift, not at the end of the week. The warehouse lead marks each ID received, records the aisle or bay, and flags mismatches on the same record. A mismatch list in a notebook does not update the claim file.

Which packout moments change the claim record?
Not every movement needs a new narrative. These moments do, because they change what an adjuster or a billing lead can rely on.
| Packout moment | Claim record to update | Leave out of the general inventory |
|---|---|---|
| Item photographed in place. | Identity, room, condition notes, photo link. | Replacement cost and depreciation. |
| Item placed in a box. | Box or item ID and room of origin. | A second description that does not match the photo. |
| Load leaves the property. | Custody handoff and job assignment. | A truck note with no box IDs. |
| Warehouse receiving. | Received status and storage location. | Assumed cleaning code from the field. |
| Non-salvage or owner hold. | Exception status, reason, and who must decide. | Automatic salvage decision. |
| Pack-back. | Returned status and any item not returned. | A closed job while exceptions are still open. |
Use the table as a gate in the weekly file review. If a moment happened and the record did not change, the job is not claim-ready yet.
Read the table from the job, not from memory. Open one active file and walk down the rows with the project manager. Ask what changed in the record at that moment, and who can see the change without a phone call. If the answer is a text message or a paper tag, the claim file is behind the work.
How do exceptions stay out of the main packout list?
Most contents stay on the operations track: identify, move, clean or store, and return. A smaller set needs a different branch. Mixing them is how claim files get bloated and how non-salvage items get lost in a box count.
Open an exception when any of these are true:
The item may be non-salvage, and a person still has to decide. The owner must authorize work, release, or disposal. The item is high value, sentimental, or needs a separate chain of custody. The box contents do not match the field list.
For a non-salvage candidate, record the visible condition and the reason it is pending. Do not write that software categorized it. After a qualified person separates it, that branch can carry Schedule of Loss detail, like-kind-and-quality notes, age, depreciation, and replacement cost or actual cash value where they apply. Until then, those fields do not belong on the packout line.
The non-salvage contents list covers that later processing. Link it when the exception is real. Do not turn every packout into a valuation project.
iCat keeps the branches apart. Photo inventory and packout tracking stay on the operations record. Non-salvage valuation is a separate workflow, and AI pricing still needs a qualified review before anyone treats it as final or uses it for a claim decision. Paid Fast LKQ is a different product path. Do not describe the two as the same thing.
What should pack-back confirm for the claim?
Pack-back closes the custody story. It should confirm three outcomes, not one.
Returned. The item or box went back, and the ID matches the field record. Still held. Storage, cleaning, or an owner decision is still open, with a current location. Not returned.* Non-salvage, disposal, or another authorized outcome, with the exception record attached.
A job is not complete because the truck made a second trip. It is complete when every ID from the field list has one of those outcomes. Open exceptions should stay visible to the project manager. Closing them in a side spreadsheet recreates the unpaid labor the packout was supposed to avoid.
Estimating can use the quantities and services on the operations record. Pack-out, storage, cleaning, and transportation each have their own estimating approach. Do not paste those prices into the inventory and call it the claim. For claim-file structure beyond the packout, see contents restoration insurance documentation.
How can a manager tell the file is working?
Review a live job, not a template. Pick one packout that reached the warehouse this week and check five points.
Every received box traces to a field ID and a room. No general inventory line carries a replacement value it does not need. Non-salvage and owner holds are separate, with a named decision owner. Cleaning or billing codes, if present, were set at the facility and reviewed. * Nothing is marked returned unless pack-back recorded it.
If any point fails, fix the handoff before the next crew rolls. The packout services workflow is the operating checklist for that fix. This claim view only tells you whether the file survived the move.
iCat is built for that check. One flat Enterprise AI plan covers unlimited jobs and unlimited users, with no per-seat fee, so a growing contents crew can share the same record without buying another login. The iPhone app keeps field capture moving when the house has no signal. The web portal lets the operations manager see receiving, storage, and open exceptions without calling the warehouse. Teams have used the platform for contents work since 2009. Current plan details are on iCat pricing.
Run the five-point check on two jobs a week until it is clean. One water loss and one fire or smoke loss is enough. The goal is not a longer report. The goal is a file that still matches the boxes when an adjuster, a billing lead, or the homeowner asks where something went.
Talk with iCat about your packout claim file
Frequently asked questions
Does a packout decide the insurance claim?
No. A packout documents what the contractor handled. Coverage, payment, and valuation decisions stay with the people authorized to make them. The contractor's job is a traceable record of identity, condition, custody, and exceptions.
Should every packed item include a replacement cost?
No. General packout inventory needs identity, photos, location, box or item ID, condition or status, and movement. Replacement cost, age, depreciation, and actual cash value belong on a non-salvage or valuation branch after that item is separated.
Can software mark an item non-salvage during packout?
No. iCat can report the condition it sees so the team can decide. A person makes the salvage decision. Until that decision is made, keep the item in a pending exception instead of writing a final disposition.
When should cleaning codes be added to the claim file?
At the facility, when cleaning is actually chosen. Do not lock cleaning codes during the on-site packout. If software suggests a billing code, a qualified billing lead reviews it before it is treated as final.
What proves the packout file is ready for review?
Every field ID has a current outcome: received, in production, stored, returned, or an open exception with an owner. Photos still match the IDs. Non-salvage lines are separate from the general inventory. Nothing is closed while a box is still unaccounted for.
Call (888) 494-4228 to see how iCat keeps packout records claim-ready