IT systems · Practical guide

Validating Greenlight Guru: linking changes, training and quality decisions

Two employees acknowledged a revised work instruction in Greenlight Guru. A third assignment is unresolved. May the new process be used? The answer depends on the medical device company's quality procedures. Trace document revision, training and quality events, assess vendor evidence and define the boundaries to clinical data capture and product validation.

Table of contents

At a glance

How do you validate Greenlight Guru for your QMS process?

Describe the intended QMS process, enabled features and installed version. Map supplier evidence to requirements. Test transitions between document change, training, quality event and decision against expected outcomes set in advance. Add evidence for configuration, migration and interfaces. The medical device scope determines the approach. A supplier package or software status does not replace a justified decision on use.

  • Greenlight Guru eQMS and the clinical EDC are different product scopes.
  • Document release, training completion, and process release require clear professional understanding.
  • A Validation Test Report is assessed for conformity; appropriate external evidence does not need to be automatically repeated.
  • Configuration, data transfers, and changes are part of the considered usage.

Properly classify QMS software in a medical device manufacturing environment

Greenlight Guru supports quality processes for medical devices. Therefore, begin with your role, the relevant products, and markets of concern. An internally approved SOP, a documented development traceability record, and market authorization address distinct questions. The suitability of the supporting software does not establish the safety of your medical device nor its full compliance.

In the EU context, the MDCG guideline 2019-07 Rev.1 outlines the manufacturer's responsibility and refers to proportionate quality management in accordance with MDR Article 10, paragraph 9. For a US scope, effective from 2 February 2026, the QMSR includes integration of ISO 13485:2016. The FDA-CSA Guidance dated 3 February 2026 provides non-binding recommendations for production and QMS software; it is not a product approval.

Define which information in Greenlight Guru is leading and which decisions are based on it. A flawed training documentation may, for example, lead an employee to use a revised inspection procedure without prior preparation. This specific impact determines the level of documentation required. Human medicinal product-GMP constitutes a distinct, and potentially additional, area of application and does not automatically follow from the term eQMS.

Sources: [1] [9] [7] [8]

Further reading:

Do not mix Quality, Ultralight and EDC

The manufacturer segments its platform into Quality Management, Product Development, and Clinical Evidence. In addition to Greenlight Guru Quality or eQMS, the designation Ultralight is also offered. The EDC for clinical data collection is explicitly provided as a separate solution. Therefore, document the scope of the agreement and the actually available functional areas prior to preparing a feature list for the audit plan.

A current, publicly verifiable build number for all customers cannot be derived from this information. The November 2025 Validation Guidance references the customer system for version numbering. Please document this status together with roles, established workflows, additional functionalities, and integrations. Older guidance documents for specific quality work areas are not automatically applicable to every Ultralight setup.

For a small team, initial document ownership with training may suffice; another operation may require additional supplier and quality events. The key factor is the specific responsibility assigned. Confirm exactly which audit documentation applies to your product line and configuration. Particularly during transitions between product offerings, existing data, historical decisions, and new status definitions must be explicitly reconciled.

Sources: [2] [4] [5] [3]

Build the justification along a change

Select a representative workflow rather than testing every menu item at the same depth. The following work aid illustrates an example of a change. SOP-17 describes a final review, CO-17 the change to revision B, and CAPA-17 the root cause. Whether your system uses these identifiers or status tags is immaterial; the relationships must be technically unambiguous.

Each requirement includes a statement of how you recognize the correct function. An existing link, for example, does not yet prove that the correct revision is linked. Likewise, an uploaded report does not prove its suitability in terms of content. Therefore, complete the actual evaluated status and remaining test tasks to the required documents.

This matrix serves as an independent planning tool. It does not require a specific document format or separate files for each step. Its value lies in making conflicting expectations visible early: if QA intends document release but production expects operational authorization, this distinction must be clarified prior to configuration.

Example: Assignment for SOP-17 and CAPA-17
Own requirementExpected evidenceSupplementary inspection
SOP-17 Revision B clearly identified Supplier filling record corresponding to document version Own versioning rule and display of previous editions
Associate CO-17 with the affected process. Evidence of change management process Correct SOP and responsible parties linked
Assign training to A, B, and C Certificate of Training Assignment Three required personnel, correct revision
CAPA-17 only close after own closing rule Supporting document for the established quality incident Action and efficacy determination are distinct.
Decision to be reviewed later Evidence for history and release Obtain the relationship in own export receive

