← All posts

Trading Plan Template: Build Rules You Can Execute and Test

September 20, 2026·11 min·trading plan
MBMarco BianchiTrading Systems Analyst · Europe
Trading Plan Template: Build Rules You Can Execute and Test
Share

Use this trading plan template to define your market, setup, entries, exits, risk limits, review process, and change controls as clear, testable rules.

Quick Answer

A useful trading plan states exactly what you trade, when you may trade it, what creates an entry, where the trade becomes invalid, how much you risk, how you exit, and when you must stop. It should also define how trades are recorded and when rules may be changed. The main limitation is that a written plan cannot make an unvalidated strategy effective. It creates consistency and testability, not guaranteed performance.

Key Takeaways

  • Separate the strategy that generates trades from the risk and operating rules that control how you deploy it.
  • Replace subjective terms such as “strong trend” or “good setup” with observable conditions.
  • Define position sizing, maximum exposure, and session limits before an entry appears.
  • Record rule adherence separately from profit and loss; a winning trade can still violate the plan.
  • Test the complete plan with realistic fees, slippage, and chronological order handling.
  • Change one rule set at scheduled review points rather than rewriting the plan after individual losses.

What a Trading Plan Must Accomplish

A trading plan is an operating document for making repeatable decisions under uncertainty. It is broader than a strategy.

A strategy defines the conditions for entries, trade management, and exits. The trading plan also covers eligible markets, trading hours, position sizing, total exposure, loss limits, data requirements, execution procedures, recordkeeping, and rule changes.

The distinction matters because the same strategy can produce very different account outcomes under different operating rules. Two traders may take identical entries but use different sizes, accept different levels of correlated exposure, or stop trading under different conditions.

A complete plan should let another informed person answer four questions without guessing:

  1. Was this trade eligible?
  2. Was it sized correctly?
  3. Was it managed according to the rules?
  4. Was any deviation intentional and documented?

If those questions cannot be answered from the written document, the plan is not yet operational.

A Practical Trading Plan Template

Copy the following structure into your preferred document or notebook. Complete each section before risking capital.

1. Trading mandate

Define what the plan is designed to do and the constraints it must respect.

  • Trading style: intraday, swing, position, or another defined horizon
  • Expected holding period: minimum and maximum
  • Permitted direction: long, short, or both
  • Decision frequency: continuous monitoring, bar close, or scheduled review
  • Capital allocation: amount or percentage assigned to this plan
  • Prohibited activity: instruments, sessions, or order types you will not use

Avoid framing the mandate as an income target. Markets do not provide a fixed salary on demand. Use process objectives such as executing only eligible setups and keeping risk within stated limits.

2. Market and data universe

Specify exactly where the plan applies.

  • Asset class and instrument list
  • Exchange or trading venue
  • Minimum price, volume, or liquidity conditions
  • Trading session and time zone
  • Chart interval and required history
  • Corporate action or market-data handling
  • Conditions that make an instrument ineligible

“Trade liquid stocks” is ambiguous. A measurable liquidity threshold or fixed watchlist is more useful.

3. Setup definition

Describe the market state that must exist before an entry is considered. Include every required indicator, price pattern, timeframe, and filter.

For each condition, state:

  • The data used
  • The calculation or comparison
  • The timeframe
  • Whether it is mandatory or optional
  • When the condition is evaluated

For example, “enter in an uptrend” is not executable. “The latest completed daily close is above the 50-day simple moving average” is observable and testable.

4. Entry rule

State the event that triggers an order and how that order is placed.

Include:

  • Signal timing: intrabar, bar close, or next bar
  • Order type: market, limit, stop, or stop-limit
  • Entry price rule
  • Maximum acceptable slippage or chase distance
  • Signal expiration
  • Gap handling
  • Re-entry policy

The plan must resolve sequencing. If a signal is calculated at a bar’s close, do not assume execution at an earlier price from that same bar.

5. Initial risk and position size

Define the invalidation level first, then calculate size from the amount you are willing to lose if the stop executes as modeled.

A basic risk-based formula is:

Position size = permitted trade risk / risk per unit

If entry is $50 and the initial stop is $48.50, risk per share is $1.50 before fees and slippage. With permitted trade risk of $150:

