Early in 2012, a portfolio in JPMorgan Chase’s Chief Investment Office was running over its risk limits. Then a new value-at-risk model arrived, and the problem seemed to vanish. The new model cut the portfolio’s reported risk roughly in half.
Months afterward, the trades that came to be called the “London Whale” had lost more than $6 billion. The bank’s own internal review found that the new model depended on spreadsheets fed by manual copy-and-paste steps, and that it contained calculation errors.
The trades were dangerous. The more unsettling failure was the number that said they were safe.
This contradiction sits at the heart of algorithmic trading risk management. Every risk system is also a model: designed by people, written in software, and capable of error. Institutions that survive have learned to ask a question most traders never consider: who measures the measurer?
The Trouble With One Number
Value at risk became popular because it compresses a portfolio’s danger into one figure. The same simplicity is its greatest weakness. VaR describes losses under ordinary conditions and says little about how bad the worst days can be.
Regulators learned this too. The Basel Committee’s revised market risk framework replaced VaR with expected shortfall in bank capital models. Expected shortfall asks a harder question: once you are in the tail, what does the average loss look like?
The principle reaches well beyond banks. Serious quantitative trading research subjects risk metrics to the same skepticism it applies to alpha signals. Each metric is tested against historical crises, its assumptions are documented, and any change to its methodology receives independent review. A risk model that cannot be challenged is merely an opinion with decimals.
Limit the Execution, Not Just the Exposure
U.S. markets experienced the Flash Crash on May 6, 2010. The joint SEC and CFTC report identified a key trigger: a sell program of 75,000 E-mini S&P 500 futures contracts, executed by an algorithm that targeted a share of trading volume without regard to price or time.
Nothing about the position was exotic. The execution simply had no constraints.
Institutions now write execution limits directly into AI trading system development. These include price collars that block orders far from the prevailing market, participation caps, order-rate throttles, and checks that pause an algorithm when conditions change faster than it was designed to handle. Exposure limits tell you how much you can lose. Execution limits decide how fast.
Defense in Layers
No mature risk architecture trusts a single control. Controls are stacked.
At the first layer, pre-trade checks stop orders that break size, price, or credit limits before they leave the firm. During the day, real-time monitoring tracks positions and losses against hard limits that halt trading and soft limits that trigger escalation. Afterward, post-trade review reconciles what actually happened against what was meant to happen.
Each layer is built on the assumption that the layer before it could fail. That assumption is not pessimism; it is engineering.
Engineer the Risk Software
The London Whale model failed partly through ordinary software problems: manual processes, insufficient testing, and weak change control. Institutional algorithmic trading software development now treats risk logic with the rigor usually reserved for trading engines. Changes are version-controlled and peer-reviewed, and a new model runs in parallel with the old one before it takes over.
Firms also run historical crises back through their systems to confirm that controls actually fire. Here AI trading infrastructure consulting often adds the most value, since an outside team with no attachment to the existing design can test whether safeguards hold under conditions their builders never imagined.
When a Limit Breaks
A limit is only as strong as the response when it more info is crossed. In disciplined institutions, a breach triggers escalation to people independent of the trading desk, and the default response is to reduce risk, not to revisit the limit.
In risk management, nothing is more dangerous than a breach that gets explained away.
A Four-Question Risk Check
Before trusting any risk framework, ask:
Who validated the risk model, and were they independent of its owners?
How does the system behave in the tail, not merely on an average day?
Could an algorithm lose money faster than a human can step in?
When a limit breaks, does the portfolio change, or does the limit?
The Comfort of a Number
There is a strange emotional force in a risk number. It lets people sleep, lets committees sign off, and turns uncertainty into something resembling knowledge.
That comfort is exactly why institutions surround them with doubt.
The London Whale trades were never hidden. They sat in plain view, measured every day. The danger was not invisible. It was written into a number everyone wanted to believe.