Home
Technical GuideProcess & TechnologyPublished Nov 13, 2026

How to Select and Qualify Software for a Pharmaceutical Plant: From User Requirements to Vendor Assessment

By the PharmaCountry team

349
1

A vendor-neutral, risk-based path for buying GxP software: decide what the system must own, write requirements you can test, assess the vendor in proportion to the risk, agree the contract, and know what you still have to validate yourself.

How to Select and Qualify Software for a Pharmaceutical Plant: From User Requirements to Vendor Assessment

Key takeaways

  • Buying GxP software is a supplier-qualification decision as much as a feature decision. You can rely on a vendor's work, but you cannot hand over responsibility for it.
  • Start with what the system must own and how much risk it carries, then write requirements you can test. "Part 11 compliant" is a claim, not a requirement.
  • Assess the vendor in proportion to risk: a questionnaire, a documentation review or an audit, depending on how critical the system is and what you plan to rely on.
  • The contract is a control. It should fix responsibilities, release notification, audit rights, inspection support and an exit that lets you keep your data.
  • Cloud and SaaS change who does the work, not who is accountable. Vendor-controlled releases make change notification and exit terms central.
  • Count the whole cost. The licence is the visible part; validation, every upgrade, interfaces and exit are not.
On this page

Most pharmaceutical software projects are described as IT projects. They are better described as supplier relationships with a quality system attached. The system will hold or process records that your inspectors, your Qualified Person or your customers rely on, and the people who build and run it work for someone else.

This guide gives a practical path from "we need a system" to "we signed a contract and know what we still have to do". It sits next to the guide on who owns what across ERP, MES, WMS, LIMS and QMS: that guide tells you which system should hold which record, this one tells you how to choose and qualify the system. It is general and vendor-neutral, and every company draws the lines a little differently.

1. Responsibility stays with you

Whoever builds or hosts the software, the manufacturer stays accountable for the records it keeps. The main sources say this in different ways:

  • EU GMP Annex 11 expects a formal agreement whenever third parties are used to provide, install, configure, integrate, validate, maintain, modify or retain a computerised system, and the agreement must include clear statements of the third party's responsibilities. IT departments are treated as analogous. It also expects the regulated user (you, the manufacturer) to take all reasonable steps to ensure the system was developed under an appropriate quality management system, and the supplier to be assessed appropriately [1].
  • The 2025 draft revision of Annex 11 goes further. It states that relying on a vendor's qualification of a system, a service provider, or an internal IT department does not change the requirements, and that the regulated user remains fully responsible based on the risk to product quality, patient safety and data integrity [2]. It is a consultation draft, so check the final text when it is published.
  • In the US, 21 CFR 211.68 requires appropriate controls over computers and related systems, so that changes to master production and control records or other records are made only by authorised personnel, and input and output are checked for accuracy [3].

The management consequence is simple. Name a process owner and a system owner before you write a request for proposal. Annex 11 expects close cooperation between the process owner, system owner, Qualified Persons and IT [1]. A project that starts as an IT purchase and meets QA only at validation usually discovers its requirements too late.

Three activities that are easy to blur. Buying software involves three different pieces of work, usually owned by different people, and mixing them is a common source of gaps:

Activity The question it answers Where this guide covers it
Software selection Does the product fit our process and our requirements? Sections 2, 3, 4, 6 and 10
Supplier qualification Can we trust this vendor's quality system, development, release and support? Sections 5, 7 and 9
Computerised system validation Is the system, as implemented and configured here, fit for its intended use? Section 8

A vendor's statement that its product suits GxP use belongs to the first two. It is an input to the third and never a substitute for it, because the implemented system, with your configuration and your procedures, is yours to validate.

2. Before you shortlist: scope, owner and risk

Three questions come before any vendor demonstration.

What must this system own? Use the ownership matrix exercise from the systems landscape guide: list the data types, name the one system that holds the official record, and mark the consumers. A new system that duplicates a record another system already owns is a boundary problem, not a feature.

What is the risk? Annex 11 asks that decisions on the extent of validation and data integrity controls rest on a justified and documented risk assessment, applied throughout the life cycle with patient safety, data integrity and product quality in mind [1]. FDA's Part 11 scope guidance takes the same line, with a blunt example: validation would not be important for a word processor used only to generate SOPs [4]. The same guidance says Part 11 will be interpreted narrowly, so fewer records are considered subject to it [4]. Establish which of your records and signatures are actually in scope rather than assuming every digital record is. A simple, illustrative way to sort candidates:

