What regulators expect when you assess a software supplier
Most regulated companies buy their computerised systems rather than build them. That makes the supplier a central part of your validation story, and an inspector will ask how you decided to trust it. This article sets out what the regulations and regulator guidance expect from a supplier assessment, what a sound assessment answers, and how to decide between a paper review and an audit.
What the regulators say
The EU GMP Annex 11 (2011) has a dedicated clause on suppliers and service providers (clause 3). Its main points are:
- When third parties provide, install, configure, integrate, validate, maintain or modify a computerised system, or retain data, formal agreements must exist, with clear statements of the third party's responsibilities. IT departments should be treated in the same way (clause 3.1).
- The competence and reliability of a supplier are key factors when choosing a product or service provider, and the need for an audit should be based on a risk assessment (clause 3.2).
- Documentation supplied with commercial off-the-shelf products should be reviewed by regulated users to check that their user requirements are fulfilled (clause 3.3).
- Quality system and audit information about suppliers or developers of software should be made available to inspectors on request (clause 3.4).
- The regulated user should take all reasonable steps to ensure the system has been developed under an appropriate quality management system, and the supplier should be assessed appropriately (clause 4.5).
The PIC/S guide on good practices for computerised systems (PI 011-3) adds the practical side. It says the regulated user should define a requirement specification before selection and carry out a properly documented supplier assessment and risk analysis for the system options. It describes this risk-based approach as useful evidence for an inspector (section 4.3). It also warns that complex analytical instrumentation is difficult to assess without the supplier's help, and that inspectors will be interested in the firm's assessment of the supplier's critical automated features (section 4.4).
Responsibility stays with you
The draft revision of Annex 11 puts this more bluntly. It was released for consultation between 7 July and 7 October 2025, and it is still a draft at the time of writing (the Commission's EudraLex Volume 4 page still lists the 2011 text). Nothing in it is a requirement today, but it shows the direction. It says that relying on a vendor's qualification of a system, a service provider, or an internal IT department does not change the requirements. The regulated user remains fully responsible, based on the risk to product quality, patient safety and data integrity (draft section 7.1).
The same draft says that, according to risk and system criticality, the regulated user should conduct an audit or a thorough assessment to decide whether the vendor's procedures and deliverables are adequate, and whether they can be used rather than repeating the work (draft section 7.2).
What a sound assessment answers
The sources do not give a fixed questionnaire, but together they point to a handful of questions. A useful assessment should be able to answer each of them in writing.
- Does the supplier develop and support the product under a quality system? PI 011-3 says reliability is attributable to the quality of the software engineering processes: design, coding, verification testing, integration and change control, including after-sales support (section 5.1).
- Is the certification relevant to what you are buying? PI 011-3 says a recognised quality management system can give confidence, but the scope of certification needs to be relevant to the application, and for critical systems the certificate alone is unlikely to be the final judge (sections 11.3 to 11.5).
- Does the supplier's track record support trust? PI 011-3 refers to supplier and developer reputations and trading histories, and expects procedures and records showing how and on what basis suppliers were selected (section 11.2). Prospective purchasers should also look at known limitations and problems for particular packages or versions, and the adequacy of corrective actions (section 5.1).
- Does the documentation show the product meets your requirements? Annex 11 clause 3.3 expects you to review the supplier's documentation against your user requirements.
- What does the contract commit the supplier to? The draft Annex 11 lists contract topics for service providers: the activities and documentation to be provided, reporting and oversight, conditions for supplier audits, support during inspections, how issues are resolved, communication of quality and security problems, an exit strategy so you keep control of your data, and how new system versions are released and tested before release (draft section 7.5).
- Can you get the data back out? The exit strategy point above is easy to overlook until the day you need it.
Paper review or audit?
Annex 11 clause 3.2 puts the decision on risk. PI 011-3 says the same: the need for a supplier audit should be linked to the regulated user's risk assessment and quality assurance standards, and the business and GxP criticality of the application determine the nature and extent of any assessment (section 5.1 footnote 5 and section 5.2). It also notes that a minority of suppliers are not responsive to requests for an audit.
A sensible way to read that is as a ladder:
| Situation | Reasonable approach |
|---|---|
| Low GxP impact, widely used product | Documented review of the supplier's information, certification and your own requirements |
| Moderate impact, configured product | Questionnaire plus review of the supplier's quality system and validation documentation |
| High impact or complex, such as analytical instruments or systems holding critical data | Audit, or a shared audit or alternative that gives equivalent information, with the rationale recorded |
The table is our practical reading of the sources, not a regulatory list. What matters is that the level you chose matches the risk and that you can say why.
Using the supplier's testing
You do not have to repeat everything the supplier has already tested, but you do have to take responsibility for relying on it. The draft Annex 11 says the regulated user should carefully review and authorise supplier documentation, consider whether it covers the version actually implemented, and decide whether it supports GMP and company processes as they are or whether parts should be repeated (draft section 9.9).
FDA's software assurance guidance, which covers medical device production and quality system software and not pharmaceutical GMP, takes a similar line. It recommends a risk-based analysis of the software vendor and lists the kinds of information that can feed it: on-site audits where feasible, certifications such as ISO and SOC reports, the vendor's software development and quality assurance practices, and the vendor's data integrity controls such as audit trails and the ability to keep and copy records. It also acknowledges that an on-site audit may not be feasible, and that a combination of other information may be used instead.
Cloud and service providers
Many suppliers now run the system for you rather than just selling software. Annex 11 clause 3.1 already covers third parties who maintain a system through remote access or retain your data, so the same assessment applies. The draft revision adds two practical points. Where you rely on a service provider or an internal IT department to operate a system, you should keep effective oversight against agreed service levels and key performance indicators (draft section 7.3). And the documentation for the activities involved should be accessible and explainable from your own facility, with the vendor's help if needed (draft section 7.4). In other words, if an inspector asks a question about a hosted system, "the vendor handles that" is not an answer you can leave to the vendor alone.
Keep the evidence together
Annex 11 clause 3.4 expects supplier quality system and audit information to be available to inspectors on request. In practice, keep one supplier file per critical system containing:
- the selection record and the reasons for choosing this supplier
- the risk assessment that set the level of assessment
- the questionnaire, audit report or certification review, with any actions and their closure
- the contract or quality agreement
- your review of the supplier's documentation against the user requirements
- a note of what you relied on from the supplier and what you tested yourself
- the date of the next review
Key takeaways
- Annex 11 says the need for a supplier audit should be based on a risk assessment, and that supplier quality information must be available to inspectors.
- Using a supplier does not move your responsibility. The draft Annex 11 states this plainly, and the current one implies it.
- A certificate is a starting point. Check that its scope covers the product and the application.
- Agree contract terms early, especially audit access, inspection support and how you get your data out.
- If you rely on the supplier's testing, review it, record the reliance and decide what you still need to verify yourself.
- Keep one supplier file per critical system.
Further Reading
- European Commission, EudraLex Volume 4, Annex 11: Computerised Systems (2011): clauses 3 and 4.5 on suppliers and service providers.
- European Commission, stakeholder consultation on Annex 11 revision: the draft revised text, including section 7 on supplier and service management.
- PIC/S PI 011-3, Good Practices for Computerised Systems in Regulated GxP Environments: sections 4, 5 and 11 on supplier assessment. PIC/S has said this document is under revision.
- FDA, Computer Software Assurance for Production and Quality Management System Software: the section on assessing the software vendor, for medical device manufacturers.
Want articles like this first?
Members get each new article before it is published here, plus the CSV 101 course, the templates and SOPs library, Regulatory Watch and Ask Iain.
This article is general information for people who work in regulated industries. It is not legal or regulatory advice. Check the regulator's own publications and your own quality system before you act on it.