$150 / $1.50 = 100 shares

Actual loss can exceed the planned amount because of gaps, slippage, liquidity, and order behavior. The plan should therefore state whether estimated costs or an additional buffer are included.

Also define maximum position value, leverage, and minimum viable size. If the calculated position breaches another limit, reduce it or skip the trade.

6. Trade management and exits

Write separate rules for:

  • Initial stop placement
  • Profit-taking
  • Trailing stops
  • Time-based exits
  • Signal-based exits
  • Partial exits
  • Overnight holding
  • End-of-session handling
  • Conflicts between exit rules

Set rule priority in advance. If a profit target and stop could both be touched within the same bar, the testing engine needs enough data or an explicit conservative assumption to determine which occurred first.

7. Account and session guardrails

Per-trade risk is not enough. Multiple positions can create concentrated exposure.

Define:

  • Maximum simultaneous positions
  • Maximum total open risk
  • Limits for correlated instruments
  • Maximum sector or asset concentration
  • Daily or weekly loss limits, if used
  • Conditions for pausing new entries
  • Rules following technical or data failures

A session limit should state what happens when it is reached. Does the trader cancel pending entries, close open positions, or merely stop initiating new trades? These are different policies.

8. Records and review

For every trade, capture the strategy version, setup, signal time, intended order, actual fill, initial stop, planned risk, exit reason, costs, and any rule violation.

Review at a fixed cadence. Useful review questions include:

  • Were all trades eligible?
  • Did execution match the plan?
  • Which deviations were preventable?
  • Were costs materially different from assumptions?
  • Is the result within the range suggested by relevant testing?

Do not evaluate discipline using profit alone. A compliant loss is different from an undisciplined win.

9. Change control

Give the plan a version number and effective date. State how much evidence or elapsed time is required before a scheduled review, while recognizing that no universal sample size is sufficient for every strategy.

Record each modification with:

  • The problem being addressed
  • The proposed rule change
  • The evidence supporting it
  • The new version number
  • The date it becomes active

Emergency suspension is different from optimization. You may pause a plan immediately if data, execution, or risk controls fail without inventing replacement rules in the middle of a session.

The Deploy dialog for a strategy: you choose a venue from thirteen options, pick paper or live mode, set paper capital, and cap max leverage, max drawdown percent and max positions before deploying. A note explains live mode runs through the validation gate first and refuses deployment with reasons surfaced if any gate fails.

Deploying a strategy to paper or live with a pre-flight gate.

Worked Example: Turning an Idea Into a Plan

Consider this hypothetical idea: buy a liquid stock when it breaks above a recent range in a broader uptrend.

The initial wording leaves several questions unanswered. How long is the range? Must the bar close above it? How is liquidity defined? Where is the stop? When does the signal expire?

A more operational version could be:

  • Universe: a predefined list of stocks meeting stated price and liquidity thresholds
  • Trend filter: latest completed daily close above its 50-day simple moving average
  • Setup: previous 20 completed daily bars define the range
  • Entry signal: daily close exceeds the highest high of those 20 bars
  • Execution: market order at the next session’s open, subject to a maximum opening-gap rule
  • Initial stop: below a mechanically defined range or volatility level
  • Size: fixed account risk divided by entry-to-stop distance, capped by maximum position value
  • Exit: predefined stop, target, trailing rule, or maximum holding period
  • Portfolio rule: no new entry if total open risk would exceed the plan limit

This is not a strategy recommendation. It illustrates how each phrase can be converted into a condition that can be executed and tested. Exact thresholds require independent research.

How to Validate the Complete Plan

Step 1: Resolve every ambiguous term

Underline words such as strong, near, significant, liquid, extended, and high volume. Replace each with a calculation or decision procedure. If discretion remains, define what evidence the trader must record.

Step 2: Test the strategy logic chronologically

Run the entry, sizing, management, and exit rules in the order information would have become available. Include fees, slippage, rejected signals, overlapping positions, and capital constraints where possible.

Step 3: Inspect more than net return

Review trade count, expectancy, drawdown, loss distribution, exposure, holding time, turnover, and sensitivity to costs. Segment results only when there is a defensible hypothesis; unrestricted slicing can manufacture attractive historical patterns.

