Portfolio stop plans versus overnight gap scenarios
Compare intended stop-distance loss with simultaneous entered adverse exits, keeping costs, account base and uncertainty explicit.
A stop plan is not a guaranteed loss ceiling
An intended stop is part of a plan. The actual execution can differ under gaps, liquidity conditions or the applicable order rules. A basket can also contain several positions whose stop plans are affected at the same time. The review should therefore separate planned price-distance loss from a declared adverse-exit scenario.
The worksheet uses positive entry, units and multiplier, an adverse stop and an entered adverse scenario price. It supports simple linear long and short positions in one supplied USD base. It does not model options, margin, liquidation priority or all possible tail events. Those would require the correct domain and account rules.
Work the populated basket
The four fictional positions have combined intended price-distance loss of two hundred forty. Entered execution costs total eighteen, so planned loss including those assumptions is two hundred fifty-eight. Under the chosen adverse exit prices, price loss becomes five hundred thirty-five and total scenario loss becomes five hundred fifty-three.
Against the entered ten-thousand account base, those amounts are 2.58 percent and 5.53 percent. The difference is two hundred ninety-five in this example. These figures are exact arithmetic under the packet, not a prediction, recommended risk limit, broker fill guarantee or observed provider result. The source of the scenario prices remains the exercise itself.
Use the same cost treatment in both comparisons
If the intended and adverse cases use different cost conventions, the difference can mix execution effects with accounting changes. The teaching basket applies each row's entered total cost to both cases. Its price-only components remain visible, so a reader can see what changed because of the exit assumption.
For a real account, the appropriate costs may differ across executions and should be recorded under their actual convention. Do not add charges already included in a net ledger. The worksheet does not infer a commission schedule, financing rate or regional tax. Its simplicity makes the assumptions reviewable instead of concealing them inside an apparently authoritative portfolio-risk number.
Preserve account-base and quantity identity
A percentage scenario loss needs a declared positive account base. Deposits, withdrawals and unrelated positions can matter in an actual account return calculation. The tool does not reconstruct that path or claim the base is an audited equity value. It compares the entered monetary scenario to the entered base only.
Each row has a unique ID and explicit quantity. Invalid stops, unsupported directions, duplicate IDs and non-finite or out-of-range decimal strings are rejected. The calculator does not quietly reduce quantities to satisfy an attractive budget. A user who changes the basket creates a different scenario and should retain that change if comparing results.
Write the scenario, not a risk promise
A useful conclusion states the basket, entered exits, cost treatment, account base and limitations. A stress result should not be called the worst possible loss or a calibrated probability without a justified model. A good stop plan can still need overnight exposure review, and a large invented stress does not prove an actual strategy will experience it.
The new tool complements the preserved single-position gap worksheet. Both help make assumptions explicit; neither recommends an allocation or verifies a historical service record. Keeping the planned and adverse cases side by side turns a vague discussion of overnight risk into an inspectable exercise without manufacturing a real-world risk forecast.
Resolve timestamp precision before joining events
Two labels recorded to the same second do not necessarily establish which event came first inside that second. Retain any source precision and uncertainty rather than inventing milliseconds. The teaching journal permits equal supplied timestamps but does not infer subscriber precedence from them. A real causal conclusion requires the precision and relationship of the actual source records. Keep publication, receipt and execution as separate events even when their displayed clock values agree.
Reference documents
These references cover mechanisms and source definitions. The worked numbers on this page are invented teaching inputs, not provider or account records.