The Five-Field Trading Journal: What to Log When You Hate Journaling

The Form Is the Problem, Not Your Discipline

Open any popular journaling template and count the fields. Twenty is common. Setup name, confluence checklist, market context, session, news events, pre-trade emotion, post-trade emotion, confidence rating, screenshot before, screenshot after, mistakes made, lessons learned, grade out of ten. Half of them are free text. Filling one in honestly takes three or four minutes, which on ten trades a week is most of an hour spent producing a document nobody opens.

People who quit that are not lazy. They ran a cost-benefit calculation and got the right answer. A field that no decision depends on is pure cost, and a form made mostly of those fields is a tax on trading dressed up as professionalism. The usual response - build the habit, be consistent, the pros all do it - puts the burden on the trader when it belongs on the form.

And There Is No Study to Wave at You

The second concession is one this series has made in every post and will not stop making: there is no credible research showing that journaling improves returns by some percentage. Anyone quoting you a figure invented it. A log does not create an edge, it does not enforce a rule, and it will not stop you re-entering something the record already told you to drop.

Which means every field has to pay for itself individually. There is no blanket argument from professionalism available here, and if a field cannot survive the test in the next section it should be deleted rather than defended.

The Test a Field Has to Pass

A field earns its place if it passes both halves of one test.

First, name the decision. Not the insight - the decision. What would you do differently depending on this field's value? If the honest answer is "I would notice something," it fails. Noticing is what a chart is for.

Second, name the number it feeds. The field has to survive aggregation across a hundred trades and come out as something comparable. This is where most of the template dies. A paragraph about what you were thinking cannot be averaged, sorted, or grouped. It is readable exactly once, by you, and only if you go looking for it.

Five fields pass both halves. The rest of this post is what they are, what to do with everything else, and what the whole thing actually costs.

The Four That Make Results Analysable

These four are the ones the first post in this series arrived at, restated here as a checklist rather than an argument.

The split that matters: the last two come free from a broker import on supported platforms, and the first two do not, because your broker never knew either of them. That asymmetry is the whole subject of the second post in this series. It is also good news for the reader this post is written for: two of the four cost you nothing.

The Fifth Field: How Far It Went Against You

Those four describe the endpoints of a trade. They say where it started, where it finished, and what you had at stake. They say nothing at all about the path in between, and two trades with identical endpoints can have completely different paths - one that moved immediately in your favour, and one that ran to within a hair of the stop before turning around.

The fifth field is the worst excursion: the largest unrealised loss the position showed before it closed, expressed as a fraction of your planned risk. In the literature it is maximum adverse excursion, and it is the cheapest useful thing you can know about the path.

It passes the test twice over. The number it feeds is the average adverse excursion on winning trades, measured against your stop distance. The decision it changes is where the stop goes and when you enter: if your winners routinely travel 0.8R or 0.9R against you before working, you are not winning because of your timing, you are winning despite it, and the same entries will eventually produce a run of stop-outs that a slightly later entry or a slightly wider stop would not have. If they rarely travel past 0.3R, your stop has more room than it needs and the risk budget is being spent on air.

For funded traders there is a second use, and it is the one that justifies the field on its own. A daily loss limit is tested against your equity path, not your closing balance. A week with four trades that each came within a fraction of the limit and then recovered looks completely clean in any record that stores only where trades ended. The excursion column is the only place that near miss exists.

Why That One and Not the Obvious Candidates

The honest reason the worst excursion wins the fifth slot is not that it is the most insightful field available. It is that it is the only high-value field with almost no marginal cost, because it is derivable. The adverse excursion is already sitting in the price history between your entry and your exit, so it can be computed from data you did not have to type. Every rival field has to come out of your head, in the moment, and that is the resource this post is trying to conserve.

The strongest rival deserves a fair hearing. A confidence rating at entry - a single number from one to five, recorded before the outcome - passes the test cleanly. It feeds expectancy per confidence bucket, and the decision it changes is a filter: if your low-confidence trades have negative expectancy over a real sample, you have found a rule worth adding. Two things keep it out of the five. It needs entry-time discipline on a field that is pure overhead at the busiest moment of the trade, and it needs a few hundred trades before the buckets separate from noise. It is an excellent sixth field, once the five have survived three months. If you run a single setup and attribution is already trivial for you, promote it above the strategy label and lose nothing.

The other candidates fail on the second half of the test rather than the first, which is worth being precise about - they are not worthless, they are unaggregatable.

Notice the pattern in the right-hand column. Almost every dropped field can be rescued by converting it from prose into a small fixed set of values chosen before the outcome. That is the general rule, and it is most of what separates a log that can correct you from one that agrees with you.

What It Actually Costs

Counting keystrokes rather than measuring anyone, because no measurement exists and an invented one would be worse than an estimate that says so.

The strategy label is a dropdown - one click, assuming the list is short. The planned risk is a number you have already worked out, because you cannot size a position without it; if you genuinely do not know what you are risking at the moment you enter, the problem the journal has uncovered is not a journaling problem. Entry, exit and result arrive from an import on supported platforms, or take twenty to thirty seconds if you type them. The worst excursion is computed rather than entered.

