What Are the Rules of Swing Risk?

Direct answer

Swing risk does not have one universal, official rulebook. In practice, people use a rule set that links (1) a holding period long enough to be called a “swing,” (2) a defined exposure amount, and (3) a way to translate that exposure into order size using measurable inputs such as price levels and your cost assumptions. The “rules” are therefore best understood as a testable checklist: you can write them down, compute the resulting order size under stated assumptions, and check whether the accounting matches your risk control goals.

To keep it non-promotional and independently verifiable, this article describes a neutral rule framework for swing risk. It focuses on stable mechanics (what must be defined and how it is computed) and explicitly separates variable conditions (how markets and execution affect realized outcomes).

Mechanism or definition: a testable swing-risk rule set

A practical swing-risk ruleset can be written as five components.

1) Define the “swing” measurement window

Assume you will hold the position for a swing horizon. You must define what “swing horizon” means in your own testing setup, for example by using a fixed number of price bars or an exit rule that can occur within that window. The key is that the rule set must not rely on changing the horizon after seeing outcomes.

Material limitation: if your “swing horizon” changes dynamically with market movement, the risk calculation becomes inconsistent and harder to verify.

2) Choose a risk accounting target

Decide what “risk” means in your rules. A common non-financial-advice framing is: “I will cap loss if price reaches a predefined adverse level.” To make that cap testable, you must state an account-level quantity (such as a percentage of account equity) or an absolute loss budget, plus whether the cap is measured before or after costs.

Stable mechanics: without a defined loss budget and its measurement basis, “risk control” is not computable.

3) Define the adverse move used for sizing

Swing risk sizing requires a measurable distance between an entry reference and an adverse reference level (often called a stop level). In a testable rule set, you compute the distance using the instrument’s price scale as it existed at the time of decision in your simulation.

Assumption you must state: whether you measure distance in pips, points, or the raw price move. Your units must match the method used to convert that distance into account currency.

4) Translate price distance into position size

The position size rule is the computational core. In general terms, it converts “risk budget” and “stop distance” into a number of lots/units that would produce the budgeted loss if the stop level is reached.

A simplified, testable formula structure (without assuming any specific broker contract details) looks like:

Position size × value_per_price_unit × stop_distance = risk_budget (under your cost assumptions)

Assumptions you must define for verification:

The value-per-price-unit model you used (how a move in price maps to account currency).
Any currency conversion assumptions if the quote or account currency differs.
Whether you model costs as zero, fixed, or estimated.

5) Apply a consistent execution and cost model in backtests

Realized swing risk is sensitive to costs and execution quality. Your rule set becomes verifiable only if it states what you assume for spread and slippage during the swing.

Example of explicit assumptions (simulation-only):

Spread: fixed at X pips.
Slippage: drawn from a fixed range or set to a conservative constant.
Stop behavior: you assume stops trigger at the level or you model potential gap-through conditions.

Material limitation / failure mode: if you ignore costs and execution slippage, your risk budget may not reflect realized losses. Historical “paper” performance can look better than forward outcomes because the risk math did not include the same frictions.

Evidence or example: how to verify your own swing-risk rules

You can independently verify whether a written swing-risk rule set is self-consistent by running a small, transparent simulation.

Example verification workflow (simulation)

Assume the following stated, testable setup:

Swing horizon: exit within the next N bars or via an adverse level.
Risk budget: a fixed percentage of account equity measured at entry.
Stop distance: computed from the entry reference to an adverse reference level.
Cost assumptions: fixed spread and fixed slippage (or set to zero for a baseline, then re-run with costs).

Then test the rule set on a small historical sample:

For each hypothetical trade, compute stop distance using the defined units.
Convert stop distance to an estimated loss in account currency using your chosen model.
Compute the position size so that estimated loss matches the risk budget.
Apply exit logic under your cost/execution model.
Compare realized loss vs. the risk budget.

What you should look for:

Consistency: does realized loss mostly match the modeled cap under your assumptions?
Sensitivity: how much does the mismatch grow when you add spread and slippage?
Stability: does changing the swing horizon definition change the outcomes materially even when risk budget is held constant?

This verification approach does not claim profitability. It checks whether the rule set is arithmetically coherent and whether the assumptions you chose are sufficient to explain realized deviations.

Limitations and risks: why swing-risk rules can fail

Even a well-defined rule set can fail for reasons that are not errors in math.

Execution uncertainty (slippage and stop behavior) Stops may fill at prices different from the level assumed in your calculations. If your rule set assumes perfect fills, the risk budget can be violated.
Spread variability across time If your rules use a fixed spread but the real spread varies, the effective cost per trade changes. That changes realized loss at the moment the stop level is tested.
Model mismatch in value-per-price conversion If your conversion from price distance to account-currency value is wrong or based on incomplete contract assumptions, computed position sizes will not match the intended risk budget.
Changing assumptions after seeing outcomes If the swing horizon, stop placement method, or cost estimates are adjusted based on observed results, the rule set becomes non-testable.
Historical relationships do not guarantee future results Even if a simulation matches risk budgets historically, the future distribution of volatility, gaps, and execution conditions can differ.