Trader's Second Brain Trader's Second Brain

Trading Plan Template: The Only Format That Works (2026)

A usable trading plan turns market scope, setup conditions, risk, orders, exits, stop conditions, and review rules into decisions that can be checked before and after every trade. This guide provides the fill-in template, an illustrative example, and a version-control workflow without promising a return.

Quick Answer

Write the exact account and market, one versioned setup, observable entry and disqualification rules, a loss budget before quantity, venue-specific order and exit behavior, a session stop, required journal evidence, and a dated review gate. Do not copy universal risk percentages or sample counts, and do not treat a planned stop as a guaranteed fill.

Your trades · one review system
Import → reconcile → review

Find the leak before the next trade.

Import or log trades. Find setup, session, and behavior leaks.

Find trade leaks →
Trader's Second Brain preview
Reading map

Three checkpoints in this guide

Follow the full walkthrough in order, or jump directly to one of its main sections.

  1. 01Opening checkpointWhat a Written Trading Plan Must Do
  2. 02Middle checkpointPersonal, Prop-Firm, and Crypto-Exchange Variants
  3. 03Closing checkpointMethodology and Primary Sources

A trading plan is useful only when another person could read it and reach the same yes/no decision you would. It should identify the market and account, define an eligible setup, cap risk before entry, specify order and exit behavior, say when trading stops, and state how the rules will be reviewed. A slogan such as “trade with discipline” is not a rule.

This page provides a complete copy-and-fill trading plan template, a worked example, and a change-control process. No template can make a strategy profitable or make leveraged trading safe. In the headline, “works” means the format is executable, auditable, and versioned—not that it guarantees a return.

Without a written plan, you cannot grade your own execution consistently. A winning trade may have broken the rules and a planned loss may have followed them. The written version supplies the benchmark that lets a later review separate process adherence from outcome.

1. What a Written Trading Plan Must Do

The direct answer: write the decisions that must exist before an order, not a story about the trade afterward. The CFTC advises traders to use risk capital and develop a plan suited to their own situation and risk tolerance. CME’s trade-plan curriculum similarly separates objectives, methodology, risk management, entry and exit strategy, and the trade log. Those sources support the structure; they do not validate any particular setup or percentage.

Document Question it answers When it changes Failure signal
Trading plan What am I allowed to trade, how is risk capped, and when must I stop? Only through a dated review and new version A live decision requires improvising a missing rule
Setup checklist Is this exact opportunity eligible now? When the parent setup is revised Two reviewers can grade the same chart differently
Trade journal What was planned, executed, and observed? Every trade and review The log cannot distinguish rule-following from outcome
Review note Does evidence justify keeping, testing, or retiring a rule? At the pre-committed review gate A losing day triggers an unplanned rewrite

A plan should be as short as it can be without hiding a decision. A one-page operating sheet plus a longer setup annex is often easier to use than either an arbitrary page limit or one giant document. Readability is a workflow test, not an industry standard.

2. The Complete Trading Plan Template

Copy the fields below into a document, spreadsheet, or journal. Replace every bracketed prompt. If a field does not apply, write why; do not silently delete it. Values shown later in the worked example are illustrations, not recommended limits.

My Trading Plan — Version [number]
Effective [date]
Account and environment
[broker/exchange/prop program, exact account, live or simulated]
Market and instruments
[exact symbols/contracts/pairs; exclusions]
Trading window
[time zone, days, start/end, venue maintenance or session boundary]
Costs and constraints
[commission, spread, slippage model, funding/borrow/data fees, margin]
Authoritative rules
[links to current broker, exchange, or exact program terms; verified date]
Setup name and version
[one stable label used in backtest, plan, and journal]
Context
[market regime, timeframe, session, liquidity, event conditions]
Required conditions
[observable conditions joined by AND/OR]
Trigger
[precise event that permits the order]
Disqualifiers
[late entry, spread, event, correlation, stale signal, rule conflict]
Evidence to save
[pre-entry chart, checklist state, planned entry/invalidation/target]
Risk base
[cash equity, usable buffer, or stricter account-specific base]
Risk unit
[1R equals the chosen maximum planned loss before costs]
Size formula
[risk budget divided by loss per unit, rounded down to a valid quantity]
Open-risk cap
[combined planned loss across correlated/open positions]
Session stop
[loss, rule breach, operational error, time, or trade-count trigger]
Account hard limits
[margin/liquidation, daily/max loss, position, product, or phase rules]
Entry order
[order type, price logic, time in force, maximum slippage or no-fill action]
Invalidation and protective exit
[market condition, order type, and venue-specific trigger behavior]
Profit-taking logic
[target, scale, trail, time exit, or opposing signal]
Gap/disconnection response
[who to contact, backup access, and action allowed after reconnection]
Cancellation rule
[when an unfilled order or stale setup must be cancelled]
Before session
[rule/version check, calendar, venue status, levels, risk capacity]
After each trade
[fills, costs, screenshots, rule grade, notes, net R]
After session
[reconcile executions; separate plan adherence from P/L]
Review gate
[date, eligible sample definition, minimum evidence, reviewer]
Change protocol
[hypothesis, one controlled change, replay/forward test, rollback rule]
Emergency override
[only risk-reducing actions; incident log required]

