Contents pack-out inventories: photos, custody and the customer's sign-off.

A contents pack-out inventory is the record of what was taken from a fire-damaged home, in what condition, where it went and what happened to it. When the record is complete, pack-back is a walk down a list. When it is not, a missing lamp or a cleaned rug the family does not recognize becomes an argument nobody can settle from memory.

This article sets out a workable inventory line, the chain of custody behind it, how an AI assistant can draft the inventory from the crew's photos and check the custody trail for gaps, and where its part ends: whether an item can be saved, and whether anything is thrown away, are settled by people.

On its S700 page, consulted on 15 October 2026, the IICRC describes the 2025 first edition of its fire and smoke damage standard. When the page sets out what is assessed for fire residues and odors, contents sit next to the building and its systems, and its scope also takes in cleaning those contents and keeping a record of what happens on the project. The page does not set out an inventory format, and this article does not claim one: the record below is Aevrion's design.

Program work adds a layer. Crawford & Company's network, Contractor Connection, includes temporary housing, odor removal and board-up in the services it offers homeowners (as checked on 15 October 2026). Whatever a program wants in the contents file is taken from that program's own papers, filed by the owner.

Each entry below is a column in the inventory spreadsheet. Labeling and tagging conventions vary between companies and between pack-out software, so the record uses the company's own codes rather than any supposed industry-wide scheme.

• ROOM AND SPOT

  The room and the place in it, as the crew recorded them, so pack-back can put the item back where it was.

• DESCRIPTION

  What the item is, in plain words, with any make, model or distinguishing mark the crew noted.

• PHOTO

  The file name of the pack-out photo, taken before the item was moved, with its label visible where possible.

• LABEL AND BOX

  The company's label number for the item and the box it travels in.

• CONDITION AT PACK-OUT

  The crew's own words on what they saw, quoted rather than rewritten.

• HANDLING

  Clean, store, or waiting for a decision, exactly as a person set it.

• WHERE IT IS NOW

  The latest custody event: on the truck, at storage, at cleaning or back in the house.

• CONSENT

  For any item that may be disposed of, a reference to the property owner's documented consent. Blank means it stays.

In Grok Bot an owner can create a named assistant for a single purpose, running on a persistent cloud computer and producing files and drafts that someone reviews. A Contents Bot, one the owner creates following Aevrion's pattern, takes the crew's photos and notes and drafts the inventory as a spreadsheet with the columns above, the kind of reviewable result with defined columns that the documentation suggests asking for, and it reads program requirements from the owner's filed copy, because a Bot's memory cannot stand in for the record. The documentation names no connector for pack-out or contents software, so reading or updating that platform is a custom integration or supervised browser use where the vendor permits it, subject to testing.

The photos travel through the owner. Since every Bot lives in a single person's account, the crew sends its pictures to the owner, or uploads them to a cloud folder the owner controls, which the Bot reads through a custom integration or supervised browser use once that route has been tested. On desktop a message carries at most six attachments, so for a room's worth of pictures the folder is the realistic route, and any file one Bot saves in the shared workspace can be read by the others. If a second Bot, say the one writing the family's updates, must examine a picture, the Contents Bot hands the image to it one-to-one, because group handoffs, per the documentation, carry only text at present. Cursor's help pages say no switch turns those direct messages off; a Bot follows instructions about them.

The draft is not the inventory until a person has checked it. The crew lead compares it with the boxes before they leave the house or as they arrive at storage, corrects descriptions and confirms label numbers. Where a photo is unclear, the line says so instead of guessing.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Custody is a sequence of states, each held by someone. The model below is how the Contents Bot keeps the trail. Each event is entered or confirmed by the person who made the move; the Bot records it and never infers it.

1. 01

   In the house

   Owner

   The contents crew

   Advances when

   Photographed, labeled and packed, with the line verified by the crew lead

2. 02

   In transit

   Owner

   The crew member driving

   Advances when

   Unloaded and checked in at storage against the box labels

3. 03

   At storage

   Owner

   The storage lead

   Advances when

   Sent to cleaning, held for a decision, or kept until pack-back

