Make a risk rule explicit.
“Stay within the limit” is not a complete rule. You need a basis, a clock, a threshold and a response when the threshold is reached.
Name the account and the basis
A rule may use settled balance, realized P&L, intraday equity or another measure. Open positions, fees and pending fills can matter differently under each definition. Begin with the exact account and phase, then name the quantity that the rule evaluates.
Do not assume a local platform setting uses the same definition as a firm’s contract. A provider connection supplies a technical path; it does not approve your interpretation of a loss rule. Keep the primary rule document and its current version with the configuration.
The clock is part of the rule
A daily loss limit needs a reset time and timezone. The trading session and calendar day may differ. Daylight-saving changes can alter a local clock relationship. A calculation can be numerically correct and operationally wrong if it resets at the wrong boundary.
A trailing floor also needs a sampling definition. Does the reference high move on every equity update, on a realized balance change, or only at end of day? When does it stop trailing? Is touching the floor a breach or is falling below it required? Each answer changes the result.
A small worked example
Consider an illustrative end-of-day trailing model. Starting balance is $50,000 and the loss distance is $2,000. The high-water balance starts at $50,000, so the first floor is $48,000. Suppose closed net day outcomes are +$600, −$300 and −$400, already including the sample costs.
After the first day, balance is $50,600 and the end-of-day high-water balance rises to $50,600. The floor becomes $48,600. The next two outcomes produce $50,300 and $49,900. They do not lower the high-water balance, so the floor stays $48,600 and final headroom is $1,300. The same balance path under an intraday-equity rule could produce a different result because the missing within-day peaks are not known.
- Final balance. $49,900 under the declared closed-outcome model.
- Trailing floor. $48,600 from the $50,600 end-of-day high water.
- Headroom. $1,300, before any next trade or unmodeled event.
The action matters too
A warning, a local order refusal, a lockout and a broker liquidation are different responses. State what the tool can do and what remains outside its authority. A local plan might stop new intents while existing market exposure still exists. A follower account might receive different fills from the source.
Protection also has a location. Broker-held and platform-held stops can behave differently when a connection is lost. Confirm the route and failure behavior instead of relying on a line drawn on a chart. Risk controls reduce specified risks; they cannot guarantee that every loss stays within a chosen amount.
Test boundary cases
A useful review includes the exact threshold, one step above and below, reset behavior, costs, open exposure, account switching and missing source data. Check duplicates and late fills as well as ordinary outcomes. The rule should not silently weaken when a record is incomplete.
Keep the expected results from an independently worked example, not a copy of the implementation’s formula. If the model lacks the intraday path needed by the contract, say that the result is unmeasured. An incomplete sample is not permission to report a pass.
Reconfirm before real use
The risk-plan demonstration on this website runs on a simulated day and a simulated account. It is not a named firm preset, operational certification or estimate of your chance of passing. The native project has scoped rule and risk evidence, while live route readiness remains a separate question.
Before any real account use, confirm the exact current rule, platform permission, data and order behavior with the relevant provider and firm. Record the assumptions and make a plan for disconnects and disputed data. The useful outcome of research is a clearer definition, not an invented guarantee.