Quant Memo
Core

What Happens When You Breach A Limit

The mechanical and human sequence that follows a risk limit breach — what gets flagged automatically, who gets called, and why the trader is rarely the one who decides what happens next.

Prerequisites: Soft Limits, Hard Limits And Warning Levels

Every desk with real risk limits has a process for what happens the moment one gets breached, and the process is built to work whether or not the trader agrees with it in the moment. The first thing that happens is almost always automated: a risk system flags the breach in real time, usually before the trader has fully registered it themselves, and the flag goes not just to the trader but to a risk manager and often a desk head simultaneously. This matters because it removes the trader's ability to quietly manage a breach on their own timeline — the clock starts the instant the number crosses the line, not whenever the trader decides to raise their hand.

From flag to resolution

What follows depends on which kind of limit was breached. A soft-limit breach typically triggers a required call or message exchange: the trader explains what's driving the position and the risk manager decides whether to allow it to continue, require a partial reduction, or escalate further. A hard-limit breach removes that discretion — new orders are blocked by the system itself, and the position that caused the breach is usually reduced by someone other than the trader who built it, often on a forced timeline that doesn't wait for the market to be convenient. The trader's input still matters — they usually know the position best — but they are no longer the sole decision-maker once a hard limit is crossed.

A breach also almost always creates a paper trail that outlives the trading day: a post-mortem, a note in the trader's file, or a formal review, even if the position ultimately worked out fine. This surprises newer traders, who sometimes assume that a breach followed by a profitable outcome retroactively excuses it. It doesn't — the review is about whether the risk-taking process was sound given what was known at the time, not about whether the position happened to make money, because a breach that worked out is still evidence the limit wasn't respected and could just as easily have gone the other way.

A concrete example: a trader's position moves against them and breaches a $5m hard VaR limit intraday. The system blocks any new orders on that book automatically. Within minutes, the desk head and risk manager are on a call with the trader, who explains the position, but the decision to cut 40% of the size immediately is made jointly by risk and the desk head, not left to the trader alone — and a formal review is scheduled for the next morning regardless of how the position performs for the rest of the day.

A limit breach triggers an automatic flag, removes some or all of the trader's discretion depending on the tier, and generates a review that happens whether or not the position ultimately made money. The review is about process, not outcome — a profitable breach is still a breach.

Related concepts

Further reading

  • Crouhy, Galai and Mark, The Essentials of Risk Management
ShareTwitterLinkedIn