Table of contents
At a glance
What makes a good URS for a GxP system?
A useful URS states the intended use and required business outcome clearly enough to determine whether the system meets it. Identify relevant conditions, roles, data and limits. Separate requirements from design decisions. Risk and GMP impact determine the necessary detail. Acceptance criteria should be testable, but they do not always need a numerical value.
- Start with process and decision-making, not with a product catalog.
- Describe permitted behavior and relevant unacceptable results.
- Separate technical should, justified operational conditions, and technical implementation.
- Ensure requirements are identifiable, aligned, and traceable through changes.
1. Determine what the URS is needed for
The URS specifies, from the end-user perspective, what a system is intended to achieve for a specific use case. It thus serves as a common foundation for selection, configuration, implementation, and documentation. A well-defined requirement already supports planning prior to testing: vendors can raise clarifying questions, business units can identify conflicting expectations, and responsible parties can define the actual scope of needed functionality.
The regulatory framework for this article is Human Medicines GMP. Annex 11 describes user requirements based on documented risks and GMP effects as well as their traceability over the life cycle. Annex 15 deals with URS and functional specifications in the qualification and validation context. Both are GMP guidelines; no form identical for all industries and systems follows.
For other GxP areas or an additional US reference, first identify the applicable requirements. A generic text template "comply with all regulatory requirements" does not substitute for this work. The tables presented here are practical aids for drafting and alignment. They are neither an official template nor a complete URS for a specific product.
2. Coming from process requirement to system limit
First, describe the process in a few clear steps. What information is generated, who handles it, and what decision depends on it? Identify the start and end points of the considered workflow. This enables differentiation between what the system is expected to do and the parallel organizational activities that remain. A software requirement should not obscure an unclear process decision.
Upon transfer of results, the considered process typically begins with a laboratory result designated for transmission and ends with its unambiguously processed status in the target system. Professional evaluation of the result may occur prior to transfer. Legal batch certification is not yet described herein. This boundary prevents a cross-system project from being inadvertently perceived as a complete representation of the quality process.
Maintain deliberate exclusions together with relevant dependencies. If an archiving function is located outside the project but later required for retention, the dependency must still be considered. Existing process descriptions and system overviews can be utilized for this purpose. It is not necessary to fully replicate all background information into the URS.
Sources: [2]
3. Clarify technical sources, responsibilities, and data
Collect the foundation for every critical requirement: approved workflow, applicable directive, known process error, or justified new need. Flag open assumptions. A personal preference for a screen view should not carry the same weight as a check against incorrect result assignment. This facilitates later decision-making in case of conflicting objectives.
Let process owners explain the meaning in the process of data. A number without a unit, a sample identifier without context, or a status without defined meaning may be interpreted differently by the recipient. IT enhances data pathways, identities, and technical dependencies. QA supports the definition of the regulatory scope and the structured handling of requirements and evidence.
During this process, verify who generates, modifies, confirms, and uses information. The required authorizations arise from these responsibilities. Do not provide a generic list of possible roles. Instead, establish a clear and traceable link between actions, the responsible role, and the resulting professional accountability. Annex 11 emphasizes the collaboration of relevant responsible parties; the specific assignment of duties should be defined for your system.
4. Separate scientific requirements from technical implementation
"Only the authorized role for this procedure may change the status" describes a technical requirement. "A blue button triggers a specific database procedure" describes a solution. If a solution is prematurely fixed, a functionally equivalent product function may be unnecessarily excluded. Conversely, a technically sounding specification is not automatically invalid: A binding interface or predefined infrastructure may constitute a justified constraint.
Identify such boundary conditions and their origin. This ensures clarity on which decisions have already been made and where a supplier has design flexibility. Subsequently, in a functional or technical specification, it can be described how the selected system meets the requirement. Documents may be combined based on scope, provided that the different statements remain clearly understandable.
In the review, address two distinct questions: Do we need this result? And is the proposed implementation suitable for achieving it? For example, if a specific documentation requirement is proposed, the rationale, required information, and intended use must be clearly defined prior to establishing a particular documentation format. A general product or GAMP category alone does not adequately address these questions.
5. Translate ambiguous expectations into clear criteria
A viable criterion links the condition, the action, and the expected observation. Add relevant roles and data when they influence the outcome. Then consult a knowledgeable individual who did not author the text: Could you determine whether the requirement is met? If multiple contradictory outcomes could still be considered successful, the criterion typically lacks specificity.
Verifiability does not mean inserting numbers everywhere. For example, an unauthorized status change must be prevented; this does not require an arbitrary percentage. In professionally relevant time limits or measurement ranges, quantitative criteria may be necessary. These values are derived from the specific process, not copied from a generic template.
| Unclear formulation | Testable formulation | Comment on usage |
|---|---|---|
| The system must be secure. | A role without change authorization must not be able to alter the specified result status. | State, role, and relevant access pathways pertinent to use. |
| Data must be accurately transferred. | Order identifier, result value, and unit must be assigned to the correct target order without alteration of meaning. | Define allowed conversions and formats separately. |
| The interface must be fast. | The agreed response must be available within the time window derived from the process. | No finished criterion yet: specify time windows and test conditions before release. |
| Duplicate data should be avoided. | A subsequent message with the same identifier and identical content shall not generate a second result dataset. | Treat content with the same identifier as a separate conflict case. |
| Errors must be displayed. | A rejected transfer must be assignable to the responsible role and must not appear as successful. | Define where the role identifies itself and specify the subsequent actions to be taken. |
6. Justification for test depth and relevant failure cases
Assess the potential implications of an unmet requirement. A misassigned result may warrant greater attention than an unfavorable column width. Consider the actual process, existing controls, and current uncertainties. ICH Q9(R1) outlines a proportionate approach to quality risk management; it does not specify a particular calculation method for each URS.
Derate targeted criteria from significant failure scenarios. What occurs with an unknown identifier, invalid unit, contradictory content, or unauthorized action? A single positive example often does not demonstrate that the process remains under control under such conditions. At the same time, every conceivable operator error does not need to be listed as a separate URS item.
Separate the requirement from the detailed test script. The URS specifies the required behavior and clearly defined criteria. Individual input values, click sequences, and proof forms can then be described in the appropriate test. The linkage remains traceable. This creates a foundation for risk-based testing, without turning the URS into an unstructured collection of test steps.
7. Example: Transfer of results to an ERP – technically evaluate the functional alignment
The following example does not describe a specific software function. A laboratory application is intended to transmit a selected result value to an ERP system. The target task P-104 already exists. Message N-17 contains a result value of 12.5 mg/l. No unit conversion is planned for the considered workflow.
The original requirement is: "The ERP should automatically take over laboratory results." This leaves open how the order is assigned, which units are allowed, what happens with a repeat and who handles errors. The team therefore complements four separate requirements. It also states that the transmission does not replace independent professional evaluation or batch certification.
Prior to selecting a technical solution, the expected outcomes are defined: the value is assigned to P-104; its unit remains mg/l; a duplicate execution generates no additional result dataset; a message with an unknown order is clearly rejected. Whether the supplier utilizes a standard function, configuration, or enhancement is then evaluated during the design phase. This separation enables comparable evaluation of proposals and supporting evidence.
Sources: [2]
8. Requirements and specific expected checks are binding
The following table presents a selection of example URS, not a complete specification. All test actions are proposals. They illustrate how criteria can enable a subsequent evaluation. During implementation, the actual system status, roles, data flow, and other relevant risks would also need to be considered.
Start with a valid message in the example and compare Source and Target. Then send the same content again. Modify the result value at the same message identifier: this conflict must not be overridden by the assumed business rule. Finally, use an unknown order identifier. For each step, the expected observation and allowable output are pre-defined.
If a proposed solution fails on any criterion, do not silently adjust expectations. Investigate whether the issue stems from an implementation error, an inappropriate solution, or a logically flawed requirement. A justified modification remains possible but must be fully supported and traceable, including all relevant documentation and evidence.
| Identifier | Technical Requirement and Criterion | Example audit |
|---|---|---|
| U-01 | Results are assigned only to a uniquely identified existing order; unknown identifiers do not trigger automatic fallback assignment. | Use P-104, then send an unknown identifier; evaluate assignment or rejection. |
| U-02 | The result and unit retain their meaning. This workflow does not silently reinterpret a unit that has not been agreed. | Compare 12.5 mg/l, then send an unsupported unit and check that the specified error handling occurs. |
| U-03 | The same message with identical content generates no additional result record; a identical key with modified content is treated as a conflict. | Check identical repetitions and subsequently altered values with the same message key separately. |
| U-04 | The responsible party identifies rejected transfers with order reference; their status must not indicate success. | Create a rejection and ensure visible assignment, status, and controlled processing capabilities. |
9. Review, Version control, and traceability management
Have the URS reviewed by people who understand the process requirements, risks and technical feasibility. Look for conflicting criteria, undefined abbreviations, open assumptions and unassigned responsibilities. A well-written document can still contain two incompatible process rules. Resolve them before configuration or testing.
Ensure requirements are clearly identifiable and their current status is readily apparent. Link changes to the relevant implementation and supporting evidence. This can be achieved through an appropriate table or system; a specific tool is not required. The URS remains a technical reference, rather than becoming irrelevant after product procurement.
Even an existing system without prior URS requires a clearly defined current requirements basis. The EMA explicitly addresses this scenario. Document the current intended use and evaluate the existing evidence supporting it. Do not date documents retrospectively and do not justify current requirements based on evidence from prior inspections. The further handling of historical gaps is a separate workflow step.
10. Provide concrete preparation for a SME to begin
For the first meeting, provide a clearly defined process, existing work instructions, known issues or difficulties, and an overview of the involved systems. Also include any open decisions. The absence of a finalized product does not prevent you from describing the technical requirements. Individual technical constraints can be added later, once they are properly justified.
The effort is shaped by process clarity, interfaces, location-specific rules, data interpretation, and the number of unexplained decisions. Document length is therefore a weak indicator. First, fully define a key workflow, and jointly agree on formatting and level of detail. This establishes a viable foundation before multiple parties concurrently develop requirements.
- Intended use, operating range and system boundary defined.
- Source of technical expertise and responsible role for each significant requirement clearly identifiable.
- Separate output of technical solution and boundary conditions.
- Acceptance criteria under defined conditions are assessable.
- Considers relevant failure scenarios and existing controls.
- Visible raw values and decisions; clarified prior to binding usage.
- Review, versioning, and linkage to subsequent evidence is defined.
Project experience and collaboration
Write a requirement that you can test
We start with a task that must work reliably in practice. A requirement for a user-friendly system becomes a question about which role must find which record under what conditions. Together, we define an assessable outcome and clarify exceptions. We can refine an existing requirement for a known process. For a new application, we walk through the work with future users first. We distinguish the business requirement from possible technical solutions so alternatives remain open.
Frequently asked questions about Writing a user requirements specification
How does a URS differ from a functional specification?
The URS specifies the intended use and the professional outcome from the end-user perspective. A functional specification provides further detail on how the selected solution fulfills this required functionality. Justified technical constraints may already be included in the URS. What is essential is the clear expression of function; depending on the project, content can be meaningfully consolidated without losing the business requirements in technical details.
Must each acceptance criterion contain a number?
No. "An unauthorized role cannot change this status" is fundamentally assessable once the role, status, and conditions are clarified. For time limits, measurement ranges, or loadings, numerical values can be significantly more relevant. In such cases, use numerically justified values derived from the process and clearly defined test conditions. A randomly invented percentage does not automatically render an ambiguous requirement more burdensome.
Do we need a URS even for unaltered standard software?
Within the GMP scope: yes. Annex 11 requires that supplier documentation for standard products be reviewed to verify that your user requirements are met (No. 3.3). These requirements must be clearly described and supported by risk assessment and GMP implications (No. 4.4). Do not rely on a manufacturer’s catalog for this purpose: clearly define your intended use and required functions with verifiable criteria. Appropriate supplier documentation supports alignment; the product name alone does not validate the suitability of your roles, data, and processes.
Sources: [2]
Can we use the supplier's requirements as a starting point?
Yes, if you assess them against their intended use and adjust accordingly. A supplier list can help clarify functionalities and identify open questions. However, it is not automatically your aligned requirements basis. Identify appropriate transfers, justify relevant additions, and remove any inappropriate specifications from the binding selection. Ensure the origin is traceable.
Who must participate in the URS and approve it?
The department must represent the required outcome; the system owner or IT shall assess dependencies and feasibility. QA supports the regulatory classification and the prescribed documentation pathway. Formal authorization shall be derived from responsibilities and the existing quality management system. A universal number of signatures cannot be inferred. Missing technical or business decisions cannot be substituted by additional signatures.
Do we need to describe every available software function?
The URS should reflect the intended use. Unused functions do not require separate requirements merely because they exist. However, assess relevant dependencies: a centralized authorization function may impact the utilized workflow, even if it does not represent a standalone business process. Justify the scope and appropriate level of detail based on impact, risks, and system interdependencies.
How do we manage an older system lacking original URS?
Determine the currently required functions and the actually intended use and establish an up-to-date requirements basis. Compare this with available evidence and identified open risks. The EMA outlines the approach for existing systems lacking historical URS. A current documentation must neither be retroactively dated nor rely on unverified historical assessments.
What do we do with unresolved values or process rules?
Mark assumptions explicitly, assign an owner and a date for resolution. Drafts may contain open issues. Before relying on a requirement for selection, implementation or acceptance, clarify the criteria that determine that decision. The timing example deliberately leaves the justified limit open and cannot yet serve as an acceptance criterion.
Can a requirement be changed after testing has commenced?
A scientifically justified change is possible but must be carefully controlled. Describe the rationale, affected criteria, implementation consequences, and necessary adjustments to documentation. A failed test must not be considered successful solely through retrospective rephrasing. Distinguish between an implementation error and an actual, legitimate revision of technical requirements, and ensure this determination is clearly and transparently documented.
What do we need to provide, and how can the effort be estimated?
Begin with process flow, relevant work instructions, roles, data pathways, and known open decisions. The effort primarily depends on how much technical scope must first be clarified and how many dependencies exist. A jointly developed key process flow illustrates the required depth. A fixed page limit or arbitrary duration is not a reliable substitute.
Sources and review date
Sources opened on 6 October 2026. The regulatory example framework is Human Medicinal Product-GMP. Annex 11, Annex 15, and Chapter 4 will be applied using the currently linked versions; draft versions will not be issued as additional obligations. Tables, formulations, and interface scenarios are standalone work aids and do not constitute completed product testing. Targeted enhancement alignment on 18 October 2026: Annex 11 Sections 3.3 and 4.4 regarding user requirements for standard products.
- European Commission: EudraLex Volume 4, current overview of GMP guidelines
- EU GMP Annex 11: Computerised Systems, January 2011 revision
- EU GMP Annex 15: Qualification and Validation, Revision 2015
- EU GMP Chapter 4: Documentation, January 2011 revision
- EMA: GMP/GDP Questions and Answers, Section Annex 11, Questions 5 and 6
- ICH Q9(R1): Quality Risk Management, European Step-5 Edition 2023
Sources checked: .
Turn process knowledge into actionable URS
Daniel Herrmann Consulting helps you distinguish business requirements, sharpen criteria, and establish a clear, traceable link between implementation and documentation.
- 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.