Typical use Example Effort you should expect
Records or decisions that directly affect product quality or data integrity Electronic batch record, LIMS holding official results, QMS deviations and CAPA, systems that record batch release Highest: formal vendor assessment, full requirements, documented testing, strict change control
Supports GxP processes but does not hold the official record Document management, training management, maintenance and calibration scheduling Moderate: assessment and testing proportionate to what is relied on
No GxP record or decision General office tools, dashboards that only read governed data Low: document the rationale

This table is a starting point. Your own risk assessment decides, and the same product can land in different rows depending on how you use it.

Where does it fit in the inventory? Annex 11 expects an up-to-date list of systems and their GMP functionality, and, for critical systems, a description of the physical and logical arrangement, data flows and interfaces [1]. Decide now where the new system will appear, because the interfaces are part of the risk.

3. Write requirements you can test

Annex 11 expects user requirements to describe the required functions, to be based on documented risk assessment and GMP impact, and to be traceable throughout the life cycle [1]. In practice a good user requirement specification (URS) has four properties: it is specific, testable, ranked (must, should, could), and traceable to a test.

Group the requirements so nothing is forgotten:

Group What it covers
Process functions The workflows the system must support, in your words, not the vendor's
Data integrity Audit trail, record linking, time stamps, who did what
Security and access Roles, authentication, administrator control
Integration Interfaces, data checks, direction of data flow
Regulatory features Electronic signatures, batch release restrictions, where relevant
Availability and continuity Backup, recovery, downtime procedure
Data lifecycle Retention, retrieval, export, archiving
Vendor and support Release notification, support hours, documentation

The difference between a weak and a testable requirement is usually one sentence:

Weak Testable (with the Annex 11 clause it supports)
"The system shall be Part 11 compliant." "Each change to a GMP-relevant record shall be recorded with user, date, time, old value, new value and reason, and be viewable in a readable audit trail report" (Annex 11 §9)
"The system shall be secure." "Access shall be limited to authorised persons by role, and the system shall record the identity of whoever enters, changes, confirms or deletes data, with date and time" (§12)
"The system shall support e-signatures." "An electronic signature shall be permanently linked to its record and include the date and time it was applied" (§14)
"The system shall support batch release." "Where the system records batch certification, only Qualified Persons shall be able to certify release, and the person releasing shall be identified and recorded using an electronic signature" (§15)
"The system shall integrate with our ERP." "The system shall send the batch status to ERP automatically, and data exchanged between the two shall be checked for correct entry and processing" (§5)
"Data shall be exportable." "Records, including audit trail, shall remain accessible, readable and accurate for the full retention period, and be exportable in a readable form" (§7, §17)

A requirement is only useful once it has a test and an acceptance criterion. One worked example, tied to the batch-status point in the systems landscape guide:

Element Example
Requirement "Stock in quarantine status shall not be issuable to production."
Test Create a stock lot in quarantine status, then try to post a goods issue to a production order.
Acceptance criterion The system rejects the transaction, the lot keeps its quarantine status and, where your risk assessment calls for it, the attempt is logged.
Evidence kept The executed test script with result, date, tester and reviewer, plus the log or audit trail entry.

Write the acceptance criterion before you run the test. "The system behaved sensibly" is not a criterion.

Two habits save a lot of trouble. Do not copy the vendor's brochure into your URS, because you will then test the brochure rather than your process. And keep the number of "must" requirements small enough that you can actually test each one.

4. What are you actually buying?

How much you can rely on the vendor depends on what kind of software it is. ISPE's GAMP 5 Second Edition (2022) puts weight on service providers and encourages regulated companies to involve suppliers and leverage their knowledge, experience and documentation where possible, alongside iterative development methods and the use of critical thinking [5]. A practical reading:

What you are buying Example What you can lean on the vendor for What stays with you
Standard product used as delivered A tool with fixed functions Product documentation, release information Review it against your URS (Annex 11 §3), test intended use
Configured product A LIMS, QMS or MES set up to your workflows The vendor's testing of the core product Verifying your configuration, workflows, roles and reports
Custom or bespoke build A one-off application Little; you need the vendor's development process in view Formal assessment and reporting of quality across the whole life cycle (Annex 11 §4.6)
Vendor-operated service (SaaS) A hosted application Infrastructure operation, availability, release process Intended-use validation, oversight, data access, exit (see section 9)

