Chapter 1 of 8

Build a trading operating system

Define what you will do before a trade, after a win, after a loss and when the conditions for your method disappear.

4 min read · Advanced process workshop

In this chapter

The decision must survive the session
Prepare the state, not a prediction
Use an order gate
Specify stop conditions and restart conditions
Separate process evidence from outcome evidence
Worked example
Common mistakes
Check your understanding

The decision must survive the session #

You do not need another rule that sounds sensible when the market is closed. You need a small set of actions that remain executable when a position is losing, an option is moving quickly, or you have just made more than expected. A process is observable: another person should be able to look at the ledger and tell whether you followed it. “Be disciplined” cannot be audited. “Stop opening new positions after the loss budget is consumed” can.

This is an original training template informed by the owner’s teaching priorities. It is not the unpublished Consistency Framework from his book, and it does not claim that following a routine guarantees earnings.

Prepare the state, not a prediction #

Before the session, record instruments permitted by your plan, scheduled announcements, contract specifications, available cash and aggregate open exposure. Write the conditions required by your strategy and the conditions that disqualify the session. A paper breakout plan might exclude scheduled-release windows and unusually wide spreads. The exclusions must be fixed before observing which excluded trades would have won.

Write separate responses for a normal start, a gap through your intended entry, a platform outage and a previously open loss. If a data or order-routing check fails, the operational response is to stop and resolve it; a more confident market view does not restore a broken connection.

Use an order gate #

Before each simulated order, record the strategy version, setup, trigger, invalidation, units, cost/slippage allowance and the earliest plausible funding obligation. If the whole-lot size is zero, the trade is skipped. If the trade is a second exposure to the same market driver, include it in the existing risk cluster rather than treating its separate symbol as independent diversification.

After a win, do not expand the size merely because the day feels easier. After a loss, do not shorten the next setup’s checklist to recover time or money. A size change belongs to a scheduled review with evidence, not an improvised response to P&L.

Specify stop conditions and restart conditions #

A useful operating limit describes the action as well as the number: cancel unfilled entry orders, do not open new positions, and manage existing positions under their original exit rules. A loss limit does not guarantee an exact cap because gaps and illiquidity can exceed it. A period limit can be based on realised loss plus conservatively estimated open risk rather than realised P&L alone.

Restart only under a predefined condition: an operational issue is resolved, a new review period begins, or a documented human review authorises a new paper-testing plan. Moving the daily threshold after breaching it makes the threshold meaningless. Taking a break is a process action; winning the next trade is not a restart criterion.

Separate process evidence from outcome evidence #

Score rule compliance, execution quality and financial outcome independently. A rule-breaking winner should remain a rule breach. A rule-following loser is not proof that the strategy is sound either; it belongs in the evidence about the strategy’s loss distribution. Both levels matter: whether you executed the rules and whether the rules deserve continued use.

At review, compare the frozen plan with the recorded decisions. Change one research variable at a time, assign a new version and preserve previous results. A better story after the outcome is known is not a better pre-trade process.

Hypothetical worked example

A fictional session with a stopping rule

A ₹2,00,000 paper account uses an illustrative ₹1,000 planned loss unit R and a session budget of 2R. These figures are not recommended limits. Two closed trades lose ₹900 and ₹800 including costs. A new candidate would add ₹600 planned open risk. The combined ₹2,300 exceeds the ₹2,000 session budget, so the order gate rejects it.

If an earlier gain offsets the displayed net P&L, the written plan must say whether the budget uses net P&L, gross losses or another measure. Choose the rule before the session and evaluate its consequences; do not switch definitions to permit the next trade.

Common mistakes

Writing limits without specifying the action after a breach.
Treating one profitable week as validation of the operating system.
Letting a friend’s screenshot override the order gate.

Check your understanding

A trade breaks the written size rule but makes money. What should the review record?

Make this chapter useful

Can you defend the reasoning?

Before moving on, answer the self-check in your own words and write why each alternative fails. Use the worked example to test that explanation. Then apply it in the module research task; keep the assumptions and the evidence that could change your answer.

Sources and further reading

Further-reading references from the curriculum source list. Contract sizes, expiry calendars, settlement references, margin parameters and tax treatment can change; verify the current operative documents for the actual product. Worked figures are illustrative, not current quotes.

Progress is stored only on this browser.

Back to Trading playbooks and professional process · Learning library · Calculators

General financial education. No securities recommendation, assured outcome or personal advice. Read the risk disclosures.