FINANCEOngoing practice92% confidence

The Concealment Spiral

Small hidden errors compound into catastrophic losses through delayed escalation

Problem it solves

delayed error escalation

Best for

Anyone in a high-stakes execution role where errors are reversible only if escalated immediately — traders, ops staff, project leads.

Not ideal for

Low-stakes creative work where iteration and hidden experimentation are productive.

Overview

Why this framework exists

The Concealment Spiral describes how a small, recoverable mistake becomes an unrecoverable disaster when the person responsible chooses to hide it rather than escalate. Each hour of delay raises the personal cost of disclosure, which in turn makes the next hour of concealment feel rational. The spiral is not about greed — it is about the asymmetry between immediate embarrassment and deferred catastrophe.

Leeson's frame is that the decisive moment is always the first one: day one, minute one. Once a loss is hidden for a single market session, the actor becomes complicit in concealment, and every subsequent decision is made from a worse position with worse options. The framework matters because it isolates the specific cognitive trap — the belief that 'just one more session' will reset the situation — that turns ordinary humans into rogue traders, fraudulent founders, or managers who hide bad news from boards.

Applied as a control, the framework forces immediate, time-boxed escalation regardless of size: the cost of disclosing a £10K error is finite; the cost of disclosing a £862M error is terminal.

Core principles

5 total
  1. The cost of disclosing an error compounds faster than the error itself.
  2. Once you hide a loss for one session, you become complicit in the concealment, not just the original mistake.
  3. Belief that you can recover the loss is what makes the next loss possible.
  4. Successfully recovering a hidden loss once is more dangerous than failing to — it manufactures false confidence.
  5. The decisive moment is the first one; every subsequent decision is made from a strictly worse position.

Steps

6 steps
  1. Define escalation thresholds before the error happens
    Set numeric and time-based triggers in advance: any loss above £X must be reported within Y minutes, regardless of recovery prospects. This converts a judgement call under pressure into a pre-committed rule.
    Pro tipMake the threshold low enough that you'll cross it routinely — desensitise the team to escalation so it's not a career event.
  2. Escalate the moment the threshold is hit, not when the situation feels resolvable
    The instinct will be to wait one session to see if the market recovers. That instinct is the spiral. Escalate first, recover second — the two are not alternatives.
    WarningIf you find yourself calculating how to disclose later with less embarrassment, you are already in the spiral.
  3. Make the receiving party competent to act
    Leeson's first escalation failed because the local head of ops had no derivatives experience and the London escalation was seven hours away. Ensure the escalation chain has someone reachable, awake, and technically competent at all times.
    Pro tipIf your escalation contact is not available within the time it takes for the situation to materially worsen, the chain is broken.
  4. Force daily reconciliation between independent records
    Compare your traded position to the exchange's record every single day. Two numbers should match; any discrepancy is the early warning of concealment, even unintentional.
    Pro tipReconciliation must be done by someone whose bonus does not depend on the trader's profitability.
  5. Treat one-off recoveries as warning signs, not validation
    If a hidden loss is fully recovered, the operator now believes recovery is possible — and the next concealment will be larger. Use successful recovery as the trigger for an audit, not a celebration.
    Pro tipThe Friday Leeson recovered £20M was the single most dangerous day of his career, not the safest.
  6. Audit funding requests against legal and capital limits
    When the operator starts asking for more capital to 'cover positions,' check the request against the bank's legal lending limits. Leeson held 13× the Bank of England's legal subsidiary limit — visible to anyone running the calculation.
    WarningIf a treasury department is sending money to a subsidiary without checking the position it funds, the spiral is already terminal.

Checklist

Saved in your browser

Examples

3 cases
The £10K error that became £862M

A junior trader on Leeson's Singapore desk made a £10K error. He attempted to escalate, failed to reach a competent contact in London, and chose to wait one session. By close that day it was £90K. By year-end 1992 it was £5M. By 1994 it was £500M. By February 1995 it was £862M and the bank collapsed.

OutcomeBarings, the UK's oldest merchant bank, was sold to ING for £1. Leeson served four and a half years in Singapore prison.
The 1992 Deloitte audit that should have caught it

At year-end 1992, the loss stood at $5M. Leeson asked the London Treasury for $5M, posted it on 30 September, received it on 1 October, creating a $5M intercompany discrepancy. Deloitte attributed it to FX and signed off.

OutcomeA single competent audit reconciliation would have ended the spiral at $5M instead of £862M three years later.
The Friday recovery in May 1993

Leeson recovered £20M of hidden losses in a single options expiry. The desk celebrated at the Hard Rock Cafe. On Monday morning, a 50-lot order error went straight back into the 88888 account — but now with the belief that recovery was possible.

OutcomeThe successful recovery manufactured the confidence that fuelled the next two years of concealment until collapse.

Common mistakes

5 traps
Treating the first hidden loss as a one-off rather than a category change
The first concealment changes you from someone who made an error to someone running a fraud. This is invisible to the actor in the moment but obvious in retrospect.
Believing 'pressure to perform' explains the spiral
Leeson is explicit: pressure is a tiny part. The actual driver is fear of failure plus an unbroken belief that recovery is one trade away. Mis-diagnosing the cause leads to wrong controls.
Building escalation procedures that punish the messenger
If escalating a £10K loss is career-ending, no one will escalate. The control fails by design. Make small escalations routine and rewarded.
Letting the same person trade and settle
Leeson controlled both the trading book and the back-office settlement of his own trades. Separation of duties is the single most-violated control in concealment cases.
Mistaking the absence of complaints for the absence of problems
Auditors, regulators, and treasury all interacted with the 88888 account and saw nothing. Lack of detection is not evidence of compliance — it is often evidence of poor controls.

Origin story

How this framework came to be

Leeson traces the spiral to a single morning in Singapore in 1992. A junior trader on his desk made a £10K error. He told the local head of operations, who didn't understand futures and asked him to refer it to London — but London wouldn't be at their desks for seven hours. With the market about to open, Leeson chose to wait and see if it would recover. It got worse. By 3pm he was now complicit, and the next escalation conversation was no longer about a £10K mistake but about a concealment.

He rebuilt the framework retrospectively in prison, recognising that every doubling of the loss corresponded to a doubling of his personal cost of confession — which is what kept him from confessing for nearly three years until £862M.

Source

Traced to primary
Source · PODCAST
The Rogue Trader Who Lost £862 Million
Nick Leeson · 2025
Open source →

Related frameworks

Browse all Finance →