Educational Simulation Archive
Comparing Planned and Simulated Execution
REVIEW GUIDE · EDUCATIONAL JOURNALING

Comparing Planned and Simulated Execution

The Review Sheet's core mechanic is a side-by-side comparison: what you planned, what the simulator displayed, and the distance between them.

Strictly educational archive. Simulated analysis and hypothetical models only.
HYPOTHETICAL SIMULATEDReview Guide 07 / 10
Comparing Planned and Simulated Execution

The Plan-Versus-Result Table

Place the plan and the simulated outcome in adjacent columns: order type, price, quantity, timing, and status. The table makes deviation visible at a glance — a changed limit, a resized quantity, a fill that arrived hours after the plan expected it.

Structure matters because unstructured reflection drifts toward narrative excuses. A table asks only: same or different, and by how much.

  • Order type: planned vs submitted.
  • Price: planned limit vs simulated fill or cancel level.
  • Quantity: planned vs entered.
  • Timing: planned window vs actual simulated event.
  • Status: filled, partial, expired, cancelled.

Measuring Deviation Without Judgment

Deviation is data before it is a grade. A limit moved by 0.25 is not automatically undisciplined — it may reflect a documented reason. The review step reads the reason field first and the deviation second, asking whether the change was a planned contingency or an improvised reaction.

Numerically, a simple running tally works: count of plans executed as written versus plans modified. Over a month, that ratio describes discipline more honestly than any single entry.

Common Deviation Patterns

Certain deviations recur so often they deserve their own labels. 'Limit chasing' — moving the limit toward the price as it retreats. 'Size drift' — quantity growing with confidence mid-session. 'Type substitution' — a market order replacing a limit when patience runs out. Naming the pattern makes it countable.

Each named pattern should appear in the review with its frequency. 'Limit chasing: 3 of 10 entries' converts a vague sense of impatience into a measurable behavior.

Updating the Next Plan

The comparison only earns its place if it changes the next entry. When deviation is intentional and successful, update the template. When it is impulsive, tighten the pre-commitment: write the invalidation level more precisely, or shorten the working window so the order cannot be nursed.

This loop — plan, simulate, compare, revise — is the Reviewbook's entire engine. Each pass produces a slightly better-calibrated next plan, which is the only improvement a simulation journal can honestly promise.

Plan vs. Simulated Result — Comparison Grid

DimensionPlannedSimulated ResultDeviation Type
Entry priceLimit at 10.00Filled at 10.00 (model touch)None — check queue caveat
Quantity100 synthetic units100 filledNone
TimingOn signal + 1 bar confirmEntered at signal barTiming — early vs. plan
ExitTarget 10.40 or stop 9.80Exited at 10.10 manuallyPlan deviation — documented
RationaleWritten hypothesis H-14Hypothesis unchangedNone
Deviations are graded as process events, never as errors-to-be-hidden.

Journal Checklist

  • Does every plan field have a corresponding result field?
  • Is each deviation typed (timing, price, size, rule)?
  • Is 'no deviation' recorded as data, not skipped?
  • Are model-caused differences tagged separately from participant-caused?
  • Does the comparison quote the plan verbatim?

Review Note

Compare plans to outcomes in the same units and the same order every time. Consistency of format is what makes deviation measurable.

Frequently Asked Questions

Because memory rewrites intent. The grid forces a field-by-field comparison where 'close enough' can't hide a deviation.

Grade it a deviation anyway. A profitable deviation teaches the wrong lesson unless the journal flags it — outcome luck and process quality are different scores.

Four cover almost everything: timing, price, size, rule. Consistent typing makes deviations countable — and countability is what turns them into data.

Continue Exploring