Captain · Independent Research and Operations · About 30–40 minutes
Safety rule: If an operating rule cannot be understood and reproduced, it is not ready for live risk.
Your mission today
By the end you can assemble a version-controlled trading manual with setup rules, risk limits and emergency responses.
Before you start
Bring the frozen Captain strategy card, demo execution journal and CP07.2 data-quality report. The trading tickets in this lesson are imaginary.
1. A manual is different from a strategy idea
A restaurant can have a wonderful recipe and still fail if staff cannot handle spoiled ingredients or a power outage. A trading strategy is similar. The entry idea is only one part of an operating system. A trading manual is the complete set of written instructions governing what may be traded, how a decision is checked, what risk is permitted, and how exceptions are handled. It should work when the regular operator is tired, uncertain or away from the screen. Begin with the actual legal trading product and account type. Include the symbol specification, contract unit, allowed hours and data source. Then write exact definitions of market context, entry, stop, management and exit. Finally, add emergency handling, recordkeeping, change control and review rules. A manual that describes only 'how to buy' is not a manual that can protect an account. It is an unfinished entry note.
2. Start every ticket with loss arithmetic
Imagine a fictional EURUSD long entered at Ask 1.08520 with a planned Bid stop at 1.08420. The difference is 10 pips. At an assumed $1-per-pip volume, the planned price loss is −$10 before fees or a worse fill. Your imaginary manual allows a maximum $12 total risk. If a separate commission allowance is $1 and additional slippage allowance is $2, the planned total under these assumptions is $13, which exceeds the cap. The trade is SKIP or requires a permitted smaller volume. A later executable Bid at 1.08670 would provide +15 pips gross in a different hypothetical outcome. That potential gain does not override the failed cash-risk gate. Include this calculation in the manual with input fields and units, not just a formula.
3. Build the manual from six operating chapters
Chapter one covers mandate and product permissions: what you study and which account may be used. Chapter two defines chart data and timeframes, including the first moment a signal can be known. Chapter three states entry, stop, exit, spread, session and event filters. Chapter four sets account cash-risk limits, combined exposure, daily loss ceilings and no-trade conditions. Chapter five describes execution steps and emergencies, including rejected stops or connectivity loss. Chapter six explains the journal, independent review and rule-version process. Each chapter should contain concrete examples of an acceptable and unacceptable action. Avoid a rule such as 'enter if momentum feels strong'. A competent reviewer needs a precise observation, such as a completed M15 close above a level marked from specified prior bars. The numerical threshold belongs in the strategy-specific manual and must be tested, not invented for marketing.
4. Emergency procedures must not depend on guessing
Suppose the demo terminal freezes just after you submit an order. You do not know whether it filled. Submitting the same order repeatedly could create multiple open positions. Your manual must direct the operator to check the broker's verified order and position records through an independent channel if available. It should list the official support method, required account verification and safe escalation sequence. Do not publish passwords or private credentials inside the manual. Another incident might involve a protective stop rejected because of a symbol rule. In that case, your account is exposed without the protection the strategy assumed. The manual needs a clear halt-and-escalate procedure, with the precise response confirmed for the actual broker and account before any live use. Emergency instructions are not promises that a market order will fill at a preferred price. Document unresolved risks honestly.
5. One version means one fixed collection of rules
Version control means keeping dated, identifiable copies of a document so later changes do not rewrite the past. Give the first draft a version such as 1.0 and record who approved it and when. A proposed change to the spread cap, entry trigger or stop logic becomes a new version. Preserve the old version alongside its historical test and journal. Do not apply version 1.1 silently to trades collected under version 1.0. A change log should identify the reason, the evidence supporting the change, its effect on execution or risk, and the testing required before release. Some changes repair a safety problem and should halt the old process immediately. Others are speculative improvements that need fresh development and independent evaluation. The documented approval process is itself a risk control.
6. Run an independent operator flight check
Hand the manual to a reviewer who has not seen your last successful trade. Give them five imaginary scenarios: a valid completed-candle setup; a quote above the permitted entry ceiling; a stop requiring excessive cash risk; a broker-rejected order; and a platform outage with uncertain fill status. Ask the reviewer to mark TRADE, WAIT, SKIP or HALT and state the exact rule. If they cannot classify a case consistently, the manual needs clearer wording. Check that they can calculate an entry-to-stop loss, locate the correct contract multiplier and identify who may approve a restarted system after an incident. Save their notes and every unresolved issue. A credible manual does not guarantee that a strategy will earn money. It proves that operations, risk decisions and evidence are defined before uncertainty arrives. Continue refining it only through documented versions and review.
Common mistake
A trader keeps a polished entry checklist but has no procedure when the stop order is rejected. The missing exception leaves the account exposed at the worst time. Fix this by adding halt, verification and escalation instructions before live deployment.
Plain-English glossary
- Trading manual: the full written operating procedure, not just an entry pattern.
- Version control: preservation of dated document changes.
- Change log: record of what changed, why and who approved it.
- Emergency escalation: defined action when a critical operating control fails.
- Risk cap: predeclared ceiling on planned account exposure.
Try it yourself
Create a six-chapter trading manual with version and approval fields. Ask an independent reviewer to classify five hidden-future trading and outage cases. Save the reviewer answers, risk calculations, conflicts and a proposed change log.
What you can now do
- Explain the operating requirement and its failure mode.
- Recompute the relevant cash-risk calculation and state assumptions.
- Preserve an independent, evidence-based decision or review record.
Next lesson
CP07.4 · Reviewing a Bad Day (Incident Review). Learn to diagnose a process failure without rewriting history.
