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 definitionsStop loss per lot・Theoretical size for a fixed budget
- Reconcile the worked exampleGo to table and calculation stepsA 25-point and an 80-point stop under one USD 500 budget
- Test exceptions and next checksGo to rules and counterexampleFeed the selected stop distance, not a qualitative volatility label, into the size formula.
How changing market movement reaches position size
Higher measured volatility is not, by itself, an instruction to reduce every position. The first question is whether the strategy needs a different invalidation distance. That distance determines the loss per lot.
If point value is unchanged and the stop widens from 25 to 80 points, loss per lot rises by a factor of 3.2. Holding the dollar budget constant makes theoretical size move in the opposite direction.
- Record the volatility window and timestamp.
- Check that the stop still represents the strategy’s invalidation condition.
- Use point value and currency conversion from the same specification snapshot.
A fixed lot is not a fixed loss
Account loss is the product of quantity, stop distance and value per point. Fixing only quantity leaves two inputs free to change.
There is also a genuine no-change case. If the strategy uses the same valid distance and point value and the budget is unchanged, a move in a separate volatility indicator need not alter the rounded quantity.
Compare two regimes with one dollar budget
The figures below are hypothetical values created only to expose the units and arithmetic. Both cases use a USD 500 budget, USD 10 per point per lot and a 0.01-lot volume step.
The theoretical result is rounded down. Multiplying the rounded quantity back through the loss formula is the final budget check.
Where this topic stops
This article covers a persistent or rolling market condition that changes the strategy’s stop distance. Event-specific execution overrun around a scheduled release belongs to Article 7; the general distribution of adverse stop fills belongs to Article 9.
Do not hide an assumed execution buffer inside a volatility stop. Keep the analytical distance and the execution allowance as separate, auditable inputs.
When a fresh number gives the same answer
If stop distance, point value, conversion rate and budget all match the prior snapshot, the rounded quantity may remain unchanged. Preserve the new timestamp and inputs instead of documenting the decision as an unexplained fixed lot.
- Recompute when any sizing input changes.
- Do not round up when the result falls below the minimum tradable amount.
- Treat the planned loss as an estimate, not a guaranteed ceiling.
Calculation framework
Stop loss per lot
Read the role of each equation first, then follow the numerical example to check the decision path.
Stop loss per lot
L_1 = D × V- L_1: account-currency loss for one lot across the stop distance
- D: selected stop distance in points
- V: account-currency value per point per lot
In plain language: With other inputs fixed, loss per lot rises in direct proportion to stop distance.
When this conclusion does not apply: Calculate only with D at least zero and V greater than zero on one product and quantity basis. Fees and execution overrun are separate additions; this formula isolates the stop distance selected for the volatility condition.
Theoretical size for a fixed budget
Q* = B / (D × V)- Q*: theoretical lots before volume-step rounding
- B: account-currency loss budget for the trade
- D × V: stop loss per lot
In plain language: For a constant budget, permissible size is inversely related to stop distance.
When this conclusion does not apply: Calculate only when B is non-negative and D and V are positive. Round the executable quantity down to the provider’s volume step and check the resulting loss again in account currency.
Trace the route from market movement to a monetary exposure
Volatility does not enter a position-size equation as a mood label. It matters only after a defined measurement changes a price-distance assumption used by the strategy. The chain is therefore measurement, analytical invalidation, stop distance, loss per lot, and executable quantity. Skipping one link makes it impossible to tell whether a smaller lot reflects evidence or an undocumented preference.
This distinction prevents a common category error. A higher standard deviation or ATR reading can coexist with the same valid stop, while a structural change in price behavior can require a wider invalidation distance even if the selected indicator moves little. The quantity decision follows the recorded distance and point value, not the adjective attached to the market condition.
The practical consequence is asymmetric. If the stop expands while account-currency budget and value per point stay fixed, one-lot loss rises and affordable quantity falls. If only the descriptive regime changes, the arithmetic may produce the same rounded lot. Both outcomes are legitimate, but each needs a dated input record that shows why it occurred.
Define a regime without looking at the later trade result
A volatility regime needs an observable definition before its trades are evaluated. The record should identify the measure, lookback, sampling frequency, price series, calculation time, and rule that maps the observation to an analytical stop. A label assigned after a loss invites hindsight: the same movement can be called routine after a win and turbulent after a loss without changing any underlying calculation.
Regime boundaries also create edge cases. A reading near a threshold can alternate classifications while the economically valid stop barely changes. A robust workflow retains the raw measure and resulting distance rather than only a category name. That permits later reviewers to see whether frequent quantity changes arose from real price-distance changes or from a fragile classification boundary.
Time scaling deserves its own field. A daily variability estimate, an intraday stop, and a weekly holding period are not interchangeable merely because they share a percentage unit. CME material distinguishes realized, forecast, and implied measures and discusses time scaling; selecting one for this sizing use remains an article-level modeling decision, not a conclusion supplied by the source.
Preserve the analytical stop before adding execution effects
The analytical distance marks where the recorded thesis no longer holds. It should not silently absorb spread, ordinary adverse fills, a scheduled-release allowance, or a weekend reopening scenario. Combining all of those into one unexplained number may still produce arithmetic, but it removes the ability to test which assumption drove the quantity and which component later failed.
A useful record carries separate fields for the chart-derived distance and any execution reserve. The volatility-conditioned distance can then be compared across market states while execution assumptions are compared across venues, order types, and sessions. This separation matters because a broad regime change and a brief release-window liquidity event have different sampling populations and different update schedules.
When the stop is unchanged, a higher volatility reading should not be forced into the money calculation by multiplying unrelated units. A price-distance input must first be resolved in points or pips on the relevant symbol basis. Only then can it be multiplied by account-currency value per unit and quantity. Unit cancellation is the simplest defense against an impressive but meaningless number.
Read the calm and turbulent cases as a controlled comparison
The hypothetical pair holds the USD 500 loss budget, USD 10 value per point per lot, product convention, and 0.01-lot step constant. It changes the stop from 25 to 80 points. That design isolates the distance effect: one-lot stop loss moves from USD 250 to USD 800, a factor of 3.2, without attributing the difference to a new account or contract.
Dividing USD 500 by USD 250 gives 2.00 lots in the calm case. Dividing the same budget by USD 800 gives 0.625 lot in the turbulent case. Because 0.625 is not executable on a 0.01 step without adjustment, the quantity is rounded down to 0.62 rather than up to 0.63. The backward check produces USD 496, leaving a small rounding residue.
These numbers are educational inputs, not observations about a live market. Their value is diagnostic: they make clear which variables were fixed and why the lot changed. Treating 2.00 and 0.62 as generally suitable quantities would erase the instrument, conversion, fees, execution, and account context that gives the calculation meaning.
Make rounding part of the risk control rather than display formatting
A theoretical quantity is a continuous result, whereas an order must conform to minimum volume, step, and precision. Downward rounding is therefore not cosmetic. At an 80-point stop, moving from 0.625 to 0.63 would turn the planned price-distance loss into USD 504 and cross the stated USD 500 budget before any separately modeled costs are considered.
The calculation should retain both raw and executable quantities. Keeping only 0.62 hides how close the result was to the next step and prevents a reviewer from reproducing the choice. Keeping only 0.625 is worse because it may imply an order that the venue cannot accept. A final multiplication through distance and value closes the loop in account currency.
Minimum volume introduces a different boundary. If downward rounding produces zero or a result below the verified minimum, the workflow must price the loss at the minimum and return no order when that amount exceeds budget. Increasing the budget or narrowing the stop after seeing the floor would change the decision rule rather than solve a rounding problem.
Control specification drift while the regime changes
A volatility comparison is valid only if the product basis remains aligned. Point value can change with contract specifications, account-currency conversion, or a platform field definition. Reusing an old value while refreshing only the stop distance creates a mixed-time calculation: the formula appears current, but one of its monetary inputs belongs to another snapshot.
The record should bind symbol, contract or calculation mode, point size, value per point per lot, profit currency, account currency, conversion factor, and timestamp. A missing or contradictory field is not permission to copy yesterday’s quantity. It is a reason to withhold the result until the economic meaning of one lot can be reconstructed.
This discipline also exposes a real no-change case. When the stop distance, monetary value per point, conversion factor, risk budget, and executable step all match the previous snapshot, a fresh regime assessment can reproduce the same lot. The repeated quantity is then a calculated outcome with current evidence, not an unexplained fixed-lot policy.
Separate model uncertainty from execution uncertainty
The chosen stop can be wrong as a model of invalidation, and the eventual fill can be worse than the stop trigger. Those are different uncertainties. The first concerns whether the strategy translated market behavior into a defensible price boundary. The second concerns available liquidity and order mechanics after that boundary is reached. One buffer cannot diagnose both failures.
A regime estimate also has sampling error. A short lookback can react quickly but produce unstable distances; a long lookback can smooth noise but lag a structural change. There is no universal window in the cited material that resolves this tradeoff for every strategy. The defensible action is to predefine the window, retain alternatives for sensitivity review, and avoid presenting one estimate as certain.
Execution loss can exceed a selected adverse-fill quantile, particularly outside the sample used to choose it. For that reason, the USD 496 backward check confirms only the arithmetic under the stated 80-point distance. It is not a guaranteed loss ceiling. Fees, gaps, slippage, and conversion changes need separate additions or scenarios before any all-in estimate is described.
Use sensitivity to identify the input that actually binds
A useful sensitivity review varies one input at a time. Widening distance with budget and point value fixed reveals inverse quantity behavior. Raising the monetary budget with distance fixed increases theoretical size proportionally, while increasing value per point reduces it. Moving several inputs together can be realistic, but it does not reveal which change caused the final order ceiling.
Step rounding creates flat regions. Two nearby stop distances may both round to 0.62 lot even though their theoretical quantities differ. That is not evidence that distance has no effect; it is an execution-grid effect. Retaining the raw result, rounded result, and residual budget makes the plateau visible and prevents analysts from inventing a causal explanation for an unchanged displayed lot.
Sensitivity should include the no-order edge. A larger distance may push theoretical size below minimum volume even when the previous regime supported an order. The consequence is not automatically to search for a closer stop. It is to record that no positive executable quantity meets the specified price-distance budget under that market state and product specification.
Design the journal so the calculation can be reproduced
A compact journal row should hold measurement time and timezone, volatility method and window, raw measure, regime label, analytical invalidation, distance unit, point value, conversion, risk budget, raw lot, step, rounded lot, and checked loss. Separate columns should capture execution allowance and known costs instead of burying them inside the stop distance.
Versioning matters when a rule changes. If a multiplier from volatility measure to stop distance is revised, earlier trades should retain the former version rather than being recomputed as though the new rule had always applied. Without that boundary, an apparent improvement can come from rewriting historical inputs, not from better out-of-sample behavior.
A no-change decision deserves the same record as a reduction. Saving only changed lots creates selection bias in the audit trail and makes the calculation appear more responsive than it was. Saving no-order outcomes is equally important because repeated rejections may reveal a mismatch between the strategy’s distances and the product’s minimum executable risk unit.
Keep the evidence claim narrower than the arithmetic
The BIS analysis supports the premise that exchange-rate volatility varies over time and can cluster. It does not directly prescribe an 80-point stop, a USD 500 budget, or any lot. Using its finding to motivate a regime-aware stop process is an inference made here, and the distinction should remain visible wherever the source is summarized.
CME educational material supports deriving position size from a logical stop location and a predetermined account-currency amount. Its worked logic explains why a wider distance permits fewer contracts under a fixed budget. The current example translates that relationship to hypothetical point and lot inputs; it does not represent CME approval of a particular instrument or strategy.
The resulting decision is modest but meaningful. A fixed quantity cannot be called fixed risk when stop distance or monetary point value changes. A calculation that preserves inputs, units, timing, and rounding can state what quantity fits the chosen assumptions. It cannot establish that the assumptions will describe the next market move or the eventual execution price.
Compare alternatives without turning the regime label into a command
A counterfactual review can hold the 80-point analytical stop and test several budgets, or hold USD 500 and test several defensible distances. It should not compare an 80-point turbulent case with a 25-point calm case while also changing the contract and conversion, then attribute the entire quantity difference to volatility. Controlled comparisons are explanatory devices, not forecasts.
Another useful comparison leaves the stop at 25 points even when the volatility measure rises. If the recorded thesis still supports that distance, the calculation remains 2.00 lots under the hypothetical inputs. The result demonstrates that regime classification is not a hidden lot multiplier. It also forces the analyst to defend the distance mapping instead of appealing to a broad market description.
If the wider stop is adopted only after seeing that a trade would otherwise have lost, the example no longer tests an ex-ante sizing process. The journal must show which information was available when the distance was chosen. Separating decision-time fields from later outcome fields prevents hindsight from manufacturing a seemingly well-calibrated volatility response.
Specify the operational state transitions that trigger recalculation
A new measurement can move the record from assessed to unchanged, resized, or unavailable. Resized means at least one active sizing input changed and a new executable lot was checked. Unchanged means the full input snapshot was refreshed but the same step-aligned result remained. Unavailable means a required value, specification, or minimum-volume condition prevented a valid positive order.
Order submission is a later state, not proof that the calculation remains current. A delay can make the regime measure, conversion factor, point value, or account budget older than its declared tolerance. The system should revalidate the necessary inputs at the transition from calculated to submitted and preserve both snapshots if a difference changes the lot or rejects the order.
After execution, actual fills and costs belong to reconciliation rather than retroactive sizing. Comparing estimated with realized loss can inform future execution allowances or model review, but it should not rewrite the original distance or raw quantity. Keeping decision and outcome states separate protects both the audit trail and the evidence needed for later improvements.
Understand the decision consequence of getting the mapping wrong
An overly wide volatility mapping can reduce participation or create repeated no-order outcomes even when the analytical thesis did not require that distance. An overly narrow mapping can make the displayed lot look efficient while leaving the stop inside ordinary movement or underestimating one-lot loss. Neither error is diagnosed by the final quantity alone; the mapping and its evidence must be inspected.
Keeping a fixed lot across the two hypothetical distances would move planned price-distance loss from USD 500 at 2.00 lots and 25 points to USD 1,600 at 2.00 lots and 80 points. That comparison does not predict a realized loss, but it shows why quantity stability can conceal a large change in the amount exposed at the selected stop.
The defensible output is conditional language: given a USD 500 budget, USD 10 per point per lot, 80-point analytical stop, and 0.01 step, 0.62 lot replays to USD 496 before separate additions. The calculation supports that bounded statement and a reproducible decision. It does not turn a volatility estimate into advice or certainty.
Decision and control rules
- Feed the selected stop distance, not a qualitative volatility label, into the size formula.
- Compare conditions under the same account-currency budget and round down.
- Reconcile the rounded quantity to account-currency loss.
- Keep scheduled-release overrun separate from the volatility-based analytical stop.
Common failure modes
- Multiplying an ATR or standard-deviation number by money without first resolving its price unit.
- Keeping quantity fixed while the effective stop loss per lot changes.
- Rounding 0.625 up to 0.63 and breaching the stated budget.
Evidence and specifications
- CME Group — Proper Position Size
What this source supports: Position size should be determined from a logical stop location and a predetermined account-currency risk amount; CME’s example shows that a wider tick distance requires fewer contracts for the same risk.
- BIS — Trading volumes, volatility and spreads in FX markets: evidence from emerging market countries
What this source supports: The primary analysis documents time-varying exchange-rate volatility and volatility clustering. Applying that finding to stop distance or position size is this article’s inference, not the paper’s direct conclusion.
- CME Group — Discover Options Volatility
What this source supports: CME’s current lesson describes underlying-price variability with standard deviation, distinguishes realized, forecast and implied volatility measures, and explains time scaling. Selecting a measure for sizing is an article-level decision.
Questions to resolve
Must size always fall when volatility rises?
No. Size falls when the valid stop loss per lot increases while the budget remains fixed. A separate indicator reading does not change quantity by itself.
Which ATR lookback should be used?
There is no universal lookback. Use the period defined in the strategy and retain its timeframe and timestamp.
Does the 80-point input include slippage?
No. It is the analytical stop distance in this example. Execution overrun should be estimated and recorded separately.
What if the result is below minimum volume?
Do not round up automatically. Calculate the loss at minimum volume and apply the explicit no-trade boundary.
Recalculate from current inputs
Enter the current stop distance and point value, then check the account-currency loss after volume-step rounding.
Important: This is educational material about volatility and position-size arithmetic, not a recommendation of a market condition, stop or quantity. A stop order may fill away from its trigger, so the computed loss is not guaranteed as a ceiling.