AI for moving companies: surveys, estimates and the federal paperwork clock.

An interstate job can go wrong a long way from the lifting: the inventory that missed the garage, the customer who did not understand what the estimate covered, and, for an interstate household-goods move, a stack of documents that each fall due at a set point under the federal movers' rules in Title 49, Part 375 (the regulation text as checked on 15 October 2026). Miss one and the problem surfaces on load day or at the customer's door, when it is hardest to fix.

The preparation is what supervised AI assistants can carry: turning the estimator's survey notes into an estimate packet with the price lines left for a person, keeping a per-move calendar of what is signed and what is not, and proposing which crew and truck go where. They do not survey a home, price a move, explain valuation, sign an estimate or a bill of lading, or take a deposit. In the design this page describes, the owner signs every estimate and every bill of lading, and no Bot sends a binding document the owner has not approved.

The rules cover a household-goods carrier working across state lines for an individual shipper: in the regulation's terms, a person who owns what is being moved and pays for the move personally (375.101, 375.103). ATA's regulatory note of October 2022 on the FMCSA final rule, which FMCSA began enforcing on 31 October 2022, treats them as rules for C.O.D. shipments that do not reach government, military or national-account moves. They produce five documents in a fixed order, as checked on 15 October 2026. The interstate paperwork timeline sets out each document's rule, section by section; the table below shows only the assistant's part.

None of this is legal advice. It summarizes United States federal regulation for interstate moves; whether a rule fits a given shipment is the owner's call, taken with legal help when the stakes warrant it.

The survey is where a moving estimate is won or lost, and it belongs to a person who knows how a three-bedroom house actually loads. Whether it happens in the living room or over video, the estimator walks the rooms, notes the heavy and fragile pieces, and asks about stairs, long carries, elevators and whether the truck can reach the door. The rule allows the survey to be skipped only if the customer waives it in writing, signed before loading, and a survey over live or recorded video counts as one (375.401(a), 375.103).

Grok Bot, as its documentation describes it, lets a business keep named Bots, each with its own job, on a persistent cloud computer, producing work a person reviews. An estimate-prep Bot that the owner creates under Aevrion's pattern can take the estimator's notes, cube sheet and photos and lay out a draft packet: the inventory by room, the services requested, every accessorial question with the customer's answer or a marked gap, the form of payment the company accepts at delivery, and the label the estimator chose. The price lines stay empty. Prices come from the carrier's tariff, and the estimator or owner fills them in.

The packet also carries the wording each label needs. A binding estimate must say on its face that it binds both sides and covers only the services it lists (375.403(a)(4)); a non-binding one must say the customer will not be required to pay more than one hundred ten percent of the estimate at delivery (375.405(b)(5)). Reading a survey tool or a moving CRM takes a custom integration or supervised browser use where the vendor permits it, subject to testing, and either route stops where that vendor's API or terms stop.

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.

The calendar is the piece of back office this trade cannot do without. Each interstate move gets a row, and every date on it is counted back from the scheduled loading day: survey done or waiver signed, estimate signed with the dated copy given, booklets sent, disclosures sent, the customer's signed, dated bill of lading no later than three days before the load, and the end of the customer's three-day rescission window. What happens when a move is booked too late for the three-day deadline is covered in the paperwork timeline.

A paperwork Bot can keep the calendar on a weekday-morning routine. A routine runs on whatever timetable the owner picks, provided runs sit at least five minutes apart. Of the four Bots in this design, the paperwork Bot alone owns the calendar, because the others work from its dates: the estimate packet waits on the survey line, and the dispatch board marks any load whose bill of lading is unsigned. Two Bots editing one calendar would leave the owner unsure which date is real. The calendar itself lives in the company's own system; the documentation is clear that a Bot's memory is no substitute for the record, and a loading date remembered from last week is wrong the moment a customer reschedules.

The calendar is an Aevrion pattern built on documented routines, not a product feature, and its warning colors follow the owner's rules, not the regulation's wording.

Peak season turns scheduling into a puzzle with too few pieces: crews, trucks, pack days, load days and the moves that cannot shift because a closing date or a lease end is fixed. A dispatch-prep Bot can lay the week out from the booked jobs and propose who goes where, marking the conflicts it finds: two loads needing the large truck on the same morning, a pack day with nobody assigned, an interstate load whose bill of lading is still unsigned.

Committing a crew is the owner's decision, and so is telling a customer that their date has moved. Who is available, who may drive which truck and anything touching pay sit outside the assistant's remit. The proposal is a draft board; the owner's edited version is the one the crews see. Storage adds its own rows to the same board, such as a container to be loaded out of the warehouse before the delivery crew arrives, and the dispatch Bot treats those as dependencies to show the owner, not decisions to make.

