But we’re scaling from 400 to 900 daily covers by May and I need an operations-first leader to standardize prep, tighten load‑out windows, and deploy 7shifts + Onfleet across two commissaries. If you’ve turned a chaotic production pipeline into a reliable 6 a.m. dock schedule before, message me with a quick win you delivered and the metrics that moved.
Rolled out 15‑minute dock slots tied to 7shifts roles and Onfleet tags; color‑coded totes per route and a ‘no dock, no load’ rule cut load‑out variance from 26 to 7 minutes, on‑time departures from 72% to 95%, and mispicks by 38% in 4 weeks. Small caveat: it only sticks if you pull procurement cutoff to 7 p.m. and staff one flex runner for late add‑ons — want the SOP template?
Building on @james_m87’s dock discipline, we added QR “route kits”: pickers scan each crate, Zapier pushes the scan to Onfleet and 7shifts marks the role’s ‘kit complete by 5:40 a.m.’ task; misloads dropped 11%→2% and load‑out dwell fell about 9 minutes across two commissaries. Small caveat: it only sticks if you freeze order edits at 9 p.m. and print labels with batch timestamps. It felt a bit like TSA for totes, but drivers stopped playing Tetris at the dock.
We moved to a departure-first prep plan — ‘work back from wheels-up’ — with T-minus timers per station fed by Onfleet route start times and 7shifts task checkoffs. That took on-time dock releases from 84% to 98% and cut departure spread by 10 minutes across two commissaries; just note it relies on shared SKUs/labels, so if yours differ, build a quick alias map first. Think mission control, minus the headsets.
We set a “dock freeze at 5:45” tied to Onfleet ETAs: if a route swings ±10 minutes, 7shifts auto-shifts station cutoffs and pings the runner; otherwise new crates can’t be staged, which cut late departures from 18% to 6% in three weeks. Only caution — hard freeze can sting on big event mornings, so we keep a manager override code on the board. Felt like air-traffic control, minus the cool headsets.
Quick win we used: a 7shifts task called ‘line-clear photo’ at each pack station that posts to Slack and tags the matching Onfleet job — like TSA: ‘no photo, no go’. That trimmed mispacks from 4.2% to 1.1% and cut schedule variance 35%; small caveat, add a cheap LED bar over the tables or 5 a.m. photos are useless.
@jessica_kane89 We paired your photo gate with tote-level QR tags by route/temp: packers scan to claim a dock slot in 7shifts and drivers must barcode-scan the same tote in Onfleet to roll — misloads dropped about 80% and dock dwell went 16→7 min… If Wi‑Fi’s flaky, cache scans on Onfleet mobile; want the label template?
@jessica_kane89 We wired a $25 stack light to an Onfleet webhook — ‘approaching’ flips yellow to stage, green to load — and it took dock dwell from 13→7 min; small caveat: add a 2–3 min buffer for GPS drift.
We set a ‘T-30 kit lock’ in 7shifts: at 5:30 a.m. the route kits freeze and a single lane owner signs off any subs, with the Onfleet task ID pasted into that step so drivers see the change note. Doing this across two commissaries took remakes down about 30% and made the 6 a.m. dock hit predictable; minor caveat, you’ve got to standardize SKU aliases first or the lock just frustrates people.
We added a ‘scan-to-seal’ step: the last tote per route gets a numbered seal; 7shifts won’t close the lane until the seal photo’s logged, and an Onfleet note flags ‘mismatch’ to hold pickup — misloads fell 1.8%→0.3% in two weeks. Only watch-out: count seals daily so they don’t get reused.