Greenlight Guru positions its design control software as a connected system for documenting user needs, design inputs, outputs, verification, and validation while maintaining traceability to risk management. The vendor's documentation describes automatic creation of a Design and Development File, or DDF, as teams work, along with links between design controls and risk control measures [1][2]. The platform is presented as purpose-built for medical device teams rather than as a general project management tool [2]. This article examines what the available documentation supports about record ownership, integration behavior, versioning, and deployment boundaries. It also identifies where the source material leaves questions open, particularly around validation responsibility and the limits of automated traceability. The analysis treats vendor claims as claims, not as independently verified performance data.

How the Design Control Record Is Structured

Greenlight Guru describes design controls as objects that can be created, linked, and attached to related documents. The vendor states that users can link complex configurations and attach documents with a single click, replacing desktop file searches [1]. The documentation names user needs, design inputs, design outputs, verification, and validation as the steps managed within the system [2]. A traceability matrix is described as automatically linking user needs to design inputs, outputs, verification, and validation activities [1]. This suggests a relational model in which the design control record is assembled from connected objects rather than stored as a single static document.

The DDF is described as building automatically as design controls begin, with every element versioned, reviewable, and export-ready [2]. Greenlight Guru also states that the DDF is auto-generating and auto-updating, which the vendor connects to 21 CFR Part 820.30 and ISO 13485 compliance [1]. The documentation does not specify the exact schema, field structure, or export format for the DDF. It also does not state whether the automatic DDF includes all artifacts required by a particular regulatory pathway or whether teams must supplement it with additional records. Those details would need to be confirmed through a vendor demonstration or configuration review.

Risk Linkage and the Limits of Automated Traceability

The platform connects risk management to design controls by allowing design controls and documents to be linked as risk control measures [1][2]. Greenlight Guru says this supports an up-to-date, audit-ready Risk Management File, or RMF, and that the software is built in accordance with ISO 14971:2019 [2]. The documentation also describes a risk matrix in which users define types of risk, severity, and probability, with risk information updated as product decisions change [2]. This indicates that risk context is intended to remain tied to design work rather than isolated in a separate spreadsheet.

The traceability claim is qualified by the vendor's own description of AI checks. Greenlight Guru states that AI checks requirements for verifiability and that real-time trace graphs expose missing links across design, risk, and test [2]. This implies that traceability is not guaranteed by the system alone; gaps can exist and must be identified. The documentation does not specify how the AI verifiability check works, what false positive or false negative rates might apply, or whether the check is advisory or blocking. Teams evaluating the software should treat the trace graph as a visibility tool, not as proof that every required link has been correctly established.

A Hypothetical Validation Scenario for a Jira-Mirrored Workflow

A team could test the integration boundary by creating a Jira project with a defined issue type for user needs and a separate type for design inputs. They would configure a JQL query to mirror only the user needs type, map a custom field for acceptance criteria, and then create three test issues. The expected result, based on the documentation, is that Greenlight Guru creates three view-only design controls populated from the mapped fields [3]. The team would then approve one record in Greenlight Guru and confirm that the approval status appears on the corresponding Jira issue [3].

This scenario would also test the limits the documentation does not cover. The team could edit a mapped field in Jira after approval and observe whether the Greenlight Guru record changes, remains frozen, or flags a discrepancy. They could delete a Jira issue and check whether the mirrored design control is removed or retained. Because the documentation states that API-built integrations require customer validation [6], the team would document these observations as part of its own risk-based validation plan rather than relying on vendor assurances. This approach treats the integration as a testable boundary, not as an assumed guarantee of synchronization.

Jira Integration and the Question of Record Ownership

Greenlight Guru's Jira integration creates design controls automatically from matching Jira issues. A Jira Query Language, or JQL, query defines which issues become design controls, and field and link mapping determines what carries across, including standard or custom Jira fields [3]. The vendor states that design controls created through the integration are view-only, keeping Jira as the single place where content is authored and preventing parallel edits from causing drift [3]. Approval status then travels back to Jira when a design control is approved in Greenlight Guru [3].

This design choice has a clear ownership implication: Jira remains the authoritative authoring environment for mirrored records, while Greenlight Guru holds the quality-controlled version. The documentation says teams can mirror user needs and design inputs from Jira while leaving other record types without a mirroring rule when those records are managed elsewhere [3]. That flexibility suggests the integration is selective rather than all-or-nothing. What the source does not specify is how conflicts are handled if a Jira issue is edited after approval, how deleted Jira issues affect existing design controls, or whether the view-only restriction applies to all field types. Those operational details would matter for a team planning a production rollout.

API Boundaries and Validation Responsibility

Greenlight Guru offers a REST API that uses standard JSON requests and responses, with API keys generated from a developer interface. The documented core actions are exporting data, importing data, and updating existing records [6]. The vendor describes bulk data movement, scheduled or triggered transfers between systems, and connections to ERP or PLM tools for parts import and approval status checks [6]. The API page also mentions linking Jira and GitHub issues directly to design controls and using an MCP server to connect approved AI tools [6].

The documentation is explicit about validation ownership. An integration built by a customer using the API is the customer's software, so it falls under the customer's own validation process and risk-based approach, the same as any custom-built tool touching the quality system [6]. Greenlight Guru states that it provides the platform, audit trail, and record integrity underneath, while the customer owns validating the connection built on top [6]. Records created or modified through the API are captured in the audit trail the same as other records [6]. This division is important for procurement decisions: the platform's validated status does not automatically extend to custom integrations, and teams must plan their own validation effort.

Deployment, Versioning, and Unresolved Questions

The documentation consistently describes Greenlight Guru as a cloud-based platform [3][4]. The QMS page refers to a validated eQMS software platform with reviews, approvals, version control, and audit trails [4]. The product development page states that every element is versioned, reviewable, and export-ready [2]. The API page adds that Greenlight Guru handles versioning and audit trails while users work in tools like Microsoft Office for Web or Google Drive [6]. These statements establish that versioning and audit trail functions are platform-level features, but they do not detail retention periods, version numbering rules, or how version history is exposed to auditors.

Several questions remain unresolved in the source material. The documentation does not specify whether the platform is deployed as a single-tenant or multi-tenant architecture, what data residency options exist, or how configuration changes are validated after release. It also does not state whether the automatic DDF export includes signatures in a format acceptable to a specific regulator. The Academy course mentions a sandbox environment and role-based access for the design controls module, including Super Admin, Quality, Product, and View-only roles [5]. That indicates some deployment and permission structure, but the public documentation does not provide a complete permission matrix. Teams should request a detailed technical and validation package before relying on any of these capabilities in a regulated workflow.