Sources: [1] [8]

Check the approved version against the people trained

The product description integrates document management, change control, and training. For your facility, it is particularly important to determine when a new version becomes effective and which personnel are affected. A training assignment may be missing, even if the document itself has been correctly approved. Therefore, verify any role changes, new personnel, or delegation of responsibilities.

Establish a verifiable rule: Personnel C must demonstrate knowledge of the current revision B of the procedure prior to independently performing the end inspection activity. A previous closure related to revision A does not satisfy this rule. The method by which required competency is determined shall be defined in your procedure; a read confirmation is not automatically considered evidence of competence.

Reference the actual work location. If a printed instruction is used, its currency must be organizationally or technically verified. If the activity is initiated in a different system, the handover requires individual evaluation. A training status in the eQMS does not imply a documented automatic lockout of a machine or an ERP user.

Sources: [1] [4] [8]

CAPA Closure and Separation of Effectiveness

Greenlight Guru describes configurable quality events and links to relevant documents, products, and changes. Review what your configuration defines as completed, verified, or closed. An executed action and documented effectiveness may occur at different times. The system should support traceability of this distinction within your process.

In this example, an ambiguous inspection instruction is revised. Evidence of implementation includes the new version and the training affected. Effectiveness may also need a planned observation of later inspections. Set the period, scope and acceptance criterion for the problem. The example prescribes no universal number of inspections.

A reasonable error scenario attempts to finalize a batch release without a valid efficacy certificate. The expected behavior may involve prevention of status change or a deliberately justified and controlled interim decision, depending on the approved procedure. Define the acceptable pathway in advance. A freely completed justification must not implicitly substitute any professional prerequisite.

Sources: [1] [5] [8]

Provider receipts according to their actual content

The manufacturer-guidance describes a validation test report with intended uses and associated test records. For product updates and certain changes a new customer review is explained. This is a concrete basis for the proof planning, but not yet an audited report of your environment.

Assign the received certificate to the company's requirements: Which function, version, configuration, and test environment are documented? Is the result traceable, are there relevant deviations, and under what conditions is the statement transferable? A robust certificate can be accepted. A genuine gap leads to a corrective action, not automatically to the repetition of all manufacturer tests.

For example, a supplier certificate may cover the triggering of a training task, while the assignment of your three roles still requires verification. Conversely, a customer-specific delivery package may already include this exact assignment. Clearly define the acceptance decision and its boundaries. A general supplier audit is only as credible as its actual scope addresses the relevant question.

Sources: [3] [8]

Simulate a target model with three training assignments assigned

The following example is not a completed product test. Initial state: SOP-17 Revision A is current; Revision B is in the change process CO-17. Personnel A, B, and C perform the same affected activity. In this case, the internal rule applies: the new procedure will only be implemented for the entire three-person team once all three required assignments to Revision B have been completed and the technical prerequisites have been verified.

Following document release, personnel A and B complete their training; C has not yet done so. This results in two out of three required assignments being fulfilled; one remains pending. A second confirmation from B does not alter this count. Only the appropriate completion by C results in three definitive assignments. This calculation validates the assignment status, not the quality of the training content.

Each table case starts with the given initial state. Keep actual observation and deviation separate from the planned target. If an attempt fails, its result is retained; a repeat test gets a recognizable reference to the correction. The table does not claim a default built-in start block of Greenlight Guru.

Example: Intended for three persons, one document revision
Initial state and actionExpected result set in advanceTechnical Rationale
Revision B not yet approved; Person A confirms that Revision A remains valid 0 of 3 closures for B Old revision does not meet current assignment.
Revision B approved; Personnel A and B complete training for Revision B 2 completed, 1 open; team start not yet authorized C is missing from this own start criterion
The same conclusion from Batch B reappears. Further 2 clear financial statements Dataset quantity does not replace personnel verification
C closes the appropriate assignment to B ab 3 completed, 0 open; further start criteria to be verified Training alone is not a complete process release.
CAPA action completed, efficacy documentation missing No final conclusion has been reached pursuant to this own guideline Implementation and effectiveness are distinct statements.

Sources: [1] [8]

Verify rights and expenditures within the complete environment.

Test with realistically scoped roles: Who is authorized to edit an instruction, approve a change, or modify the configuration of a quality event? A user with read-only rights should not be able to override relevant decisions within their own rights framework. Additionally, verify that former personnel remain identifiable in historical records.

The manufacturer's contribution to Quality Processes from June 2025 includes additional fields and task exports. Such a CSV extract is not automatically the complete quality dataset. At a selected event, identify which equipment, references, decisions, and historical information are actually included. An exported task without its technical context may be insufficient for subsequent evaluation.

During a migration, it is necessary not only to reconcile document volumes but also to align revisions, validity periods, responsible parties, and outstanding tasks. Determine the required retention and access scope based on your process. Whether electronic signatures are required and what specific requirements apply must be defined separately; the provision of a Part 11 functionality suite does not establish a universal requirement for electronic signatures nor ensures automatic compliance.

Sources: [6] [4] [10] [8]

Changes to the own process flow in the cloud environment

The manufacturer guidance distinguishes Product Updates, Maintenance Releases, and Patches. Use this categorization as entry-level information. Then assess whether your process or its supporting documentation is affected. A change in role assignment may be more significant for your training than a visibly larger but underutilized new feature.

Compile relevant requirements, existing supplier documentation, and additional activities. If the assignment rule is changed, the three-person model may again be appropriate. For a mere display correction, another, justified justification may suffice. Neither a full retest nor a complete test waiver follows solely from the batch release label.

Changes introduced by your own administration also fall within this consideration: new mandatory fields, different approvers, altered roles, or an additional interface. Document the assessed state following each change. For outages, it must be clearly defined which critical activities may continue, how temporary records shall be later reviewed and verified, and who shall resolve conflicting information.

Sources: [3] [8]

Further reading:

Introduction, inventory, and resource planning deliberately prepared

In a smaller company, QA should own the decision rules, IT should describe the technical environment and integrations, and the process owner should supply representative cases. Administrators explain the configuration and the supplier provides the agreed documentation. One person can cover several tasks if responsibility and necessary checks remain clear.

Before initiating the process, you do not need artificially extensive records; instead, reliable source information is sufficient. Effort primarily arises from unclear processes, inconsistent document versions, multiple roles, additional integrations, and poorly structured legacy data. In the case of an existing system, open events and already made decisions must also be considered. Allocate time for professional clarification of these matters prior to finalizing test schedules.

The following list helps prepare a reviewable introduction or modification. Mark each point as existing, to be clarified, or outside the scope of your own assessment. This results in a justified work scope; product selection alone does not enable reliable project duration estimation.

  • Product line, modules, version, and responsible system administrator to be documented.
  • Scope, primary records, and relevant decisions are determined.
  • Define document revisions, roles, and training requirements professionally.
  • CAPA action, effectiveness assessment, and closure criteria differ.
  • Request supplier reports and document acceptance decisions.
  • Study subjects, initial data, required settings and reset preparation.
  • Verify data migration, exports, and external transfers for the specific data record.
  • Close open deviations, operating procedures, and usage decisions in a traceable manner.

Sources: [4] [8]

Project experience and collaboration

Link a document change to the associated training

In a medical device QMS, a document change with related training offers a starting point. With your quality team, we establish which version applies to which activity and what evidence the people involved need. We map supplier documentation to the Greenlight Guru functionality actually enabled. A limited workflow change may need targeted additional tests. For an implementation involving legacy data and new roles, we first agree decision rules and data migration. The approach follows your quality process.

Frequent Questions About Greenlight-Guru Process Procedures

Has Greenlight Guru been validated when the supplier delivers a package?

The package alone is not sufficient. It can provide substantial evidence. The decisive factor is which of your requirements it covers for the actually used product line and version. Check also configuration, environment and relevant deviations. Document suitable takeovers and remaining tasks. A flat-rate repetition of each manufacturer test is just as little justified as the unchecked adoption of a package name.

Sources: [3] [8]

