An ETQ audit finding needs separate containment and CAPA records

The finding records an observed gap

An audit finding should identify the audit, requirement or approved procedure, sampled population, objective evidence, observed condition, affected location and process, auditor, date, classification, auditee response, and any disputed fact. It is evidence that the audit reached an observation under a defined scope. It is not by itself a root-cause conclusion, product disposition, regulatory report, or proof that every affected record was identified.

The system should preserve the issued wording and later responses as attributable versions. If a factual correction narrows or expands scope, the original record should remain reviewable. Permissions should distinguish who may document evidence, accept the finding, classify significance, assess product or patient impact, and approve the eventual response.

Containment protects the present scope

Immediate containment answers what must be controlled while investigation continues. Depending on the issue, that can include holding material, suspending a process, restricting system access, increasing review, preserving data, notifying an owner, or checking a bounded population. The containment record needs affected product, lot, site, system, document, period, rationale, owner, start time, verification, exceptions, and release authority.

Completing containment does not prove the cause is known or recurrence is prevented. A temporary control can also create new risks or become obsolete as facts change. The platform should expose expiry, reassessment, and handoff rules, and it should prevent an administrative closure of the audit response from silently releasing held scope or ending an interim control.

CAPA requires its own problem and effectiveness logic

A CAPA should state the problem definition, investigation boundary, evidence, cause status, risk and impact assessment, correction, corrective or preventive action, owners, approvals, implementation evidence, due dates, changes, training effects, and planned effectiveness question. Not every finding requires the same CAPA path, and several findings may support one systemic action only when that relationship is explicit.

Effectiveness needs a prospective measure, population, observation period, acceptance threshold, reviewer, and response to an inconclusive or adverse result. A completed action is evidence of implementation. It does not establish that the action solved the defined problem. If later monitoring contradicts the conclusion, the system should reopen or supersede the decision without erasing the approved history.

Evaluate the cross-record boundary

A representative evaluation should issue one audit finding, identify an affected lot after the audit, impose time-limited containment, reject an initial cause, revise an action, and receive an adverse effectiveness result. Reviewers should reconstruct every version, signature, dependency, product-impact decision, release state, overdue item, and escalation while the finding, containment, CAPA, change, and effectiveness records retain separate owners and statuses.

ETQ's official page supports the described configurable life-sciences QMS positioning. It does not establish a buyer's intended use, configuration, validation state, procedure, audit quality, investigation sufficiency, CAPA effectiveness, release authority, or outcome. Regulated organizations retain responsibility for quality, validation, regulatory interpretation, manufacturing, laboratory, clinical, security, privacy, compliance, and legal judgment.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.