Real systems mix these. A configured product with a few custom reports and a vendor-hosted database is three different things in one box, and each deserves its own level of scrutiny.

Equipment with embedded software, such as the control system on a tablet press, belongs here too. Put the software requirements (audit trail, user roles, data export) into the equipment specification, and ask the equipment supplier for the same software evidence you would ask a software vendor. The Manufacturing Equipment & Utilities categories on PharmaCountry list suppliers by equipment type.

5. Assess the vendor in proportion to risk

Annex 11 says the competence and reliability of a supplier are key factors when selecting a product or service provider, and that the need for an audit should be based on a risk assessment. It adds that quality-system and audit information about software suppliers should be made available to inspectors on request [1]. That points to three levels of assessment, used in proportion:

Level What it involves Typically enough when
1. Questionnaire and public evidence A structured questionnaire, certificates, references from other regulated users The system is lower risk, standard, and you rely on little of the vendor's documentation
2. Documentation review and meeting Quality manual, development and release procedures, test summaries, release notes, security documents, and a call with the vendor's quality contact Moderate risk, or a configured product where you will reuse the vendor's testing
3. Audit (remote or on site) Examining the vendor's processes and records directly High risk, custom code, vendor-hosted GxP data, or you plan to rely heavily on the vendor's validation deliverables

These are typical patterns, not prescribed ones. What matters is that the level is chosen on a documented risk basis and that the result is filed where an inspector can find it.

What to ask, whichever level you use:

Area Questions worth asking
Quality system Is there a documented quality management system? Who owns quality, and can we talk to them?
Development How are requirements, design, coding and testing controlled? How are defects tracked and prioritised?
Release How are versions tested before release? How are customers told what changed, and how far in advance?
Configuration Can we see what the standard product does and what is customer-specific? How is customer-specific code controlled?
Data integrity How are audit trails, time stamps and user identity handled? Can audit trails be switched off, and by whom?
Security How is access controlled? How are vendor staff accessing the system (remote access) controlled and logged?
Hosting and subcontractors Where is the data? Which subcontractors touch it? How is a change of hosting provider notified?
Continuity What are backup and recovery arrangements, and have they been tested?
Vendor viability What happens to support and to our data if the vendor is acquired or stops trading? Are there arrangements such as source-code escrow for custom code?
Support Hours, response and resolution times, and named escalation path
Regulated-industry experience Which regulated customers use it, and has it been inspected?

A word on certificates. An ISO 9001 or ISO 27001 certificate shows that a management system exists within the scope on the certificate. It does not tell you whether the product supports your intended GxP use. Likewise, a statement that a product is "Part 11 compliant" cannot be verified by itself, because the outcome depends on how you configure and use it. Ask what the product provides, then test it.

6. Test before you commit

Before signing, run a scripted demonstration or trial built from your top requirements rather than the vendor's showcase. A good script includes:

  • creating a record, changing it, and reading the audit trail afterwards;
  • applying an electronic signature and trying to change the signed record;
  • logging in with different roles and attempting something each role should not be able to do;
  • exporting a complete record, with its audit trail, in a readable form;
  • one failure path (wrong input, failed interface, lost connection);
  • upgrading a test environment to a new release and seeing what changes.

If you are replacing an existing system, plan the data migration early. Annex 11 expects validation to include checks that data are not altered in value or meaning when moved to another format or system [1]. Migration is where projects most often discover that two systems did not mean the same thing by the same field.

7. The contract and quality agreement

Annex 11 requires formal agreements with clear statements of responsibility [1]. The 2025 draft revision is more specific about what a contract with a service provider should cover. Even as a draft, its list is a useful checklist [2]:

Contract item Why it matters
Activities and documentation to be provided You can only rely on what is promised
Company procedures and regulatory requirements to be met Ties the vendor's work to your quality system
Regular, ad hoc and incident reporting, with service levels and response and resolution times Gives you something to oversee
Conditions for supplier audits Keeps audit rights from being renegotiated later
Support during regulatory inspections Inspectors may ask about the vendor's processes
Resolution of issues raised in operation, audits and inspections Avoids open-ended findings
Communication of quality and security issues You hear about problems from the vendor, not from users
An exit strategy by which you keep control of your data Prevents lock-in at the end of the contract
The release process for new versions, and your chance to test before release Protects your validated state

