AuctionLogistix editorial guide, published August 15, 2026. Manheim’s official logistics page and the official 2025 CFR annual edition on GovInfo were reviewed on August 15, 2026 for limited marketplace and carrier-side context; this is operational education, not auction policy, legal, or carrier-compliance advice.
Sources:
An award is the start of the file, not an instruction to move
Winning a vehicle establishes that a buyer has work to do; it does not by itself establish that the unit can be collected or that a transport provider has accepted the move. Treat the award as its own status: capture the VIN or stock number, auction branch, buyer reference, sale record, and the person who owns the next release step. Then open separate fields for release and transport assignment. This avoids the familiar failure mode where a team sees “purchased” on a spreadsheet and reads it as “ready for pickup.” The distinction matters most with a group purchase, where one unit may have complete release information while another has an unresolved document, key, location, or condition question. The purchase list should show the difference without forcing anyone to decode notes or old messages.
Make the release decision explicit
Release is a permission-and-location question. The practical record should say what pickup authority is known, who controls it, where the vehicle is physically held, and what source supplied those facts. It should also carry the usable unit reference, current yard or branch address, available lot or row detail, facility hours or appointment constraint when supplied, and a contact for a gate question. A blank field is better than an invented answer. Auction processes can differ by location, account, and vehicle status, so do not turn a general memory of a branch into an instruction for a specific unit. Mark the release state as ready, pending, or hold, and state the next action needed to move it forward. That turns release from a vague adjective into a handoff another person can actually check.
Give transport assignment a separate owner and evidence
A transport request is a planning event; an assignment is a later operational state that needs its own confirmation. Keep the carrier or coordinator contact, shipment reference when issued, current pickup constraint, destination contact, and the source of the latest update together. Do not copy an expected pickup date into the release field, and do not call a truck “assigned” merely because a form was submitted or a quote was discussed. Manheim’s logistics page illustrates why these states are separate in the market: its Central Dispatch description says users can list vehicles, name a price, choose a delivery date, and select a carrier. Those are workflow choices within that platform, not a universal auction rule or a promise for another shipment. The useful operating lesson is that release readiness and transport selection must both be confirmed for the same unit.
Treat dates as constraints, not proof of a pickup
Every date should answer a specific question. A sale date tells you when the award was made. A release deadline or storage date, if the auction provides one, is a facility constraint. A requested pickup date expresses a planning preference. A carrier-provided window is a coordination update. They should not be collapsed into a single column named “pickup date.” Add a source and timestamp beside each material date, especially after a change. If no confirmed window exists, say that plainly rather than filling the gap with an internal target. This keeps a receiver, a buyer, and a coordinator from making separate decisions based on an identical-looking date that meant different things. It also gives multi-unit planning a clean way to group compatible deadlines without implying that timing or availability is guaranteed.
State known condition facts without assigning carrier duties
Condition information belongs in the handoff because it affects the conversation about how a unit may be handled, not because the buyer is deciding equipment or securement. Record only what is known: keys present or unknown; reported to run, steer, brake, and roll or not; and visible loading-relevant constraints such as low clearance or loose components when documented. Keep the source—auction condition report, photo, or direct observation—beside the note. The official 2025 annual edition of 49 CFR § 392.9 on GovInfo is useful background: it addresses a driver’s duty not to operate a commercial motor vehicle unless cargo is properly distributed and adequately secured, along with cargo inspection and reexamination. That rule is carrier-side context, not a buyer checklist and not a promise about a particular truck. The buyer’s job here is simply to avoid concealing or guessing at a material condition fact.
Build the receiving decision before the vehicle leaves
The third decision can look complete at pickup and still fail at delivery. Before assignment is treated as workable, record the receiving business or person, full destination, reachable phone number, normal hours, entry instructions, and any known restriction on accepting the vehicle. If the destination is provisional, label it provisional; a familiar address from a prior shipment is not confirmation for this one. For a multi-vehicle purchase, give every unit its own receiver and status even when several vehicles share a market or ZIP code. This prevents one ready receiver from being treated as approval for the full group. A clean delivery handoff also makes an assignment more useful to a coordinator, because the pickup side and the receiving side can be evaluated together rather than as two separate emergencies.
Use a three-line control before you request movement
Before transport planning, read the unit through three short lines: award recorded; release usable; transport and receiving handoff executable. Each line should have a status, owner, source, and next action if it is not ready. If release is pending, the transport team can still understand the lane, but the record should not imply collection is authorized. If a carrier contact exists but the receiving gate is closed or unknown, assignment is not operationally complete. Preserve the final record with the auction confirmation, release evidence, condition documentation, and later pickup or delivery updates. That small discipline gives everyone the same current facts, limits handoff drift, and makes exceptions visible before they become an expensive yard-side surprise.