01Freeze the comparison population
Open the record with load ID and version, facility, dock, route, carrier, service, destination set, planned vehicle or equipment, cutoff, loading window and responsible shift. Capture the released staging snapshot by package, pallet, cage or other handling-unit ID, including parent-child relations and assigned lane. Separate released from merely picked, packed, label-created or planned. A package still on quality, credit, document or customer hold is not load-ready even if it appears in an order total. Record cancellations and re-routes as changes to the expected population rather than deleting them. If a wave or load is reopened, preserve the original snapshot and the exact delta. This creates a stable baseline for the loader, dispatcher and later investigation.
02Identify the physical loading event
Verify the actual vehicle, trailer or container at the dock using the identifiers authorized by the operation. Record arrival, dock assignment, load start, load finish and departure separately. Each load confirmation should connect the handling unit to equipment, location, time and operator or device. GS1 EPCIS models identified-object aggregation and loading events, but the business must define which local event is authoritative. Check offline scanner queues, duplicate scans, device clock drift and scans made at a nearby door. A scan at staging is not proof of vehicle entry. When a manual contingency is necessary, use sequential pages or controlled line entries, two-person verification where risk requires it and later line-by-line system reconciliation.
03Compare identities before totals
Create four lists: expected at staging, observed loaded, removed after release and found after loading. Compare package and handling-unit IDs, not only cartons, pallets or units. Then check destination, route, carrier, service, order, shipment, SKU or lot where required, quantity and unit. Recalculate parent totals when a pallet is broken or cartons are moved. Detect the common hidden swap: one expected carton remains in the lane while an equal-count carton for another route is loaded. Flag an item on two loads, a child under two parents, a parent loaded without required children, an unknown package and a loaded object whose status prohibits shipment. Preserve the supporting scan or witnessed record for each exception.
04Authorize additions, removals and substitutions
Give every change a reason, requester, decision owner, time and physical outcome. Typical removals include damage, incomplete documents, customer hold, missed cutoff, equipment capacity, temperature or compatibility concern, wrong route and package not found. A late addition needs confirmed identity, release state, route fit, space, document impact and loading evidence. Do not use a generic quantity adjustment to hide which object moved. Product or package substitution requires the applicable order and quality authority; loading staff should not make it silently. When a partial shipment results, update the remaining demand and customer or carrier communication through the approved process. Protect a removed package in a named lane or status so it cannot be loaded later without a new release.
05Control equipment and seal changes
If the planned vehicle is replaced, link old and new equipment IDs, reason, transfer time, transferred handling units, responsible people and any new route or capacity check. For a transload, record what left the original equipment and entered the replacement; do not assume the populations match. Where seals are part of the approved process, record seal application, inspection, removal or replacement with time, person and reason. A seal supports tamper evidence for the sealed boundary but does not prove the listed goods are inside. Keep broken or mismatched seal exceptions separate from package-count differences. Photographing or retaining seal evidence depends on policy, privacy, security and transport requirements; do not publish sensitive vehicle or route data.
06Align load, manifest and carrier records
Update the load record, shipment allocation, package hierarchy and manifest only through versioned actions. A loaded-but-unmanifested package, manifested-but-removed package or carrier-rejected package needs an explicit resolution before departure or an authorized contingency. Preserve the original carrier response and correlation ID when a manifest is amended. Keep document transmission, carrier acceptance, physical loading, custody and gate departure as different events. UNECE DESADV provides useful structure for despatch parties, consignments, packages, items and quantities, while GS1 events can connect logistics units and loading. Neither source makes an internal record universal transport or customs proof. Match each document version to the physical cohort it describes.
07Sweep residuals and close the discrepancy
After loading, sweep the assigned staging lane, exception area, dock plate, nearby doors and scanner offline queue. Bridge every released unit to loaded, removed, held, carried forward, returned, quarantined or unknown. Compare the final system load and applicable manifest to the physical population and carrier handover. Investigate unknowns before changing inventory. Record root cause separately from immediate correction: wrong lane, premature release, label duplication, scan bypass, late order change, equipment swap or weak cutoff control. Monitor loaded-not-expected, expected-not-loaded, wrong-route load, manual confirmations, post-close changes, residual aging and reconciliation time by dock, shift, route and reason. Close only after the bidirectional trace works from expected package to outcome and from departed package back to release authority.