IT systems · Practical guide

Validating Qualio: linking document versions, training and CAPA

Qualio connects document control, training and quality events in a cloud QMS. Can staff identify the effective SOP, see who is trained and demonstrate when a CAPA may close? Relate supplier documents to the actual configuration and process evidence. The examples are for QA, IT and process owners in SMEs manufacturing human medicines under EU GMP.

Table of contents

At a glance

How do you validate Qualio for your intended use?

Define the intended use, affected quality records and configured Qualio workflows. Match relevant supplier evidence to your requirements and test outstanding gaps. Pay particular attention to document versions, training assignments, CAPA and change processes, and effective permissions. The supplier package can contribute evidence. Your organisation remains responsible for its risk assessment and justified release decision.

  • Qualio is a cloud-based eQMS; the scope is determined by booked functions and actual user permissions.
  • Supplier documentation is evaluated based on feature, version, and requirement coverage.
  • Document release, training, CAPA action, and effectiveness evaluation remain distinct pieces of evidence.
  • Configuration changes and releases are reviewed and controlled based on the affected processes.

Distinguish Qualio and the actually booked functional scope

The current Qualio Assistance describes a cloud-based eQMS featuring documents, training, events, and reporting. In the user guide, sandbox and production environments are selected separately. A sandbox thus represents an available work context, but does not constitute evidence that its configuration aligns with your production environment.

Capture the actually booked and activated functional scope prior to commencement. The authorization documentation specifies package boundaries: Events is excluded in the Starter plan; API access is described for Growth and Scale plans. Your contract and the release of your organization remain decisive. A general product page does not enable full derivation of the customer scope.

Additionally, document the version status from the Product Change Log and the relevant settings. Whether you include only SOPs and training or also CAPA, suppliers, and interfaces significantly impacts the audit trail. Functions such as Design Controls are only included if they are actually implemented; they are not equated here with pharmaceutical process validation.

Sources: [1] [2] [7]

Define GMP scope and responsibilities prior to package inspection

The regulatory examples relate to human medicinal product GMP. Annex 11 is the applicable GMP guideline for computerised systems within GMP-regulated activities. Separate guidelines shall be established for medical devices, veterinary medicinal products, and other areas. FDA Part 11 shall be evaluated in accordance with the underlying record-keeping obligations and actual electronic usage.

An eQMS can support quality-related decisions, even if it does not control production equipment. A flawed SOP version or inadequately justified CAPA can have implications for subsequent activities. Therefore, evaluate your processes and root cause consequences; avoid a blanket low-risk classification based solely on a general supplier methodology.

Separate responsibilities: Qualio provides the software and agreed supplier certifications. Your organization determines the intended use, evaluates suitability, and is responsible for its own processes. The older Qualio validation assistance explicitly confirms that any additional user requirements must be documented, risk-assessed, and reviewed. This delineation is more appropriate than a blanket label applied to the entire system.

Sources: [9] [8] [10] [3]

Evaluate the validation package based on specific requirements

Qualio describes Feature Val Packs per Launch Train or version. Among other elements are user requirements, design specifications, test plan, traceability matrix, and change history. The public resource overview explains the storage arrangement; it does not verify the content or suitability of each package for your client.

Request the appropriate documentation and confirm its unique status. Compare your requirements with the supplier’s demonstrable scope: a general document release test does not automatically address your specific role assignments, migration data, or handover to a different process. Justify which evidence you will accept and which gaps require independent verification.

The following matrix is an internal working aid. It is intended to facilitate decision-making regarding validation evidence and is not an additional Qualio function. A linked package constitutes usable evidence only when a subject matter expert understands which question it addresses in the context of its intended use.

Mapping supplier evidence to the work the user still needs to perform
Record receivedWhat you should verify herePossible own addition
Feature Requirements and Traceability Does functionality, version, and documented testing align with own requirements? Check for divergent process or additional requirements
Test plan and results documentation Are the workflow, results, and limitations traceable? Test a failure or role scenario that existing evidence does not cover
Change history Is this a technical change or merely a document update? Assess impact on own configuration
Operations and Safety Documentation Does responsibility, capability, and evidence align with the agreement? Review own access, outage, and restart procedures

