01Open the staging assignment
Create a staging ID and link facility, shipping date, wave or batch, route, stop, carrier service, sales order or transfer, shipment and dock appointment. Identify the planned package population and whether the assignment is single-order, multi-order, parcel sort, route consolidation or full-load staging. Record requester, release time, cutoff source and version. Separate planned vehicle from confirmed physical vehicle. Prevent two active assignments from claiming the same package or one assignment from spanning incompatible destinations without an explicit consolidation design. Define status such as planned, open, receiving packages, complete, held, door-released, loading, closed or canceled. A printed route sheet does not establish physical presence; the first verified package movement does. Preserve the original assignment when a route is changed and retain which packages moved to the replacement.
02Qualify packages before staging
Verify package ID, parent pallet or handling unit, order and destination, packed quantity, label, closure, weight or dimensions only when measured, document readiness and any temperature, security or special-handling status. Confirm the pick-and-pack process has completed its required checks; staging should not hide incomplete work. Reject an unreadable ID, leaking or damaged carton, open package, wrong destination, duplicate label, missing child carton or package under quality, payment, export or customer hold. Keep a controlled rework or hold position rather than mixing the exception into a ready lane. When a package is intentionally short of a planned shipment, update the expected population and approval instead of marking the lane complete by count alone. Use packaging hierarchy so one pallet scan does not falsely prove every expected carton is physically attached.
03Assign location, capacity and segregation
Use maintained staging locations with route, carrier, temperature, security, hazard, product-compatibility, package-size and capacity attributes approved by the facility. Allocate one current location per package or parent handling unit. Prevent different routes or stops from sharing an unlabeled floor area. Where several shipments share a lane, preserve boundaries and a count by destination. Mark overflow through an approved location, not free text. Keep aisles, exits, dock approaches, fire protection and equipment paths available under the site's qualified plan. OSHA identifies hazards in warehouses and loading docks; physical safety rules govern the layout, not a software capacity number. Review lane occupancy in both units and usable floor or position capacity. A lane can be numerically under capacity yet unusable when its exit is blocked or the next package cannot be safely handled. For parcel sort, distinguish induction, destination chute, containerization, manifest close and carrier handover. For multi-stop routes, divide the lane by stop sequence and protect reverse loading order without allowing a painted zone to replace a package scan. For mixed-SKU pallets, display parent identity and carton count at the accessible face, then preserve child membership digitally. Track gaylord, rolling cage, tote, pallet, oversize floor spot and loose carton as different handling-unit types. Define whether consolidation closes at a clock, package count, trailer plan or manifest event. Late-arriving parcels need a deliberate miss-sort, alternate-service or next-dispatch decision; slipping them behind a closed parent creates an invisible package.
04Control moves, custody and cutoff
Record every move from packing to staging, between lanes, to a hold or rework area and from staging to the door. Capture origin, destination, package or parent ID, operator or system, event time and reason. GS1 EPCIS provides event concepts for identified objects, location and business context; define which local event changes custody or shipping status. Restrict route changes and priority overrides to authorized roles. Track carrier cutoff, dock window, order promise and internal ready-by time separately. When the cutoff is at risk, decide whether to expedite, split, resequence, rebook or hold through the approved commercial and transport process. Do not record a package as loaded to make it disappear from a late lane. For third-party pickup, protect driver and access data and confirm handoff through site procedure. When conveyors, sorters or autonomous equipment feed staging, reconcile induction and discharge counters with accepted package events and divert unreadable labels to a named recirculation or exception point. Detect repeated recirculation, chute full, jam clearing, emergency stop and manual takeaway without guessing package fate. A telemetry pulse proves equipment activity, not carton identity. After recovery, scan the affected accumulation zone and rebuild sequence before reopening the destination. Maintain contingency labels and handheld assignments under change control so offline sorting does not create a second unlinked manifest.
05Verify door, vehicle and load release
Before moving to the dock, confirm actual door, vehicle, trailer or container identity, route, carrier, destination, load plan and readiness. Check that the trailer and dock have passed the site's applicable safety and entry controls. Compare expected parent and child packages with the staged population. Record door release authority and time. Stop on wrong vehicle, changed seal instruction, missing document, load-capacity issue, unsafe condition or package discrepancy. UNECE DESADV structures consignment, package hierarchy, item quantity, transport and reference detail; use the final supported load facts rather than the early staging plan. Loading sequence may follow stop order, weight distribution, temperature or handling requirements defined by qualified operators. This checklist does not prescribe safe loading design or vehicle capacity.
06Record loading and resolve exceptions
Verify package or handling-unit identity as it enters the actual conveyance and link loader, event time and door. Preserve split pallets, repacked cartons and newly created parent IDs through authorized hierarchy events. Classify wrong lane, wrong vehicle, missed scan, damaged package, missing carton, extra carton, label mismatch, route change, no-show, capacity failure and document or safety hold. Move affected packages to a visible exception location and update downstream shipment expectations. Do not delete a planned package to make loaded totals match. For manual contingency, retain a controlled list and reconcile it back to system events. If a package is removed after loading, record unload, location and revised load totals. Loading completion is not gate departure; keep those events distinct.
07Reconcile lanes and improve flow
Bridge packed quantity to staged, loaded, held, reworked, returned to stock, canceled and remaining quantity by package and shipment. Clear parent-child assignments, open tasks, temporary locations and canceled labels. Physically verify an apparently empty lane before release. Compare system-to-ground and ground-to-system: every staged package must appear in the system and every active staged record must be found or explained. Monitor staging dwell, on-time ready, wrong-lane move, residual package, load removal, rehandle, damage and missed cutoff by route and process. Sample completed shipments back to pack records and vehicle events. Use recurring causes to repair wave timing, label control, lane design, carrier schedule, package hierarchy or door communication. Do not improve dwell by sending incomplete loads or moving exceptions outside the tracked area. Run a sweep after manifest or load close for orphan cartons, abandoned totes, labels without physical packages, physical packages without active labels and parent units whose child count changed after close. Reconcile carrier container count and internal shipment count separately. Measure accumulation curve by dispatch cycle, peak lane saturation, time from first package to consolidation close, dwell after close, reopening frequency and packages diverted to later service. These reveal whether picking releases too early, packing finishes too late or route planning changes after physical sort. Review a recurring overflow as a flow-design problem, not permanent unmarked capacity.