Dispatch Planning interview prep.

Train dispatchers / Rail Traffic Controllers (RTCs), chief dispatchers, NOC controllers, corridor planners, service designers, fluidity + capacity planners, crew + MoW planners at Class I + regional carriers (US + Canada).

What interviewers look for

  • Can the candidate issue movement authority safely under GCOR / NORAC / CROR + 49 CFR Part 220 with rules discipline?
  • Do they sequence meets + passes on single-track territory without inducing fluidity collapse?
  • Are they fluent in HOS clock management + recrew / dog-catch coordination at the network level?
  • Can they protect MoW + Form B windows while keeping the railroad moving?
  • Do they understand PTC + signalling enforcement interaction with dispatcher authority?
  • Are they grounded in fluidity metrics - velocity, terminal dwell, train length, on-time originations + PSR discipline?
  • Long-game fit - dispatcher / chief dispatcher / corridor planner / service designer / NOC manager / superintendent trajectory?

Behavioural questions to expect

  1. Walk me through your railroad career + dispatch + planning experience.

    What it tests: Story arc - training path, certifications, territory + traffic dispatched, rules + authority + crew-clock + MoW rhythm. Interviewers screen for deliberate dispatch path, not accidental transfer.

  2. Tell me about a dispatch desk or planning operation you've owned end-to-end.

    What it tests: Authority + rules + crew-clock + MoW + fluidity decision-making + outcome. Can the candidate walk territory framing -> action -> outcome -> stakeholder management cleanly.

  3. Why freight rail dispatch + planning vs running trains, yard, or trucking dispatch?

    What it tests: Authentic alignment - authority discipline, network view, rules + safety culture, multi-train sequencing craft vs single-cab running.

  4. Why this dispatch model - centralised NOC vs distributed division desks, single-track corridor vs heavy-CTC main?

    What it tests: Specificity. Generic 'I like dispatch' fails.

  5. Why this firm?

    What it tests: Real homework - territory + traffic + culture + safety + dispatch model - not name-drop.

  6. What's your read on our network + dispatch territory structure + fluidity performance?

    What it tests: Industry literacy - division + corridor structure, NOC location, method-of-operation mix, fluidity metrics (velocity, dwell, train length), recent operational events.

  7. Tell me what you understand about our safety + RRP / SSP posture from a dispatcher's seat.

    What it tests: Safety programme + just-culture + C3RS + dispatcher efficiency testing fluency on this firm's record.

  8. Walk me through a difficult meet/pass or sequencing decision on single-track territory.

    What it tests: Sequencing craft - single-track meet/pass discipline, siding capacity, train priority hierarchy, fluidity preservation, HOS clock awareness across multiple crews.

Technical concepts to master

Authority issuance + PTC interaction

Mandatory directive + readback discipline
49 CFR Part 220 mandatory directive - any movement authority must be transmitted, read back verbatim, and confirmed before execution.
CTC route + signal sequencing
Dispatcher sets routes + signals from CTC desk; trains move on signal indication; meet/pass via siding routing.
Track warrant issuance + voiding
TWC warrant - numbered, voice-issued, readback-verified, voided by time / mile / signal / report on arrival.
PTC dispatcher interaction (I-ETMS / ACSES)
PTC overlays + enforces authority - dispatcher authority shows on locomotive PTC screen; deviations trigger enforcement; exception territory + initialisation requires extra care.

HOS Act + crew-clock management at network level

HOS Act - 49 CFR Part 228
12-hour max on duty for train + engine service; 10-hour minimum off; limbo time (off train, awaiting transport) outside HOS but reportable; consecutive-starts limits.
Dog catch + recrew
Dog catch = vanning a fresh crew out to a train whose crew is about to expire HOS; recrew = relieving the expired crew at a terminal.
Tie down + secure
When no recrew option, train is secured on main or siding per rules and crew is taken off; train waits for next crew.
Crew-calling coordination
Crew calling pool = next-out crew at each terminal; calling rules union-negotiated; predictive crew calling pilots emerging.

MoW + Form B + foul time coordination

Form B / track bulletin
Authority granting MoW exclusive use of named track between named limits + named times; trains restricted at limits + must contact EC-1.
Foul time + working limits
Foul time = temporary blocking of track for short MoW task (inspection, minor repair); shorter + lighter than Form B.
EC-1 coordination
Employee in Charge of MoW limit holds primary safety responsibility within limit; dispatcher + EC-1 coordination is critical safety interface.
MoW window planning + curfews
Capital-programme work planned in pre-negotiated windows or curfews; corridor planners + service designers + chiefs coordinate weeks ahead.

Fluidity + PSR + service design

Network velocity
Average train miles per hour including dwell - the headline PSR fluidity metric reported weekly to AAR + investors.
Terminal dwell
Average hours from inbound arrival to outbound departure at named terminal - choke-point indicator for network fluidity.
Train length + tonnage strategy
PSR-era doctrine - longer + heavier trains reduce crew + fuel per ton, trade siding capacity + handling complexity.
Service design + line-of-road plan
Service designers build the network plan - origins, destinations, train symbols, blocks, schedules - dispatchers execute.

Practical drills

  • You are dispatching a single-track TWC subdivision with three sidings at MP 12 (8,000 ft), MP 34 (12,000 ft), MP 58 (6,500 ft). You have four trains in play: Train A (eastbound intermodal, 7,800 ft, on time at MP 5 with 6 hrs HOS remaining), Train B (westbound coal unit, 14,200 ft + DPU, at MP 75 with 7 hrs HOS), Train C (eastbound manifest, 10,500 ft, behind A at MP 0 with 9 hrs HOS), Train D (westbound local, 4,200 ft, at MP 50 with 4 hrs HOS finishing work). MoW has Form B requested for MP 28-32 from 14:00-16:00. Walk through your authority + meet/pass plan.
  • Train B (eastbound manifest) at MP 95 has 5 hrs HOS remaining. Destination terminal is at MP 175 (80 mi to go). Subdivision speed limits average 35 mph except a 10-mi segment at MP 130-140 restricted to 15 mph (slow order from broken-rail repair). One opposing train (Train E, westbound intermodal priority) will meet at MP 145 siding (planned 25-min delay). Crew base for dog catch is at MP 140 with taxi vendor (30-min response). Walk through the HOS + recrew math + decision.
  • Tuesday 03:00. A 32-car manifest derails at MP 142 on your primary east-west single-track corridor; no injuries, no hazmat release, but the main is blocked for an estimated 36-48 hrs while clean-up + track restoration proceed. You have 14 trains within the corridor at the time of derailment (8 staged at terminals, 4 mid-line, 2 originating in the next 6 hrs). An alternate corridor exists via a parallel subdivision 60 mi north, but it adds ~120 mi + requires foreign-line cooperation for 40 mi (run-through). Walk through your first 90 minutes + the 24-hour fluidity recovery plan.

Smart-question anchors

  • Dispatch territory structure - division, NOC location, corridor desks, method-of-operation mix
  • Fluidity + PSR posture - velocity, terminal dwell, train length, on-time originations
  • Safety + RRP / SSP - dispatcher-implicated events, just-culture, C3RS, efficiency testing
  • PTC + signalling - I-ETMS coverage, exception territory, foreign-line interoperability
  • MoW + capital programme - window strategy, Form B intensity, corridor capital season

Related roles

Sourced from

Ready to Generate Your Own Prep?

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.