The journal that actually improves you: Risk Management

Why this matters

A journal is only useful if it records what can be changed. Direction and outcome are noise, setup quality, size discipline and rule adherence are the levers.

Without a journal the sample is memory, and memory keeps the wins and drops the leaks. Expectancy computed off memory is always flattering.

The point is not documentation, it is the weekly review that turns records into one concrete change.

What to log per trade

Log the R multiple, the setup name, the planned stop, the actual stop, the size and a state word.

Violations are binary fields: size discipline, stop moved, plan followed. Binary beats commentary because it is countable.

Two lines per trade is enough. The journal is an evidence file, not a diary.

Metrics that matter and their bars

Rule adherence, target above 95% of trades, ranked ahead of any strategy work. Size discipline violations, target under 5%.

Expectancy per trade, target above zero overall and positive per live setup. Average R, tracked to compare setups against each other rather than as an absolute target.

Skip rate, tracked to confirm the ratio floor is genuinely enforced, and breaker activations, tracked as success. Four bars and three counters is enough; more fields quickly turn filling into a chore.

Turning violations into money

Every violation gets a money cost: a moved stop costs the pips it added, an oversized trade the extra risk money.

The costs rank the leaks. The highest cost leak is the week's single fix, which turns behaviour into an arithmetic problem rather than a resolve problem.

A violation that costs nothing still gets logged, because the count matters even when the money is small.

The weekly review agenda

Thirty minutes, six slots. Minutes zero to five total trades and total R plus the max loss streak. Five to fifteen group by setup and compute expectancy and average R per group.

Fifteen to twenty count the binary violations and convert each into money. Twenty to twenty five identify the highest cost leak and decide its fix.

Twenty five to thirty rest any setup negative over twenty trades and choose the one change. Write the change as an action with a number, for example zero moved stops.

Sample sizes and resting rules

Twenty trades is the resting threshold, because below that expectancy is too noisy to judge. At two trades a day that is about two weeks per setup.

Do not rest a setup on five trades however ugly, unless violations rather than the edge caused the loss. A rest removes the setup from the list for a full week, then returns it at base size.

Two rests in a row on the same setup means retirement. Record the reason for every rest so the decision is auditable.

One change per week

Check last week's change first and record whether it fired and whether it helped.

The week's change is one item applied to the weakest live setup, written with a number so success is measurable.

One improvement per week keeps the table moving up rather than churning, and keeps the review to thirty minutes.

Why it pays

The journal is the only place a hit rate, an expectancy and a violation count can exist at the same time, which is what makes the fix arithmetic instead of opinion.

It also proves the process to the person running it on a red week, when the balance is least convincing.

Keeping the records is the difference between resting a setup and abandoning it, and between a leak and a fix.

Worked example

$100,000 account, 0.5% base risk, one month of 20 trading days, 3 trades a day. Metrics come from the journal columns.

Trades in the month	60
Base risk money per trade	$500
Expectancy needed to clear 2% a month at that size	3.00%
Money cost of 3 stop violations at 0.4% extra	$1,200
Size discipline bar, violations allowed in 60 trades	3
Longest losing streak to expect at 40% wins	36.0
Journal minutes per day at one minute per close	3
Weekly review minutes once a week	30

A 0.1R edge on 60 trades at 0.5% risk is 3% a month. The journal is what proves the edge and catches the leaks.

Common mistakes

Logging only winners	The wins are already remembered. Logging them twice hides the leaks that actually cost money. A 0.2% size violation per trade over 60 trades is 12% of equity hidden.
Recording commentary instead of fields	Paragraphs are hard to aggregate. Binary columns and numbers group cleanly and settle arguments. Five prose rows take 3 times longer to sort than 5 binary rows.
Changing five things at once	Nothing is isolated, so the review cannot attribute the result to anything and the next month is guesswork. Five changes at once means none of them can be proven in a 20 trade sample.
Skipping the review	A journal without a weekly sort is a diary. The sort is where the improvement happens. Thirty minutes a week is the whole cost, and it converts leaks into money numbers.

Checklist

Fill the row within a minute of every close.
Log setup, size, stop placement and three binary adherence columns.
One word on state, no essay.
Weekly: group by setup and compute expectancy and average R.
Convert every rule violation into money.
Rest any setup negative over 20 trades.
Choose exactly one change for the next week.

Key terms

expectancy: Average result per trade, the number the review sorts on.
adherence: How often a written rule was actually followed.
sample: A group of trades large enough to judge, around 20.
average R: Mean result in risk units across a set of trades.

Trading involves risk. Educational only, not advice. Mark it complete to bank progress.

The journal that actually improves you