Computerized Systems · 8 min read

Spreadsheet Validation: Define the Use Before You Test the Formulas

Start with the record and the decision, then define the workbook boundary and evidence needed for its actual use.

Start with the record and the decision

Before validating a spreadsheet, describe what people rely on it to do. A planning worksheet, a calculation supporting a controlled decision and a retained electronic record present different questions. Identify the process, users, inputs, outputs and record owner. Ask qualified quality/regulatory personnel which underlying requirements and electronic-record obligations apply.

Part 11 scope depends on the records and applicable FDA requirements, rather than the mere presence of a spreadsheet. FDA’s scope guidance explains that underlying predicate-rule obligations continue [V1]. Do not treat every workbook as equivalent or assume a protected cell establishes compliance.

Fix the validation boundary

Identify the workbook version, approved location, macros, formulas, linked files, external data and export/reporting steps. Include the operating environment and intended users. If the spreadsheet depends on another workbook or a manual copy step, show that dependency rather than testing an isolated file that nobody actually uses.

State allowed changes and excluded uses. Decide who can edit formulas, approve a release, enter data or review a result. These are proposed project-scoping questions; the required controls depend on the actual use.

Challenge the calculation and the workflow

Translate intended functions into testable examples with expected outcomes established independently of the workbook under test. Include ordinary cases, boundary values, invalid or missing inputs, units, rounding, error handling and relevant lookup or macro behavior. Copying the spreadsheet’s own result into an expected-result column does not create independent evidence.

Test the complete workflow where it matters: data entry, review, approval, saved record and transfer to another system. Record who performed the check, the version tested and the observed outcome. Investigate deviations before accepting the system for its defined use.

Include the record lifecycle

Ask where the authoritative record resides, how versions are distinguished, how access is managed and how retained records can be recovered and understood. Where electronic signatures are used, assess the actual signature and record relationship rather than relying on a typed name in a cell. Evaluate applicable Part 11 controls against the current regulation and actual context [V2].

Keep backup/recovery, retention and change responsibilities explicit. A backup existing somewhere is different from evidence that a needed record can be restored and interpreted.

Agree the handover

A practical validation package can include intended use, requirements, risk rationale, test evidence, deviations, approval, operating instructions and change triggers. This is a proposed evidence structure, not a universal template mandated for every workbook. Make the package proportionate and obtain appropriate specialist review.

  • Project brief: process and record; decision supported; workbook/version; calculations/macros/interfaces; user roles; applicable requirements; test approach; expected records; review/approval; change and recovery responsibilities.
  • Submit a private validation-project brief with system type, intended use and timing. Do not send confidential workbooks through a general initial inquiry.

Primary sources

This project-scoping framework is original educational guidance, not a regulation or a software certification. FDA guidance contains nonbinding recommendations; applicable regulations and predicate rules remain distinct.

Describe the system, intended use and timing. Keep confidential records, credentials and workbooks out of the initial inquiry.

Discuss a private validation project

Information published on ValidationEngineering.com is educational and informational. It is not legal or regulatory advice and is not a guarantee of regulatory compliance or of any inspection outcome. Organizations remain responsible for their own quality decisions.

FAQ

Frequently asked questions

Does password protection validate a spreadsheet?
No. Protection settings address only part of a broader intended-use and control assessment.
Must every formula receive the same test effort?
Set effort from the function and consequence of failure, with a documented rationale and appropriate review.
Can a vendor template replace our intended-use assessment?
No. Evaluate the template within your configured workflow and responsibility boundaries.
What about a workbook with no macros?
Inputs, formulas, links, decisions and record handling can still warrant assessment.
When should the assessment be revisited?
Define triggers such as formula, interface, configuration, environment or intended-use changes.
Can a typed name be treated automatically as a compliant signature?
No. Evaluate the actual signature implementation and applicable requirements.