AuctionLogistix editorial guide, published September 8, 2026. Copart and IAA official pickup guidance was reviewed on September 8, 2026. Their workflows are platform-specific examples, not universal auction rules. This is operational education, not auction policy, legal advice, carrier-compliance advice, or a promise of pickup, delivery, price, or availability.
Sources:
A sale branch is not automatically a dispatch instruction
An auction record may name a selling branch, while the operational pickup question is narrower: where is this particular vehicle available to be collected right now? Treat those as separate fields. The sale branch can remain useful for researching the purchase, but it should not silently become the carrier’s destination. Build the transport record around a confirmed physical pickup site: facility or storage name, street address, branch or yard identifier when supplied, and any current check-in or appointment instruction. If that information is not confirmed, say pending. A guessed pickup point can waste a driver visit, obscure the real release question, and spread through a lane file as if it were a verified fact.
Start with one unit, one location record
Keep the location record attached to a single vehicle rather than a broad purchase group. Use the VIN when available, together with the auction lot or stock number, year, make, model, buyer reference, and selling branch. Then add a distinct physical-pickup field. Record the source beside it: auction account screen, release confirmation, facility message, or a dated instruction from the responsible party. A line such as “Dallas branch” is too vague if the address, actual yard, or vehicle status has not been verified. A clear record lets a coordinator identify what is known without turning a nearby city, an auction brand, or a sale listing into a claim about the truck’s proper arrival point.
Preserve the facility workflow without copying it into your own rules
Copart’s official buyer guidance describes arranging transport promptly, and its third-party-transporter process begins with selected vehicles in the buyer’s Payments Due account before the transporter receives pickup-booking and check-in instructions. IAA’s official guidance likewise presents its pickup and delivery workflow through its buyer tools. Those sources are useful reminders that a platform can control the pickup process and that a transport request is not itself release confirmation. They do not create a universal procedure for every auction, branch, storage yard, or vehicle. Keep the current facility instruction with the unit file, follow the applicable platform’s process, and avoid telling a carrier that a particular gate, queue, or appointment method applies unless the facility has actually supplied it for that unit.
Separate location status from release status
A unit can have a confirmed address and still be unavailable for pickup. It can also be released while its precise physical location or check-in process still needs confirmation. Use separate statuses for each: pickup site confirmed or pending; release access confirmed or pending; facility instruction received or pending. That prevents a phrase such as “ready at auction” from carrying more meaning than the evidence supports. The file should also show the time of the last check and the person responsible for resolving any gap. For example, “physical pickup site pending; buyer operations to verify against current auction account” is actionable. “Auction location issue” is not. The goal is not a complicated tracker; it is a record that makes the next required call or account check obvious before dispatch is treated as executable.
Make changes visible, especially in a multi-unit lane
Location data can change during an auction move. A vehicle may be assigned to a different storage point, a release contact may provide revised instructions, or a transport partner may be replaced. Do not overwrite the old note and assume everyone who saw it understands the change. Add a dated update that identifies the unit, the prior location reference, the new source-backed information, and who needs the revision. In a multi-unit purchase, keep the summary subordinate to those unit records. The lane sheet can say “three pickup sites confirmed, one pending,” but it should link back to the vehicle-specific evidence. That stops an operationally incomplete unit from being swept forward because the rest of the group looks ready.
Give the driver-facing handoff only what is current and usable
Once the physical pickup site and release process are confirmed, the active handoff should include the exact vehicle reference, confirmed facility name and address, current facility-provided access or appointment instruction, reported keys and mobility facts, and a contact for a last-mile question. Do not attach stale locations, broad credentials, or unsupported loading directions simply because they appeared earlier in the purchase. Keep sensitive pickup credentials in their controlled release process rather than in a wide distribution note. A destination record deserves the same discipline: receiver, address, receiving hours, access notes, and any known exception. The handoff is a current operating snapshot, not an archive of every message that led to it.
Run a location check before transport planning and again before pickup
Before beginning a transport request, ask whether another person can identify the vehicle, see the source for its actual pickup point, distinguish that point from the sale branch, understand whether release is confirmed or pending, and reach a real delivery contact. Before pickup is treated as ready, compare the active record with the current auction instructions again. A planning conversation can begin while an item is pending, but the pending item should be named rather than concealed. This guide does not promise that a facility will release a vehicle, that a carrier will accept a load, or that a requested date will be met. It gives the transport team a cleaner factual file. When the pickup site, release details, condition notes, and receiver information are current, send the lane through the AuctionLogistix planning flow.