Practical guides · Practical guide

Which evidence can you use from a supplier’s validation package?

A supplier validation package can support local testing when its evidence applies to the intended use. Link each item to the requirement, release, configuration and observed result. A CAPA example shows when evidence can be reused, when a condition needs checking and what still requires a local test.

Table of contents

At a glance

Which evidence can you use from a supplier’s validation package?

Suitable evidence can include completed supplier tests with traceable results and relevant development or configuration records. Map each item to your own requirements and assess the version, environment, results and deviations. Blank templates do not demonstrate successful testing. An overall package status does not show which specific tests were carried out. Reuse evidence that applies to your intended use and test the remaining gaps.

  • Evaluate each accepted validation protocol against a corresponding requirement and its acceptance criteria.
  • An appropriate supplier and an appropriate individual batch release address different questions.
  • Different environments do not automatically exclude transfer; their significance must be established.
  • Document the transfer conditions, remaining tests, and subsequent change evaluation.

1. Separate the supplier assessment decision from the acceptance decision.

The supplier assessment evaluates whether a supplier and its capabilities are adequately managed. This involves a focused determination: Which specific evidence supports a particular requirement of your system? A positively assessed software vendor may provide documentation that is inappropriate for a specific interface. Conversely, a partner report may already comprehensively address your individual workflow, including negative test cases. Such assessments can only be determined by examining the content. An audit report may also contain specific, relevant evidence; however, its credibility depends on the actual scope of the audit.

The regulatory example framework for this article is Human Medicinal Product-GMP. Annex 11 is a GMP guideline; the currently linked version addresses, among other things, user requirements, supplier documentation, and risk-based validation. Annex 15 provides additional considerations regarding the use of external data and the suitability of third-party inspection protocols. Its qualification examples do not constitute a blanket approval for any cloud-based application.

The following matrices are intended as internal reference tools. They neither replace the evaluation of the specific regulatory area nor your duly authorized final decision. Separate determination of applicability is required for medical devices, other GxP areas, or an additional US context. Acquisition of a package does not constitute a general compliance assurance.

Sources: [1] [2] [3]

2. Start with your requirement and the required result

First, clearly define the specific assertion you intend to validate. "CAPA works" is too vague for this purpose. Are you seeking evidence for release authorization, for effectiveness assessment, for time-based calculations, or for the unchanged transfer of a dataset? Each of these scenarios may require different prerequisites and supporting documentation. Reference a specific, unambiguous requirement identifier with version number, rather than associating the manufacturer's test merely to a general module heading.

Describe in addition the intended use: involved roles, data used, activated functions, relevant interfaces and dependencies. Document which erroneous outcome would compromise the process. From this, it follows precisely how you must evaluate test results and transferability. The mere number of existing test cases provides little insight.

Explicitly identify requirements outside the scope of the delivery package. This ensures that an organizationally governed decision is not inadvertently treated as a software function. This prework can link existing URS, process descriptions, and configuration lists; an additional comprehensive document is not automatically required. Annex 11 requires traceable user requirements, but does not specify a particular tabular format for their presentation.

Sources: [2]

3. Identify the package, product status, and actual delivery contents

Capture document identification, revision, date, and associated product status. Distinguish planned inspections from completed protocols, summaries from individual results, and product documentation from implementation records. A file named "Validation Report" may contain very different contents. What is essential is whether the required relationship between the tested function, prerequisites, and results remains traceable.

A real-world organizational example is provided by Qualio: The publicly accessible manufacturer page "Validation Resources" outlines Feature-ValPacks following Launch Train or Release and differentiates documentation areas. Historical records are also available. This reveals a version-specific filing structure. However, the publicly viewable overview page neither confirms the content of a specific test report nor verifies its suitability for your configuration.

Therefore, verify the actually received delivery scope. It may include standard functions, configured workflows, or customer-specific features. Do not request additional testing solely because such tests were performed externally. Similarly, avoid an indefinite reference to "current documentation" if the alignment to the assessed system version remains unclear.

Sources: [6] [3]

4. Lead an commented line of decision per proof

The worksheet links each requirement to its supporting record. Use separate rows or subentries when multiple requirements can be assessed independently. You can reference the same document several times while keeping a single copy. Distinguish evidence that is suitable in principle from conditions you still need to verify before using it.

