How to Write a Trading Plan (With a Template)

A trading plan is a written specification of what you may trade, the conditions for acting, how size and exits are determined, when to pause and how decisions will be reviewed. Write it so another person can distinguish a permitted action from a breach without knowing the outcome. A complete plan makes decisions inspectable; it does not establish that the strategy will be profitable.

Use the trading-process library

Scroll horizontally to read every column.

Use the plan to define intended behaviour, the journal to record actual behaviour and the review to explain differences. A profitable rule breach still belongs in the deviation log; an allowed losing trade is not automatically a process failure.

Which decisions belong in a trading plan?

Choose the holding style in the context of time and monitoring requirements. Scalping concerns short-duration trades; day trading defines a session-end boundary; swing and position approaches involve longer holding horizons. None supplies a rule set by itself. Overnight exposure, transaction costs and the ability to monitor exceptions remain separate decisions.

Goals can include a research deadline, a complete record or reliable reconciliation. Financial objectives should remain hypotheses to evaluate, not prescribed monthly returns. A plan also needs a list of actions you will not take, such as discretionary size increases or unscheduled parameter changes.

Copy this blank trading-plan template

Fill every field in your own terms. “Not applicable” needs a reason; “to be decided” identifies unfinished work. The template supplies no recommended instrument, strategy, risk percentage or indicator setting.

1. Owner, version and purpose: plan owner ___; version/date ___; objective ___; evaluation horizon ___; time available ___; funds and accounts in scope ___.
2. Markets and data: instruments ___; chart provider and exact identifiers ___; broker symbols ___; chart type/timeframe ___; account currency ___.
3. Holding style and sessions: intended holding horizon ___; allowed days/hours ___; named timezone ___; daylight-saving policy ___; overnight/weekend policy ___.
4. Setup as conditions: inputs ___; calculation/lookback ___; comparisons including equality ___; evaluation moment ___; entry event versus ongoing filter ___.
5. Fundamental inputs and vetoes: data/calendar source ___; release time and availability ___; covered events ___; manual decision owner ___; blackout rule ___.
6. Entry and ownership: order type ___; symbol ___; permitted direction ___; existing-position check ___; strategy/account scope ___; repeat, reversal and conflicting-signal rules ___.
7. Initial risk and sizing: risk basis ___; stop definition ___; cash-risk calculation ___; volume units ___; broker minimum/step/maximum ___; treatment if valid size is unavailable ___.
8. Exits: stop ___; target ___; time or condition exit ___; partial-close rule ___; order location and enforcement owner ___; evidence of a completed close ___.
9. Limits: aggregate exposure ___; daily/weekly loss measure ___; reset timezone ___; trade-count limit ___; response to each breach ___.
10. What I will not do: prohibited changes or actions ___; circumstances requiring a pause ___; how an exception is authorised and logged ___.
11. Testing: frozen rule version ___; data period and costs ___; development versus held-out sample ___; boundary/failure cases ___; demo reconciliation evidence ___.
12. Monitoring and recovery: checks and owner ___; unavailable-monitoring response ___; uncertain order outcome procedure ___; open-position handling during a pause ___; restart conditions ___.
13. Journal and review: fields ___; session check ___; review cadence ___; metrics and denominators ___; change log ___; evidence required before a revision ___.

How do risk, sizing and drawdown differ?

Initial trade risk is the planned loss between entry and the initial stop, expressed in money under stated assumptions. Drawdown measures a decline from a running account peak. A percentage of capital used for a trade's risk budget is not itself that account's drawdown.

Illustrative cash-risk budget = reference capital × chosen risk fraction
Illustrative position size in lots = cash-risk budget / (stop distance in pips × pip value per 1.00 lot)

Illustrative arithmetic, not a recommendation. A 10,000 USD reference balance multiplied by an assumed 2% fraction gives a 200 USD planned budget. With an assumed 20-pip stop and 10 USD per pip per 1.00 lot, the simplified calculation gives 200/(20 × 10) = 1.00 lot.

The example assumes stable pip value and excludes additional costs. It is not a maximum realised loss: gaps, slippage and costs can change the result. Check the actual symbol's contract size, minimum volume, volume step and maximum volume. MetaTrader exposes those as broker-specific symbol properties.^[1]

Use the position-sizing guide to define the method, and the risk library to distinguish per-trade risk, total exposure and daily loss limits. State whether each limit blocks new entries, requests closes or requires manual action.

Why does a target risk-reward ratio not establish expectancy?

A planned target-to-stop ratio describes intended distances. Realised average wins and losses describe completed trade results. The two need not match. A plan should define both the intended exits and how realised outcomes will be measured.

Cash expectancy = (win frequency × average win) − (loss frequency × average loss magnitude)

