NQ · LIVE ENGINE Algomyth
Foundations

How to Keep a Trading Journal for an Automated System

A trading journal for an automated system logs what the bot cannot: when to run or pause it, the sizing, and the drawdown you can tolerate.

Published 5 min read By the Algomyth desk

Illustration for the Algomyth guide on journaling an automated system

The most common reason people skip a trading journal once they automate is that their system trades itself. The bot placed the order, set the stop and the target, and closed the position, all without a decision from you. So what is left to write down?

Why journal something that trades itself?

A discretionary trader journals to improve entries and exits. You have handed those to the software, which is the whole point of automated trading, so that reason is gone. But a new set of decisions replaces it, each higher-stakes, because it affects every future trade rather than a single one.

The one thing to remember

An automated system removes your discretion over execution, not your judgment over operation. The journal is no longer about entries and exits. It is about the run, pause, size and account decisions the software will never make for you.

The decisions the bot does not make

Before you decide what to log, be clear on what you are still responsible for. Four things, and all of them are yours alone.

  • Run or pause. Whether the system trades on a given day, and why. This is where most self-inflicted damage happens: switching off during a drawdown and missing the recovery.
  • Tolerance. The drawdown you decided in advance you could sit through, recorded before the drawdown arrives, so the panicked version of you cannot quietly rewrite it.

What to actually log

Keep it short enough that you will actually do it. A journal you abandon after two weeks is worse than a lean one you keep for a year. Here is a working set of columns.

FieldWhat goes in itWhy it matters later
DateThe trading dayAnchors everything else
Ran?Yes or no, and why if noCatches the pause-during-drawdown mistake
ContractsSize traded that dayMakes every result figure comparable
ResultThe day's net, from the platformYour real curve, not the backtest
BalanceEnd-of-day, and distance to the drawdown lineEarly warning before a rule triggers
NoteOne sentence, only if something happenedContext you will not remember in a month

Write down your drawdown tolerance before you need it

A written tolerance, set in a calm moment, is the thing you check against when that temptation arrives. If your live drawdown is inside the range you already accepted, the journal tells you to do nothing, which is usually the correct and hardest action. This is the same discipline described in the most common automation mistakes, where turning the system off at the bottom of a normal drawdown is the recurring one. It is worth settling before you fund, which is what getting started walks you through.

A weekly review beats a per-trade one

Discretionary traders review trade by trade because each trade contained a decision. Yours did not. So review by the week instead, and ask operational questions: did I run the system every day I intended to? Did I change size, and why? How did my live week compare to the backtest's average? Am I drifting toward any account rule?

Once a month, zoom out. Compare your running results against the backtest, not to see whether you are "beating" it, but to check you are in the same universe. A live stretch that looks nothing like the simulation is a signal to investigate, not to add contracts.

A simple template you can copy

You do not need software. A spreadsheet with the columns above, one row per trading day, is enough for a single account. If you run several accounts, give each its own tab, because their drawdown lines and trading-day counts move independently, and blending them hides exactly the number you most need to watch.

Add three fixed cells at the top that you set once: your maximum acceptable drawdown, your planned contract size, and the rule that would make you pause the system. Everything below is a daily record; everything above is the plan it is measured against. When the two disagree, the plan wins, because you wrote it when you were thinking clearly.

Frequently asked questions

How often should I review it?

Weekly for operations, monthly for the bigger picture. A weekly review checks whether you ran the system as planned, whether you changed size, and how your results compare to the backtest average. A monthly review checks that your live curve is still in the same universe as the simulation. Reviewing trade by trade is a habit from discretionary trading that does not fit an automated system, because the individual trades did not contain your decisions.

Should I copy every trade's entry and exit into the journal?

No. NinjaTrader 8 already stores every fill, price and timestamp, and its trade performance reports reproduce them whenever you want. Duplicating that by hand wastes the time you need for the entries that matter, which are the operational ones. Let the platform keep the trade record, and let your journal keep the record of your own decisions around it.

Can a journal stop me from making automation mistakes?

It cannot stop you, but it makes the mistakes visible while they are still small. Writing down your drawdown tolerance in advance gives you something to check against when you are tempted to switch the system off at the bottom of a normal losing stretch. Recording every pause forces you to give a reason, and a weak reason is easier to notice on paper than in your head. The judgment stays yours; the journal just keeps you honest about it.

Sources and further reading
  • NinjaTrader 8 documentation, "Trade Performance" reports and account data.
  • CFTC, "Customer Advisory: Be Cautious of Trading Systems and Robots."
  • Brett N. Steenbarger, "The Daily Trading Coach."

Educational content, not investment advice. Trading futures involves substantial risk of loss and is not suitable for every investor. Any reference to Algomyth results is hypothetical, simulated over historical data, and shown in full on the performance page; past performance does not guarantee future results.

Algomyth Live

Take the seat: watch the engines live

Three specialist engines on Nasdaq, S&P and Gold, every signal streamed the moment it happens, with the stop and the target written before the trade. From $149 a month per market.