At the start of 2012, a portfolio held by JPMorgan Chase’s Chief Investment Office kept breaching its risk limits. Then a new value-at-risk model was introduced, and the problem appeared to disappear. The new model roughly halved the portfolio’s reported risk.
Within months, the trades later known as the “London Whale” had generated losses of more than $6 billion. When the bank investigated, its own review found that the model ran on spreadsheets fed by manual copy-and-paste steps, and that its calculations contained errors.
The trades themselves were dangerous. Far more unsettling was the figure that called them 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. The institutions that endure have learned to ask what most traders never do: who measures the measurer?
Why a Single Number Fails
The appeal of value at risk is that it condenses a portfolio’s danger into one number. Its simplicity is also its flaw. 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 applies far beyond banking. Rigorous quantitative trading research doubts its risk metrics as much as it doubts its alpha signals. Every metric is tested against historical crises, its assumptions are written down, and changes to its methodology go through independent review. An unchallengeable risk model is just an opinion with decimals.
Constrain How You Trade, Not Only What You Hold
The Flash Crash struck U.S. markets 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.
The position was not exotic. The execution was unconstrained.
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 set how much you can lose. Execution limits set how fast.
Stack the Controls
Mature risk architectures rarely rely on one control. They stack them.
Before an order leaves the firm, pre-trade checks reject it if it violates size, price, or credit limits. Intraday monitoring follows positions and losses in real time, using hard limits that stop trading and soft limits that trigger escalation. Post-trade review then compares what happened with what was supposed to happen.
Each layer assumes the one before it might fail. That assumption is not pessimism. It is engineering.
Treat Risk Code as Critical Code
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.
Give Breaches Authority
A limit is only as strong as the response when it is crossed. At disciplined institutions, a breach is escalated to people independent of the trading desk, and the default response is to cut risk rather than revisit the limit.
The riskiest moment in any risk framework comes when someone explains a breach away.
The Four-Question Audit
Before you trust a risk framework, ask four questions:
Who validated the risk model, and were they independent of its owners?
What does the system do in the tail, not just on an average day?
Could an algorithm lose money faster than a human can step more info in?
When a limit is breached, which changes: the portfolio or the limit?
The Number That Feels Like Safety
Risk numbers hold an odd emotional power. They help people sleep and let committees approve. They make uncertainty look like knowledge.
Institutions surround these numbers with doubt for exactly that reason.
The London Whale trades did not hide. They sat in plain view and were measured every day. The danger was not invisible. It was written into a number everyone wanted to believe.