Sources: [4] [3] [8]

Further reading:

Document version, change and effectiveness linked cleanly

Qualio distinguishes between a change control entry for a single document version and a Document Change Request (DCR) covering multiple documents. The version-specific entry, once effective, cannot be reopened or modified. For bundled DCRs, both individual documents and the overarching request are approved.

Choose the path following your change: A new inspection instruction may stand alone; a modified process sequence may affect multiple SOPs and forms. Verify that related documents remain clearly linked and that the intended version is available at the workplace in a timely manner. An approved change request and an effective document represent distinct states.

A test case may be established using a SOP with a pre-approved draft version, a new draft, and a subsequent validity date. Allow the author, approver, and regular user to each perform the intended access. Verify content, identity, version, and availability. Requirements for clear, approved, and controlled instructions are described in GMP Chapter 4; the specific implementation must be demonstrated in your configuration.

Sources: [5] [1] [12]

Demonstrate training conducted at the correct document version

Qualio describes the assignment of training and overviews per document, group, or employee. For completion, the help text specifies reading the document, conducting an evaluation or learning check, and providing electronic confirmation. This does not imply that each individual training or task authorization is automatically correctly configured.

Define who must be competent to perform a modified instruction for a specific activity. Assess a relevant individual, a newly onboarded employee, and a person outside the target group. Verify specifically that a closing signature corresponds to the correct document version and determine how a repeat training requirement following a change is handled.

A training report can show a status. Depending on the task, the process owner may also need practical training or authorisation to establish competence. An open Qualio training status only establishes a block in SAP, the laboratory or production if that connection has been specified and tested.

Sources: [1] [11]

Further reading:

Connect CAPA measures with documents and evidence of effectiveness

Qualio Events, according to the manufacturer's description, supports templates, steps, and tasks for quality incidents. Events can be linked to documents and training records. For more complex changes, the system provides a configurable change request event. These functionalities establish connections; they do not autonomously determine whether a root cause has been adequately investigated or whether a corrective action is effective.

Therefore, define in your CAPA process which information enables the next step. A logical and effective investigation cycle should include: record findings, assess the investigation, determine actions, provide evidence of implementation, and evaluate effectiveness. GMP Chapter 1 addresses root cause analysis and the monitoring of CAPA effectiveness. The specific design of your template remains a justified process decision.

Verify linkings down to their content. A reference to a SOP alone is insufficient if it is unclear which version of the amendment has been implemented. Similarly, completion of a training exercise does not automatically serve as evidence of an effective correction. Document the specific professional assessment that leads to closure and define how an inadequate result will be further addressed.

Sources: [6] [5] [11]

Verify valid authorizations and traceable decisions

Qualio differentiates user roles as well as additional administrative and function-specific permissions. In particular, event access can be individually disabled. Therefore, the role name alone does not reliably describe every possible action. Verify the actually assigned permissions using named test users.

For example, investigate who can modify an event template, close an event prematurely, or reopen a completed process. Such actions may be authorized, but require clear professional justification. Enhance role transitions and revocation of permissions. The desired segregation of duties should be demonstrable through observed behavior.

Qualio's help lists an audit trail report. Evaluate its coverage for your relevant changes and decisions, rather than deducing a complete history of all data from the mere existence of the report. In electronic confirmations, check identity, meaning and permanent assignment to the relevant record. An instruction manual for the signature function is not a flat-rate commitment to Annex-11 or Part-11 conformity of your process.

Sources: [2] [1] [8] [10]

Example: CAPA with SOP amendment and training

The following example is a separate test aid and not a Qualio test. After a deviation, a cleaning instruction is to be specified. The planned process requires the approved SOP amendment, the training of the group concerned and a later evaluation whether the measure has achieved its goal.

Design a manageable test dataset comprising a pre-release version, a new version, and two distinct user groups. Separate the verification of implementation from the evaluation of effectiveness. The required technical lock or documented additional control shall be predefined prior to testing. The example assumes no immutable Qualio standard configuration.

Ensure the relationship between event, document version, and evidence is maintained so that another qualified reviewer can understand and justify the decision. If a release can be authorized despite the absence of evidence, assess the actual control in place. A simple display of a green status would not constitute sufficient test results to meet this requirement.

