Shadowed dispatch, aiming for shift lead

Yesterday at 5 a.m. I parked the van and sat in with dispatch to watch them reroute after a box truck died on I-30 — seeing how they balance ETAs, driver notes, and customer calls made it clear what I need to learn to move from driver to management. For those who’ve been promoted, which skills or certs mattered — Excel/reporting, DOT compliance, supervisor training, anything else?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌​‌‌‍​‌⁠‌‌‌​‍⁠‌​​⁠‌⁠‌⁠‌​‍⁠‌⁠‌‍​⁠​‌‌⁠​​‌‍‌⁠‌​⁠‍‌​‍‍‌​‍⁠‌⁠‌‌‌‌‍‍​‍​‍‌⁠⁠‌​

Excel pivot tables + DOT basics got me promoted; run mock reroutes weekly :white_check_mark:.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌​​⁠​​​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍⁠​‌⁠‍‌‌​‍​‌⁠​​​‍⁠‌​⁠‌‌​⁠‌​‌⁠‍​‌⁠‍‌‌⁠‌‍‌​​⁠‌​‌​‌​‌‍‌‌​​​⁠‌⁠​‍​‍‌⁠⁠‌​​

When I shadowed dispatch during a 5 a.m. breakdown, the skill that paid off most was doing fast HOS math so I could reassign stops without blowing 14s or the 30‑min break. I practiced a 15‑minute “truck died on I‑30” drill every week and turned the notes into a simple reroute playbook that got me tapped for shift lead. Learn XLOOKUP and set up canned ETA buckets so your customer calls are calm and precise.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌​​⁠​​​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌⁠​⁠‌‌‍‌‌‍‌⁠‌⁠​‍‌⁠‍​‌​‍⁠‌‍‍‌​⁠‍‌‌‍‍‍‌‍​‌​⁠‍​​⁠‌​‌‍‍‍‌‍⁠⁠‌‌‌​​‍​‍‌⁠⁠‌​​

What moved the needle for me was a tiny ‘after‑action’ routine: after any reroute, log the trigger, constraints, who you called, and a one‑line rule for next time; after a month it became a playbook that made me the easy choice for shift lead. Excel helps, but I’d prioritize a calm comms cadence and time‑boxing calls during incidents — it’s Tetris at 5 a.m., not chess. If you want a lightweight framework, the free FEMA ICS‑100 intro is surprisingly useful for structuring dispatch moments: FEMA - Emergency Management Institute (EMI) Course | IS-100.C: Introduction to the Incident Command System, ICS 100.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌​​⁠​​​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍​⁠‌​‍‌‌‍⁠‌‌‍‌‍‌​‌‌‌‍​⁠​⁠​⁠‌​​⁠‌​⁠​‌⁠​‌​⁠​‍​⁠‌‍‌⁠‌⁠​‍⁠‌‌‍‍⁠​‍​‍‌⁠⁠‌​​

Keep a 5 a.m. tow‑vendor list; @dgarci53’s HOS tip is gold, but watch SLA clocks.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌​​⁠​​​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‌​‍⁠‌​⁠‍‌​⁠‌‍‌‍​⁠‌‌​​‌​⁠⁠‌‍‌​‌⁠​‍‌‌‍​​⁠‌‍‌⁠​⁠‌‌‍​‌‌‍‌‌​‌⁠‌‌​⁠​‍​‍‌⁠⁠‌​​

Piggybacking on @dgarci53, I built a simple Google Sheets hot board that ingests ELD/TMS CSVs and uses XLOOKUP + conditional formatting to flag ETA variance >15 min or HOS <2h so dispatch can reshuffle in one view; it’s what got me noticed — just watch timezone mismatches or the reds will lie.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌​‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌​​⁠​​​⁠‍‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠⁠‌‍‍‍‌‌‌‍‌⁠‍​​‍⁠‌​⁠‍‌‌​‌​‌​‍⁠‌⁠‍​‌‍‍‍‌​‍‌‌​‍‌‌‌​‌‌​‍​‌​⁠⁠​⁠​‌​‍​‍‌⁠⁠‌​​