A takeover decision should end in clear language. For example: "Document P-17 covers the described negative case for configuration K-0; for K-1, the identical control logic still requires confirmation." This makes an open assumption visible and assigns ownership. This is more informative than a simple green field indicating "package available."

Own work aid: Minimum content of a specific acceptance decision
FieldWhat you enterWhy does the decision change
Own requirement Identification, Revision, Acceptance Criteria and Intended Use A general product function is not automatically the required outcome.
External evidence Document revision, test case, and actually performed step A template alone does not yet prove successful implementation.
Version and Configuration Reviewed status; Comparison with your usage Deviations may relate to the reviewed logic or be reasonably insignificant.
Test environment Relevant roles, data, services, and interfaces Differences are evaluated based on their impact.
Results and Deviations Observation, acceptance evaluation, linked findings The overall status must not obscure conflicting individual results.
Transfer condition What must be demonstrated regarding the use of the ledger Identify the assumption as a condition that needs testing.
Outstanding evidence Specific open question, existing enhancement or targeted test The supplement follows the gap, not universally the entire package.
Decision Rationale, Responsible Party, Release Status and Reason for Reissue The subsequent reader will recognize the scope and limits of the adoption.

Sources: [2] [3]

5. Review of Completed Results and Actual Deviations

For relevant test cases, trace the chain of conditions through action to observation and finally to evaluation. An expected result in an empty template is still not an observed result. A screenshot may serve as evidence of a key observation, but it often does not alone indicate the specific role, configuration, or input combination used. Conversely, a screenshot is not necessarily the most appropriate form of evidence for every assertion.

Review open deviations to assess their significance for your requirements. Has a failed step been removed only in scope? Does a known defect affect the function being used? Is a correction linked to a compatible version and supporting evidence? Completion of a supplier assessment does not automatically indicate that customer-specific impacts have been resolved.

Missing details initially trigger a targeted follow-up inquiry. A supplementary report or a logically justified explanation may exist. Only when the required evidence does not emerge from such an inquiry shall a suitable addition be determined. Criteria for foreign protocols and the handling of deviations are primarily outlined in Annex 15; the scope and application to the computerized system remain to be clearly justified.

Sources: [3] [2]

6. Evaluate differences based on their impact on the result

Product name does not imply identical validation basis. Specifically compare functional state, relevant parameters, role model, time zones, data formats, and integrated services. A difference is neither automatically insignificant nor automatically a grounds for exclusion. Inquire whether the difference could alter the validated mechanism, its input data, or the technical outcome.

At a system interface, a supplier may have demonstrated the receipt of valid messages, while your partner may have additionally verified field mapping, repetition, and error handling. Together, these documents can provide substantial coverage of the process. Where only the specific authorization assignment remains unresolved, a targeted verification of that element is more efficient than a full reexecution of the interface testing.

Document the rationale even for differences assessed as insignificant. Reference, for example, a validated configuration or an approved comparison. The level of detail required shall be determined by the affected function. Annex 11 addresses the suitability of test environments; accordingly, it does not impose a universal requirement that external and production environments must be identical in every detail.

Sources: [2]

7. Example: Step-by-step walkthrough of CAPA acceptance

The following scenario does not constitute a completed product test and is not a statement regarding Qualio. A company plans to implement a CAPA process on system version S-2. Its internal requirement CAP-01, Revision 1.2, permits closure only after documented effectiveness assessment. The reference configuration is designated K-0, while the intended configuration is K-1. These designations are for explanatory purposes only.

The approved manufacturer's report P-17 describes a final test without effectiveness evaluation and then an acceptable conclusion. Prerequisites, observations and evaluation are understandable; there are no open reported deviations for this function in the scenario. A confirmed configuration comparison shows that K-1 uses the relevant final condition unchanged. This can be taken over with this proof for CAP-01.

However, the own role "QA decision-maker" is different from the reference role. The CAP-02 requirement for permission has not yet been completed. In addition, the desired reminder process uses working days during the assumed sample test uses calendar days. Both differences are processed separately. An appropriate partner proof could close them already; otherwise you plan exactly the missing tests.

Sources: [2] [3]

8. Takeover, condition and residual test separately decide

