Page 1 of 1

Writing Your System Manual: One Document That Holds Everything

Posted: Wed Oct 07, 2026 8:59 am
by Fairman
Writing Your System Manual: One Document That Holds Everything

When your trading plan lives only in your head, it changes with your mood. A system manual fixes it in writing, and becomes the reference you can follow under stress.

Structure it simply. Begin with purpose and constraints: your goals, time available, and capital. Next, markets and sessions: the pairs you trade and when. Then analysis: your process for determining bias, marking levels, and checking the calendar.

Then the strategy section. For each setup, give the name, conditions, entry trigger, stop, targets, management, and skip conditions. Include a screenshot example or two.

Add the risk section: risk per trade, maximum open risk, daily and weekly limits, correlation rules, and the graduated return plan after drawdowns.

Add operations: the pre-session checklist, the pre-trade checklist, the post-trade routine, and the review schedule. Include the journal fields and the metrics you track.

Add contingencies: the platform outage plan, the losing-streak protocol, and break conditions.

Finally, include a change log. Record every change to the manual, with the date and the reason, so that you can see how the system evolves, and avoid impulsive modifications.

Keep it short enough to read in twenty minutes, perhaps five to ten pages.

Review the manual quarterly, and update based on data.

Practical step: start the manual with three sections today: markets, risk rules, and the pre-trade checklist.

Re: Writing Your System Manual: One Document That Holds Everything

Posted: Wed Oct 07, 2026 9:25 am
by Fairman
The change log is the best part. Seeing changed stop rule after three losses written down with a date makes impulsive tweaks a lot more obvious. Each entry should have the date, the rule before, the rule after, the reason, and the number of trades the old rule had. That last field is the one that keeps you honest. If you're changing a rule after 12 trades, the log shows it plainly. I also add a review date a couple of months later to check whether the change helped. Many changes made in frustration turn out to make no difference, and some get reversed, which is useful to see before the next impulse arrives.

Re: Writing Your System Manual: One Document That Holds Everything

Posted: Wed Oct 07, 2026 9:57 am
by Fairman
Keep the screenshots in the manual of both a good example and a borderline one you'd skip. The borderline examples are where most rule confusion lives. A textbook setup is easy to recognise. The hard cases are a pullback that went slightly past the zone, a trigger candle that's a bit small, or a setup forming 20 minutes before US data at 1:30pm Lagos. Write a line under each borderline screenshot saying skip or take, and why. Over time this becomes the most useful part of the manual, because it records decisions about the grey areas that would otherwise be made differently every time depending on mood.