Table of contents
At a glance
How do URS, FS and DS differ in computer system validation?
The URS describes what users need for the intended process. The FS explains how functions will meet those needs. The DS specifies the technical design required. Adapt names and document boundaries to the project while retaining clear requirements, traceable implementation and suitable evidence. Three separate files are not automatically required for every system.
Three levels, three different questions
A User Requirements Specification addresses the question: What outcome must the system enable under intended use? A Functional Specification describes the functional behavior, including permitted states and responses. A Design Specification defines technical decisions, such as data model, interface agreement, or customer-specific implementation. Acronyms are commonly used; their specific application must be clearly defined within the quality management system.
Do not confuse document names with the evidence. Annex 11 requires, among other things, documented user requirements based on risk and GMP implications, along with traceability throughout the lifecycle. This does not imply a general obligation to maintain three equally sized files. For standard software, supplier documentation and a controlled configuration description can cover significant portions. For in-house software, technical specifications will be more comprehensive. What is essential is that all stakeholders understand the same intended use, the same boundaries, and the same acceptance criteria.
What should be included in a good URS
Describe the process, users, relevant data and boundaries. “The system must be GxP compliant” states a goal without specifying testable behaviour. A more specific requirement is “A blocked batch must not be confirmed for delivery in the defined shipping process.” Add who may set the status, which interfaces are affected and how deviations are handled.
Every requirement must have a unique identifier, a clear and understandable statement, and a justifiable means of verification. Distinguish essential requirements from convenience features, without concealing process risks associated with low priority. Operations, recovery, retrieval, permissions, and archive access can also constitute user requirements. Document assumptions: which data originate from another system, and which department is responsible for its quality? Otherwise, the URS will appear to describe a closed process, despite critical steps occurring outside its scope.
Sources: [1]
How the FS transforms requirements into actionable behavior
The functional specification explains workflows, states, and exceptions. For batch locking this means: When is the status verified? What feedback does the user receive? What occurs in the case of simultaneous status changes or an unreachably interfaced system? A description limited to the successful standard case leaves critical error pathways unaddressed. Therefore, the FS should not merely rephrase the URS using different verbs.
It may reference an appropriate standard functionality description and complement it with customer-specific settings. The reference must include product version and a unique section identifier. "See manufacturer's manual" is overly vague when multiple versions and numerous modules are involved. Additionally, verify discrepancies between documented standard functionality and your actual process. If the standard only validates at order entry, but your process requires a recheck prior to dispatch, this difference remains a deliberately addressed requirement.
Sources: [1]
When a DS provides additional clarity
Technical details should be provided where they enable clear understanding and traceability of implementation or subsequent modifications. For a custom-developed interface, relevant details may include field mapping, data types, status codes, logic for repetition, and error logging. For a configured standard application, a released parameter list supplemented with relevant enhancements may suffice. A Data Sheet (DS) should accurately describe the actual system architecture; it does not need to replicate internally inaccessible development details of a SaaS vendor.
Depth is determined by complexity, novelty, supplier evidence, and risk. A technical description is particularly important when multiple teams share responsibility or when changes could have unforeseen impacts. For example, document which component definitively provides batch status. A diagram with an arrow "ERP to warehouse" is insufficient for this purpose. Required are the relevant data, professional interpretation, and behavior under outdated or conflicting information.
Sources: [1]
Worked example following a blocked batch
An ERP system transmits batch status to a warehouse application. URS-017 requires that locked batches shall not be shipped. The FS describes the verification prior to shipping confirmation and the handling of unavailable status information. The DS documents the data source, status mapping, and technical handling of a failed call. The test cases validate these statements using known input data.
In this example, the process holds shipment confirmation and alerts a named owner when the status is unknown or out of date. This is an example process rule. Its suitability must be assessed for each interface. It must be feasible to implement, covered in training and tested. A successful case with a released batch is insufficient. Test status changes during processing, repeat requests and the difference between successful transmission and acceptance by the receiving process.
| Level | Example Specification | Relevant evidence |
|---|---|---|
| URS-017 | Do not dispatch a blocked batch | Attempt dispatch with a blocked batch |
| FS-017a | Testing prior to shipment confirmation | Process flow and critical inspection timing |
| FS-017b | Reset unknown status | Failure and error scenario |
| DS-017a | Assignment of Source Status Values | Mapping against reference data |
| DS-017b | Detect obsolete response | Boundary case for the agreed freshness of the data |
| Operation | Exception responsible to edit | Processing including additional review |
Sources: [1]
Traceability without triple documentation
Link requirement, implementation, risk and test where the relationship arises. A small mapping table can be sufficient. For larger projects, a suitable tool supports maintenance. It is crucial that an examiner gets from a critical requirement to the relevant results and can evaluate a change in the opposite direction. The number of completed table cells says little about this usability.
A requirement may necessitate multiple functions and tests. Conversely, a process validation demonstration may cover several requirements. Do not enforce a forced one-to-one correspondence. However, justify when a requirement is supported solely by document review or supplier test results. Unresolved coverage gaps should remain visible. Copying text into URS, FS, and DS increases maintenance burden and introduces inconsistencies whenever only one of the three versions is updated.
Sources: [1]
Address software standards, SaaS, and in-house development appropriately
In SaaS environments, customer-specific intended use, configuration, and interface integrations are key evaluation points. The provider is responsible for its development and operational services within the agreed scope; the regulated user assesses suitability for their process. Supplier evidence is evaluated for currency, extent, and transferability. Lack of source code access does not justify fabricated design information. Instead, the available architecture and assessed limitations should be described.
For in-house developments, requirements and technical design must be closely aligned. Even an agile project requires controlled decisions, traceable changes, and appropriate validation evidence. Specifications may evolve incrementally, provided that the approved version and its review remain clearly identifiable. A rigid document sequence is no indicator of quality, nor is an unverified backlog. Define in the plan which information must be binding prior to implementation, prior to testing, and prior to use.
Sources: [1]
Checklist for the next specification review
Take a critical requirement and trace it fully through the project. Does the department understand the statement? Is implementation clearly assigned? Have negative cases and operating conditions been considered? Can an independent tester predict the expected outcome prior to execution? Where these questions remain unanswered, additional text is rarely helpful. In such cases, there is a lack of decision, definition, or verifiable linkage.
At conclusion, open items should have a designated responsible party and a defined deadline. Modifications to already approved requirements shall be evaluated for their impact on configuration, test data, training, and existing validation evidence. The historically reviewed version shall be maintained. A revised URS issued retrospectively must not appear as though the specific version had been originally tested and validated. A lean, well-maintained specification package provides greater clarity than three extensive documents lacking credible interconnections.
Project experience and collaboration
Link the required outcome to the function and its technical implementation
With process owners and the implementation team, we examine one requirement. Users describe the needed outcome, and technical staff explain the function and its implementation. We identify decisions already made and assumptions still open. A small standard application may combine these views in one controlled document. Custom development or several suppliers may need clearer separation. What matters is that each view can be traced to the eventual test.
Frequently asked questions about URS, FS and DS
Are URS, FS, and DS always three separate mandatory documents?
No. Document structure and terminology must align with the system and quality system. The necessary information and its traceability remain required. For standard software, appropriate supplier documentation and configuration evidence may cover certain aspects. Consolidation must not obscure responsibilities, approved authorities, or acceptance criteria.
Sources: [1]
How does a URS relate to a customer requirements specification?
In day-to-day project practice, the scope statement and URS often serve similar purposes: they describe what the customer requires. In contrast, a contractor's responsibility statement tends to focus more on the intended implementation and may overlap with functional specifications. The URS for a GMP system must describe the required functions in a risk-based and traceable manner (Annex 11, Section 4.4). Clarify the definitions and content at project inception; a familiar document title alone does not establish completeness or suitability.
Who prepares the FS: customer or supplier?
This depends on the contract and implementation. Typically, the supplier describes the functional behavior, while the user evaluates it against their requirements. Customer-specific configurations require clearly defined responsibilities. A supplier's signature does not replace the user's technical assessment of the process coverage.
Does standard software require a in-house developed DS?
Not automatically. Review existing technical documentation and document relevant configurations, enhancements, and interfaces. Do not request inaccessible manufacturer details. If the actual behavior becomes incomprehensible without additional technical description, supplement it selectively and under controlled conditions.
Can tests substitute for the missing specification?
Tests require a justified expected result. Without clear requirements, there is a risk of merely confirming observed behavior as correct. Existing test cases can help identify specification gaps. The technical rationale must nevertheless be clearly defined and reviewed prior to final assessment.
Sources: [1]
How detailed should a URS be?
So detailed that critical requirements are clearly implementable and verifiable. Describe results, relevant conditions, and limitations. Avoid unnecessary implementation details at the user level. For complex functions, provide clear examples and reference controlled functional or technical specifications.
Sources and review date
As of October 14, 2026. The regulatory classification is based on the listed original sources. Example requirements and assignment matrix are standalone reference tools; adapt them to your specific project.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
- European Commission: EU GMP Annex 15, Qualification and Validation (2015)Qualification and validation, supplemented by the specific framework for computerized systems.
Sources checked: .
How we can support you
Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