Step 4: Challenge the assumptions

Vary plausible parameters rather than relying on one optimized value. Use out-of-sample evaluation, walk-forward analysis, and stressful historical periods where appropriate. Stability across reasonable assumptions is generally more informative than one exceptional configuration.

Step 5: Rehearse execution

Use replay or paper trading to identify operational problems that a historical simulation may miss: missed alerts, impractical order timing, platform limitations, or rules that require more attention than you can provide.

Step 6: Approve a fixed version

Freeze the plan before controlled deployment. Record deviations, but do not modify the live version after every trade. A stable rule set is necessary to distinguish strategy behavior from continuous intervention.

Once the document is precise, Kvants Studio can turn plain-English ideas into editable, auditable strategy logic. Its event-driven backtests run on NautilusTrader and support parameter sweeps, walk-forward analysis, crisis-stress validation, and controlled paper or live workflows for stocks and crypto. The Kvants documentation can help you structure and inspect that research process. These tools test assumptions; they do not establish that a strategy will work in the future.

The Strategy Studio editor showing a compiled momentum-crossover strategy: a header names the strategy with Save, Templates, Deploy, Backtest, Competition and Import Pine actions and metric tiles for Sharpe, win rate, max drawdown and live status, while a structured readout lists the price feed, indicators (EMA 12, EMA 26, RSI 14), the crossover condition, AND logic, long entry and exit signals, position sizing, stop-loss and take-profit risk, and market execution with slippage.

A strategy laid out end to end in the Kvants editor.

Common Trading Plan Failure Modes

Writing principles instead of rules

“Stay disciplined” and “avoid bad trades” are intentions. They do not identify a valid signal or specify what action to take.

Ignoring interactions between positions

A plan may size each trade responsibly while allowing several highly related positions to create excessive combined exposure.

Testing signals without testing operations

A signal-only backtest can overlook next-bar execution, position limits, order conflicts, unavailable capital, and session restrictions.

Optimizing around historical noise

Repeatedly changing lookback periods, filters, and exits until the past looks attractive increases overfitting risk. Validation must use information not consumed by the selection process.

Changing rules after a small number of losses

Losses do not automatically prove that a plan is broken. They may reflect ordinary variance, poor execution, unusual market conditions, or a genuine weakness. Diagnose the cause before revising the rules.

Treating compliance as optional

If unplanned trades are mixed with planned trades, the resulting record cannot cleanly evaluate either the strategy or the trader’s execution.

The Backtest panel where you configure a run: a date-range period, starting capital, timeframe, and toggles for a timeframe sweep and multi-coin testing, with a Run Backtest button. A footer reports the requested bars, assets, timeframe and dataset row count, and notes synthetic OHLCV is used for the demo while real exchange data requires API keys.

Configuring a backtest in Kvants Studio.

Frequently Asked Questions

What is the difference between a trading plan and a trading strategy?

A strategy defines the setup, entry, management, and exit logic. A trading plan includes the strategy plus market eligibility, sizing, portfolio limits, operating procedures, recordkeeping, review, and change control.

How long should a trading plan be?

It should be as short as possible without leaving material decisions unresolved. A simple strategy may need only a few pages. Complexity is justified only when it removes genuine ambiguity.

Should a trading plan include profit goals?

You may track long-term objectives, but a required daily or weekly profit can encourage forced trades and excessive risk. Process goals—such as rule adherence and controlled exposure—are more directly actionable.

Can discretionary traders use this trading plan template?

Yes. Discretion should be bounded and recorded. Define the evidence considered, which decisions remain flexible, and what would make a trade ineligible. Replay and structured journaling can then assess whether the discretion adds consistent value.

How often should I update my trading plan?

Review it on a preset schedule or when a material assumption changes. Suspend it sooner if data, execution, or risk controls malfunction. Avoid permanent rule changes based only on one trade or a brief losing streak.

Risk Note

This article is educational and is not investment advice. Trading involves risk, and actual losses may exceed planned losses because of gaps, slippage, liquidity, leverage, and execution failures. Backtested performance does not guarantee future results. Kvants is a research tool, not an investment adviser, and does not guarantee performance.

Read more