Own test matrix for a CAPA with modified work instruction
VariationProfessional ExpectationEvidence to retain
SOP still in draft version Implementation must not be erroneously considered effectively introduced. Version, Status, and documented decision
Make the affected person aware of the training An open requirement is identified in the anticipated workflow. User group assignment and version-specific training status
Person not affected receives task Incorrect assignments will be detected and corrected. Requirement, Assignment, and Correction
Effectiveness assessment is missing Final CAPA closure follows the previously defined procedure. Event steps and professional justification for closure
Closed process will be reopened Authority and further processing pathway remain traceable. User, process and relevant history

Sources: [6] [5] [11]

Plan releases, migration, and ongoing operation jointly

Qualio integrates new features and enhancements approximately quarterly through Launch Trains, as described in the vendor support documentation. Changes affecting customer processes are first deployed in sandboxes for a 30-day validation period before being implemented in production. In cases of differing timelines, the most recent Release Notes shall govern. Plan your own evaluation and any necessary supplemental assessments based on this specific window and the affected usage scenarios.

Assess the change history, map impacts to your processes, and evaluate relevant dependencies. A new training approach may affect the handover of a SOP amendment, even if the CAPA template itself remains unchanged. The evaluation concludes with a justified decision regarding documentation, open items, and usage; a full retest of every function is not automatically required.

During a migration, you will additionally require a reconciliation of document identity, version, status, and relevant links. Define what is transferred and what remains available in the controlled legacy environment. Establish data access controls, failure procedures, recovery strategies, and subsequent export or system decommissioning plans. A PDF export does not automatically constitute a complete replacement for all relationships and histories of an electronic quality process.

Sources: [7] [3] [8] [12]

Enable a small team to become operationally ready for project initiation

Before initiation, your core processes should be clearly defined. Who authorizes instructions, who determines training needs, and who evaluates the effectiveness of CAPA? A software configuration cannot resolve conflicting responsibilities. First, select a representative process and make open questions visible.

QA is responsible for technical quality requirements, while IT supports identity management, system integrations, and operational issues. Document owners, training coordinators, and CAPA responsibility holders provide the actual variations. Management ensures time for decision-making and technical evaluations. For effort estimation, data quality, migration scope, number of templates, special permissions, and integrations carry more weight than a generic product name.

  • Intended use and regulatory basis formally documented in writing.
  • Recorded functions, version status, and productive settings documented.
  • Document, training, CAPA, and change roles aligned.
  • Supplier documentation requested and evaluated for coverage.
  • Representative documents, user groups, and events prepared as test data.
  • In normal circumstances, missing evidence and unauthorized actions are planned.
  • Migration, storage, and traceable linkages governed.
  • Release assessment, deviation closure, and handover to operations.

Sources: [8] [11]

Project experience and collaboration

Check the quality process against relevant supplier evidence

Quality selects a Qualio workflow in actual use, such as a document change followed by training assignment. We map supplier evidence to that workflow and its configuration. Focused additions may suffice where the supplier evidence covers the intended claim. Local process variants need further cases. Together, we assess announced changes during the available sandbox window. Your authorised owners decide on actual use.

Frequently asked questions about Qualio

Is Qualio validated for GMP use through its validation package?

The package provides potential incoming evidence. You must evaluate whether functions, versions, and documented workflows meet your requirements. Custom configurations, migration needs, and additional process requirements may necessitate further assessments. Qualio explicitly notes the customer's responsibility for additional user requirements. Therefore, a justified release of your intended use only arises from a comprehensive evaluation.

Sources: [3] [8]

What kind of Qualio documents should we specifically request?

Start with the feature packages for the actually utilized functions and the corresponding release. The resource support includes requirements, design specifications, test plan, traceability, and change history, along with supporting operational documentation. Verify currency, interpretable results, and limitations. The public list is not a substitute for reviewing the specific documents and does not constitute confirmation of their suitability for your organization.

Sources: [4] [3]

Do we need to perform all manufacturer tests in Qualio again?