Call it around ten seconds of typing per trade on top of an import, or under a minute fully manual. At ten trades a week, that is a couple of minutes a week against the three or four minutes per trade the twenty-field template was asking for.

The seconds are not the real cost, though, and it is worth being straight about that. Two of the five have to be recorded at entry, which is the most attention-scarce moment in the whole trade. The fix is not willpower, it is placement: capture those two where the decision already happens - on the order ticket, in the same window, as part of sizing the trade - rather than in a separate app you open afterwards. A field recorded afterwards is a different field, and usually a worse one.

The Failure Mode That Actually Kills It

It is not the number of fields. It is the two habits that make a small log useless.

The first is backfilling. Reconstructing Monday's strategy label on Sunday evening produces a beautifully organised dataset in which every setup works and only your discipline failed, because memory reconstructs with the outcome already known. A losing trade quietly becomes one that was not really your setup; winners are admitted to whichever strategy you currently believe in. Two of these five fields are worthless unless they are recorded before you know how the trade ends.

The second is never querying it. A log that is written and not read is the hobby the sceptics described, and cutting it to five fields does not save it. So pair the form with exactly one recurring question, asked monthly, on a schedule. Something like: which strategy label has the worst expectancy over my last fifty trades, and is it still getting the same size? If the answer has never once changed what you did, stop logging. You will have run the experiment properly and earned the right to say the sceptics were correct about you.

When Five Is Still Too Many

Three cases where fewer is the right answer, stated plainly because a post arguing for a minimum should be able to name its own.

You genuinely run one strategy. One setup, one instrument class, one sizing rule, no discretionary overrides. The strategy label is a constant and carries no information, so drop it. Your minimum is planned risk plus whatever the import gives you - and the load-bearing field becomes the planned risk, because without it you have dollars instead of R and no way to compare a trade on a quiet day with a trade on a violent one.

You are under about twenty trades. Log them, because the record cannot be created retroactively, but compute nothing from them. Per-strategy numbers on a handful of trades are descriptions of what happened, not estimates of what will happen.

The logging is displacing the trading. If the record has become the ritual, cut to the five and then keep cutting. Our earlier post on whether you need a journal at all works through that decision properly, including a test you can run on a broker statement without adopting anything.

And if you will only ever maintain one field by hand, make it the planned risk at entry. It is unrecoverable after the fact, it is the denominator that turns every other number in the record into something comparable, and it is the field a broker statement can never give you.

What SignalDeck Does Here, and What It Does Not

All five fields exist on a trade. The strategy label is a picker applied when the trade is created, planned risk is the stop you enter, and R-multiples and expectancy are computed from it. Entry, exit and result arrive from a broker import where your platform is supported, and which platforms those are varies enough that our platform support guide is worth checking against your own setup rather than assuming.

The fifth field is the one worth explaining, because it is the claim this post leans on hardest. Adverse and favourable excursion are computed automatically when a trade is closed, from daily price bars covering the period between your entry and exit dates, and stored on the trade. You do not type them. They also appear as an R-normalised scatter of adverse against favourable excursion, which is the chart the entry-timing question above is actually asked from.

Four limits on that, all of which change how you should read the number:

• It is measured on daily bars. For a position held over several days that is close to right. For an intraday trade it is not: the day's high and low cover the whole session, including the hours before you entered and after you exited, so the figure is an upper bound on what your position actually experienced rather than a measurement of it.
• It needs a stop on the trade. The R-normalised view is computed from your planned risk, so a trade logged without one is excluded from that chart entirely - the fifth field depends on the second.
• Forex trades are excluded from that scatter. The excursion values are still computed and stored on the trade itself and visible on it, but they are skipped by the execution-quality view. If you trade FX, read them off the trade rather than expecting the chart.
• A failed price lookup is silent. If no data comes back for the symbol and period, the trade closes normally with the excursion fields left empty and no warning on the trade. An empty column means "not computed," not "no excursion."

One more constraint worth knowing before you plan a labelling scheme around this: the Free tier carries unlimited trades and basic R-value analytics but caps you at three strategies and ten tags, which bites exactly the trader this post is describing. Unlimited strategies and tags, along with SQN, Kelly and Monte Carlo, are Pro at $30/mo; MT4/MT5 live sync is Elite at $50/mo. Everything is unlocked at no cost during the beta.

Where the Series Ends Up

The objection this series opened with was that a balance already tells you whether you are making money and everything past that is procrastination. Four posts later the concession is larger than it looked: most of what people call journaling is procrastination, the emotional half is unfalsifiable as usually recorded, and no study exists to tell you otherwise.

What survives is small. Two fields your broker cannot know, two it hands you, and one a computer can work out from the price history. That is not a practice or a discipline. It is a form with five boxes, and it is the smallest thing that makes a claim about your own trading falsifiable.