Define eligibility, execution, exits, size, aggregate limits, and review with validated rules—without treating example percentages as prescriptions.
A trading plan is a versioned set of testable commitments
A plan does not predict the next move. It defines the universe and conditions that make an order eligible, the information available at the decision timestamp, how the order will be executed, which observations invalidate the thesis, the maximum planned exposures, and what evidence permits a future change. “Buy when it looks strong” is not auditable. A close above a named level with a specified data source and time is auditable, but it is still only a hypothesis until point-in-time research supports it. Record strategy and configuration versions, ownership, effective date, exception authority, logging, and rollback. Discretion can remain when the allowed observations and boundaries are explicit. Another reviewer should be able to classify the same event without knowing its later return. SEC material warns that day trading can produce severe losses and that order choice changes execution risk; the plan must treat survival and executability as constraints, not slogans. [1][2] The uncomfortable implication is that specificity does not create edge—it only makes the claim falsifiable.
Table 1. Testable commitments| Element | Vague | Testable | Control |
|---|
| Entry | Looks strong | Rule with source and time | Point-in-time |
| Exit | Feels wrong | Trigger and order | Gap handling |
| Size | Normal | Formula plus constraints | Stress loss |
| Review | Occasionally | Cadence and evidence | Version |
Falsifiability
A precise example is not an edge until independent evidence supports it.
Every entry needs a setup, trigger, filter, and timestamp
The setup describes the opportunity context; the trigger is the current event that authorizes action; the filter blocks an otherwise valid trigger; the timestamp fixes what could have been known. A trend setup may use adjusted price structure, a mean-reversion setup a predefined deviation, and a catalyst setup a public release time. Terms such as resistance, oversold, volume expansion, or earnings week require exact windows, adjustments, calendars, and data vendors. Preserve every eligible candidate, including rejected signals, so selection can be measured. Test false triggers, stale quotes, halts, gaps, spread, depth, borrow, and capacity. The entry cannot be evaluated independently from the exit and sizing rules because a profitable signal at small executable size can fail after a different stop or larger participation. Highly skewed individual-stock outcomes also caution against treating a few spectacular winners as a typical entry edge. [3] A filter added after observing losses is a new model version, not an explanation. Store the rejected population and run it through the same later analysis.
Table 2. Entry components| Style | Setup | Trigger | Filter |
|---|
| Trend | Defined structure | Confirmed break | Event/liquidity |
| Reversion | Measured deviation | Defined reclaim | Spread/regime |
| Catalyst | Timestamped event | Follow-through | Capacity |
| Breakout | Encoded range | Price and volume | False-signal rule |
Stop risk
A stop is an instruction, not a guaranteed execution price.
Exit rules need price, time, thesis, and execution instructions
A price stop limits exposure under its execution assumptions; a time exit ends an opportunity that did not develop; a thesis exit responds to predefined evidence; a profit rule governs realization. None guarantees a fill during a gap, halt, limit state, or thin book. Specify trigger source, order type, regular or extended hours, partial fills, cancel/replace behavior, market closure, and fallback when the stop venue or data feed fails. Fixed and trailing stops can help or harm depending on strategy and path; validate the entire entry-exit combination on held-out or walk-forward data with spread, slippage, borrow, and gaps. [5] Do not widen a stop after entry merely to preserve a story. A planned thesis update must name the new public fact, authorized response, and revised risk before the order is changed. Expressing distance in R standardizes the plan but does not make the loss bounded: an overnight jump can bypass the price. What most investors get wrong is confusing a stop instruction with a guaranteed transaction price.
Table 3. Exit instructions| Exit | Purpose | Failure | Required control |
|---|
| Fixed | Planned exposure | Gap or noise | Slippage |
| Trailing | Profit rule | Chop | Path test |
| Time | Capital horizon | Premature exit | Clock |
| Thesis | Invalidation | Discretion | Named evidence |
Sizing
Nominal stop distance omits gaps, liquidity, correlation, and operational failure.
Position size starts with plausible loss, not stop distance alone
The familiar shares formula—dollar risk divided by entry-to-stop distance—produces nominal size, not worst-case loss. For a $50,000 account, an illustrative $500 risk budget and $2 distance gives 250 shares; a $5 overnight gap produces about $1,250 of price loss before costs, not $500. Add a loss distribution with gaps, spread, slippage, market impact, borrow, leverage, currency, contract multiplier, and the chance that the stop does not execute. Then constrain notional, participation, concentration, correlation with existing positions, factor exposure, and aggregate portfolio loss. Percentages such as 0.5% or 1% of equity are examples, not suitability conclusions. “Lower-quality setup” cannot justify an improvised size reduction unless quality is defined and calibrated; otherwise it is discretionary confidence in numeric clothing. Worked example: 250 shares at $2 planned distance have $500 nominal risk, but a stress loss of $5.30 per share including gap and slippage is $1,325. Compare both to the approved portfolio budget. The plan should survive plausible joint losses, not only a stop-fill spreadsheet.
Table 4. Nominal versus stressed size| Input | Illustration | What is missing |
|---|
| Account equity | $50,000 | Portfolio exposure |
| Nominal budget | $500 | Suitability |
| Stop distance | $2.00 | Gap and fill |
| Nominal shares | 250 | Liquidity |
| Stress loss/share | $5.30 | Scenario |
| Stress loss | $1,325 | Aggregate budget |
Governance
Illustrative limits must be calibrated before they can control live capital.
Four aggregate limits must distinguish loss, model, and infrastructure
Trade, day, week, and strategy-level limits can block new orders, reduce exposure, or initiate review, but values such as 2R daily, 4R weekly, or 6% monthly are not universal. Estimate the system's loss distribution, clustering, autocorrelation, concurrent positions, leverage, liquidity, and operational incidents. Distinguish a market loss within expectation from a model breach, data failure, rejected order, or broken risk control. Define whether a trigger means flatten, hedge, cancel new entries, or seek approval; state treatment of open positions, re-entry, reset evidence, responsible person, and maximum response time. Five successive 2% account losses compound to 1 − 0.98⁵ ≈ 9.61%, not exactly 10%; correlated gaps can be worse. Treat all such numbers as scenario arithmetic, not recommended limits. A circuit breaker protects capital and operations, but an unvalidated low threshold can stop a strategy during an expected cluster and create timing discretion. Calibrate on data independent from the final evaluation and test the operational path, including who receives the alert when automation fails. [6]
Table 5. Aggregate controls| Level | Trigger type | Candidate response | Reset |
|---|
| Trade | Invalidation | Exit or hedge | New setup |
| Day | Loss or incident | No new entry | Next-session checks |
| Week | Unexpected cluster | Review | Approval |
| Strategy | Model or control breach | Pause | Validation |
A pre-trade checklist blocks known errors and records exceptions
The checklist confirms strategy version, clock and data health, event risk, spread and depth, borrow, existing and correlated positions, order instructions, buying power, plausible gap loss, aggregate limits, stop handling, logging, and required approvals. A failed item blocks the order or invokes a named exception process with reason, approver, expiry, and reduced boundary; “special situation” is not evidence. Automate objective checks while retaining human confirmation for genuinely discretionary facts. Two minutes is not a universal maximum: a simple stock order may need seconds, while a derivative, event trade, or cross-currency position can require more analysis. Measure completion time and abandonment, then remove redundant fields without deleting a material control. After an incident, perform root-cause analysis before changing the checklist; a normal loss does not prove a missing control. Include a kill switch test and verify that logging survives canceled, rejected, and partial orders. The checklist earns its place by preventing a known failure at acceptable latency, not by being short or ceremonial.
Table 6. Checklist controls| Check | Evidence | Failure response |
|---|
| Version/data | Current and healthy | Block |
| Liquidity/order | Spread and depth | Resize or block |
| Loss/exposure | Stress calculation | Block or approve |
| Exception | Owner and expiry | Audit |
Monitoring, research, and model approval need separate cadences
Execution and risk monitoring can be continuous; fill and incident review can be daily or weekly; strategy inference needs a defined effective sample; model changes need independent approval and rollback. “Every 20 trades” can be far too few when outcomes are noisy or far too slow for a high-frequency execution defect. Separate three questions: was policy violated, did outcomes remain within predefined ranges, and did market or data conditions change according to a validated regime rule? Correct an operational incident first, research the strategy second, and change parameters only through the model-governance process. Review winning periods too, because a favorable regime can conceal slippage, concentration, or rule drift. Include rejected signals, costs, turnover, benchmark, data quality, and composition changes. Published anomalies can weaken after discovery, but that does not authorize relabeling every drawdown as decay. [4] Predefine the evidence that retires, pauses, or scales a version. A calendar ensures attention; it does not provide statistical power.
Table 7. Review governance| Process | Cadence driver | Output | Not allowed |
|---|
| Risk monitoring | Urgency | Intervention | Rewrite model |
| Execution review | Incidents/fills | Diagnosis | Change signal |
| Strategy research | Effective sample | Test | Auto-deploy |
| Approval | Material evidence | Version/rollback | Erase history |
One template can govern discretionary and systematic styles
The template records market condition, universe, source and timestamp, eligibility, exact trigger, filter, order instructions, invalidation, price/time/thesis exits, planned and stressed loss, size, aggregate limits, dependencies, checklist results, exception, journal fields, kill switch, and rollback. For discretionary trading, list which observations permit judgment and how a reviewer will audit them. For systematic trading, link every field to a code, configuration, data, and deployment version. Before live capital, use point-in-time backtesting, replay, paper execution, and limited-scale validation in proportion to risk; none alone proves future edge. Show how each trade fits portfolio concentration, liquidity, and correlation because an individually valid order can violate the total risk budget. A one-page summary may point to longer specifications, but it must not omit operational dependencies or exception authority. Practical takeaway: the plan is ready only when eligibility, execution, loss under stress, and stop authority are reproducible—and when a failure can safely prevent new exposure without inventing a market forecast.
Related analysis
trading-planrisk-controlchecklistbehavioral-financeexecution
Sources & Further Reading
- U.S. Securities and Exchange Commission. Investor Bulletin: Day Trading: Your Dollars at Risk. Source
- U.S. Securities and Exchange Commission. Investor Bulletin: Trading Basics. Source
- Bessembinder, H. (2018). Do Stocks Outperform Treasury Bills? Review of Financial Studies, 31(9), 3375–3431.
- Marquering, W., Nisser, J., & Valla, T. (2006). Disappearing anomalies: A dynamic analysis of the persistence of anomalies. Applied Financial Economics, 16(4), 291–302. Source
- CFA Institute. Stop-Loss Orders and Risk Management. CFA Institute Research and Policy Center.
- U.S. Securities and Exchange Commission. Regulation NMS and market structure resources. Source