Spreadsheets remain the most widely used and least controlled computerised tool in regulated companies, and inspectors know exactly where to look for the weaknesses.
Why spreadsheets are different
A spreadsheet is both the software and the data. Anyone with access can alter a formula, overwrite a result or save over a file, often without leaving a trace. That makes it a particular concern for data integrity, which regulators address through ALCOA+ principles and through EU GMP computerised-system expectations.
Decide whether validation is needed
Not every spreadsheet needs full validation. A simple list used for reference differs from a workbook that calculates a release result or a pharmacovigilance metric. The first step is an inventory and a risk assessment based on the impact on product quality, patient safety and data integrity, and on the complexity of the calculations.
Controls that make a spreadsheet defensible
- Lock and protect cells holding formulas and macros, leaving only designated input cells editable.
- Document the intended use, the calculation logic and the version in the file itself.
- Test calculations against independent results, including boundary and invalid values.
- Store the master in a controlled location with restricted write access and a defined change process.
- Keep a record of who ran the spreadsheet, when and with which inputs, or use a system that captures this automatically.
Maintaining control over time
Validation is not a one-off event. Changes to formulas, new versions of the spreadsheet application and migration to new platforms all need assessment. Periodic review should confirm that the file is still used as intended, that protection settings remain intact and that no uncontrolled copies are circulating.
When to replace the spreadsheet
If a spreadsheet has grown into a critical process tool, with multiple users, complex logic and regulatory impact, a validated system with an audit trail is usually safer and cheaper in the long run than perpetual spreadsheet controls.
Related reading
- Computerised System Validation: A Risk-Based Lifecycle That Survives Inspection
- Data Integrity and ALCOA+: Turning Audit Trail Review into a Real Control
- Computer Software Assurance: What FDA’s Final CSA Guidance Changes
How PQRA helps
PQRA inventories and risk-ranks spreadsheet use, designs proportionate controls and test approaches, and advises on when a validated application is the better answer.
Ready to talk it through? Contact the PQRA team.


No responses yet