3. How to Fill the Template Step by Step

Choose the exact market, account, and operating window

“I trade forex” or “I trade crypto” is not enough. Record the exact instrument, contract or pair, venue, account mode, permitted direction, session or maintenance boundary, and the data source used for decisions. CME’s methodology lesson asks traders to identify the markets, when they are open, available equity, and willingness to risk. The CFTC separately warns that experience in one market may not transfer to another.

Make the account state explicit. A personal cash account, margin account, simulated evaluation, funded-simulation program, and live exchange-routed account can have different loss mechanics and permissions even when the screen shows the same headline balance. Link the official rule page and add a verified date; memory is not a source.

Turn a setup into a testable decision

Give each setup one stable name and version. Then write context, required conditions, trigger, invalidation, and disqualifiers as observable statements. “Strong momentum” is not reproducible. “The named input is above its pre-defined threshold at the close of the decision bar” can be checked—provided the indicator, timeframe, data source, and threshold are defined elsewhere in the plan.

Pre-entry gate
Every item resolves yes/no
  • The account, instrument, session, and setup version match the plan.
  • Every required condition is present and no disqualifier is present.
  • Planned entry, invalidation, target logic, estimated costs, and quantity are recorded.
  • Existing positions do not breach the combined or correlated-risk cap.
  • The account remains inside every broker, exchange, and exact-program rule.
  • A pre-entry chart or equivalent evidence is saved before the order.

Define the loss budget before quantity

Do not copy a universal percentage from an article. Start with money you can afford to lose, your account agreement, product leverage, liquidity, and the worst credible execution path. The CFTC’s pre-trade checklist asks whether the trader has identified the amount of risk and loss they can sustain; CME asks for intended leverage, maximum trade loss, maximum day loss, simultaneous positions, and total exposure.

Risk unit
cash risk budget = documented risk base × chosen risk fraction
Quantity
floor(cash risk budget ÷ estimated loss per unit)

Estimated loss per unit includes the distance from intended entry to invalidation, contract/pip/point value, and a documented allowance for costs and adverse execution. Product rules can make this simple formula incomplete; verify margin, option payoff, liquidation, gap, and venue mechanics before use.

Round quantity down to a valid unit and recalculate total planned loss. If the minimum tradable unit exceeds the budget, the valid size is zero. For prop accounts, size from usable loss room and the exact program phase—not the advertised account label. The prop-firm position-sizing guide shows that distinction in detail.

Calculate the quantity, then copy the inputs into the plan

Use TSB’s free calculator as arithmetic support. Verify contract value, pip value, fees, leverage, and the account’s actual rules independently.

Open position size calculator

Write order behavior—not just chart levels

An entry price and stop line do not fully specify execution. For securities, Investor.gov explains that a market order seeks immediate execution but does not guarantee the price, while a limit order controls the acceptable price but may not execute. Its August 18, 2026 stop-order bulletin also notes that a stop price is a trigger rather than a guaranteed execution price and that broker trigger standards can differ. Futures, options, forex, and crypto venues may implement different order types, triggers, protections, and liquidation paths, so the plan must point to the rules for the actual venue.

DecisionWrite in the planFailure case to model
EntryOrder type, trigger, limit/stop price logic, time in force, partial-fill handlingNo fill, delayed fill, partial fill, price gap, rejected order
Protective exitInvalidation condition, order type, placement timing, modification rightsGap through trigger, slippage, unavailable order type, liquidation first
Profit exitTarget/trail/time/opposing-signal logic and quantity at each stepPartial fill, fast market, target unavailable, remaining quantity error
Operational incidentBackup access, broker/venue contact, permitted risk-reducing actionData freeze, platform outage, lost connection, duplicate order

Define stop conditions and a review rhythm