The following constructed cases preserve useful arithmetic from the earlier plan guides. Every case assumes no breakevens, no additional costs and the stated average outcomes. They are not forecasts, backtests, target settings or comparable strategy rankings.

These cases demonstrate why win rate alone cannot describe the arithmetic. With breakevens, count them in all closed trades and calculate loss frequency separately. When initial cash risk varies, calculate each trade's R-multiple before averaging. Do not divide average cash outcome by an average risk budget.

Use expectancy, profit factor and drawdown together. MT5's report describes Expected Payoff as an average result, and defines the profit-factor and drawdown fields separately.^[2]

How does the plan become an automation specification?

For each rule, add an enforcement location and an observable acceptance case. The phrase “one trade at a time” is incomplete until it names the symbol, strategy and account scope, plus how an unresolved previous request is handled. A TradingView simulated position is not the broker's position.

For example, turn “avoid major news” into a named calendar, event list, timezone, pause interval and accountable manual veto unless a supported automated implementation has been verified. Turn “stop after the session” into separate decisions about new signals, pending orders, existing positions and close verification.

The full automation rule specification supplies the next step. As of 25 September 2026, the PineConnector converter documentation states that its broker stops and targets operate separately from simulated strategy exits. Its adapter does not resynchronise their positions.^[3]

Before creating any executable test alert, verify that every account sharing the chosen License ID is a demo account. Then use your own symbol, permitted size and rules, following the documented demo verification procedure. Confirm alert delivery, processing, broker acceptance, deals and positions separately.^[4] A stop activating does not prove that a position closed.

How do you test and revise the plan?

Freeze the definitions before evaluating them. Record data coverage, costs, missing inputs and the difference between development data and the held-out test. TradingView's strategy documentation warns about look-ahead bias, selection bias and overfitting, including adjusting a rule to fit a particular historical sample.^[5]

There is no universal number of months that makes every plan validated. Consider trade count, varied conditions, dependencies and the way the strategy was selected. A high win rate alone neither proves robustness nor diagnoses overfitting. See the backtesting library.

Changes in conditions can justify research, but “adapt” is not permission to rewrite the plan after every loss. Record a specific hypothesis, the evidence that would contradict it and the test data reserved for that change. Do not assume a strategy family must work in a market simply because the market is labelled trending or ranging.

What review routine helps you follow the plan?

1. Before the session: confirm the active version, instruments, session clock, vetoes, receiving accounts and unresolved exposure.
2. After an event: log the intended condition, alert time, requested action, broker response, actual size/price, exit and any deviation. Keep uncertainty visible.
3. At session end: reconcile orders and positions, record costs and classify rule adherence independently of profit or loss.
4. At the chosen review: compare outcomes and deviations by plan version. Decide whether the issue was the rule, its implementation, its execution or an unauthorised override.
5. Before restarting after a pause: confirm the stated restart evidence and owner. Inspect existing exposure before resending an ambiguous order request.

Record breaks and stress-related pauses as explicit process choices. Automation changes how an instruction is executed; it cannot prevent you from changing the instruction or taking an unplanned manual trade. Use the journal and overtrading checks to inspect that difference.

Frequently asked questions

How do I write a trading plan?

Write the allowed markets, conditions, timing, size, exits, limits and review process in observable terms. Add the owner and enforcement location for each rule. A finished plan lets another person identify permitted actions and breaches without judging whether a particular trade made money.

What should a trading plan template include?

A trading plan template should cover purpose, data, sessions, setup conditions, entries, sizing, exits, limits, prohibited actions, testing, monitoring and review. Include handling for unresolved orders and open positions during a pause. Leave recommended trading settings out of the template; those need separate justification.

How often should I review my trading plan?

Set a review cadence that matches the plan's activity and available evidence, while reconciling operational incidents when they occur. Keep rule changes separate from routine record checks. A losing trade alone does not establish that the plan needs changing, and a profitable breach does not validate the breach.

Can PineConnector make me stick to a trading plan?

PineConnector can process supported instructions sent through a configured workflow, but it does not decide whether your rules are appropriate or prevent every manual override. Document who monitors the workflow, how broker outcomes are reconciled and when it pauses. Strategy design and adherence still require human decisions.

Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account and no code was compiled.

Related reading

• Risk management library
• Backtesting library
• From discretionary to automated trading
• Trading metrics library

Sources

1. MetaQuotes – Market Watch: symbol specification, accessed 25 September 2026.
2. MetaQuotes – Testing Report, accessed 25 September 2026.
3. PineConnector – Pine Script converter, accessed 25 September 2026.
4. PineConnector – Test your setup, accessed 25 September 2026.
5. TradingView – Strategies: backtesting, forward testing and biases, accessed 25 September 2026.

PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.