Daily Session Scripting
8 min read
Write a daily session script that transforms your bias into a structured behavior flow for the trading day.
8 min read
Write a daily session script that transforms your bias into a structured behavior flow for the trading day.
If your execution breaks down under pressure, it’s not your strategy — it’s your lack of a script.
A session script is not a journal. Journals look backward at trades you already took; scripts look forward at trades you have not yet earned the right to take. This lesson is about the forward document — the 10-minute pre-session contract that makes post-session journaling honest. For the post-session counterpart, see Journaling for Growth and Trader Journaling OS.
A session script is a short written game plan that aligns bias, execution, and emotional posture into a single performance-ready document. It answers, before the open:
This post shows you how to write one in 10 minutes or less. A script will not improve your edge or reduce price variance — it reduces behavioral variance, which is the only variance you fully control. A bad script followed mechanically is worse than no script at all, so revise it weekly against your journal.
| Dimension | Pre-Session Script | Post-Session Journal |
|---|---|---|
| When written | Before market open | After session close |
| Time horizon | Forward | Backward |
| Primary content | Bias, levels, setups, no-trade rules, daily-loss cap | Trades taken, intent vs execution gap, emotional state |
| Decision type | Pre-committed if/then branches | Diagnostic post-mortem |
| Failure mode | Becomes a stale ritual | Becomes a venting diary |
| Tomorrow's input | Yesterday's journal gap | Today's script intent |
Pre-session scripts work because of implementation intentions: "if X, then Y" written ahead of the moment is far more likely to execute than an in-flight decision (Gollwitzer, 1999). They convert open-ended discretion into pre-committed branches. They do not reduce price variance — they reduce behavioral variance, which is the only variance you control.
When in doubt, you default to the script.
Write this before the session or active trading window. Keep it short — max 5–7 bullets. Same place every day (one Notion page, one paper notebook, one pinned Discord self-DM). Yesterday's script gets archived next to today's journal entry so you can compare intent to execution.
What is price doing on the HTF?
Example:
Where are the high-probability areas for action?
What would make you say: “This is a greenlight trigger”?
Example:
When do you not trade?
“No trade” is a winning decision when it prevents loss.
What kind of trader are you choosing to be today?
Bias: BTC is in 4H uptrend; 15m building higher lows. Expecting upside continuation above 62.7k.
Key POIs:
Valid Setups:
Invalidation:
Behavior: Stay patient. One A+ trade only. Walk away if none.
A short pre-session document (5–7 bullets, under 10 minutes to write) that defines today's bias, key levels, valid setups, invalidations, and behavioral commitments before the market opens.
The script is forward-looking and written before the session; the journal is backward-looking and written after. Use both — they form a feedback loop.
One per active trading window. If you trade London and NY, two scripts; one daily-loss limit shared across both.
A strategy is what you believe; a script is what you commit to do under pressure. Without the script, your strategy is a hypothesis. With the script — and tomorrow's journal grading it — your strategy becomes a tested process.
Module 6 / Post 5 – Execution Visualization Recap & Routine Templates (PDF Pack Ready)
Ready to finish the module?