Durable reference map
A three-stage method to reuse whenever conditions change
Keep the sequence of inputs, calculation and exception testing stable instead of relying on a market forecast.
- Align inputs and unitsGo to equations and definitionsAnalytical stop distance・Theoretical lot after distance is fixed
- Reconcile the worked exampleGo to table and calculation stepsA hypothetical long from 1.2050 invalidated at 1.2010
- Test exceptions and next checksGo to rules and counterexampleRecord invalidation before opening the quantity field.
Keep price analysis and money management in their proper order
An invalidation price is not a control used to make a desired quantity fit. It is the point at which the recorded trade thesis no longer holds.
Money management adjusts quantity. A wider valid stop means fewer lots; if the result cannot meet minimum volume without breaking the budget, the trade remains unavailable.
- Timestamp the entry candidate and invalidation price.
- Fix the account-currency budget and value per pip before the order.
- Do not rewrite invalidation after viewing the lot result.
The two contradictions created by forcing one lot
At the valid 40-pip stop, 1.00 lot produces a USD 400 planned loss and exceeds the USD 300 budget. If distance alone is shortened to 30 pips, the stop becomes 1.2020, ten pips inside the recorded invalidation at 1.2010.
The first choice breaks the budget; the second changes the trade thesis. Neither is a reason to reject the calculated 0.75-lot result.
Audit the same setup under two decision orders
The table uses hypothetical EUR/USD-style notation solely to expose the units. One pip is 0.0001 and the value is assumed to be USD 10 per pip per lot; these are not live product specifications.
Only the structure-first row preserves both the analytical invalidation and the USD 300 budget.
Separate this error from volatility and minimum-volume constraints
Article 1 covers a valid stop distance that genuinely changes with the market condition. This article covers moving an unchanged invalidation level merely to accommodate quantity.
Article 10 addresses the risk floor after a correct calculation falls below minimum volume. Moving the stop to make minimum volume fit is precisely the reversal addressed here.
The short record that makes the order auditable
Store entry, invalidation, distance, risk budget, loss per lot, theoretical size and rounded size on one record. Preserve the same fields for a no-trade result so the stop cannot be rewritten after the fact.
- Require a new analytical reason for a stop change.
- Record a size change as a consequence of distance or budget.
- Reconcile the eventual exit separately from the pre-trade stop.
Calculation framework
Analytical stop distance
Read the role of each equation first, then follow the numerical example to check the decision path.
Analytical stop distance
D = |P_entry − P_invalid| / pip_size- D: stop distance in pips
- P_entry: planned entry price
- P_invalid: price that invalidates the trade thesis
- pip_size: price movement represented by one pip
In plain language: The two analytical prices determine distance; preferred quantity does not.
When this conclusion does not apply: Calculate only when pip_size is positive and entry and invalidation prices are valid on the same price basis. Use absolute distance for either direction and verify the provider’s trigger convention separately.
Theoretical lot after distance is fixed
Q* = B / (D × V_pip)- Q*: lots before volume-step rounding
- B: account-currency risk budget
- V_pip: account-currency value per pip per lot
In plain language: Once the valid distance is known, solve only the quantity that fits the budget.
When this conclusion does not apply: Calculate only when B is non-negative and D and V_pip are positive. Allow explicitly for fees, spread and execution overrun rather than hiding them in an altered invalidation price.
Start with the condition that makes the original thesis false
The invalidation price belongs to the analytical description of the setup, not to the order-size preference. It should be recorded before the quantity field is opened, together with the market evidence and timestamp that justify it. Once entry and invalidation are fixed on the same price basis, their distance becomes an input to money management rather than a number available for negotiation.
For a long position entered at 1.2050 and invalidated at 1.2010, the 0.0040 difference equals 40 pips only after division by the stated 0.0001 pip size. Multiplying a raw decimal price difference by a pip-value field would mix units and understate loss by orders of magnitude. The unit conversion must therefore precede any lot calculation.
Direction changes the placement of invalidation but not the need for a positive analytical distance. A short setup can use the corresponding absolute separation after verifying trigger convention and price basis. Spread, fees, and adverse execution remain explicit additions; they should not be disguised by moving the thesis boundary toward entry.
Why choosing a familiar lot reverses the control sequence
A lot-first workflow begins with the answer it wants and changes other inputs until the equation agrees. This reversal is attractive because the order size looks stable across trades, but it transfers variability into the stop or the monetary budget. The displayed quantity becomes predictable while the economic loss and analytical meaning become inconsistent.
With a USD 300 budget, 40-pip valid stop, and USD 10 per pip per lot, one lot carries USD 400 of price-distance loss. Preserving one lot therefore requires either accepting USD 100 more loss or moving the stop to a 30-pip distance. The first option breaks the budget; the second places the stop ten pips inside the recorded invalidation.
Neither contradiction is repaired by calling the nearer stop conservative. An earlier exit can reduce loss in some paths, but it also closes the position while the original thesis remains valid. That creates a different analytical rule whose behavior must be evaluated on its own history. It cannot be adopted solely because it makes a preferred quantity fit.
Resolve price analysis and capital allocation in separate stages
The first stage defines entry, invalidation, price unit, and distance from market reasoning. The second stage fixes the account-currency loss budget and constructs loss per lot from the distance and verified monetary value. The third divides budget by that amount, rounds down to the permitted step, and checks the planned loss after rounding.
This staged design makes responsibility visible. A changed invalidation must carry a new analytical reason and time; a changed budget must carry a capital-policy reason; a changed lot can then be traced to either input set. When all three are edited in one form without order or history, a reviewer cannot tell whether the trade thesis or the risk allowance moved first.
An implementation can enforce the order without claiming to validate the market thesis. It can lock the original invalidation record, calculate distance, and prevent an upward lot adjustment that exceeds the budget. It cannot know whether 1.2010 is analytically correct. That judgment remains evidence-dependent and should be described as an input, not a product guarantee.
Reproduce the two decision orders with the same hypothetical setup
The structure-first row retains entry at 1.2050, invalidation at 1.2010, a 40-pip distance, and USD 300 budget. Dividing USD 300 by the product of 40 and USD 10 gives 0.75 lot. Multiplication back through the same distance yields USD 300, so the price boundary and monetary limit coexist without changing either assumption.
The quantity-first row sets 1.00 lot and solves backward for the distance that fits USD 300. That distance is 30 pips, which places the stop at 1.2020 for the hypothetical long. Although its table row also shows USD 300 loss, it does so by substituting a new analytical boundary without supplying new market evidence.
These numbers do not show that 0.75 lot or either price is suitable for a real order. They expose a dependency: when budget, pip value, and valid distance are stated, quantity is the remaining variable. If actual product costs or execution reserves are added, the affordable lot can be smaller, but those additions still do not justify editing invalidation.
Recognize a legitimate stop revision before it is confused with distortion
A stop can change for a valid analytical reason. New information may alter the point at which the thesis fails, or a corrected data feed may show that the earlier level was wrong. The safeguard is temporal: document the evidence and revised invalidation before recalculating quantity, rather than discovering the justification only after the preferred lot fails the budget test.
The counterexample uses this boundary. If information available before sizing genuinely moves invalidation from 1.2010 to 1.2020, a 30-pip stop is not automatically quantity-driven. The record should retain both versions, the event that triggered the change, who or what approved it, and the calculation produced from the revised distance.
A favorable outcome does not validate the revision process. A distorted stop may avoid a later loss by chance, while a well-recorded invalidation may be reached. Process evaluation therefore compares ex-ante rules and complete samples, not isolated outcomes. Otherwise hindsight can turn every convenient edit into apparent analytical skill.
Treat minimum volume as a no-order boundary, not a reason to pull the stop
When the calculated lot is below the symbol’s minimum, the setup and product may be economically incompatible with the stated budget. Moving the stop inward until minimum volume fits repeats the lot-first error in a different form. The correct test prices the loss at minimum volume using the valid distance and all required monetary inputs.
If that minimum-lot loss exceeds budget, zero quantity is a complete computed result. The record should retain raw size, minimum, volume step, minimum-lot loss, and amount of excess. This preserves evidence that the system did not fail to calculate; it correctly found no positive executable size under the combined analytical and execution constraints.
Reviewing a genuinely finer product specification can be a separate design choice, but only after tick value, contract size, costs, conversion, liquidity, and protection are verified. Importing another provider’s smaller minimum while keeping the current product’s other fields would create a synthetic contract that cannot be ordered or reconciled.
Build a state history that resists silent overwriting
A reliable record keeps the original entry thesis, invalidation price, price source, timestamp, and version. Later edits append events rather than replacing values. Each event identifies whether the change concerned analysis, account budget, specification, or execution allowance. This event history prevents a final tidy row from concealing how the decision actually evolved.
Quantity should be derived from the active version, not pasted from a prior trade. The system can store the raw price difference, pip conversion, loss per lot, raw size, step, rounded size, and account-currency replay. A hash or immutable identifier is useful only if the underlying fields are complete; integrity cannot compensate for omitted semantics.
Rejected and canceled possibilities also belong in the history. If one lot was considered and rejected because it implied USD 400 loss, retaining that check demonstrates that the USD 300 boundary operated. Deleting the rejected state leaves only the accepted 0.75 result and makes it harder to test whether the control would respond consistently in another case.
Keep execution allowances visible after the stop is fixed
The USD 300 example isolates price distance and assumes a stated pip value. A real all-in estimate can also include known costs and a condition-specific adverse-fill allowance. Those additions reduce affordable quantity because they increase loss per lot or consume a fixed portion of budget. They do not change the price at which the thesis becomes invalid.
This separation is especially important for stop orders. The trigger price is not a guaranteed fill, so execution beyond the analytical stop can add loss. Hiding an allowance by pulling the stop closer creates two errors: the thesis is exited early in ordinary conditions, and the adverse-fill risk beyond the new trigger still exists.
A stop-limit order changes the tradeoff rather than eliminating it. Price can be constrained, but execution may not occur after the trigger. The order type, limit relationship, duration, and venue behavior therefore belong beside the analytical stop. A single field labeled stop cannot safely represent invalidation, trigger, fill assumption, and price guarantee.
Use failure cases to test the decision architecture
One adversarial test enters the lot before invalidation and checks whether the form allows the stop to be solved backward. Another changes the budget after a wide stop produces an unfamiliar lot. A third supplies a raw decimal price difference without pip conversion. Each test targets a distinct route by which the final monetary loss can look plausible while its reasoning is corrupted.
Boundary tests should include zero or missing pip size, nonpositive monetary value per pip, invalid prices, and a budget below minimum-lot loss. The safe response is no quantity with an explicit reason. Defaulting a missing field from the last calculation is particularly dangerous because it produces a polished answer that silently mixes trades, symbols, or timestamps.
A useful review also checks direction. Entry and invalidation may be reversed for a short, yet the distance supplied to loss per lot must remain positive. Using an absolute distance is appropriate only after verifying both prices belong to the same quote basis and the stop is on the protective side. Absolute value should not make an analytically impossible order appear valid.
Interpret the cited sizing logic without extending its claim
CME educational material supports placing a stop at a logical level that identifies when the thesis is wrong and then deriving quantity from account risk and tick value. The arithmetic relationship also shows that a wider stop permits fewer contracts under a fixed loss allowance. It does not identify the correct invalidation level for this hypothetical currency notation.
The rule against moving a stop merely to preserve quantity is a control inference from that ordering. It should be labeled as such rather than presented as a verbatim source command. This evidence boundary matters because analytical placement, execution venue, and account policy are not established by a general educational example.
What the calculation can conclude is narrow: under the given 1.2050 entry, 1.2010 invalidation, USD 10 pip value, and USD 300 price-distance budget, 0.75 lot preserves both recorded constraints. It cannot conclude that the setup should be traded, that the stop will fill at its trigger, or that the budget captures every loss component.
Govern revisions with an explicit separation of duties
Where more than one person or component participates, the analytical service should publish invalidation and version before the sizing service reads it. The sizing service can reject missing units or an over-budget quantity but should not move the price boundary. This division does not make either judgment infallible; it makes unauthorized substitutions observable and reviewable.
A single-user workflow can apply the same idea through staged form states. Editing invalidation after seeing the calculated lot should create a new analysis version and require a reason, rather than silently refreshing the result. Editing the budget should identify the governing capital rule. The additional friction is purposeful because both changes can make the preferred quantity appear acceptable.
Approval logs should not claim that a reviewer endorsed future performance. Their scope is narrower: the input order, units, budget authority, and arithmetic were checked. A valid process can still produce a losing outcome, while a profitable outcome can come from a distorted stop. Governance is about preserving the rule, not certifying the trade.
Audit misuse through invariants rather than visual plausibility
One invariant is that invalidation remains unchanged when only the requested quantity changes. Another is that multiplying rounded lot by valid distance and monetary pip value cannot exceed the price-distance budget before separately stated additions. A third is that narrowing the stop requires an analytical-version event earlier than the recalculation timestamp.
These invariants catch polished but inconsistent screens. A row can show a logical-looking stop, a round lot, and a familiar money amount while failing the decision order. Automated checks should compare field lineage and timestamps, not merely whether every box contains a number. A complete-looking calculation built from overwritten inputs is not reproducible evidence.
The strongest negative test uses the exact hypothetical contradiction: request 1.00 lot, retain a 1.2010 invalidation, and enforce USD 300. The system must reject either the quantity or the impossible simultaneous constraints; it must not invent 1.2020 without a new thesis record. Passing this test demonstrates control over input priority, not market validity.
Carry the no-trade result into downstream decisions
A zero quantity should prevent order construction while leaving the analytical setup available for review. The interface can explain that minimum volume, budget, or missing specification blocked execution. It should not offer a one-click upward round or silently relax the stop, because those shortcuts make the exceptional path less controlled than the ordinary calculation.
Repeated zero outcomes may reveal a structural mismatch: the account-currency budget is too small for the strategy’s valid distances on the selected product. That observation can support a separate product-design review, but it is not evidence for enlarging the per-trade allowance. Any alternative needs a fresh contract, cost, conversion, and liquidity analysis.
The final decision consequence is clarity about what changed. If new evidence truly shifts invalidation to 1.2020, the revised 30-pip calculation can be documented on its own terms. If no such evidence exists, 0.75 lot or no order preserves the original setup. The workflow does not select a market view; it prevents quantity preference from rewriting one. That provenance remains essential even when both paths happen to finish with the same outcome.
Decision and control rules
- Record invalidation before opening the quantity field.
- Solve quantity from distance and loss per lot.
- Do not pull the stop inward when the result is below minimum volume.
- Use the record to distinguish analytical stop changes from quantity-driven edits.
Common failure modes
- Moving the stop closer to preserve a familiar lot.
- Increasing the loss budget after selecting a wider stop.
- Multiplying a raw price difference by pip value without converting it to pips.
Evidence and specifications
- CME Group — Proper Position Size
What this source supports: CME states that a stop should be placed at a logical level that identifies when the trade thesis is wrong, after which account risk and tick value determine position size.
- CME Group — The 2% Rule
What this source supports: The worked exchange examples hold a maximum account loss constant and show that a wider stop permits fewer contracts. The rule against moving the stop to preserve quantity is this article’s control inference from that arithmetic.
Questions to resolve
Must every stop come from technical analysis?
The method depends on the strategy, but the stop should represent a pre-defined invalidation condition rather than a number chosen to make quantity fit.
Is using one lot inherently wrong?
No. One lot is consistent when its loss at the valid stop is within the stated budget.
Can I tighten the stop to reach minimum volume?
Doing so solely for quantity changes the trade. Compute the minimum-volume loss and retain no trade as an explicit outcome.
Does the stop guarantee a USD 300 maximum loss?
No. A stop trigger does not guarantee its execution price. Adverse fills must be measured separately.
Recalculate from current inputs
Enter the planned entry and invalidation prices first, then calculate the quantity that fits the distance and budget.
Important: This article explains calculation order and does not recommend a price, stop or quantity. The hypothetical pip value and order behavior may not match any live product.