Happened again on the 0200 out of ORD: ops shifted two 1,100 kg pallets of lithium batteries after we’d signed the load sheet, and we burned 35 minutes redoing W&B, segregation, and straps. I shut it down for safety, but how are you enforcing a hard lock without killing turn times — do you rely on a cutoff policy, dispatcher sign-off, or something else that sticks?
We hard-freeze at T-25 with a “LOAD LOCK” ACARS, and any post-lock move — esp. lithium — needs @dispatch sign-off plus new NOTOC/W&B, and it auto-codes a cargo delay, not flight. That accountability cut the 0200-ORD shuffles to near zero without killing the turn; if they break it, we shut it down, . Do you have a way to auto-tag that 35‑min hit to ops?
We added tamper seals on DG pallets tied to the load plan barcode; any after-lock reseal scan throws a ‘POST-LOCK MOVE’ alert to duty, forces new NOTOC/W&B, and auto-codes the delay to the station instead of flight ops. It cut the debates because the system makes the call — like moving the couch after you’ve measured the door. Do you have door scanners to enforce a seal/ULD rescan, @d_hughes89?
Quick example: we use a simple ‘green card’ handoff at the cockpit — ramp lead brings the finalized load card at T‑30; any change after that means the lead has to come back up, swap it for a yellow card, and the station chief @ops signs at the door, which pretty much stops casual swaps. If they truly have to move lithium, we pre-brief a 10‑minute buffer in the station playbook so the delay is owned and predictable. Would ORD buy into a door‑signature step?
But we run a simple “no-call, no-move”: once the flight deck signs, any swap requires the ramp lead to call the cockpit or duty manager; if they skip it, it dings the handler’s scorecard… Do you have leverage with your handler to tie a KPI to late swaps? Funny how a cockpit call makes pallets grow roots.
We require any after-lock change to be raised as a short ‘change ticket’ in the ramp app with a two-minute window: ramp opens it, the EFB prompts the cockpit to accept, and if it expires the duty manager is paged and the move pauses. It added about 90 seconds on average but cut surprise swaps by half — @k_wright100 your comms point fits, and the timer works like a shot clock that keeps everyone honest.
We switched to a numbered cargo-door seal at T-35 — scan the seal into the flight in the ramp app and use a simple “seal broken = sheet broken” rule; if they pop the door again, ACARS auto pushes a revise prompt and blocks push until we accept. It added maybe two minutes once a week, but it stopped quiet swaps and kept DG segregation honest. @LoadPlanNina do you tie the seal to ULD barcodes or just the hold?