A trading routine is a repeatable sequence for deciding whether to trade, executing the written plan, and reviewing what happened. It does not create an edge or make discipline automatic. It reduces the number of decisions you must improvise while prices are moving.
The useful structure has three phases: pre-market preparation, during-session control, and post-session review. The duration and exact checks should match your market, strategy, schedule, and evidence—not somebody else's ideal morning.
The Three Phases of a Trading Routine
| Phase | Decision it controls | Minimum record |
|---|---|---|
| Pre-market | Is this a valid session to trade, and what is allowed? | Readiness, events, setups, risk limits |
| During session | Does this opportunity match the frozen plan? | Setup, invalidation, size, exceptions |
| Post-session | Was the process followed, and what needs investigation? | Executed trades, missing data, deviations, one next action |
Your trading plan defines the strategy and risk rules. The routine defines when and how you consult those rules.
Why Most Traders Skip Their Routine
Routines usually fail for operational reasons: the checklist is too long, its trigger is unclear, it asks for information that is unavailable, or skipping it has no defined consequence. “Be more disciplined” does not repair any of those problems.
Make every step observable
Replace intentions such as “check the market” with an action and an output: “review the event calendar and record the next event relevant to my instrument.” A completed box is useful only when it represents a real decision.
Define the skip rule
If a required input is missing, specify the safe output in advance: delay the decision, use a documented fallback, reduce an approved risk limit, or do not trade. The fallback belongs in the plan; it should not be invented after a setup appears.
Shorten before adding
Start with the checks that can change a trading decision. Add a new step only when you can explain what failure it detects and what action follows.
Pre-Market Routine: Decide What Is Tradable
A pre-market routine should produce a session brief, not a prediction. The detailed pre-market guide expands the workflow; this is the pillar version.
- Confirm account and market context. Record the account, program stage if relevant, instrument universe, session, and platform status.
- Check scheduled constraints. Review official event sources and any venue or prop-program restrictions that apply to the exact account.
- Declare eligible setups. Write the setup versions, conditions, and invalidation logic that may be traded.
- Freeze risk limits. Record the per-trade and session limits in the units the account actually enforces.
- Run a readiness gate. Decide whether you are able to follow the plan before opening risk.
Useful output: “Account A; New York morning only; Setup v3; no new entry during the recorded event window; session loss limit X; stop after Y defined breach; readiness PASS.” Replace X and Y with your approved rules, not universal numbers from this article.
Sleep, Illness, and Readiness Belong in the Gate
This section absorbs the useful intent of the retired sleep-performance URL without claiming a universal performance effect. If you are too tired, ill, impaired, distracted, or emotionally activated to apply the written process, the routine needs a predefined response.
Use a short self-check tied to observable function: Can I read the rules, calculate size, wait for confirmation, and stop when required? A vague mood score should not automatically change position size. Define the allowed response in advance—normal session, restricted session under a written rule, simulation/review only, or no trading.
This is risk control, not medical diagnosis. Persistent sleep or health concerns belong with an appropriate professional. The burnout recovery guide covers a conservative return-to-process framework.
During-Session Routine: Execute the Frozen Plan
The live routine should be brief enough to use without hiding the decision. Before an order, confirm:
- the setup name and current version;
- the evidence that makes the setup eligible now;
- entry, invalidation, order type, size, and cash risk;
- account-level loss room and any program restrictions;
- whether this is a planned opportunity or an exception.
If the check is performed after entry, label it as a late record. Do not rewrite the plan field to make the trade look compliant. The execution protocol checklist gives a more detailed order-level version.
Use event-based pauses, not arbitrary timers
A pause can be triggered by a rule breach, defined loss limit, connectivity problem, unexpected event, or inability to state the setup. A fixed emotion timer may help one trader, but it is not a universal control. Record the trigger and the action so it can be audited later.
Post-Session Review: Reconcile Before Judging
- Reconcile executions. Confirm that fills, fees, account, symbol, direction, and timestamps are complete.
- Preserve planned fields. Keep the setup, planned invalidation, risk, and reason as they were known before the outcome.
- Mark deviations. Record which explicit rule applied and whether it was followed. Do not grade the process from P&L alone.
- Separate fact from explanation. “Entry occurred outside the allowed window” is observable. “I lost because I was impatient” is a hypothesis until supported.
- Choose one next action. Fix missing data, review a repeated deviation, or leave the process unchanged when the evidence is insufficient.
Reviewing trades within one hour of the session close can preserve fresh timestamps, chart context, and decision notes. Treat one hour as an operational default, not a universal performance threshold: if executions or broker statements arrive later, mark the review provisional and reconcile it when the authoritative records are available.
The full trade-review guide shows how to move from a reconciled record to a defensible decision.
Weekend Review Template: Test the Routine Itself
A weekly review should ask whether the routine was usable, not whether every trade won.
| Question | Evidence | Possible response |
|---|---|---|
| Which required steps were skipped? | Completion record plus reason | Shorten, clarify, or change the trigger |
| Did the routine change a decision? | Trade, delayed trade, or no-trade record | Keep the useful gate; remove decorative work |
| Were inputs missing or late? | Import/reconciliation exceptions | Repair the data path |
| Did a recurring deviation appear? | Predeclared rule labels | Investigate one mechanism on later trades |
Do not infer that routine completion caused better P&L from a small self-selected comparison. Completion may correlate with different markets, available time, sleep, or trade selection. Treat the first comparison as a hypothesis.
Minimum Viable Routine for Beginners
If the full framework is not sustainable, keep one decision in each phase:
- Before: identify the eligible setup and the session risk limit.
- During: record setup, invalidation, and size before the order.
- After: reconcile the trade and mark any rule deviation.
Run that version consistently long enough to observe where it fails. Expand only when a missing check repeatedly prevents a safe or reviewable decision.
Run the Routine on Reconciled Trade Evidence
Trader's Second Brain is our product. It can consolidate imported and manual trades, preserve account and strategy context, and break review evidence down by recorded fields. TSB recognizes 328 import profiles and has processed 600K+ imported trades. Those are ingestion facts, not proof that a routine improves returns.
Use the journal as the evidence layer: reconcile executions, retain missing-data counts, label the routine version, and compare predefined process outcomes. Planned setups, skipped opportunities, sleep/readiness, and reasons for no-trade must be recorded by the trader; fills alone cannot reconstruct them.
Implementation: Build One Phase at a Time
- Write the minimum pre-market output and its no-trade fallback.
- Add the smallest pre-entry check that preserves setup, invalidation, and risk.
- Add reconciliation and one explicit deviation label after the session.
- Review usability on a fixed cadence; change one routine element at a time.
- Version the checklist so results from different processes are not mixed silently.
The Bottom Line
A useful trading routine does not promise discipline or profit. It makes the session's inputs, permissions, execution checks, and review outputs explicit. Start with three observable decisions—before, during, and after—then add only the steps that improve safety or evidence quality.
