AuctionLogistix editorial guide, published September 14, 2026. Copart and IAA official guidance on keys status and Pickup PIN controls was reviewed on September 14, 2026. Platform-specific references are examples, not universal auction rules. This is operational education, not auction policy, legal advice, carrier-compliance advice, or a promise of pickup, delivery, pricing, or availability.
Sources:
A key note is not one simple yes-or-no fact
“Keys included” can be useful, but it is not a complete transport instruction. It may reflect an auction listing field, information reported to the buyer, keys seen at a yard, or keys physically handed to a driver. Those are different points in time and different levels of certainty. Build the unit file around the exact known fact: keys reported present, keys reported absent, keys status not confirmed, or keys transferred at pickup. Add the source and the time it was checked. Do not turn an old listing field into a claim that a driver will receive a working key at a particular gate. The useful goal is a handoff that makes uncertainty visible before a truck arrives.
Keep pickup authorization separate from vehicle keys
A pickup credential authorizes a person to retrieve a vehicle; it is not evidence about the vehicle’s ignition key or its loading condition. IAA’s published Pickup PIN guidance says its PIN is unique to the vehicle’s stock number and is used to authorize pickup. That control belongs in a restricted release-access field, not in a general keys note. Copart’s official glossary separately defines its “Keys” listing term as whether Copart is in possession of the vehicle’s keys. The distinction matters operationally: a unit can have valid release access while its keys are absent, and a keys listing cannot establish who is allowed to remove the vehicle. Track both facts, but never merge them into a vague “ready for pickup” label.
Use four fields instead of one keys checkbox
A compact record can preserve the important difference. First, record the auction-reported status exactly as supplied: present, absent, or not shown. Second, state the evidence source: listing, current account view, condition report, release contact, or another dated record. Third, note the operational status: no special handling reported, mobility still to be confirmed, or loading exception reported. Fourth, record the transfer status at pickup only when that event is actually documented. For example: “Keys: Copart listing shows keys in possession; checked September 14; run/steer/brake/roll not confirmed; no pickup transfer record yet.” That sentence is more useful than “keys yes” because it identifies both fact and limit.
Do not infer movement from a keys listing
A vehicle can have keys and still be unable to start, steer, brake, or roll as needed for ordinary loading. It can also be described as having no keys while another current instruction changes the handling plan. The buyer’s role is not to diagnose the vehicle or prescribe equipment. It is to communicate known condition facts without embellishment. Keep keys status beside, rather than inside, the mobility note. Use straightforward fields such as “reported to run,” “reported not to run,” or “not confirmed,” and distinguish an auction-provided report from a direct observation. If a material fact is unknown, say unknown. A coordinator can then ask the correct follow-up instead of discovering a conflict during pickup.
Protect release credentials while keeping the handoff usable
Because IAA says anyone with a shared Pickup PIN is authorized to retrieve the related vehicle, a PIN should be handled as a controlled credential, not copied into a broad lane manifest or casual status thread. The driver-facing handoff can identify that release access has been confirmed and point to the approved delivery channel for the credential. It should still carry usable non-sensitive facts: vehicle identity, confirmed pickup site, applicable appointment or check-in instruction, reported keys status, reported mobility facts, and a contact for a last-mile question. This approach reduces exposure without withholding the details needed to evaluate the move. Follow the auction’s current process for the particular unit; these fields do not replace it.
Make multi-unit reports honest about exceptions
In a multi-vehicle purchase, do not summarize the group as “keys ready” because most units have an ordinary listing status. Count the exceptions: keys reported absent, keys not confirmed, access pending, mobility pending, or handling details unresolved. Keep the lane summary subordinate to unit records so each stock number or VIN can be checked against its own source. When a status changes, add a dated update instead of overwriting the earlier note. A clear update might say: “Stock 4821: keys status changed from not shown to reported present in current auction account; release credential remains controlled; mobility not confirmed.” That preserves the source trail and gives the transport conversation a current operating picture.
Check the record again before it becomes a dispatch handoff
Before a pickup is treated as executable, ask a short set of questions. Can the unit be identified without ambiguity? Is the actual pickup site confirmed? Is release access controlled through the current facility process? Does the keys field say what the source supports, rather than more? Are known mobility or loading exceptions visible? Can the destination receive the vehicle? If an answer is pending, label it and identify who owns the next update. A transport planning request can begin with open items, but open items should not disappear inside a generic ready status. This guide does not guarantee that keys will be available, that a vehicle can be loaded, or that pickup will occur on a requested date. It helps buyers send a cleaner, source-backed unit file when they are ready to plan the lane.