The second support document builds on the example. It illustrates why a package may be immediately useful for certain requirements and insufficient for others. "Supplement" initially means obtaining a missing validation evidence; only thereafter is it determined whether a new test is required.

When testing is required, write down the open question prior to execution. In the workday example, a weekend and the employed holiday calendar would represent targeted conditions. Expected timelines shall be derived from the agreed business rule. The result must not be defined only after observing system behavior.

Example: CAPA acceptance decision for system status S-2
Own requirementEvidence assumed to be availableJustified decisionRemaining evidence
CAP-01: Effectiveness assessment prior to completion P-17 evaluates negative and positive cases in K-0; the comparison confirms unchanged conditions in K-1. Accept for this condition. No repetition without additional cause; reference comparison and report.
CAP-02: Completion only by authorised role P-17 checks reference role; assignment of own role is missing. Mechanismus available, own assignment open. Obtain suitable partner certificates or approve and review deliberately the acceptance or rejection of unauthorized closures.
CAP-03: Reminder after agreed working days P-22 verifies calendar days; the actual result is traceable. The own deadline regulation does not apply. Demonstrate calendar configuration and relevant edge cases.
CAP-04: Assign the correct CAPA to the ERP notification P-31 verifies message reception; customer-specific assignment is not included. Interface foundation partially usable. Close mapping, assignment, and failure scenarios based on relevant integration documentation.

Sources: [2] [3]

9. Ensure traceability of decisions regarding changes

Maintain the used documentation revision and the acceptance decision in a continuous, linked record. A link to a continuously replaced download is often inadequate as a sole identifier. Proactively clarify access, provision, and contractual arrangements for retention. This relates to verifiable evidence, not an unnecessary accumulation of copies or circumvention of usage rights.

When a change is made, assess which prerequisites are affected. If a release alters the release logic, the CAP-01 decision must be re-evaluated. If the change involves an unused area with no relevant dependencies, the assessment may be shortened accordingly. This assignment thus enables targeted re-evaluations instead of an automatic full reprocessing.

Annex 11 addresses controlled changes and periodic evaluation. For actual outsourced GMP activities, appropriate responsibility and documentation requirements from Chapter 7 are applied. Therefore, every software purchase is not automatically considered an outsourced GMP activity. Agree on the required evidence of compliance in accordance with the actually performed functions.

Sources: [2] [5] [4]

10. Start with a manageable workbench

For initiation, you require a clearly defined scope of use, the relevant requirements, the current system status, and access to pertinent documentation. The process responsible party provides a technical overview; the IT or system owner clarifies configuration and dependencies; QA evaluates the established evidence and decision pathway. The supplier addresses specific gaps in the delivered material.

The effort primarily depends on the traceability of documentation, differences from current usage, and the significance of remaining gaps. A comprehensive package may require minimal clarification; a brief document can trigger time-consuming follow-up queries. Therefore, start with a key requirement and validate the decision-making framework based on that before processing the entire dataset.

  • Requirement, revision, and acceptance criteria clearly specified.
  • Document revision, product status, and actual execution identified.
  • Evaluated relevant configuration and environment differences.
  • Investigate results and relevant deviations.
  • Transfer conditions documented or marked as open with responsibility assigned.
  • Specific residual content described and appropriate existing supplements reviewed.
  • Decision and subsequent reevaluation occasions documented.

Sources: [2] [3]

Project experience and collaboration

Map supplier evidence to your requirements

We compare the manufacturer's package against the requirements of your configured solution. With process owners and IT, we identify the version, configuration, test scope and results. Applicable evidence need not be reproduced without a reason. We plan additional evidence for uncovered functions or workflows of your own. If gaps are extensive, rebuilding the internal test plan may be more practical than adding entries to the supplier package.

Frequent Questions on the Acceptance of Manufacturer Certifications

Is a validation package automatically usable after a positive supplier assessment?

No. Supplier assessment builds trust in suppliers and performance, but it does not address every question regarding the suitability of a specific report. Always verify its alignment with your own requirements, system status, and intended usage conditions. Leverage previously collected supplier information as background context, without deriving a blanket acceptance decision from it. This approach avoids redundant supplier inquiries and maintains awareness of specific gaps in evidence.

Sources: [2]

