Superintendent here. Ove the past two weeks I've taken ChatGTP and turned it into a JRMI with personality. We've build an entire railroad architecture that has improved my rulebook and generated switch lists for the upcoming operating session. Let me tell you it's a lot of work. Constant logic checking and paperwork. But I'm learning to use it as the tool that is and we have some really good ideas moving forward. I asked it to explain how we came up with the checklists so perhaps you could mess around with the idea. too.
**Building Switch Lists That Actually Work:
A Practical, Human-Centered Approach to Model Railroad Operations**
By ChatGPT
(Operations Clerk for the Clearwater Pacific Railway)
One of the most common questions I see in model railroad operations circles is:
“How do you build switch lists that feel realistic, stay manageable, and don’t collapse under their own complexity?”
The short answer is:
you design the paperwork to serve the railroad, not the other way around.
What follows is the logic and process behind the switch lists used on the Clearwater Pacific Railway (CSLP) — a small, modern shortline designed around deliberate traffic flow, limited track capacity, and human-scale operations.
This isn’t about automation, software, or random generators.
It’s about thinking like a railroad, then writing paperwork that supports that thinking.
1. Start With Geography, Not Cars
Before a single car is assigned to a switch list, the CSLP starts with a brutally simple question:
What is this place actually for?
On the CSLP:
-
Edmonds Landing is the only yard
-
Clearwater is industry only
-
Seeley Lake is interchange plus light local demand
That distinction matters more than any car roster.
If a town isn’t a yard, the paperwork must not treat it like one.
Our switch lists reflect that by:
-
Prohibiting classification in Clearwater
-
Forcing all organization work to happen at Edmonds Landing
-
Making industry jobs feel intentional, not opportunistic
This one decision eliminates most “why am I doing this?” moments during an operating session.
2. Separate Crew-Facing and Superintendent-Facing Information
A major breakthrough in our process came when we stopped giving crews everything.
The CSLP uses two layers of paperwork:
Crew-facing documents
-
Session Daily Instructions (SDI)
-
Job cards (Blue Star, Yard Sort, Lake Turn)
-
These contain:
-
What to move
-
Where to move it
-
What not to touch
Superintendent-facing documents
-
Pull lists
-
Car staging sheets
-
Traffic outlooks
Crews don’t need to know why a car exists — only what to do with it.
By hiding planning logic upstream, the switch lists become simpler, clearer, and faster to execute.
This mirrors real railroads more than many modelers realize.
3. Track Length Is Law
Every switch list on the CSLP is constrained by measured siding length, not theoretical capacity.
For example:
This does two things:
-
Forces better car selection
-
Creates operational tension without frustration
Switch lists are written to the track, not to the roster.
If a car doesn’t comfortably fit, it doesn’t appear — no exceptions.
This philosophy owes a lot to Lance Mindheim’s “less is more” approach, and it’s the single biggest reason our sessions stay relaxed and engaging.
4. Each Job Has a Narrow Purpose
Every CSLP switch list answers one question:
What problem is this job solving today?
Examples:
-
Morning Sort (YRD-201)
Solves the problem of overnight inbound chaos.
-
Blue Star Job (BLS-101)
Solves one customer’s needs, once, completely.
-
Lake Turn (LT-301)
Solves interchange obligations — nothing more.
Because each job has a narrow purpose:
If a move doesn’t serve the job’s purpose, it doesn’t belong on the list.
5. Rules Live in the SDI, Not the Job Card
Safety and local operating rules — bell use, whistle use, restricted areas — live in the Session Daily Instructions, not repeated endlessly on every switch list.
Job cards then reference the SDI rather than reprinting rules.
This keeps switch lists:
It also mirrors real railroad practice: rules are stable, jobs change daily.
6. Design for Humans, Not Perfection
Finally — and this matters — CSLP switch lists are written with the assumption that:
-
Crews will make judgment calls
-
Not every move needs to be scripted
-
The goal is flow, not optimization
You’ll see phrases like:
That’s intentional.
A good switch list doesn’t eliminate thinking — it channels it.
Closing Thought
Good switch lists aren’t clever.
They’re clear.
If your crews finish a session feeling like:
…then your paperwork is doing its job.
The CSLP didn’t arrive at this process overnight. It evolved through testing, pruning, and a willingness to throw things out when they stopped serving the railroad.
And that, more than any template or software, is the real trick.
— ChatGPT
Operations Clerk, Clearwater Pacific Railway
