Early in 2012, a portfolio in JPMorgan Chase’s Chief Investment Office was running over its risk limits. Then the bank adopted a new value-at-risk model, and the problem seemed to go away. 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. 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. The institutions that endure have learned to ask what most traders never do: who measures the measurer?
Why VaR Is Not Enough
Value at risk won its popularity by reducing a portfolio’s danger to a single figure. That simplicity is also its weakness. It describes what losses look like on ordinary days and says almost nothing about how bad the worst days can get.
Regulators absorbed the lesson. In its revised market risk framework, the Basel Committee moved bank capital models from VaR to expected shortfall, which measures the average loss once you are already in the tail.
This principle extends well past the banking sector. Serious quantitative trading research subjects risk metrics to the same skepticism it applies to alpha signals. Metrics are tested against historical crises, their assumptions are documented, and any methodological change is independently reviewed. A risk model that cannot be challenged is just an opinion with decimals.
Limit the Execution, Not Just the Exposure
The Flash Crash struck U.S. markets on May 6, 2010. A joint SEC and CFTC report pointed to 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.
Execution limits are now a core part of institutional 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.
Layer the Defenses
Mature risk architectures rarely rely on one control. They stack them.
Pre-trade checks reject orders that violate size, price, or credit limits before those orders leave the firm. 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
Ordinary software problems contributed to the London Whale model’s failure: manual processes, too little testing, and weak change control. In institutional algorithmic trading software development, risk logic now receives the same rigor as the trading engine itself. Changes are version-controlled and peer-reviewed, and a new model runs in parallel more info 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 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:
Was the risk model validated by people independent of its owners?
How does the system behave in the tail, not merely on an average day?
Can an algorithm lose money faster than a human can intervene?
When a limit breaks, does the portfolio change, or does the limit?
Why Risk Numbers Need Doubt
Risk numbers carry a strange emotional power. They let people sleep. They let committees approve. They turn uncertainty into something that looks like knowledge.
That comfort is precisely why institutions surround such numbers with doubt.
Nothing about the London Whale trades was concealed. They were in plain view and measured daily. The danger was never invisible. It was recorded in a number everyone wanted to believe.