spreadsheetssuck.xyz Built with SaaSClaw →
six exhibits · all documented · please do not touch the formulas

The Museum of
Spreadsheet Disasters

Real errors. Real money. Really just cells. Every exhibit below actually happened — a misplaced minus sign, a copy-paste, a file that quietly stopped at row 65,536.

Admission is free. The exits are too — see the gift shop at the end.

88%
of audited spreadsheets contain errors
field audits, Prof. Ray Panko, Univ. of Hawaii
~1 in 100
formula cells is wrong
same body of audits
$6.2B
single worst documented loss
Exhibit A, below

The permanent collection

Curated with sources. No urban legends, no "a friend at a bank" — each one made the papers, the filings, or a Senate report.

Exhibit A · 2012

The London Whale

JPMorgan Chase · Chief Investment Office
−$6.2 billion

A portfolio ballooned into a monster trade while risk reports said everything was fine — because a manually operated spreadsheet was doing the math wrong after a copy-paste.

= sum of rows ÷ 7, instead of ÷ ~500 — volatility halved, alarms silenced

Source: US Senate Permanent Subcommittee on Investigations (2013); JPMorgan task-force report.

Exhibit B · 2020

The Vanished Cases

Public Health England · COVID contact tracing
15,977 people

Positive test results fed into a file in the legacy XLS format — which silently stops at 65,536 rows. Nearly 16,000 infections never reached contact tracers during a surge; tens of thousands of contacts were warned days late.

row 65,537 … +15,976 rows: gone. no error shown.

Source: BBC / Guardian reporting, October 2020.

Exhibit C · 2010

The Austerity Paper

Reinhart & Rogoff · "Growth in a Time of Debt"
a decade of policy

The famous claim that growth collapses past 90% debt-to-GDP was cited by finance ministers on two continents to justify austerity. A grad student replicating it in 2013 found the Excel had omitted years of data — the "collapse" largely an averaging artifact. The authors conceded the coding error.

= AVERAGE(mostly_the_rows_we_remember)

Source: Herndon, Ash & Pollin (2013), UMass Amherst.

Exhibit D · 2003

The Misaligned Bid

TransAlta · US power transmission auction
−$24 million

Bids for transmission contracts were assembled in a spreadsheet. Rows got shifted during a cut-and-paste — so the company attached its bids to the wrong contracts, and overpaid by $24M for capacity it didn't want.

one row off. $24,000,000.

Source: TransAlta disclosures; Globe and Mail.

Exhibit E · 1995

The Missing Minus

Fidelity · Magellan Fund accounting
$1.3 billion, sign-flipped

An accountant omitted a single minus sign, converting a $1.3 billion loss into a paper gain — and quietly inflating the fund's reported returns until the audit caught it. One character. Twelve zeros of meaning.

1300000000.00 ← should read -1300000000.00

Source: contemporaneous press, 1995.

Exhibit F · 2008

The Hidden Rows

Barclays · Lehman Brothers bankruptcy purchase
179 toxic contracts

When Barclays bought Lehman's assets, contracts to be excluded were listed in a spreadsheet — some in rows that were hidden. The team rebuilding the list didn't see them, and Barclays accidentally purchased 179 unwanted contracts it then spent years untangling in court.

rows 49–227: hidden. still binding.

Source: court filings; The American Lawyer.

What's yours costing?

The exhibits are spectacular. Yours is quieter: the hour your team loses every week untangling the sheet — plus the error you haven't found yet.

$10,920 per year, just herding the grid — 312 hours of it

Back-of-envelope estimate: people × hours × rate × 52. Doesn't count the errors — and field audits say there's an 88% chance there's at least one in there.

How common are spreadsheet errors, really?

Field audits of real operational spreadsheets (Prof. Ray Panko, University of Hawaii) find errors in roughly 88% of them, with about 1 in 100 formula cells wrong. That's not carelessness — it's what happens when people hand-build software with no compiler, no tests, and no review.

What's the most expensive spreadsheet error ever documented?

Among publicly documented cases, JPMorgan's 2012 "London Whale" — about $6.2 billion, traced in part to a copy-paste formula error in a manually operated risk spreadsheet.

How do I avoid becoming an exhibit?

Stop treating the grid as a system of record. Move the data into a real app — typed fields, validation, access control. You can watch your own spreadsheet become one, in your browser, in about four seconds: the converter is right here.

The gift shop.

You've seen where the grid leads. Take home the exit instead: drop your spreadsheet on the converter and watch it become a real app — search, forms, stats — without uploading anything, ever.

Escape the museum → Build real apps with SaaSClaw