NQ · LIVE ENGINE Algomyth
Getting started

How to Keep a Trading Journal for an Automated System

OCT 25, 2026 · 9 MIN READ

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?

Plenty. Automation removes your discretion over execution. It does not remove your discretion over everything around it: whether the system runs today, how many contracts it trades, which funded account it sits on, and whether you can stomach the current drawdown. Those decisions determine your result, and they are exactly the ones a journal exists to catch.

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.

Turning the system off during a normal losing streak is a decision. Adding a second contract after a good month is a decision. Moving to a larger funded account is a decision. Ignoring a consistency rule until it closes your account is, by omission, also a decision. None of these show up in the strategy's trade log, because the strategy did not make them. You did. A journal is the only place they get recorded, and the only place you can later see whether they helped or hurt.

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.
  • Sizing. How many contracts, on which account, and at which of the three published levels. The Algomyth engine figures quoted for a $50,000 account are the Medium level. Anything beyond that is a choice you made, and it should be written down as one.
  • Account state. Which funded account is live, how close it sits to its trailing drawdown limit, how many trading days it has, and where it stands against payout thresholds.
  • 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
AccountWhich funded account, and its sizeTies results to the right rules
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

Notice what is not there: no entry price, no exit price, no chart screenshot. The platform already stores all of that, and NinjaTrader 8's trade performance reports reproduce it on demand. Copying it by hand adds nothing. Your journal records the layer above the trades, the layer the software does not track.

Log your prop-firm state, not just your profit

If you trade funded capital, the single most useful column is the distance between your account balance and its trailing drawdown line. A funded account does not close because you lost money overall. It closes the instant it touches that line, even on the way down from a high, and even if the strategy would have recovered. Writing down that distance every day turns an invisible cliff into a number you can see coming.

Record the boring administrative state too: minimum trading days, consistency-rule status, and how far you are from a payout threshold. These sit between a profit on the screen and money in your bank account, and are easy to forget until one blocks a withdrawal. The mechanics are in funded account rules explained and how trailing drawdown works.

See the numbers your journal measures against

The published backtest is the benchmark your own results should sit beside. Read it in full, then keep your live journal next to it.

Write down your drawdown tolerance before you need it

This is the entry that saves accounts. Before you fund anything, decide the size of drawdown you are willing to sit through without switching the system off, and write it down with the date. The Algomyth engine backtest shows a worst drawdown of $5,273 on a mid-size account, in simulation. Sitting through that on paper is easy. Sitting through it with your own money is different, and the version of you inside the drawdown will be tempted to call it "different this time".

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.

Hypothetical performance. The $5,273 drawdown and any other figure here comes from a backtest of the Algomyth engine over historical data, not a live account. Simulated results carry no financial risk and cannot fully reflect real execution. Past performance, real or simulated, does not guarantee future results.

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

Do I really need a journal if the system is fully automated?

Yes, but not the kind a discretionary trader keeps. Full automation removes your discretion over entries and exits, so logging those adds nothing the platform does not already store. What it does not remove is your control over whether the system runs, how large it trades, which funded account it sits on, and whether you hold through a drawdown. Those decisions are yours, they are not in the strategy's trade log, and a journal is the only place they get recorded and reviewed.

What is the single most important thing to record?

The distance between your funded account balance and its trailing drawdown line, recorded at the end of each day. A funded account closes the moment it touches that line, so watching the gap shrink is your earliest warning before a rule ends the account. If you keep only one column, keep that one, with your contract size beside it so the numbers stay comparable.

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.

In short: automating a system moves the journal's job. It is no longer about entries and exits, which the platform records for you, but about the decisions the software cannot make: when to run or pause, how many contracts to trade, which funded account is live and how close it sits to its drawdown line, and the drawdown tolerance you set before you needed it. Keep it lean, review it weekly, and measure your live results against the backtest rather than against your hopes.
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."

Watch the engine, not the promises

Everything we write comes back to one idea: verify, then decide. The live terminal exists for exactly that.

Unlock Algomyth Live