Validation Is Not a Documentation Exercise: What a Coffee Cup Teaches Us About Intended Use

September 14, 2026
KurtsK

Risk-Based Quality in Practice

Author: Jonatan Irizarry, Founder and CEO, GlobalNEP

Modern validation begins with a clear understanding of intended use, process risk, and the critical functions that protect product quality and the patient.

Validation should demonstrate understanding

Across regulated industries, validation is still too often treated as a documentation exercise. Teams begin by listing the expected deliverables: a validation plan, user requirements, specifications, protocols, traceability matrices, and a final report. Each document may be necessary. Yet when the package itself becomes the objective, the organization can produce an impressive archive without demonstrating that it understands how the process or system protects product quality and the patient.

Modern quality systems require a different starting point. Validation should be a knowledge-centered lifecycle activity grounded in intended use, process understanding, quality risk management, and objective evidence of fitness for use.

Information is not the same as knowledge

An organization can maintain document repositories, requirements databases, protocols, SOP libraries, and extensive electronic records and still lack usable knowledge. Information management preserves what was written. Knowledge management preserves why the process exists, how its elements interact, where risk resides, which functions are critical, and what evidence supports continued confidence.

When that rationale is missing, requirements become generic, risk assessments become superficial, traceability loses meaning, and testing becomes disconnected from the regulated outcome.

Begin with the most important question

A colleague once used a simple interview question for CQV professionals: 'Validate this coffee cup.' Many people immediately ask for drawings, material specifications, protocols, or test cases. But the first question should be much simpler: What will the cup be used for?

A cup intended for hot coffee has different material, thermal, handling, and safety requirements than one used for cold liquid, outdoor service, a child, decorative photography, or an industrial process. The object has not changed. Its intended use has changed - and intended use changes the risks, critical characteristics, and evidence required.

The same logic applies to regulated systems

A useful intended-use statement forces the team to describe how a facility, utility, equipment item, automation function, or computerized system will operate within the actual process. It should help the team ask:

• What outcome is the system expected to support?

• Which product quality attributes and process parameters could be affected?

• Which functions or features protect the process or detect loss of control?

• What users, environments, interfaces, and operating conditions matter?

• What could go wrong, and how significant would the consequence be?

Without that discussion, the team cannot intelligently decide which requirements matter most, where supplier or engineering evidence can be leveraged, or which verification activities provide meaningful assurance.

Risk should shape the validation strategy

ASTM E2500 and ICH Q9(R1) support an approach in which process knowledge and risk guide the identification of critical aspects and the degree of rigor applied. This does not eliminate documentation or testing. It improves their scientific basis.

Not every function has the same relationship to product quality. Not every requirement deserves identical scrutiny. Not every test contributes equal assurance. Effort should be proportionate to intended use, the significance of the risk, the uncertainty involved, and the strength of available controls and evidence.

Performing the risk assessment after requirements are frozen is backward

A common failure mode is to finalize requirements first and conduct the risk assessment later as a confirmation exercise. If the organization has not understood the relevant CQAs, CPPs, process vulnerabilities, operating context, and data needs, it cannot know which requirements deserve priority. The risk assessment must inform the requirements and design, not merely decorate them.

Validation is knowledge operationalized

A strong validation package should allow a knowledgeable reviewer to understand what the system is intended to do, which risks matter, why particular controls were selected, and what evidence demonstrates that those controls perform as intended. The documentation is important because it preserves and communicates that rationale - not because completing the template is the regulated outcome.

The practical test
Before asking which protocol or document comes next, ask whether the team can clearly explain intended use, critical functions, associated risks, selected controls, and the evidence needed to demonstrate fitness for use.

Questions leaders should ask

• Can our team explain intended use in operational and product-quality terms?

• Were requirements prioritized using process knowledge and risk before they were approved?

• Can every critical test be traced to a meaningful requirement, risk, or control?

• Are we leveraging appropriate supplier, engineering, and commissioning evidence?

• Does lifecycle governance preserve the rationale when the process or system changes?

Validation is not the generation of documents. It is the demonstration that we understand the process, understand the risks, know which functions matter, and possess objective evidence that the system remains fit for its intended use.

Related services: Quality Risk Management | Regulatory Compliance | Digital Transformation | Project Delivery Discuss your challenge
GlobalNEP helps life sciences organizations design risk-based CQV and system-assurance strategies that connect intended use, process knowledge, criticality, and evidence. Contact us to discuss a focused assessment or a broader program.

GlobalNEP is a technical and scientific consulting firm helping life sciences organizations strengthen quality, 

compliance, data, digital systems, and regulated project delivery through practical risk-based methods.
ASTM International organizational member, E55 Committee | Certified Minority Business Enterprise
Copyright GlobalNEP LLC. All rights reserved.
Power by
ekselence-logo