A daily stop can be based on loss, rule breach, operational error, trade count, time, or a combination. It should be decided while calm and should never be looser than an account’s hard limits. A break after a particular losing streak or number of minutes is an optional personal control, not a scientifically universal reset.

  1. Before the session: confirm the current plan version, venue status, event calendar, risk room, and whether any existing position changes exposure.
  2. Before each order: run the setup gate and save the planned state before the result is known.
  3. After each execution: reconcile fills, costs, quantity, and whether the action matched the plan.
  4. After the session: grade adherence separately from P/L; a profitable violation is still a violation.
  5. At the review gate: compare like-for-like trades, document uncertainty, and decide whether to keep, test, or retire a rule.

4. Filled Trading Plan Example

This is a deliberately generic simulated example. It demonstrates specificity; it is not a strategy recommendation and does not claim an edge. Replace every line with evidence from your own market, venue, and testing.

FieldIllustrative entryWhy it is auditable
EnvironmentSimulation only; one named liquid instrument; one stated time zone and sessionAccount state and eligible observations are bounded
SetupSetup A v1; context, trigger, and invalidation each use pre-defined fieldsThe label connects plan, test, and journal records
Risk1R is the pre-committed maximum planned loss; total open risk cannot exceed 1RResults can be compared without pretending the account label is risk capital
EntrySubmit only after the trigger; cancel after the stated time or if a disqualifier appearsLate and improvised entries become identifiable violations
ExitProtective and profit-exit logic are recorded before entry; actual fill can differThe journal separates planned levels from execution
Session stopStop after the first hard-rule breach, operational-control failure, or the chosen R limitThe stop is triggered by observable state, not mood
ReviewFreeze v1 until the dated gate; compare only eligible Setup A v1 records after costsThe rule is not rewritten to explain yesterday’s outcome

5. Personal, Prop-Firm, and Crypto-Exchange Variants

The core template stays the same, but the authoritative constraints change. Do not paste one market’s defaults into another.

ContextRisk baseExtra fieldsSource of truth
Personal broker accountCash/equity and personal loss capacity, subject to marginBuying power, settlement, borrow, gap risk, tax-lot or account restrictionsBroker agreement, order policy, venue and regulator disclosures
Prop programUsable room to the nearest binding limit in the exact phaseProgram ID, account size, region, daily/max loss mechanics, consistency, days, payout and conduct rulesExact current program dashboard, agreement, and official rules
Crypto exchangeCollateral actually at risk under spot, margin, or derivatives modeLeverage, liquidation/mark price, funding, fee tier, maintenance, custody, API and jurisdiction limitsExact exchange product specification, fee schedule, status page, and account terms

The CFTC warns that leverage amplifies virtual-currency trading risk and that customers should understand how settlement or reference prices are determined. A generic “crypto trades 24/7” line is therefore not an operating rule: the plan must state the exact venue, product, maintenance behavior, funding clock, collateral, liquidation reference, and backup procedure.

No firm or exchange card appears on this page because no named provider determines the generic template. When a specific program or exchange is part of a later guide’s decision, that guide should render its exact canonical server-side card instead of copying live terms into prose.

6. Goals, Journal Fields, and Change Control

A profit target can create pressure to manufacture trades when eligible setups do not exist. Keep financial objectives visible as constraints, but grade controllable execution separately: eligible setups taken, disallowed trades avoided, planned risk respected, costs captured, and evidence completed. Do not call plan adherence proof of profitability; it only tells you whether the strategy received a fair test.

CME’s trade-log lesson recommends recording items such as entry and exit points, targets, time, technical inputs, news context, drawdown, and performance by system. Add the plan version, setup version, pre-trade eligibility, planned and actual risk, estimated and realized costs, maximum favorable/adverse excursion where available, and a binary rule-adherence grade. The trade-review workflow shows how to turn those fields into a repeatable post-session audit.

Do not use a universal “50 trades” rule

No fixed sample count makes a strategy statistically significant. Required evidence depends on event frequency, outcome dispersion, dependence between trades, the size of the effect being tested, costs, and the precision needed for a decision. Pre-commit an eligible sample definition and review date; report the count and uncertainty; keep backtest, replay, simulation, and live observations distinct. The sample-size guide explains why a threshold must come from the question and data rather than a slogan.