Add three items the draft does not itemise but a buyer should: who owns the data and where it is held, how a change of subcontractor or hosting location is notified, and how long the vendor will support a version.

Retention deserves a specific line. In the EU, batch documentation must be kept for one year after expiry of the batch or at least five years after certification by the Qualified Person, whichever is longer [6]. A subscription that ends in three years, with no way to export records, is a problem you will meet on a specific date.

8. What you still validate yourself

Using a vendor's documentation saves work, but it does not remove yours. After selection, plan at least these activities, with the depth set by risk:

  • Intended-use testing against your URS, in your configuration.
  • Configuration verification: workflows, roles, reports, calculations and limits.
  • Traceability: a matrix linking each requirement to the test that proves it, so that nothing is untested and nothing is tested without a reason [1].
  • Interfaces and data migration, including checks that data are not altered in value or meaning [1].
  • Backup and restore: regular backups, with the integrity of backup data and the ability to restore it checked during validation and monitored periodically [1].
  • Review of results before release: validation documentation includes reports on any deviations observed [1]. Decide on each open item, with its risk, before the system is released for GxP use, rather than carrying it silently into operation.
  • Procedures and training for users, administrators and the people who review audit trails.
  • Change and configuration control: any change to the system or its configuration happens in a controlled way under a defined procedure [1].
  • Business continuity: for systems supporting critical processes, an alternative arrangement such as a manual process, adequately documented and tested [1].
  • Periodic evaluation: confirm the system remains in a valid state, looking at functionality, deviations, incidents, upgrade history, performance, reliability, security and validation status [1].
  • Archiving and retrieval: archived data checked for accessibility, readability and integrity, and retrieval tested when the system changes [1].

For the validation life cycle itself, see the guides on computer system validation using the GAMP 5 risk-based approach and computerized system qualification. For laboratory systems in particular, LIMS implementation considerations covers the lab-side detail.

9. Cloud and SaaS

The 2011 text of Annex 11 does not use the words cloud or SaaS [1]. Its principles still apply, but the practical questions change, because the vendor now runs the system and often controls when it changes.

  • Release cadence. A SaaS vendor may update the product on its own schedule. You need advance notice, release notes and, if the system is critical, a test environment where you can assess a release before it reaches your live system.
  • Shared responsibility. Infrastructure, application and your configuration are looked after by different parties. Write down who qualifies, operates and monitors each layer.
  • Subcontractors. The SaaS vendor may itself rely on a hosting provider. You are assessing a chain, not one company.
  • Data access and location. You need to be able to reach your records, including audit trails and metadata, for the full retention period, wherever they are stored.
  • Exit. Decide on the first day how you will get your data out in a readable form on the last day.

The 2025 draft Annex 11 addresses this directly: it expects the regulated user to oversee service providers against agreed service levels and key performance indicators, to ensure documentation is accessible and explainable from its own facility, and to agree an exit strategy and a process for releasing new versions that lets it test them first [2]. ISPE's second edition of GAMP 5 added appendix material on cloud computing and other newer topics [5].

10. Compare options: scorecard and total cost

A scorecard turns a long evaluation into a decision you can explain to management and to an inspector. A simple, illustrative version:

Criterion Example weight
Fit with "must" and "should" requirements 30%
Vendor quality evidence (assessment result) 20%
Data integrity and security 15%
Total cost over the life of the system 15%
Lifecycle and support (release, notification, exit) 10%
Integration with existing systems 10%

Two rules keep the scorecard honest. First, gates before scores: an option that fails a "must" requirement, or has a critical finding in the vendor assessment, drops out regardless of its total. Second, record who scored what and why, so the decision survives staff changes.

Total cost is where many business cases are weakest. The licence or subscription is the visible part. The rest is easy to leave out:

  • initial validation effort, and the vendor assessment itself;
  • impact assessment and regression testing for every release;
  • interface build and maintenance;
  • training, periodic review and archiving;
  • migration, both in and out.

A cheaper product that needs heavier validation, or a SaaS system with frequent releases, can cost more over five years than it appears to at signing.

