AuctionLogistix editorial guide, published September 2, 2026. Copart and IAA official pickup guidance was reviewed on September 2, 2026. Their platform-specific processes are examples, not universal auction rules. This is operational education, not auction policy, legal advice, or a promise of pickup, delivery, pricing, or availability.
Sources:
A pullout order is an operating sequence, not an arrival promise
A multi-unit auction purchase may look like one transport job from a distance, but the pickup side is still a set of individual vehicles with separate release, location, condition, and timing facts. A pullout order is simply the order in which those units should be considered or presented for pickup based on the information currently available. It is not a guarantee that a carrier will arrive in that order, that a facility will pull vehicles in that order, or that all units can be collected on one visit. Keeping that boundary clear protects the buyer from treating an internal spreadsheet sequence as a confirmed appointment. The useful goal is narrower: give the transport conversation a current, unit-level file that makes it easier to identify what is ready, what has an exception, and what should not be represented as ready yet.
Start with constraints already supplied by the facility
Do not create a pickup sequence from sale order alone. First collect each facility-provided constraint and preserve its source: actual pickup location, release state, stated appointment or check-in process, hours, lot or stock reference, title-handling information when relevant, and any storage-related date the facility supplies. A unit sold at the same auction can still have different facts from another vehicle in the group. Copart’s official guidance describes a process for a buyer to send a unit to a third-party transporter through Payments Due; the transporter receives a Gate PIN and instructions to book pickup and check in. IAA’s official guidance says its Tow App can provide stock details, title-handling instructions, outstanding storage-charge visibility, scheduling, check-in, and a defined pullout order. Those are examples of facility-specific workflows, not instructions to apply at another auction. Verify the current process for the actual branch and account before acting.
Build the sequence from unit-level readiness, not preference
Create one line per vehicle before rolling the group into a route or pickup proposal. Use a stable identifier such as VIN when available plus lot or stock number, year, make, model, sale branch, and confirmed physical location. Then show the current status of release authority, key and reported mobility information, actual pickup constraint, destination contact, and any open exception. A sequence can be as simple as: ready to discuss first, ready to discuss after a stated facility condition is met, and hold pending confirmation. Do not use labels such as “scheduled” or “first pickup” when they only reflect a buyer preference. If a vehicle has a missing key, unclear release reference, different storage location, or unknown receiver, leave that unit visibly separate. The team can still plan the lane around known facts without silently converting incomplete information into an instruction.
Keep auction workflow separate from transport coordination
Facility workflow and carrier coordination meet at pickup, but they are not the same decision. At Copart, the third-party-transporter flow described in its help center starts in the buyer’s Payments Due screen and includes an email address for the transporter, followed by the Gate PIN and pickup instructions. At IAA, the help-center article describes the Tow App as a tool for a transporter to see stock details, define load order, schedule pickup, check in, and receive a digital manifest after check-in. Those descriptions do not establish that any particular vehicle is released, that a truck has been assigned, or that a stated date will be met. Record facility details in the release-and-pickup portion of the file. Record a transport request, carrier contact, proposed timing, and later coordination update separately. That separation prevents a completed app step or a submitted request from being misread as a promise that the vehicle is already collectible.
Use a compact pullout sheet that another person can read
A useful sheet does not need routing software. For each unit, list: the identifier; auction or storage location; release status and source; location or gate reference when supplied; keys and reported run, steer, brake, and roll facts; facility-provided pickup constraint; destination contact and hours; proposed pullout position; exception owner; and timestamp of the last check. Add a short reason beside the proposed position, such as “release evidence retained,” “location confirmation pending,” or “receiver closes early.” Keep original release messages, permitted condition material, and facility confirmations attached or linked to the relevant vehicle record. The sequence sheet is a map back to evidence, not a replacement for it. If two people can read the sheet and reach different conclusions about what is ready, the labels or sources are not clear enough yet.
Do not turn the sequence into a promise to the receiver
A buyer may have a sensible preferred order and still lack a confirmed pickup window. Do not tell a receiving lot that Vehicle A will arrive before Vehicle B merely because that is the proposed pullout sequence. Facility queues, release status, vehicle condition, carrier capacity, and destination availability can change the working plan. Use precise language internally and with partners: requested, ready for planning, pending facility confirmation, or updated by the transport side. If a facility provides an appointment, check-in result, or other current instruction, record the source and time rather than overwriting the prior note without context. A clean distinction between request, facility step, and coordination update gives the receiver a better basis for planning without implying a guaranteed outcome.
Recheck the sequence at the handoff points
Review the file before transport planning and again before a pickup is treated as executable. At the first review, ask whether every unit can be identified and whether material unknowns are visible. At the second, verify the current release information, physical pickup point, known condition facts, and receiver availability against the active record. A changed yard, new key issue, or revised destination should trigger a new dated entry and a notice to the party using the prior information. Do not quietly edit a shared list and assume the revision reached everyone. For a group purchase, keep the lane summary subordinate to the unit records: it should show which vehicles are ready to discuss, which have open facility questions, and which are waiting on a delivery-side fact. When that file is usable, use the AuctionLogistix planning flow to share the complete multi-unit lane with the transport team.