Does Annex 11 apply automatically to Greenlight Guru?

No. This guide addresses QMS software in medical device manufacturing. Here, the specific EU or US regulatory framework and the organization's quality management system are decisive. An additional human medicinal product GMP application would require separate evaluation. The terms quality, validation, or cloud are insufficient for transferring a pharmaceutical regulatory framework.

Sources: [9] [7] [11]

Are eQMS, Ultralight, and the EDC subject to the same validation scope?

No. The clinical EDC is, according to the supplier, a separate product. Even for Quality and Ultralight designations, you must identify the actually activated functions, documents, and contract boundaries. A report for a specific department does not constitute automatic evidence of clinical data capture or any other product generation.

Sources: [2] [4] [5]

What must be available prior to a validation project?

The following are required: a described process, system status, a point of contact for configuration, and representative data. In the example presented in this article, document revisions, affected personnel, and the importance of a training completion certificate are included. Request appropriate supplier documentation early. Uncertain technical guidelines cannot be replaced through standalone test execution.

Sources: [3] [8]

How do we verify training following an SOP amendment?

Review the combination of personnel, required review, and release. A release for a prior version or a duplicate dataset must not substitute for an outstanding release of the new revision. Additionally, specify which activities are permissible prior to qualification. Whether the process is technically blocked or otherwise controlled must be clarified for your workflow.

Sources: [1] [8]

Which CAPA failure cases are particularly indicative?

Appropriate scenarios include the absence of a potency certificate, an incorrect document reference, an uncompleted task, or an unauthorized release attempt. Select cases based on actual risk. Prior to selection, describe whether the system prevents the transition, requires documentation of an interim decision, or mandates an alternative controlled pathway. Any arbitrary status change constitutes no valid potency evidence.

Sources: [5] [8]

Does an export of tasks serve as a complete audit trail?

An export of responsibilities is only sufficient when it provides complete and clear evidence of the required traceability. Status and ownership information may be included, while documents, decisions, or previous revisions remain at another location. Review a specific event data set including its associated references. Define which components must be shared and remain readable in the future; CSV or PDF formats do not guarantee this.

Sources: [6] [4]

Do we need to perform complete retesting for every cloud update?

No, a blanket full validation is not a sensible starting point. Evaluate modified functions, affected requirements, and the credibility of new supplier documentation. Assess remaining risks specifically. Even a minor configuration change can be significant. The decision should be based on the actual impact, not solely on the name of the release class.

Sources: [3] [8]

Does every batch release require an electronic signature?

Which signature is required for release follows from the professional judgment and the applicable record-keeping and signature requirements. The software designation does not establish this. If an electronic signature is used, verify identity, intent, authorization, and linkage to the correct dataset. A visible button does not substitute for this evaluation.

Sources: [10] [8]

Who must collaborate and what affects effort and duration?

QA, process owners, and the responsible IT or administration require shared working hours. The supplier provides agreed documentation and answers functional queries. Efforts primarily involve migration, role complexity, configuration, interfaces, and unresolved legacy issues. Start with a clearly defined and limited workflow and expand incrementally. A credible assessment requires an understanding of the scope and available personnel.

Sources: [4] [8]

Sources and review date

Manufacturer stand of October 6, 2026; Validation Guidance of November 10, 2025. Product line, activated scope and customer version are to be determined separately. The FDA-CSA-Guidance of February 2026 concerns production and QMS software in the applicable medical device scope.

  1. Greenlight Guru: Medical device QMS software
  2. The Greenlight Guru Platform
  3. Greenlight Guru eQMS Software Validation Guidance
  4. Greenlight Guru Quality Pricing & Packages
  5. Ultralight eQMS
  6. Introducing Adaptable Quality Processes
  7. FDA: Quality Management System Regulation
  8. FDA: Computer Software Assurance for Production and Quality Management System Software
  9. MDCG 2019-07 Rev.1: Guidance on Article 15 MDR/IVDR
  10. FDA: Part 11 – Scope and Application
  11. EudraLex Volume 4

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the scope of our own QMS evidence base

We support you in assigning existing records to your processes and addressing specific gaps in configuration, transfers, 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.

Send a project enquiry Customer testimonials →