What This Tool Is For
Central Station makes the NST capacity model experiential rather than didactic. Instead of explaining why a client runs out of fuel, you play through a day together and let the gauges do the explaining. The simulation creates a shared reference point — that moment when the planning fuel ran out — that you can return to in future sessions without rebuilding the context from scratch.
It works best as a mid-treatment tool, after basic psychoeducation is in place, when you need to move from understanding to design — from "I know why this is hard" to "here is what a different day could look like."
Setting Up the Session
Decide whether to run it jointly or debrief after. Some clinicians play through the game with the client, pausing at each task. Others let the client play independently and use the debrief as the clinical entry point. Both work. Joint play with pause is richer but takes a full session. Independent play followed by debrief can be done as homework before the session.
Choose the scenario before the session. Each scenario is built around a different capacity pattern. Use the Scenarios tab to match the right one to what you\'re working on. Starting with the Regulated Day first is useful for establishing a baseline — it shows what the gauges look like when conditions are right, which makes the other scenarios land harder by contrast.
Let the client set their own starting gauges. The setup screen asks for starting capacity. Letting the client set these to match how they actually feel today — rather than the scenario defaults — makes the simulation more personally relevant and surfaces real-time capacity data before you\'ve said anything.
What Clinician Mode Adds
When activated, clinician mode adds to each route card: the NST mechanism label (MOD stage and ISI disruption point), a clinical note on what the route does or doesn\'t address, and a cost comparison table showing the gauge impact of every available route side by side. A ⏸ Pause for Discussion button appears in the game header — pressing it freezes the game and surfaces the clinical discussion prompt for that task.
The Pause Button
Each task has a linked discussion prompt visible only in clinician mode. Pressing ⏸ Pause for Discussion freezes the game and brings up that prompt alongside the task name and domain. You don\'t need to pause on every task — use it selectively, on the tasks most relevant to what you\'re working on with this client.
The pause overlay also shows the cost comparison table for the current task — useful if you want to discuss what each route actually costs before the client chooses.
Letting the Client Choose Routes
The most clinically useful information comes from letting the client choose without prompting, then discussing afterward. Their instinctive choices are data. A client who consistently selects high-cost routes in the game often does the same in their actual day — and seeing the gauge consequence makes that pattern visible without it feeling like criticism.
If the client is stuck or disengaged, you can discuss the cost comparison table openly: "Look at what each of these costs. What do you notice?" This shifts the conversation from judgement to engineering.
What to Watch For
Where the gauges drop fastest. This often points to the domain that is carrying the highest real-world load — and the one most worth designing around first.
Route selection under depletion. Watch whether the client's choices shift as gauges drop. Clients who start selecting engineered routes but revert to unstructured ones under low-capacity conditions are showing you exactly what happens in their actual life when they\'re depleted.
Emotional responses to collapse. If the simulation ends in collapse or siding buildup, notice how the client responds — relief, shame, recognition, surprise. That response is clinical material.
Using the Route Map Strip
The rail map at the top of the game screen shows each task as a stop. Completed tasks are marked. This gives both you and the client a visual representation of where in the day you are, and how much is left — which has its own therapeutic relevance for clients with time perception difficulties.
Each route option in the game maps to one of four NST routing types. These appear as labels on route cards in clinician mode and as a pattern bar in the debrief.
Track 1 · Engineered
Mismatch addressed at source. Structure, accommodation, or pre-built protocol removes or reduces the demand before it lands. Lowest gauge cost. Requires advance design — it doesn\'t happen in the moment.
Track 1+2 · Dual Move
Environmental modification plus narrative reframe — the mismatch is reduced and named. Two things happen: the cost is lowered and the story is updated. Highest therapeutic yield per task.
Track 2 · Reactive
Coping in the moment without changing the source. The demand is managed but not modified — full cost is absorbed. Necessary and valid, but cannot be the only strategy across a full day.
Dysregulated · No Framework
No structure, no reframe. The demand lands unmanaged. Highest gauge cost. In real life: avoidance, reactive response, shutdown, or push-through. The pattern that builds chronic depletion.
What the Route Pattern Tells You
A client who selects T1 routes early but slides into DX routes under depletion is showing you that their coping architecture is capacity-dependent — it works when they have fuel, and collapses when they don\'t. The clinical target is building structure that runs at lower capacity, not better coping that requires more of it.
A client who selects T2 routes consistently across the whole day is managing well in the moment but not building anything — the full cost of every demand is absorbed each time. The clinical question is what prevents the shift to T1: narrative barriers ("I shouldn't need structure"), environmental constraints ("I can\'t control my schedule"), or design gaps ("we haven\'t built the protocol yet").
Each scenario isolates a different capacity variable. Match the scenario to what you\'re working on, or use multiple scenarios across sessions to compare patterns.
Regulated Day
Baseline. Use first to establish what a well-resourced day looks like. Useful for clients who don\'t believe they can have a good day, or who need to see the contrast before the harder scenarios land.
Unstructured Day
For clients who struggle on days off, can\'t rest, or report that weekends are worse than weekdays. Useful for the "I didn\'t do anything, so why am I exhausted" pattern. Works well with ADHD presentations and autistic clients who rely on external scaffolding.
Depleted Day
For clients in chronic overload, burnout, or who report that their "normal" is what the simulation calls depleted. Useful for building the case that starting reserves matter and that recovery time is not optional.
High-Masking Day
For clients who mask extensively in professional or social contexts. Useful for the post-event crash, imposter syndrome patterns, and explaining why social success doesn\'t feel like success. Also useful for couples or family work where one person's "fine" needs unpacking.
Cascade Day
For clients whose bad days "come out of nowhere" despite good starting conditions. Useful for making disruption density visible — distinguishing between "a hard day" and "a day where recovery windows closed before they opened."
New Environment
For clients in transition: new job, new city, new school, new relationship. Useful for normalising disproportionate post-transition exhaustion. Makes the familiarity-as-resource concept concrete and observable.
Caregiver Day
For parents of neurodivergent children, carers, or anyone whose environment is another person's state. Especially useful when the client is themselves neurodivergent and carrying both their own mismatch load and a caregiving load simultaneously. Works well in family sessions.
School Day
For teenage clients and their families. The CM discussion prompts for this scenario have two tracks — one for working directly with the young person, one for family sessions. Use the scenario to map what the school day actually costs before moving into strategies. The debrief often does more in one session than weeks of verbal explanation.
What the Debrief Shows
The debrief screen displays the client-facing narrative and the NST frame insights — but when clinician mode is active, it also generates a Clinical Formulation Summary below those sections. This includes a routing pattern bar (visual breakdown of T1/T2/DX choices across the session), an NST formulation paragraph, and a domain analysis identifying which gauge took the most load.
The Post-Session Routing Map
Below the formulation summary is the Post-Session Routing Map — a tool for mapping real-life choices rather than game choices. Routes chosen in play are pre-populated, but you can override any of them to reflect what the client actually does in their real day. Pressing Regenerate Pattern Summary produces a written formulation based on the adjusted choices.
This is the primary documentation tool. The generated summary can be copied into session notes, used as a handout, or shared with other members of a care team as a capacity formulation.
Using the Formulation With the Client
The most effective use of the debrief is to read the formulation aloud together. Hearing their own pattern described in structural rather than characterological terms — "your day shows a T1-dominant morning that collapses into DX routing by mid-afternoon" — is often the moment when the framework shifts from intellectual to felt.
If the client's reaction is "that\'s exactly it" or "I\'ve never heard it described that way," the formulation has landed. If the reaction is defensive or confused, the override tool lets you adjust the map until it reflects what they recognise as true.
Between Sessions
The simulation resets each play, so there is no persistent record across sessions in the tool itself. If you want to compare routing patterns across sessions — tracking whether a client's T1 use increases over time — you can copy the formulation summary from each debrief into session notes and compare manually. This also works as a progress indicator the client can see and interpret themselves.
Introducing the Tool
Keep the introduction short. The game explains itself better than you can. Something like: "We're going to play through a simulated day. You\'re the dispatcher — tasks arrive as trains, you choose a route for each one. The gauges track your capacity. Just make your choices without overthinking them." Don\'t walk through the framework in advance. The experience of watching the gauges move is the framework.
If the client asks what they\'re supposed to be learning, you can say: "We'll look at what happened afterward. For now just play it as if it were a real day." Holding the interpretation until the debrief keeps their choices from becoming performed rather than instinctive.
During Play — What to Say
The most clinically useful position during play is quiet observation. Avoid commenting on individual choices as they happen. If you do speak, stay cost-facing rather than evaluative:
"What drew you to that one?" · "What would the other option have taken?" · "What do you notice about the gauges right now?"
These questions surface reasoning without steering. Avoid anything that sounds like encouragement or correction — the gauge consequence is the feedback, not you.
When a Gauge Goes Critical
When EF or another gauge drops into the red zone, don\'t soften it. Let it land. If the client comments, reflect the number rather than the meaning: "That\'s planning fuel at 14." The meaning comes in the debrief. Jumping to reassurance here short-circuits the experience.
If a client looks surprised — "I didn\'t think it would drop that fast" — that\'s useful data. A brief "hold that thought for the debrief" is enough.
At Collapse
If the simulation ends in collapse, let the screen do the work. Wait before speaking. The collapse screen's language ("This is not a willpower failure") is doing the clinical reframe — don\'t compete with it by explaining. A short silence after collapse often produces more than anything you could say.
If the client tries to justify the collapse — "I should have chosen differently back there" — you can gently redirect: "That\'s exactly what we're going to look at. Let's see what the debrief shows." This holds the self-criticism for analysis rather than dismissing it.
Reading Emotional Reactions
Silence often means recognition — the simulation has hit something real. Sit with it rather than filling it. Rapid justification often means shame or defensiveness — the pattern feels exposing. Don\'t push; the debrief framing will do the reframe. Flat affect or disengagement may mean the scenario didn\'t match their actual experience — try a different day type, or move to the override tool in the debrief to map what their real day looks like.
Using the Pause Button Mid-Session
The ⏸ Pause for Discussion button is most useful on the two or three tasks that are most relevant to what you\'re working on — not every task. Before pressing it, let the client choose their route first. Pausing before the choice turns the simulation into a lesson; pausing after lets the choice be data. The discussion prompt that appears in the pause overlay is a starting point, not a script.
Transitioning to the Debrief
Move to the debrief simply: "Let's look at what happened." If clinician mode is active, a clinical formulation will be waiting. Rather than walking through it section by section, try reading the formulation paragraph aloud together before discussing it. Hearing their own pattern described in structural rather than characterological terms is often the moment the framework shifts from intellectual to felt.
If the client's reaction is recognition — "that\'s exactly it" — the formulation has landed and you can work from it directly. If the reaction is confusion or pushback, use the override tool to adjust the routing map until it reflects what they recognise as accurate. A formulation the client helped build carries more than one you handed them.
Minimum Playthrough
A full session run uses all available tasks per scenario. If time is limited — or if a client fatigues quickly — you can reach a clinically useful debrief with a shortened run. The rule of thumb is: play enough tasks to see at least one gauge move significantly and one routing pattern emerge. That is usually sufficient for a formulation.
Minimum viable task sequences by scenario:
Regulated Day
18 tasks · full run ~25 min
Minimum (6 tasks): Morning Routine · Inbox · Video Meeting · Lunch Break · Work-to-Home Transition · Wind Down. This arc covers the morning load, a social demand, the mid-day recovery decision, and the close of day — enough to see how the client handles both high-cost and low-cost tasks from a full starting state.
Depleted Day
18 tasks · full run ~25 min
Minimum (5 tasks): Morning Routine · Inbox · Mid-Task Interruption · Time Blindness · Decision Fatigue. The depleted scenario's point lands quickly — by Task 3 the gauges are already under pressure. The minimum run is enough to demonstrate that the same tasks that work on a regulated day stall here, without needing the full arc.
Cascade Day
18 tasks · full run ~25 min
Minimum (7 tasks): Morning Routine · Inbox · Video Meeting · Mid-Task Interruption · Administrative Tasks · Family Call · Decision Fatigue. The cascade scenario needs enough tasks for the event chain to land — the point is disruption density, not just low starting reserves, so you need at least two unplanned events to fire before the pattern is visible. Don\'t cut below 7.
Unstructured Day
10 tasks · full run ~12 min
Minimum (5 tasks): Morning Without Anchor · The First Decision · Planning Unstructured Time · The Drift Window · The Day Audit. These five tasks carry the core arc — the cost of generating structure without external scaffolding. The Drift Window and Day Audit are the most clinically pointed; don\'t skip them.
High-Masking Day
8 tasks · full run ~10 min
Run in full. The scenario is already short and the arc is tightly sequenced — the pre-event preparation, the performance event itself, and the post-masking crash are all load-bearing. Cutting tasks here removes the cause-and-effect chain the debrief depends on.
New Environment
8 tasks · full run ~10 min
Run in full. The automation gap builds gradually across all 8 tasks — cutting it short removes the cumulative cost that makes the end-of-day depletion land. If pressed for time, skip Zone 5 (Automation Gap) only — it is the most conceptual task and the others demonstrate the same point behaviourally.
Caregiver Day
10 tasks · full run ~13 min
Minimum (6 tasks): Morning Routine (Doubled) · Transition Resistance · Unexpected Sick Call · Co-Regulation Event · Evening Routine · Post-Bedtime Recovery. This subset covers the doubled load, the unpredictability variable, the co-regulation cost, and the no-recovery-window evening. The Solo Window (Task 4) can be skipped only if the clinical focus is on cost rather than the contrast between supported and unsupported time.
School Day
10 tasks · full run ~13 min
Minimum (6 tasks): Morning Routine · Arrival · First Period · Hallway Transition · Lunch · Homework Window. These tasks carry the fixed-environment argument and include both a sensory transition and the end-of-day margin. In family sessions, keep the Homework Window — it is usually the task that resonates most with parents, because it\'s where the school day's accumulated cost becomes visible at home.
If You Run Out of Time Mid-Play
You can end the game at any point using the standard end-of-session flow — the debrief and clinical formulation generate from whatever tasks were completed. A partial run still produces a routing pattern. Label it as such when reading the formulation aloud: "We only got through the morning, so this reflects the first half of the day — but notice what it already shows about how you route under early-day load." Partial data is still clinically usable; the Post-Session Routing Map lets you extend it manually by marking routes for tasks you discussed verbally but didn\'t play.