At a review gate, compute net results after costs, expectancy by setup, distribution of R outcomes, drawdown, and adherence. Use the expectancy formula guide to keep win rate, average win, average loss, and sample size visible instead of compressing the evidence into one headline percentage.

  1. Freeze: name the current plan and setup versions before collecting the next sample.
  2. Diagnose: separate execution deviations, data defects, market-regime differences, and strategy outcomes.
  3. Propose: write one change, its mechanism, expected trade-off, and failure criterion.
  4. Replay: apply the new rule to chronological data without peeking or selectively excluding losses.
  5. Forward test: use simulation or the smallest appropriate exposure; never infer safety from a backtest alone.
  6. Version or roll back: record the decision, date, evidence window, and exact prior version.

7. Use TSB as the Evidence Layer

8. Common Trading Plan Mistakes

  • Using inspirational language as a rule. Replace “be patient” with the exact condition that permits or cancels an order.
  • Copying somebody else’s risk percentage. A number without loss capacity, account mechanics, liquidity, and leverage is not a risk assessment.
  • Treating a stop as a guaranteed fill. Document the actual order, trigger policy, slippage, gap, liquidation, and outage path.
  • Changing multiple variables together. The next sample cannot identify which change caused the difference.
  • Grading by outcome. A winning rule breach remains a breach; a compliant loss remains evidence about the strategy.
  • Leaving emotion rules undefined. If urgency, anger, or fear matters, specify an observable response and log when it fires. The revenge-trading guide provides a bounded review protocol without diagnosing the trader.
  • Ignoring source drift. Version the official rule links and verification date whenever the account, program phase, exchange product, or venue changes.

9. Methodology and Primary Sources

This fact cycle used the page’s GSC and GA4 diagnostic snapshot, the production-read-only guide export, local TSB product truth, and current first-party or regulator material. Examples are labeled; no performance threshold is presented as universal. The plan is educational analysis, not individualized financial advice, and no strategy, order, stop, or journal can guarantee execution or profit.

Igor Manuilov
Written and reviewed by
Igor Manuilov
Founder of Trader's Second Brain · Trader since 2014
Editorial accountability

Trader since 2014. Built Trader's Second Brain to make execution review more evidence-based and less dependent on memory, scattered spreadsheets, or vague journaling.

Your trades · one review system
Import → reconcile → review

Your trade history already knows what to fix next.

Import or log trades. Find setup, session, and behavior leaks.

Find trade leaks →
Trader's Second Brain preview

Frequently Asked Questions

Quick answers to the most common questions about Trading Plan Template.

A trading plan is a versioned operating document that defines the account and market, eligible setups, required and disqualifying conditions, risk and position-size logic, order and exit behavior, stop conditions, evidence fields, and the process for changing a rule. It is not a promise that the strategy is profitable.

There is no evidence-based universal page count. Keep the operating sheet short enough to use before an order, and move detailed setup definitions, examples, and source material into a versioned annex. The test is whether every live decision is clear without hiding an essential constraint.

Include the exact account, venue, instruments, time zone and session, setup version, entry trigger, disqualifiers, risk base, size formula, combined exposure, order types, exits, event and outage handling, session stop, journal fields, and a dated review gate. Verify broker and venue rules independently.

No percentage is suitable for everyone. Set a cash loss budget from money you can afford to lose, personal risk tolerance, the account agreement, leverage, liquidity, gap or liquidation risk, and the nearest binding account limit. If the minimum tradable quantity exceeds that budget, the valid size is zero.

There is no universal 50- or 100-trade threshold. The needed evidence depends on the setup frequency, outcome dispersion, dependence between trades, costs, effect size, and precision required. Pre-commit an eligible sample and review date, report uncertainty, and keep backtest, replay, simulation, and live records distinct.

Use the same core structure but add the exact firm, program, phase, region, account size, daily and maximum loss mechanics, consistency, minimum-day, payout, conduct, platform, and reset rules. Size from usable room to the nearest binding limit, not the advertised account label.

Name the exact exchange and product, spot/margin/derivatives mode, collateral, leverage, mark and liquidation price mechanics, fee tier, funding clock, maintenance behavior, custody and API risk, jurisdiction limits, and backup procedure. A generic 24/7 label is not an operating rule.

No. Trigger and execution behavior varies by product, broker, exchange, liquidity, and market conditions. A stop may become a market order, execute away from the trigger, fail under a venue-specific condition, or be preceded by liquidation. Read the exact order policy and model slippage, gaps, and outages.

No. A plan can make decisions and deviations measurable, but it cannot create an edge, guarantee execution, prevent loss, or make leveraged trading safe. Grade adherence separately from P/L and test each strategy with costs and uncertainty visible.