Trade journaling

What makes a trading journal useful? Write the plan down before the trade.

Entry, exit and P&L tell you what happened. They don't tell you which of your habits keeps costing you money. For that, the journal needs one thing most journals skip: a record made before the outcome was known.

Traders keep a journal to find repeating mistakes: revenge trades, moved stops, late entries, ignored levels, broken setup rules, overtrading, sloppy risk.

So they add mistake tags and review them at the weekend, but patterns rarely emerge. The problem isn't the tags; it's what they're checked against.

This guide shows how to make mistake tracking measurable instead of opinion-based, with a worked example and a five-step routine for your next trade.

Prefer to watch? See a 2-minute review of one trade in Krino

The problem: tagging after the fact

A mistake is a gap between what you meant to do and what you did. If "what you meant to do" only exists in your head, every review compares the trade against a memory, and that memory has already seen the outcome.

A moved stop becomes "giving it room" if the trade recovers and "bad luck" if it doesn't. The same action gets tagged by its outcome.

Key takeaway

A mistake tag is only as trustworthy as the plan it's checked against. If the plan was written after the entry, or edited since, the tag measures hindsight, not discipline.

Every common mistake is a measurable gap

Once the plan exists before the order, most mistakes stop being judgment calls. Each is a difference between two recorded facts:

MistakeWrite down before entryCheck after the trade
Entering latePlanned entry priceFill vs. planned entry, in R
Moving stopsPlanned stopFinal stop vs. planned stop; was the loss bigger than 1R?
Ignoring key levelsThe levels the plan is built onDid entry and stop respect them?
Breaking a setup ruleThe rules that must be trueWas the trade taken with a rule unmet?
Revenge tradeTime the plan was madePlan made minutes after a stop-out, or no plan at all
OvertradingDaily trade cap or risk budgetTrades without a plan; budget exceeded
Poor risk managementPlanned money at risk (1R)Realized loss in R

R is the amount you planned to risk on the trade. Measuring every deviation in R makes a late entry on a $20 stock and on a $600 stock comparable.

Worked example: one trade, two mistakes

The plan, written before the order:

Entry612.00
Stop-loss595.00
Take-profit650.00
Quantity8 shares
Risk per share (612 − 595)17.00
Planned risk, 1R (17 × 8)136.00

What actually happened:

  • Situation: the price ran before the order went in. The trader chased and filled at 618.
  • Decision: the price then dipped toward 600. To "give it room", the stop was moved from 595 to 588.
  • Outcome: stopped out at 588. Loss: (618 − 588) × 8 = 240.

Against the written plan, the review needs no interpretation:

Late entry (618 − 612) / 17+0.35R worse
Moved stop (595 → 588)Yes
Realized loss 240 / 1361.76R

Without the plan, the journal says "−240, stopped out". With it, the trade has two priced tags: the loss was 1R by design and 0.76R by behaviour.

Try it on your last trade

What did your behaviour cost, in R?

The plan, before the order
What actually happened
1R planned136
Late entry+0.35R
Result−1.76R
Cost of behaviour0.76R

See how Krino records the plan side → Opens the live demo with sample trades. Nothing to install.

Four ways to keep a journal

ApproachHindsight-proofFinds patternsMeasures the costEffort
Notes after the tradeNoHardNoLow
Mistake tags after the tradeNoYesRarelyLow
Plan written before, editable laterPartlyYesPartlyMedium
Plan locked before entry, compared afterYesYesYes, in RMedium

"Editable later" is the trap: a plan you can quietly adjust after entry ends up agreeing with whatever you did.

Common journaling mistakes

  • Reviewing only losers. A winning trade with a moved stop is still a moved stop. Review every trade against its plan, whatever the outcome.
  • Editing the plan after entry. It erases the very gap you're trying to measure. Change the plan by recording a new version, and keep the old one.
  • Too many tags. Thirty tags spread the data too thin. Start with the seven above.
  • Counting tags instead of costing them. "Moved stop × 6" matters less than "moved stops cost 4.1R this quarter".
  • Free text only. Paragraphs are hard to search. Put numbers in fields, and keep notes for the why.

