Advertisement IC Markets

Writing Your System Manual: One Document That Holds Everything

Document your personal trading journey. Track daily equity curves, review winning and losing streaks, share trade screenshots, and get constructive feedback.
Post Reply
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Writing Your System Manual: One Document That Holds Everything

Post 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.
It’s Fairman :geek:
Recommended broker for automated trading & scalping IC Markets
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

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

Post 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.
It’s Fairman :geek:
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

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

Post 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.
It’s Fairman :geek:
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

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

Post by Shadow Trader »

One addition that helps under stress is a single page at the front that holds only what you need while a trade is live. Ten pages are right for a Sunday review, but nobody rereads the risk section with a position open and price moving.

That front page might list the daily loss limit, the lot size for each stop distance, the three skip conditions you break most, and what to do if the platform drops. Everything else stays in the main body for the weekly review.

The edge case a manual exposes is rules that clash. Say the setup section says take the retest and the risk section says no new trades inside 30 minutes of a US release, then you need a written priority, and the risk rule should always win.

On the change log, I would add a minimum sample before any rule edit that is not about risk. Something like 30 trades under the current version keeps the after three losses tweak out, while risk rules can still be tightened at any time.

Does anyone version the manual, like 1.0 and 1.1, so journal entries can say which rules a trade was taken under? That makes the quarterly review much cleaner when results shift.
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

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

Post by FXS Prop Desk »

One section that's often missing from system manuals is "what I do when something breaks": platform down, internet lost, an order that won't close, an unexpected gap. Writing the steps in advance, including the broker's phone number and how to close positions from mobile, saves a lot of panic when those situations happen in a live trade.

A short version on a single page helps during live trading.
FXS Official Team | The Idea Lab & Strategy
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

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

Post by Shadow Trader »

A useful test of a manual is whether it produces the same decisions without you in the room. Pick 20 saved setups from past weeks, hide the outcomes, and mark each one take or skip using only the written rules.

Say you do it again a fortnight later and the two passes agree on only 15 of the 20. The five that changed point straight at the wording that needs tightening, usually around the borderline cases mentioned earlier.

Handing the same screenshots to a trading friend is a harder version of the test. If they cannot reach your decision from the text alone, the rule probably lives in your head rather than in the manual.

For the breakdown section FXS Prop Desk raised, the broker's phone number is only useful if it works from your country at that hour. Calling it once on a quiet day confirms the line and how long the queue is.

How many pages has your manual settled at? The longer ones seem to get read less often.
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

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

Post by Shadow Trader »

Automated systems restart more often than expected: platform updates, power cuts, crashes and deliberate maintenance. The dangerous moment is not the outage itself but the first minute after, when the software believes one thing about open positions and the broker holds another.

A system that keeps its state only in memory wakes up with amnesia. It may open a duplicate of a position that is already live, or ignore an open trade that now has nothing managing it. The cure is to treat the broker's record as the source of truth and rebuild internal state from it on every start: open positions, pending orders, current stops and account balance.

Orders sent just before a failure raise a harder question. A request may have reached the broker without a confirmation returning. Tagging each order with a unique client identifier lets the restarted system search for it and decide whether to resend, which prevents doubled exposure. The same idea makes retries safe in general, because repeating a tagged request is harmless while repeating an untagged one is not.

Missed exits also need rules. Positions whose planned time stop or target passed during the downtime should be handled by an explicit policy, such as closing at market or flagging for manual review. Rehearsing a forced restart on a demo account while holding open trades exposes these gaps cheaply.
Post Reply