Does a manufacturer's package always cover only unaltered standard functions?

No. A manufacturer package may also include configured or customer-specific tests. Review the contract, protocols, and results jointly. An appropriate implementation report may, for example, already verify your role workflow. Conversely, a general-purpose package description should not be considered valid evidence of such services. What is essential is verifiable coverage.

Sources: [3] [6]

Must we fully reperform accepted tests with caution?

A flat-rate repetition does not replace a suitability assessment. If existing evidence reliably covers the requirement under suitable conditions, you justify their use. If conditions remain open, you obtain a suitable supplement or plan a targeted test. Document which question is answered by it. The scope follows the concrete risk and the evidence, not the mere origin of the test.

Sources: [2] [3]

Can records from an older version still be used?

Possibly yes. The key factor is whether the documented mechanism and its relevant prerequisites remain applicable for the current usage. For this, a traceable change evaluation is required, not merely a similarly sounding version name. Historical records can support the chain of evidence. A manufacturer's release-specific archive aids in assignment but does not replace the evaluation of the affected function.

Sources: [2] [6]

Does a summary with the result "passed" suffice?

It may constitute part of the evidence, but it must carry the required assurance. If the scope of testing, system status, criteria, or relevant deviations derived therefrom are not clearly evident, specifically request additional information. A summary is not inherently inadequate merely due to its brevity. Similarly, a detailed report provides little proof if the relationship between observation and the specific requirement remains unclear.

Sources: [3]

Must the manufacturer's test environment fully match our environment?

Not every detail needs to be identical. Investigate differences that could influence the outcome: for example, roles, data, interfaces, parameters, or services. Justify the transferability or identify the open condition. The mere statement "different test system" is no more sufficient than "same software." What matters is the suitability of the environment for the specific claim being evaluated.

Sources: [2]

What do we do with an open deviation in the supplier's report?

Clarify which specific requirement and which usage scenario are affected. Take into account the current correction status, available supplements, and potential implications. An open deviation must not be eliminated merely because of the overall package status. Whether documentation can still be used for a clearly defined, separate factual situation must be reasonably assessed; this does not lead to automatic release of the entire system.

Sources: [2] [3]

Who should professionally evaluate the transfer decision?

Engage personnel who are capable of assessing requirements, system configuration, and the prescribed validation pathway. These are typically process owners, system owners, or IT and QA, supplemented by the supplier upon inquiry. Roles may overlap within a small and medium-sized enterprise (SME), provided responsibilities and competencies remain clearly defined. A fixed, universal number of signatures does not follow.

Sources: [2]

What must we prepare prior to commencement, and what drives the effort?

Useful are defined scope of use, identified requirements, current configuration status, and available reports. Effort arises from unclear assignments, missing results, relevant differences, and unexplained deviations. Provisionally fully edit a key requirement to reveal concrete information gaps and involved roles more reliably than an estimate based solely on package size.

Sources: [2] [3]

When must a previously documented transfer decision be re-evaluated?

If its assumptions change—for example, due to a relevant release, a configuration change, a new interface, or a known deviation—utilise the existing mapping to identify affected requirements. Periodic evaluation may additionally detect whether the overall setup remains valid. A universal, annual re-creation of all transfer decisions cannot therefore be inferred.

Sources: [2]

Sources and review date

Sources opened on 6 October 2026. Regulatory example framework is Human Medicinal Product-GMP. Chapter 7 addresses actual outsourced GMP activities. The Qualio overview page confirms the described document structure; individual ValPacks and their review results were not assessed. Both tables, the CAPA scenario and the checklist, are standalone work aids.

  1. European Commission: EudraLex Volume 4, current overview of GMP guidelines
  2. EU GMP Annex 11: Computerised Systems, January 2011 revision
  3. EU GMP Annex 15: Qualification and Validation, Revision 2015
  4. EU GMP Chapter 4: Documentation, January 2011 revision
  5. EU GMP Chapter 7: Outsourced Activities, Revision 2012
  6. Qualio: Validation Resources, Version 23. May 2026

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Supplier documentation to support reliable, independent decisions

Daniel Herrmann Consulting assists you in aligning existing evidence with specific requirements, clarifying transfer conditions, and strategically planning remaining assessments.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →