November 16, 2026

What should an end-user computing (EUC) policy include?

A spreadsheet inventory tells you what exists. It doesn't control what happens inside those files. Here's the rest of what a real EUC policy needs, and why regulators are drawing this line now.

An end-user computing (EUC) policy should cover five things: which spreadsheets count as critical, validation of data as it’s entered, a recorded history of who changed what and when, access control over who can edit which fields, and evidence a reviewer can check without taking anyone’s word for it. Most EUC policies only do the first of these.

Why this is worth writing down now

On 17 April 2026, the US Federal Reserve, together with the OCC and FDIC, issued SR 26-2, replacing the older SR 11-7 model risk guidance. Commentary on the new guidance describes a structure that separates traditional statistical models from a “non-model tools” category covering things like spreadsheets and deterministic calculations — placing most spreadsheets outside formal model validation rather than inside it. In the UK, the PRA’s SS1/23, effective from 17 May 2024, takes a related but distinct approach: it explicitly includes end-user computing applications and calculators within its scope, and expects firms to include EUCs in their model inventory where they meet the relevant definition.

Read together, the direction is the same even where the mechanics differ: a spreadsheet that drives a real financial, operational, or compliance decision doesn’t automatically get the scrutiny of a formal model, but it doesn’t get a free pass either. The expectation lands on a separate EUC policy — and that expectation isn’t limited to banks. The same logic applies to any organization running a critical process on spreadsheets outside the regulated sectors these rules were written for.

The five things a real EUC policy covers

What makes a spreadsheet critical. Not every file in the business needs this level of attention. The ones that do: anything feeding a number into a financial close, a regulatory filing, a production batch release, a capacity plan, or a board report.

Validation at entry. A value outside the expected range, in the wrong format, or inconsistent with a related field should be caught the moment it’s typed — not discovered weeks later during a review.

A change record. Every edit needs an author, a timestamp, and ideally a reason. This is what separates a correction, which is visible and traceable, from a silent overwrite, which isn’t.

Access control. Not everyone who can open a spreadsheet should be able to edit every field in it. Who can change what should be defined deliberately, not left to whoever has the file open.

Evidence a reviewer can check. An auditor, a regulator, or an internal reviewer shouldn’t have to trust that a spreadsheet’s numbers are correct. They should be able to see the validation rules that were applied, the change history, and who had access — without relying on the file itself as the only record.

An inventory alone only covers the first item on this list. It tells a reviewer which spreadsheets exist. It does nothing for the other four.

EUC in banking: what regulators expect

Banks treat certain spreadsheets as model-risk scope because the number they produce — a provision estimate, a liquidity input, a capital calculation — feeds a decision with the same consequences as a formal statistical model, even when the spreadsheet itself is just a calculation, not a model in the technical sense. That’s the logic behind both SR 26-2’s “non-model tools” category and the PRA’s SS1/23: the control doesn’t disappear because the tool isn’t formally a model, it moves into a separate EUC policy instead.

Across both pieces of guidance, the recurring expectations are: an inventory of which spreadsheets are critical and why; clear ownership, so someone is accountable for each one; access control over who can view or edit it; change and version control, so every edit is attributable and reversible; validation of what goes into it, so bad inputs are caught rather than propagated downstream; and reconciliation plus an audit trail, so a reviewer can check the output against its source without relying on the file’s own say-so.

The five controls above map onto this almost directly: criticality definition is the inventory step; validation at entry and access control are named outright; a change record covers version control and much of the audit-trail expectation; and evidence a reviewer can check closes the reconciliation gap. None of this requires replacing the spreadsheet — it requires controlling what happens inside it.

For how this compares with tools that stop at the inventory step, see IT-TIDY vs. spreadsheet risk / EUC tools; to test these controls on one process directly, a 30-day pilot runs it end to end.

A worked example

Consider a capacity-planning spreadsheet a telecom network-operations team updates every month: inputs from several regional teams, formulas rolling up into one utilization forecast, feeding a report that shapes real infrastructure decisions. Under an inventory-only approach, this spreadsheet gets flagged, logged, and assigned an owner — useful, but it still relies entirely on each regional planner entering the right number in the right format. A full EUC policy instead defines what a valid entry looks like for each field, blocks or flags anything outside it at the moment of entry, and keeps a record of every change — so when a number in the final rollup needs to be checked six weeks later, there’s an actual history to check, not just a spreadsheet and a hope.

What this looks like with IT-TIDY

IT-TIDY governs all five of these inside the Excel files a team already uses — no migration required. Validation rules are defined field by field and enforced at entry. Every change is recorded with who, what and when. Access is controlled per field and per role. And in a group with roughly 100 foreign subsidiaries running cross-border procurement planning, this approach took data correct at first submission from 39% to 97%, and cut central corrections by 85%, following a Lean Six Sigma (DMAIC) method on a certified path.

If you want to see where your own critical spreadsheets stand against these five controls, the free 60-second check-up gives an initial risk score. To test entry-level control and a real audit trail on one process directly, a 30-day pilot runs it end to end. For the broader case against inventory-only tools, see IT-TIDY vs. spreadsheet risk / EUC tools, and for the related three-step framework behind this policy, see spreadsheet risk management: three steps, not just an inventory.

Sources:

end-user computingEUC policyIT governancespreadsheet risk
← Back to blog

FAQ

What should an end-user computing (EUC) policy include?

Five things: a clear definition of which spreadsheets count as critical, validation of data as it's entered, a recorded history of who changed what and when, access control over who can edit which fields, and evidence a reviewer or auditor can check without having to trust the file.

Do banking regulators still treat spreadsheets as models?

The US Federal Reserve's SR 26-2 guidance, issued 17 April 2026, replaces the older SR 11-7 and places tools like spreadsheets and deterministic calculations in a separate, non-model category rather than treating every one as a formal model. That doesn't mean no controls apply — it means the controls come from an EUC policy, not model validation.

Does this only matter for banks?

No. The regulatory language is bank-specific, but the underlying expectation — that a spreadsheet driving a real decision needs some form of documented control — applies to any critical process, in any industry, that still runs on Excel.

Is an inventory of spreadsheets the same as an EUC policy?

No. An inventory identifies which spreadsheets exist and who owns them. A policy also says what happens inside those spreadsheets: what counts as a valid entry, what gets recorded, and who can change what.

Can we write this policy without replacing our spreadsheets?

Yes. The controls — validation, a change record, access rules, auditable evidence — can sit behind the Excel files a team already uses, rather than requiring a migration to new software.

What is EUC in banking?

In banking, EUC stands for end-user computing: spreadsheets, calculators and similar tools built and run by business teams rather than IT, that feed into financial, regulatory or risk decisions. Regulators such as the US Federal Reserve (SR 26-2) and the UK PRA (SS1/23) expect banks to manage these under a dedicated EUC policy covering ownership, access, validation, change history and reconciliation, even when the tool isn't a formal statistical model.

Find out how exposed your spreadsheets are

Ten questions, 60 seconds, an instant risk score.

Start the free check-up →