How to Review Trades Against Your Trading Rules

You finish a trade, see the loss, and remember that your plan called for a smaller position. The temptation is to jump straight to “that rule would have saved me $X.” A better review separates what the trade record proves from what must remain hypothetical.

A useful rule audit makes the calculation reproducible and the missing evidence visible.

Start with a narrow, recent sample

Review a handful of completed U.S.-dollar equity trades rather than importing an entire trading history. For each trade, record the ticker, average entry, average exit, quantity, and gross fill-price result. Then capture the account equity and rule settings used for the comparison.

Keep the original trade facts unchanged. The rule-adjusted result belongs in a separate scenario column. That distinction prevents a hypothetical outcome from replacing the broker record.

Run the review in four steps

1. Confirm coverage. Exclude open positions, unsupported currencies or assets, and trades whose entry, exit, or quantity cannot be reconstructed reliably.
2. Load the saved rule. Use the saved maximum position value, concurrent-position limit, or risk-per-trade percentage and the account-equity input shown in the review.
3. Compare like with like. A position-value rule compares capital deployed. A risk-budget scenario compares gross fill-price loss. Do not present them as the same calculation.
4. Record the finding and limitation. Preserve the rule, inputs, estimated difference, and missing evidence beside the result.

A fictional position-size example

Assume a fictional trader enters the demo symbol ABCD at $50 with 300 shares in a $100,000 account. Their saved maximum position is $10,000. At the recorded entry, the rule-supported cap is 200 shares.

If the completed trade exits at $42, the broker facts imply a $2,400 loss before any unrecorded fees. Applying the 200-share cap to the same entry and exit produces a hypothetical $1,600 loss. The estimated difference is $800.

• Recorded position value: 300 × $50 = $15,000.
• Saved position cap: $10,000.
• Rule-capped shares: floor($10,000 ÷ $50) = 200.
• Hypothetical loss difference: $2,400 − $1,600 = $800.

This comparison is data-supported only when the completed trade is an eligible U.S.-dollar equity trade and the required entry, exit, quantity, and saved position-cap data are available. It still assumes the capped shares would have received the same average exit. A gap, partial fill, fee, or different execution path can change the outcome.

Why risk-per-trade is a different scenario

Suppose the same account has a 1% per-trade risk budget, or $1,000. If a completed trade had a $2,400 gross fill-price loss, clipping that modeled loss at $1,000 creates a $1,400 hypothetical difference. It does not prove that $1,400 would have been saved.

The original stop, whether it was entered, any gap through it, slippage, fees, and intraday execution sequence may be absent from a broker activity record. Without those facts, the calculation is a gross-fill-price-loss scenario, not a verified stop-based reconstruction. Do not add it to the position-size difference as though the two were independent.

A finding is not the same as positive savings

If an oversized trade made money, it can still produce a position-size finding while showing no positive hypothetical loss difference. That is the right result. The purpose is to reveal where behavior diverged from the saved rule, not to relabel every exception as a loss.

The same principle applies when the available timestamps prove that a new entry exceeded the saved concurrent-position limit. That can be a supported rule finding, but the result of skipping the trade is unknowable, so it should add no dollar savings.

Connected and manual reviews have different gaps

Broker-assisted review

TradeRegimen can use a limited recent history window to reconstruct up to ten eligible completed trades during onboarding. When the full transaction backfill is not ready, a complete holdings snapshot may support an early result from up to 90 days of executed orders. That result is labeled partial because older trades and non-order activity may be absent. Broker and third-party data can also be delayed, duplicated, or missing enough detail to pair an entry and exit. The preview should show how many trades were analyzed and identify when there was not enough eligible data.

Manual review

If you prefer not to connect a brokerage, enter up to five recent trades manually. This keeps the exercise useful without granting account access, but the result is only as accurate as the supplied prices, quantities, and account equity. Use the broker statement to verify them.

How TradeRegimen uses the method

During onboarding, you first configure supported rules in your Trading Constitution. You can then connect a supported brokerage for a bounded preview or enter recent trades manually. TradeRegimen shows the input, the matching rule, the finding, and any estimated hypothetical loss difference before you decide whether the ongoing Pro workflow fits your process.

The review is educational decision support. TradeRegimen is not a broker or custodian, does not place or block orders, and does not provide individualized investment advice. No retrospective estimate guarantees savings, fewer losses, or better future performance.

Use the result for one concrete revision

Look for one repeated, supported finding. If position size is the issue, decide where the calculated cap needs to appear before the next order. If the evidence is incomplete, fix the recordkeeping before changing the rule. A small honest audit is more useful than a precise-looking estimate built on missing inputs.

To define the inputs before reviewing past trades, use the step-by-step Trading Constitution guide. For the broader behavioral workflow, read why trading rules keep breaking.

Method and limits

• Fictional educational example using demo symbol ABCD; it is not a security recommendation or a report of customer results.
• Calculations use the supplied account equity and Constitution settings. They exclude unknown fees, taxes, opportunity costs, market impact, and execution changes unless those inputs are explicitly available.
• Broker and third-party data may be delayed, incomplete, or inaccurate. Past performance and hypothetical results do not guarantee future outcomes.
• Product behavior was reviewed against the onboarding recent-trade review implementation on September 20, 2026. See the complete disclaimer.