A blanket reexecution of all tests is not a prudent starting point. Assess which supplier documentation already adequately addresses your requirements, and justify the remaining tests. Special roles, deviating templates, data migration, or handovers may introduce additional risks. What is essential is traceable coverage of your own process, not the maximum number of re-performed test steps.

Sources: [8] [3]

What distinguishes Document Change Control (DCC), DCR, and a Change Request Event?

The version-controlled change control record documents a single document amendment. A DCR aggregates multiple documents and includes an overarching approval. For more complex changes, Qualio describes an adaptable event workflow. Select the appropriate workflow based on the affected process and review the transition points. Completion of a request does not automatically imply that each associated instruction is already in effect at the correct location.

Sources: [5]

Does a completed training status confirm that an employee is authorized to perform any task?

First of all, it demonstrates the system-led qualification for the training in question. Check the document version, target group and final criteria used. Depending on the activity, practical instruction or further qualifications may be required. Automatic authorization in production or laboratory only follows from the Qualio status if the concrete connection is provided and proven.

Sources: [1] [11]

How do we assess a CAPA process as reasonable in Qualio?

Use a representative process from deviation through to bioequivalence assessment. Vary missing evidence, inappropriate responsibility assignments, and a re-opening scenario. Verify actual linked document versions and training records. Completion of a task can serve as evidence of execution; however, whether the corrective action was effective requires a appropriate technical evaluation and its traceable documentation.

Sources: [6] [2] [11]

Are all functions and permissions identical across each Qualio package?

No, the current support references package and release boundaries. For example, events are excluded from the starter plan there; API rights are also limited. Additionally, user rights can be configured differently. Please verify the contract, active functions, and effective rights within your organization. General product descriptions or the role name "Quality" are insufficient as a complete justification.

Sources: [2]

What does a new Launch Train mean for our validation status?

Use the 30-day Sandbox window described by Qualio for affected functions to evaluate proposed changes and the impacted internal processes. Significant schedule deviations are listed in the latest Release Notes. Utilize appropriate, updated supplier certifications and perform risk-based assessments as required. Qualio notes that packages may also be updated for administrative document corrections. Therefore, the update of a new file does not necessarily imply the same extent of technical changes. Document the justified closure decision and any outstanding issues.

Sources: [7] [3] [8]

What must be ready prior to startup, and who must collaborate?

The following core workflows, designated responsible parties, available supplier documentation, and representative test data are required. QA, IT, document owners, training, and CAPA responsibility holders should be able to jointly demonstrate their handovers. The Qualio point of contact shall address functional and evidence-based questions. For a small team, a focused initial process is often more feasible to plan than the concurrent implementation of all available functions.

Sources: [8] [11]

What drives the effort and duration of Qualio validation?

Key factors include the extent of migration, the quality of existing documents, different templates and responsibilities, as well as additional integrations. Missing process decisions and the availability of qualified reviewers also impact the workflow. Suitable supplier documentation can reduce internal effort, but cannot replace such decisions. Reliable timelines are established following a scope and gap assessment; fixed time or cost commitments cannot be derived solely from the product.

Sources: [8] [4]

Sources and review date

We reviewed the public Qualio help on 6 October 2026. Check the stated features, packages and permissions against your own organisation. We did not test a specific tenant build or inspect individual supplier packages. We considered the 2024 validation guidance alongside newer feature and release information. The tables and test case are our own examples.

  1. Qualio: New User Guide — Quality Users
  2. Qualio: User Permissions
  3. Qualio: Executing Qualio Validation
  4. Qualio: Validation Resources
  5. Qualio: Change Management Options in Qualio
  6. Qualio: CAPA & Non-Conformance Management Software
  7. Qualio: Launch Trains
  8. EU GMP Annex 11: Computerised Systems
  9. European Commission: EudraLex Volume 4
  10. FDA: Part 11 — Scope and Application
  11. EU GMP Chapter 1: Pharmaceutical Quality System
  12. EU GMP Chapter 4: Documentation

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Define the scope of evidence for your Qualio processes

Daniel Herrmann Consulting supports you in bringing together Qualio documents, own quality processes and open proof questions for a comprehensible validation planning.

  • 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.

Send a project enquiry Customer testimonials →