Launch Lumiere

Workflow comparison

Pre-trade review versus a trading journal

A pre-trade review supports the decision before an order. A trading journal preserves the plan and what happened so the decision can be examined later. Serious practice can use both, but they solve different timing problems.

Reviewed by Lumiere Trading Mentor

Direct answer

What is the difference?

A pre-trade review asks whether the proposed setup, invalidation, risk, source quality, and execution assumptions are coherent before participation. A journal records the plan, decision, process, and outcome so patterns can be reviewed after the fact. One is a decision gate; the other is a feedback record.

Side-by-side

CriterionPre-trade reviewTrading journal
Primary timingBefore the order decisionDuring and after the planned trade
Core questionIs the risk decision explicit enough to consider?What did I plan, do, observe, and learn?
Minimum evidenceSource, setup, invalidation, risk, size, execution limits, no-trade conditionOriginal plan, changes, process notes, outcome, review notes
Useful outputProceed conditionally, revise, or no tradeA record that supports later review
Cannot proveThat the trade will win or loss will be cappedThat a past outcome validates the decision process

Why a journal alone can be too late

A detailed journal can identify recurring process problems, but it cannot retroactively make an unstated risk decision inspectable before entry. If invalidation, risk budget, source freshness, and no-trade conditions were absent at decision time, filling them in after the outcome creates hindsight risk.

The solution is not to abandon the journal. Save the pre-trade card first, preserve later changes separately, and keep the original plan available during review.

Why a pre-trade review alone is incomplete

A pre-trade review describes the plan but does not show whether the user followed it, whether the assumptions changed, or whether a favorable outcome came from a weak process. A journal closes that loop by preserving the original plan, deviations, execution observations, and later reflection.

Where broker-native risk tools fit

IBKR TWS can preview commissions and margin impact, and Risk Navigator can compare current and hypothetical portfolio risk. Those are useful broker-native checks. They do not automatically supply the user’s thesis, invalidation logic, source-quality review, or no-trade condition; a separate review workflow can preserve that context.

Platform source: IBKR TWS: Check Margin Pre-Order.

Platform source: IBKR TWS: Check Risk Pre Order.

The combined loop

  1. Review.State the setup, source, invalidation, risk budget, size, execution assumptions, and no-trade condition.
  2. Decide.Proceed conditionally, revise the plan, or stand aside. A completed “no trade” is a valid outcome.
  3. Preserve.Save the original plan before recording later changes or outcomes.
  4. Journal.Record what changed, what was followed, what was missed, and what should be tested next.
  5. Review the process.Evaluate decision completeness separately from profit or loss.

See the combined loop

Review the sample from evidence through saved plan.

Open the demo