4. 04

   Awaiting a decision

   Owner

   The restorer, with the property owner

   Advances when

   A salvage decision recorded by a person, with a name and a date

   Ends when

   Disposal only with the property owner's documented consent, referenced on the line

5. 05

   At cleaning

   Owner

   The cleaning technician

   Advances when

   Cleaned, photographed again and returned to storage

6. 06

   Back in the house

   Owner

   The contents crew and the family

   Advances when

   Placed, checked against the sheet and signed for at pack-back

   Ends when

   Closed when the family signs, or held open as an exception for the owner

An assistant can show that a decision is waiting; it cannot make one. Whether a sofa can be cleaned or a shelf of books is beyond saving is a judgment for the restorer, made with the property owner, and it goes on the line as that person's decision, with a name and a date. The Contents Bot never proposes a disposition, never marks an item for disposal and never changes a handling code because of how a photo looks.

Disposal needs more than a decision. Nothing leaves custody to be thrown away until the property owner's consent is documented and the line points to it. Separately, changing or deleting an inventory line is among the actions the documentation recommends keeping behind an explicit approval boundary (Allow once, Always allow or Deny); that card controls the Bot's edit, never the disposal itself. An approval never reverses work already done, so the boundary belongs before the edit, not after it.

The family may need a list of what could not be saved for their own claim. The Contents Bot can draft that list from the lines a person has marked, with photos and descriptions, for the owner to hand over. It assigns no values and no replacement prices. In Texas the line is statutory: under Insurance Code §4102.163 (text checked on 15 October 2026), a contractor with current or prospective work on a property may neither serve as its public adjuster nor advertise to adjust the claim. The statute is Texas law only; owners elsewhere confirm their own state's position with a qualified professional. The list is the family's to use, and the restorer does not negotiate it.

Early each Monday a scheduled routine can set the inventory beside the custody log and the storage records and list what does not match. If Monday morning passes with no list, the storage lead treats that as a fault and finds the cause before anything moves that week; the documentation describes no automatic retry. If an export it depends on is absent, the routine says the check could not run instead of leaning on last week's data.

What the reconciliation looks for, in Aevrion's version (rename the checks to match the company's codes):

• LINE WITHOUT A LABEL

  An inventory line with a photo but no label number.

• BOX WITHOUT A LINE

  A box checked in at storage that no inventory line points to.

• DECISION WAITING

  An item held for a salvage decision longer than the owner's own limit.

• DISPOSAL WITHOUT CONSENT

  Any line headed for disposal with an empty consent reference, raised to the owner first.

• LOST AT CLEANING

  An item sent to cleaning with no return event.

The reconciliation prepares a list and sends nothing. Any approval request from the Monday run would show Expired once roughly ten minutes (Cursor's help pages say thirty) passed unanswered, with nothing carried out, so the design never relies on one.

For pack-back the Contents Bot prepares a sheet from the verified inventory, ordered by the room each item returns to, with its pack-out photo and, where one exists, its after-cleaning photo. As items come off the truck and into place, the household reads down the list beside the crew lead, ticking each line or recording an exception: missing, damaged or not theirs. A person collects the family's signature, and every exception goes to the owner, who decides what happens next.

For the wider rules on designing a routine like this one, such as what to do when the data is missing and who reads the run history, see the guide to reliable home-service workflows. Setting up the inventory record, the reconciliation and the pack-out software link is work Aevrion Ops can plan with a restorer; that link is a custom integration, built if the vendor's terms and API allow it and tested before use. Contact us to talk through a contents back office.

1. Photograph, label and log every item leaving a fire-damaged home, and record each move as it happens.
2. Crew pictures reach the Contents Bot through the owner or a connected folder; an image another Bot must examine goes one-to-one, not through a group handoff.
3. The Bot drafts the inventory spreadsheet; a person verifies it against the boxes.
4. Salvage calls belong to people, and disposal waits for the property owner's documented consent.
5. A weekly reconciliation lists gaps in the custody trail and sends nothing.
6. At pack-back the family signs against the inventory, and every exception goes to the owner.