October 20, 2026
What is end-user computing risk, and how do you control it without banning spreadsheets?
EUC risk is what happens when critical business logic lives in spreadsheets nobody governs. Banning spreadsheets doesn't fix it — governing them does.
End-user computing (EUC) risk is the exposure a company carries when a critical calculation, decision or report depends on a spreadsheet that IT doesn’t control. You control it by governing the spreadsheet where it already lives, not by trying to ban it.
Why banning spreadsheets doesn’t work
Most EUC policies start the same way: identify the critical spreadsheets, then migrate them into a “proper” system. In practice, that migration project is slow, expensive, and often resisted by the team that built the model, because the spreadsheet was solving a problem faster than any system IT could procure. Years later, the spreadsheet is usually still there, now even less visible, because it went underground after the ban.
The risk isn’t that spreadsheets exist. It’s that nobody validates what goes into them, nobody records who changed what, and nobody can prove which version is correct when it matters.
What EUC risk actually looks like
A formulation sheet with no range checks on a dosage field. A capacity model edited by five regional teams with no single current version. A consolidation template re-keyed by every subsidiary, with corrections made by hand and no record of the original entry. None of this shows up as a system outage. It shows up as a wrong number that nobody catches until it’s expensive — or until someone asks for evidence of who entered it.
A governance layer, not a rebuild
The alternative to banning or inventorying spreadsheets is governing them in place: validating values as they’re typed, recording every change automatically, locking closed periods, and measuring how reliable each field is over time. Teams keep the models they already trust. IT gets the audit trail and the control it needs, without a migration project. That’s the approach behind IT-TIDY — see how it works or read about the risk tools built for banking compliance that stop at inventory instead of active control.
It isn’t hypothetical
The cost of ungoverned records isn’t abstract. In 2026, Britain’s electricity system operator, NESO, was investigated after whistleblowers alleged that control-room staff were told to keep “live documents” with no version history during periods of grid stress — removing the audit trail a regulator or the public could later request. The independent investigation by Eversheds Sutherland found no evidence that records were altered or concealed to avoid scrutiny, but it still identified governance and control issues for NESO to address (NESO, Ofgem). The allegation alone shows what’s at stake: a document with no version history is a document nobody can later prove was accurate.