GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building a CAPA system for TB laboratories

A corrective and preventive action (CAPA) system gives a tuberculosis laboratory a consistent way to respond when work falls short of requirements. It connects an identified problem with its cause, the action needed to correct it, and evidence that the problem will not recur. For TB laboratories, this may involve contamination, delayed results, equipment failure, biosafety incidents, documentation gaps, or errors in specimen handling.

An effective CAPA process should be practical for the laboratory’s workload and resources. It does not need complex software or lengthy forms. A controlled register, clear responsibilities, root cause analysis, deadlines, and documented effectiveness checks can create a reliable foundation for quality improvement.

The GLI Quality Tool supports this work through a four-phase roadmap aligned with twelve Quality Systems Essentials. Its guidance helps laboratories connect CAPA with related systems such as assessment, equipment, personnel, process management, documents and records, and continual improvement.

Define the purpose and scope of CAPA

Before opening individual cases, the laboratory should establish what qualifies as a CAPA event. Sources may include internal audits, external quality assessment results, supervisory visits, incident reports, customer complaints, rejected specimens, quality indicator trends, staff observations, and management reviews. Defining these sources prevents important signals from being handled informally and forgotten.

The laboratory should also distinguish between a correction and a corrective action. A correction addresses an immediate problem, such as repeating a failed test or removing a damaged reagent. Corrective action removes the underlying cause, such as revising stock rotation procedures or improving staff competency assessment. Preventive action uses risk information to reduce the likelihood of a similar problem occurring elsewhere or in the future.

The CAPA procedure should specify who can report an issue, who evaluates its significance, who approves the action plan, and who closes the record. In a small facility, one person may hold several roles, but the person responsible for implementing an action should not be the only person deciding whether it was effective.

Connect CAPA with the quality system

CAPA works best when it is integrated into routine laboratory management rather than treated as a separate administrative exercise. A failed temperature check belongs in the equipment or facilities process, while a repeated specimen rejection may require changes to pre-examination procedures, training, communication with clinics, or collection materials.

Use a single CAPA form or electronic record with a unique identification number. At minimum, record the date, source, description of the nonconformity, affected process, immediate containment, risk rating, assigned owner, due date, root cause, planned action, verification method, and closure decision. Attach supporting evidence such as photographs, temperature logs, amended procedures, training records, or repeat audit findings.

A useful CAPA register should make overdue actions visible. Review it during quality meetings and management reviews, looking for repeated causes, delays, and issues that affect several sections. Trends often reveal system weaknesses that individual case reviews cannot show.

Detect problems and assess their risk

Good detection depends on meaningful quality indicators. TB laboratories may monitor culture contamination, specimen rejection, turnaround time, equipment downtime, invalid molecular tests, stock-outs, biosafety incidents, reporting errors, and participation in external quality assessment. Indicators should be defined clearly, measured consistently, and reviewed against an agreed target or action limit.

When an event occurs, first protect patients, staff, specimens, and results. This may mean quarantining a reagent lot, stopping use of a malfunctioning instrument, reviewing reports already issued, or notifying the relevant supervisor. The response should be proportionate to the risk. A minor isolated documentation error does not require the same investigation as a possible false-negative result or exposure incident.

For contamination-related events, the laboratory can use a structured troubleshooting guide to examine specimen quality, workflow, environmental conditions, equipment, media, and staff practices. The purpose is not to assign blame. It is to preserve facts while they are available and determine whether immediate containment is sufficient or a formal CAPA is necessary.

Record and investigate the root cause

A CAPA record should describe what happened in precise, neutral language. Include the test or process involved, dates, batches or equipment identifiers, number of affected specimens, staff or work area involved, and how the problem was detected. Avoid unsupported conclusions such as “staff was careless” or “human error” unless the investigation demonstrates what permitted the error.

Root cause analysis should examine the process around an event. The five-whys method can be useful for straightforward problems, while a fishbone diagram or process map may be better when several factors are involved. Consider personnel competency, workload, workflow design, supplies, equipment maintenance, environmental conditions, instructions, supervision, communication, and management decisions.

The investigation should test possible causes against evidence. For example, if culture contamination increases, compare contamination rates by media lot, work area, staff shift, specimen type, date, and equipment. Review cleaning records, incubation conditions, aseptic technique observations, and supply storage. A plausible cause becomes more credible when it explains the pattern and is supported by records or direct observation.

CAPA element Key question Typical TB laboratory evidence
Immediate correction What must be done now to control the event? Recalled reports, isolated reagent, repeated test, temporary workflow change
Root cause Why did the problem occur? Process map, audit findings, equipment records, staff interviews
Corrective action What will remove the underlying cause? Revised procedure, repair, competency assessment, workflow redesign
Preventive action Where else could the same weakness appear? Risk review, cross-section audit, preventive maintenance, broader training
Effectiveness check How will success be demonstrated? Improved indicator, follow-up audit, observation, zero recurrence over a defined period

Plan actions that are specific and achievable

Each action should state what will change, who owns it, when it is due, and what resources are required. “Retrain staff” is too vague unless the record identifies the competency gap, training content, trainer, assessment method, and completion date. Actions should address the root cause rather than simply restating the immediate correction.

Prioritize actions according to risk and feasibility. A high-risk issue affecting patient results should receive prompt containment and management attention. Lower-risk issues may be grouped into an improvement plan, provided that ownership and deadlines remain clear. If an action cannot be completed on time, the delay and interim controls should be documented rather than silently extending the deadline.

Practical controls that strengthen CAPA include:

A revised standard operating procedure alone may not solve a problem. Staff need access to the current version, instruction on the change, an opportunity to demonstrate competence, and supervision during implementation. Where possible, simplify the workflow so that the desired practice is easier to follow than the old one.

Verify effectiveness before closing a case

Completion is different from effectiveness. A signed attendance sheet proves that training occurred, but it does not prove that staff can perform the task correctly. A repair invoice proves that equipment was serviced, but it does not establish that performance returned to an acceptable level.

The effectiveness check should be defined when the action is planned. Depending on the issue, it might involve reviewing a set number of subsequent tests, observing a procedure, repeating an internal audit, checking a quality indicator for several reporting periods, or comparing results before and after the intervention. The review period must be long enough to detect recurrence.

If the action is ineffective, reopen the CAPA or create a linked case. Repeating the same action without reassessing the cause wastes time and can conceal ongoing risk. A failed effectiveness check is useful information: it may show that the original root cause was incomplete, that implementation was inconsistent, or that the chosen control was too weak.

Use CAPA to drive continual improvement

CAPA data should be analyzed collectively at planned intervals. Management can look for recurring equipment failures, common documentation errors, delays in procurement, training gaps, or weaknesses shared by several testing areas. Several small events with the same cause may justify a broader preventive project.

The laboratory should communicate meaningful outcomes to staff. When employees see that reports lead to practical changes rather than punishment, they are more likely to identify hazards and nonconformities early. Feedback can be shared through team meetings, noticeboards, revised procedures, or short learning sessions while protecting confidential information.

The GLI Quality Tool provides phase-specific checklists, user instructions, downloadable materials, and practical guidance that can help laboratories place CAPA within a broader quality management system. Laboratories can use its roadmap to build progressively, beginning with clear documentation and basic follow-up before adding more advanced trend analysis.

A mature CAPA system becomes part of daily laboratory discipline. Problems are recorded promptly, risks are controlled, causes are investigated fairly, and actions are checked against evidence. Start by reviewing recent incidents and audit findings, create a simple CAPA register, and bring the first set of open actions to the next quality meeting.