A five-step routine you can start tomorrow

  1. Plan before the order. Entry, stop, target, size, the one-line reason, and the rules that must be true.
  2. Timestamp it and freeze it. Any change becomes a new, dated version. Nothing gets overwritten.
  3. Record fills against the plan. Every buy and sell is linked to the plan it executes.
  4. Derive the mistakes from the gap. Use the mistake map above, and express each deviation in R.
  5. Review weekly. Rank the tags by total R lost, and pick one habit to fix next week.

What this looks like in Krino

Krino is built around steps 1 and 2: a plan made, checked and timestamped before you act. The video shows one trade's week reviewed against its plan.

Watch · 2:05

One week of one trade, reviewed against its plan

A CRM plan is written before the open: entry 250, stop 241, 20 shares, 180 at risk. The review then checks the week against it, one screen at a time.

  • Entered lateFilled at 254.60, 4.60 above the plan.
  • Moved the stopA new plan, dated after the fill, widened it from 241 to 236.
  • Revenge tradeA bigger position 29 minutes after the stop-out, with no plan behind it.
  • Poor riskThe planned trade lost 372: 2.1× the 180 the plan allowed.

Illustrative prices on a staged week. The mistake captions are added for the video and read off the screens.

You just watched the review. Now click through it yourself.

The demo has the plan, the checklist, the revision history and Decision Compare from this article, with sample data. It opens in your browser — no signup, no email, no card.

The same routine, screen by screen:

The plan, with its timestamp

Decision Readiness shows the plan your rules produced: entry, stop, target, quantity, R:R and expected P/L. It's stamped with the time it was made, along with the risk budget it uses and the entry and sizing strategy applied.

Krino Decision Readiness screen for META, timestamped Sep 29, 2026 05:08 AM, showing the rules' Buy verdict, decision gates, and a Trade Snapshot with entry 612, stop loss 595, take profit 650, quantity 8, R:R 2.24 and expected P&L 304.
Krino.io — the plan exists, with its numbers and timestamp, before any order does.

Your rules, confirmed before execution

The Pre-Trade Checklist asks you to confirm capital, stop-loss, size and the risk boundary before the plan can move to execution. It turns "breaking a setup rule" into a recorded yes or no.

Krino Pre-Trade Checklist with confirmations for available capital (10,000), stop-loss (595), position size (8) and accepting the risk constraints (allowed loss 1,200).
Krino.io — the checklist records which rules you confirmed, and when.

Plans aren't edited, they're versioned

Every decision is stored as an append-only history. Re-evaluating a plan adds a new revision. The earlier one stays in the Decision Register's revision history, read-only. Once a plan is accepted, its entry and sizing strategy are locked.

Krino Decision Register listing decisions with status, lifecycle, unrealized P&L, planned versus live reward-risk, and a Revision History link on each decision.
Krino.io — every decision, its timestamp, and its full revision history.

See exactly what moved

Decision Compare sets any later snapshot against the original plan. Entry, stop, target, size and confidence are each marked as changed or unchanged. A moved stop shows up here as a number, not a memory.

Krino Decision Compare showing a later snapshot drawn against the baseline plan: entry moved from 612.00 to 607.50, stop, target, confidence and size unchanged, with plan drift, risk pressure and signal instability bars.
Krino.io — drift against the baseline plan, level by level.

Krino doesn't tag your mistakes for you. It keeps the record made before the trade, so the tags you add, in Krino or elsewhere, are checked against something that can't change afterwards.

Quick start checklist

  • Write entry, stop, target and size before placing the order.
  • Note the time the plan was made.
  • Write the one rule that must be true for the trade to exist.
  • Never edit a live plan. Save a new version instead.
  • After the trade, record the fill and the final stop.
  • Express every deviation in R.
  • Tag with at most the seven mistakes above.
  • Each week, find the tag that cost the most R and work on that one.

The question that actually matters

Not "what mistakes did I make?" Asked after the outcome, that question gets answered by the outcome.

The better question: "Where did I depart from what I wrote down beforehand, and what did it cost in R?"

Start with your next trade: write the plan before the order, freeze it, compare afterwards. A few weeks of that shows your patterns more clearly than a year of after-the-fact tags.

Start with your next trade.

Plan it in the demo first: your entry and stop, Krino works out the size and keeps a timestamped record. No signup needed.

Krino executes rules and risk limits you configure. It is not personalized investment advice. Trading involves risk of loss. You are solely responsible for your own trading decisions. The worked example in this article uses illustrative figures; screenshots show Krino's demo mode.

↑ Back to top