11. Red flags

Any of these is a reason to slow down:

  • The vendor declines audits or documentation access without a reason, or only answers with marketing material.
  • "Compliant" is asserted but nobody can describe how.
  • Audit trails can be switched off, or edited, by administrators.
  • You cannot export complete records with their audit trails.
  • Releases arrive without notice or release notes.
  • Defects are not tracked, or the vendor cannot say how a release was tested.
  • Customer-specific code sits inside the standard product without separate control.
  • Subcontractors who touch your data are not disclosed.
  • There is no named quality contact.
  • The contract has no exit terms.

12. The whole path in ten steps

  1. Name the process owner and system owner.
  2. Define what the system must own, using the ownership matrix.
  3. Do a documented risk assessment and decide the effort level.
  4. Write a URS with ranked, testable, traceable requirements.
  5. Identify what you are buying (standard, configured, custom, service).
  6. Shortlist, then assess each vendor at the level the risk justifies.
  7. Run a scripted demonstration or trial against your top requirements.
  8. Score the options with gates, including total cost.
  9. Agree the contract and quality agreement, including release, audit, inspection support and exit.
  10. Plan your own validation, procedures, training, periodic review and archiving before go-live.

FAQ

Do I have to audit every software vendor? No. Annex 11 says the need for an audit should be based on a risk assessment [1]. A lower-risk standard tool may need only a questionnaire and a document review. Record the reasoning either way.

Can I rely on the vendor's validation documents? Partly. Annex 11 expects you to review the documentation supplied with commercial off-the-shelf products and check that your user requirements are fulfilled [1], and GAMP 5 Second Edition encourages leveraging supplier knowledge and documentation where possible [5]. You remain responsible, and you still verify your configuration and intended use.

Is an ISO 27001 or ISO 9001 certificate enough? No. It shows that a management system exists within its scope. It does not show that the product supports your GxP use, so it is one input to the assessment, not a substitute for it.

Does FDA's Computer Software Assurance guidance apply to drug manufacturers? That guidance, in its February 2026 version (which supersedes the September 2025 one), gives recommendations on computer software assurance for computers and automated data processing systems used in medical device production or the quality management system, in the context of 21 CFR Part 820 [7]. Drug manufacturers should start from 21 CFR 211.68 [3], Part 11 and FDA's scope guidance [4], and check with their regulatory function.

What about software that ships with equipment? Treat it as part of the equipment purchase. Put audit trail, user roles and data export requirements into the equipment specification, and ask for the supplier's software documentation.

Who should be on the selection team? At least the process owner, system owner, QA, IT, whoever will validate the system, and procurement. Where the system touches batch certification, include the Qualified Person early.

Sources

[1] European Commission. EudraLex Volume 4, Annex 11: Computerised Systems (2011). https://health.ec.europa.eu/system/files/2016-11/annex11_01-2011_en_0.pdf
[2] European Commission. Stakeholders' consultation on EudraLex Volume 4: Chapter 4, Annex 11 and Annex 22 (draft revised Annex 11, section 7, 2025; consultation draft, not final). https://health.ec.europa.eu/consultations/stakeholders-consultation-eudralex-volume-4-good-manufacturing-practice-guidelines-chapter-4-annex_en
[3] US eCFR. 21 CFR 211.68: Automatic, mechanical, and electronic equipment. https://www.ecfr.gov/current/title-21/section-211.68
[4] US FDA. Part 11, Electronic Records; Electronic Signatures: Scope and Application (guidance for industry, 2003). https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application
[5] ISPE. GAMP 5: A Risk-Based Approach to Compliant GxP Computerized Systems, Second Edition (2022). https://ispe.org/publications/guidance-documents/gamp-5-guide-2nd-edition
[6] European Commission. EudraLex Volume 4, Chapter 4: Documentation (clause on retention of batch documentation). https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-4_en
[7] US FDA. Computer Software Assurance for Production and Quality Management System Software (guidance, February 2026). https://www.fda.gov/regulatory-information/search-fda-guidance-documents/computer-software-assurance-production-and-quality-management-system-software

This guide is general information, not regulatory or legal advice. Scores, weights and classifications are illustrative. The 2025 draft revision of Annex 11 may change before it is published in final form. Which assessment level and which controls apply to your system should follow your own quality system and risk assessment.