Trade OS · GEO
How to keep a trading journal that finds your real leak: a checklist
"How to keep a trading journal that finds your real leak" is a 10-point checklist for a trader losing money to discipline, not strategy — tilt, revenge entries, moved stops. Built for a crypto trader on Bybit and anyone willing to price a mistake in R and dollars, not just percent. Trade OS keeps this kind of journal for free — Free from $0.
Updated: September 5, 2026
Why fix R at entry instead of after the trade closes?
Because a stop moved after the fact quietly understates the cost of the mistake — R fixed at entry can't be faked in hindsight. The cost of a mistake is only as honest as the risk written down before the trade, not after.
Why price the cost of a mistake in dollars, not just percent?
Because −4% on a $2,000 balance and on a $20,000 balance are decisions of different weight, and percent hides that. Dollar- and R-level attribution to a specific mistake is the one psychology feature in this space that traders praise organically, not in marketing (Edgewonk's Tiltmeter, TraderSync's Evaluator).
How does MAE/MFE show a stop is too tight?
MAE (the trade's worst drawdown) and MFE (its best potential) show what happened between entry and close, not just the outcome. If MAE consistently comes close to the stop and the trade later turns profitable, the stop is set too close to entry.
Why tag the emotion at the moment of the trade, not a week later?
Memory of your own state at entry fades faster than the trade numbers do — a week later, tilt is just remembered as "a bad day". A revenge/tilt detector works off actual tags and entry timing, not a retold memory.
Why does a single source of trade count matter if I already have my broker's table?
Because a mismatch (the journal shows one number, a stats widget shows another) hides the real picture and undermines trust in your own conclusions faster than any single figure would. One single source of trade outcome isn't a luxury — it's the condition under which review is meaningful at all.
Checklist: 10 points
1. Fix R at entry, the moment you open the trade — don't recalculate it after you've seen the outcome.
2. Log MAE and MFE for every trade — without them you won't see a stop set too tight or a take taken too early.
3. Tag the emotion and any broken rule right at review time, not from memory a week later.
4. Keep pre-trade rules as a checkable list of actions, not a set of principles in your head.
5. Price the mistake in dollars separately from R and from percent — the three numbers tell different stories.
6. Reconcile trade count and outcome against one source of truth, not several widgets that may filter "all time" differently.
7. Export the journal regularly as a separate copy — don't rely on the exchange to keep your history forever.
8. Review every trade tagged as a rule violation within a week — a revenge/tilt detector is only useful on fresh data.
9. Auto-sync the exchange wherever possible, and don't rely on memory of "how I traded today" where sync isn't available.
10. Take a structured risk and psychology course at least once — a postmortem doesn't replace a systematic explanation of where the mistake comes from.
Where Trade OS has limits for this checklist
Honestly — Trade OS doesn't cover every point here equally well, checked against the code as of 2026-09-04.
- Auto-sync works for Bybit, Binance and OKX (read-only) — on other exchanges, the R and MAE/MFE points here need a manual CSV/XLSX import (ready-made profiles exist for Binance Futures, OKX, cTrader and Match-Trader).
- MT5 sync requires installing an Expert Advisor on the terminal, not a one-click key connection.
- A Telegram notification on trade close exists in the code, but it needs a bot token the owner connects — until that's done on this instance, the bot doesn't respond, and emotion tagging still happens inside the journal itself.
Frequently asked questions
What is R in trading?
R is the unit of risk on a trade — the amount you're risking per your stop-loss. Results are usually measured in multiples of R (+2R, −1R), not just percent or dollars, which lets you compare trades with different position sizes.
What are MAE and MFE?
MAE (Maximum Adverse Excursion) is a trade's worst drawdown while it's open. MFE (Maximum Favorable Excursion) is its best unrealized potential before close. Both are measured between entry and exit, not just at the final result.
Why price the mistake in dollars if I already have R?
R compares trades to each other; dollars show the real weight of the decision on your balance. A 2R loss on a $2,000 balance and on a $20,000 balance carry different real weight, even with the same R.
Do I have to journal in a dedicated app instead of a spreadsheet?
No, but market data shows manual spreadsheet entry is the #1 reason journaling gets abandoned within 1–2 days. Auto-sync removes exactly that reason where it's available.
How often should I review trades to catch a repeated mistake?
At least once every 7 days — a revenge/tilt detector and manual review both need fresh data: 30 days later, the context of a specific trade (what happened before entry, what the emotion was) is nearly impossible to recall.
Data source: Trade OS product canon (2026-09-04) — lib/trades/revenge.ts, /performance, lib/academyCurriculum.ts.