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

Visible synthetic example

A no-trade decision can still create a useful record.

Assume a hypothetical long-share review—not a current security or market quote—with a 50.00 USD entry condition, 49.20 USD thesis invalidation, 80.00 USD dollar-risk budget, and 4,000.00 USD capital ceiling. The arithmetic produces a theoretical 80-share lower ceiling and 64.00 USD of planned price risk. It does not approve a trade.

Planned risk per share50.00 USD - 49.20 USD = 0.80 USD
Risk-budget ceilingfloor(80.00 USD / 0.80 USD) = 100 shares
Capital ceilingfloor(4,000.00 USD / 50.00 USD) = 80 shares
Lower paper ceiling80 shares · 64.00 USD planned price risk

The written no-trade conditions are: stop if the cited source becomes stale or if the observed spread exceeds 0.10 USD. At the decision point, source freshness fails. The correct completed outcome is no trade: no order, no fill, and realized profit or loss is not applicable.

StageFrozen evidenceWhat the record supports later
Before · T-10Entry 50.00 USD, invalidation 49.20 USD, lower ceiling 80 shares, source-freshness and 0.10 USD spread gates.Shows what was actually known and required before the outcome.
Decision · T0Source freshness failed; the review stopped with no order and no fill.Preserves the rejection reason instead of backfilling a trade thesis.
After · T+15Original plan unchanged; process status “gate followed”; realized P/L not applicable.Lets the user review whether the process was followed without rewarding or punishing it for later price movement.

Example boundary: This static example does not collect a symbol, worksheet value, note, account detail, broker datum, order, or fill. Anonymous pageview measurement still applies under the Privacy Policy.

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.

Four rules that reduce hindsight edits

  1. Freeze the original plan.Preserve the pre-trade source, setup, invalidation, constraints, and no-trade conditions as they existed at the decision.
  2. Record changes separately.Add later observations and review notes without silently replacing the original fields.
  3. Separate process from P/L.A profit does not repair a weak decision record, and a loss does not by itself prove that a documented process was poor.
  4. Keep non-trades reviewable.Stopped, missed, expired, and invalidated plans can reveal whether the decision gate was followed even when there is no fill or realized P/L.

Journal notes should not contain broker credentials, account numbers, authentication data, or broker-session details. Lumiere's protected journal stores the signed-in user's plan and later review fields; full journal history remains a paid or invited-beta feature.

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 reviewed August 4, 2026: IBKR TWS: Check Margin Pre-Order.

Platform source reviewed August 4, 2026: 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

Inspect the public sample, then practice one protected review and save.

The protected sample includes one analysis and saved sample plan after email verification. Full journal history remains paid or invited beta.

Open the sample review Verify email and practice