The week before a move produces the questions that fill an office's afternoons: what time the crew arrives, what to pack, what happens to the plants, where the truck will park. A customer-support Bot can draft confirmations and answers from the job file and the owner's own FAQ. The documentation describes how such a draft appears: an editable email showing recipients and body, which goes only when the owner chooses Send. There is no telephony in the documented product, so the assistant takes no calls and sends no texts; those stay with the office.

The line that matters most is between a reassuring message and a binding one. Anything that changes the estimate, adds a service, moves a date on the bill of lading or explains the customer's valuation choice is written by the owner. The documentation recommends explicit request boundaries for sending messages, for financial transfers and for accepting legal terms, and in a moving company the estimate and the bill of lading are the legal terms. That boundary is given to every Bot as a lasting rule to remember, which is guidance to the Bot rather than a technical lock, so the owner still reads each draft before sending it. Approvals are configurable, not automatic for every action, and approving a step never reverses work already done.

On rosters the documentation's advice is to begin small: one Bot owning an outcome end to end, and another only once a specialist role has settled. For a mover, a sensible order is the paperwork calendar first, because every interstate deadline hangs on it; then estimate preparation; then dispatch preparation; and customer-support drafts last. Four is the ceiling in this design, not the starting point.

The morning routine ends in drafts and a list, since an approval it raises with nobody watching lapses at roughly the ten-minute mark (Cursor's help pages say thirty minutes). The four Bots also share one cloud computer, so signed estimates, customers' addresses and the moving CRM login there are visible to all of them; separate Bots are not a security boundary, and the documentation's answer where real separation is needed, as for the bank and card-processing logins, is a separate user account. Logins, two-factor codes and payment steps go to a person through a takeover of the computer. Cursor's help pages add a Vault, where saved logins and cards let a Bot sign in and check out without seeing them, and no setting asks for approval each time a saved card is used, so this design saves no card there.

Everything in the calendar above is United States federal regulation for interstate household-goods moves. Moves that stay inside one state answer to that state, and this page does not cover intrastate rules. Removal firms in the United Kingdom and removalists in Australia work under their own consumer law and trade practice; the FMCSA sequence does not carry across, and a business there should not build its calendar on it.

The pattern does carry across: survey notes, an estimate packet, a document calendar and drafts. It can be set against whatever rules a business actually works under, once the owner has written those rules down from a primary source.

Each item is tied to the tariff, the estimate or the bill of lading, which is why it is a person's act.

• THE SURVEY

  Walking the rooms or running the video survey, and judging what will load. The assistant works from the estimator's notes.

• ESTIMATE TYPE AND PRICE

  Binding or non-binding, every price line and every accessorial charge, set by a person from the tariff.

• SIGNATURES

  The owner signs every estimate and every bill of lading. A Bot signs nothing and sends nothing binding.

• WAIVERS

  Whether to accept a survey waiver, and making sure it is in writing and signed before loading.

• VALUATION

  Explaining the customer's liability choice. The assistant drafts nothing about it.

• CHANGES BEFORE LOADING

  Reaffirming, re-estimating or converting an estimate when the customer adds goods or services.

• CREW COMMITMENTS

  Who goes where, and telling a customer that a date has moved.

• MONEY

  Deposits, refunds and collection at delivery. Payment steps are a human takeover.

• CLAIMS

  Settling a damage claim. The assistant can structure the intake; a person decides.

The most useful first step is to take the next three interstate jobs and write out, for each, the date every document went to the customer and the date it came back signed. That shows whether the gap is the survey, the estimate, the booklets or the bill of lading, and it gives the calendar its first real rows.

What Aevrion Ops would scope with a moving company is turning the applicable sections into the calendar's rules, deciding which Bots to create and the points at which each hands back to the owner, and connecting the survey tool and moving CRM the company already runs, wherever the vendor's API or terms permit and only once tested. To start, send a note through the contact page, ideally with one recent interstate job file, customer details removed, to work from.

1. US interstate household-goods moves for individual shippers run on a federal sequence: survey or written waiver, labeled and signed estimate, booklets, disclosures, then a bill of lading signed at least three days before loading.
2. An estimate-prep Bot can lay out the inventory, services and accessorial questions from the estimator's notes; the price lines stay blank for a person.
3. A paperwork calendar counted back from each loading date is the core assistant job, kept in the company's own system rather than in a Bot's memory.
4. Crew allocation is a draft board; committing crews and telling customers about date changes stay with the owner.
5. The owner signs every estimate and bill of lading; overnight and early-morning routines end in drafts, because unattended approvals expire after about ten minutes (Cursor's help pages say thirty).
6. Intrastate moves and UK or Australian removals follow other rules, which this page does not describe.