Building a TB Laboratory Non-Conformity Report Template
A monthly report on non-conformities gives a tuberculosis laboratory a consistent way to record deviations, assess risk, assign corrective actions, and identify recurring weaknesses. Used well, it turns scattered incident notes into evidence for management review and continual improvement.
The report should be brief enough for routine completion but detailed enough to support investigation. It may cover errors in specimen collection, testing, biosafety, equipment operation, records, reporting, supply management, or compliance with approved procedures.
A strong template also supports the laboratory’s quality management system. It should fit the laboratory’s existing document-control process and reflect the Quality Systems Essentials rather than becoming a separate administrative exercise.
Define The Report’s Purpose And Scope
Begin by stating what counts as a non-conformity. This may include any departure from a standard operating procedure, approved work instruction, safety requirement, quality indicator, equipment specification, or reporting deadline. Near misses can also be included when they reveal a credible risk, even if no incorrect result was issued.
The reporting period should be clear, such as the first through the last day of the month. Identify the facility, testing area, reporting officer, date of review, and approving manager. If several testing sites report to one central laboratory, include a field for the site or department where each event occurred.
Avoid using the monthly form as a disciplinary record. Staff should be able to report problems promptly and accurately, including events discovered during internal audits, external quality assessment, supervisory visits, instrument checks, or routine work. A fair reporting culture improves the reliability of the information collected.
Capture Essential Event Details
Each event needs a unique identification number so it can be followed from discovery to closure. A simple format may combine the year, month, and sequential number, such as 2026-04-03. The number should remain unchanged in corrective action records, meeting minutes, and supporting documents.
The description should answer what happened, where it happened, when it was detected, and how it was detected. Record facts rather than assumptions. For example, “the refrigerator temperature was 11°C at the morning check” is more useful than “the refrigerator was not working properly.”
Include the process involved and the immediate containment action. A specimen may be placed on hold, an instrument may be removed from service, or a result may be withheld pending review. The report should also identify whether patient results, staff safety, specimen integrity, turnaround time, or surveillance data may have been affected.
Useful fields include:
- Event identification number and date detected
- Laboratory section, instrument, or work area
- Related procedure, standard, or quality requirement
- Person reporting the event and person responsible for follow-up
- Description of the deviation and immediate containment
- Affected specimens, results, records, or staff
- Supporting evidence, such as logs, photographs, worksheets, or audit findings
Link Findings To Quality System Areas
Classifying each event makes monthly analysis easier. A laboratory can use the twelve Quality Systems Essentials as categories, including organization, personnel, equipment, purchasing and inventory, process management, information management, documents and records, customer focus, assessment, facilities and safety, and continual improvement.
The classification should describe the system area where the weakness occurred, not simply the location where the event was noticed. For example, repeated missing temperature records may be detected in the testing room but relate primarily to equipment management, documents and records, or personnel competency.
A practical reporting layout can combine event classification with risk and follow-up status:
| Field | Example entry |
|---|---|
| Event number | 2026-04-03 |
| Date detected | 18 April 2026 |
| Quality area | Equipment and facilities |
| Non-conformity | Storage refrigerator recorded 11°C |
| Immediate action | Specimens transferred to validated unit |
| Potential effect | Specimen stability possibly affected |
| Risk rating | Moderate |
| Root cause | Alarm check was not included in the duty checklist |
| Corrective action | Revise checklist and brief assigned staff |
| Responsible person | Section supervisor |
| Due date | 30 April 2026 |
| Verification | Review four weeks of completed checks |
| Status | Open / closed / overdue |
This format can be adapted to a paper register, spreadsheet, or electronic quality management system. The important feature is that every entry connects the finding to an action and a later verification decision.
Assess Risk And Investigate Causes
Risk assessment should consider the likelihood of recurrence and the potential consequence. A missed signature may have low immediate impact but still indicate weak document control. A failed decontamination step, incorrect result, or compromised specimen may require urgent escalation.
A simple three-level scale is often sufficient. Low-risk events can be managed through routine correction and monitoring. Moderate-risk events may require documented investigation and management review. High-risk events should trigger immediate containment, evaluation of affected work, and notification according to local policy.
The root-cause field should go beyond the first visible mistake. Ask whether the problem arose from unclear instructions, insufficient training, workload, staffing, poor layout, unreliable utilities, inadequate supplies, equipment failure, weak supervision, or an ineffective checking process. Use evidence from records and interviews rather than assigning blame to an individual.
Where a personnel issue is identified, a structured mentorship program guide can help laboratories support new TB technicians through supervised practice, feedback, and competency development. The monthly report should record the support provided and how competency will be reassessed.
Plan Corrective And Preventive Actions
Correction addresses the immediate problem; corrective action addresses the cause. If a result was delayed because a reagent was out of stock, the immediate correction may be to obtain an approved replacement. The corrective action may involve minimum stock levels, reorder points, supplier review, and a weekly inventory check.
Preventive actions are useful when the laboratory sees a credible risk before a failure occurs. For example, a review of power interruptions may lead to a preventive action for backup temperature monitoring, even if no specimen has yet been lost. Actions should be specific, measurable, realistic, and assigned to a named role.
Each action entry should include an owner, due date, required resources, and evidence of completion. “Staff reminded” is usually too vague. A stronger entry would state that the procedure was revised, five staff members completed a competency observation, and the supervisor will review compliance for four consecutive weeks.
Temperature-related findings deserve particular attention because storage conditions can affect reagents, controls, and specimens. A practical temperature monitoring guide can support decisions about device placement, recording frequency, alarm response, calibration, and escalation.
Verify Effectiveness Before Closure
An action should not be marked closed simply because a meeting was held or a document was revised. Closure requires evidence that the change was implemented and that it reduced the chance of recurrence. The verification method may be a record review, direct observation, repeat audit, competency assessment, equipment check, or analysis of the next month’s results.
The report should include a verification date, reviewer, evidence examined, and decision. Possible decisions are effective, partially effective, ineffective, or requires further action. If the action did not work, keep the original event open or create a linked follow-up record rather than deleting the history.
Overdue actions should appear clearly in the monthly management review. The report can show the number of open actions, actions due this month, overdue actions, and events awaiting root-cause analysis. Escalation rules should specify when a section supervisor, laboratory manager, quality officer, or facility leadership must be informed.
Make Monthly Analysis Practical
The report becomes more valuable when individual events are summarized as trends. Compare the number and type of non-conformities across months, but interpret the figures carefully. A rise in reported events may indicate worsening performance, or it may show that staff have become more willing to report problems.
Useful monthly indicators include repeat events, high-risk events, overdue corrective actions, average time to closure, events affecting patient results, and findings associated with external quality assessment. Break down recurring events by quality area, process, shift, instrument, or testing site where this information supports action without exposing confidential staff information.
At the monthly quality meeting, select a small number of priority findings for discussion. Confirm containment, review root-cause evidence, check action ownership, and record decisions in the meeting minutes. Link the report to audit findings, safety reviews, equipment logs, inventory records, and management review outputs so that quality activities reinforce one another.
Keep The Form Clear And Consistent
A good template uses controlled terms, drop-down options where possible, and enough writing space for a factual description. Define risk categories and closure requirements in the user instructions. If the form is electronic, use mandatory fields for event date, classification, responsible person, due date, and status.
Use these design practices when preparing the final version:
- Keep event description, root cause, correction, and corrective action in separate fields.
- Include an option for “not applicable” rather than leaving important fields blank.
- Use consistent status labels such as open, under investigation, action in progress, overdue, and closed.
- Protect patient identifiers and store supporting records according to the laboratory’s confidentiality and document-control procedures.
- Review the template after several reporting cycles and remove fields that do not support decisions.
The final report should be easy for a technician to complete, easy for a quality officer to review, and useful to a laboratory manager making resource decisions. Downloadable guidance and phase-specific checklists from the GLI Quality Tool can help align the form with the laboratory’s current quality improvement work.
Adopt the template through the laboratory’s document-control process, train staff using realistic TB laboratory examples, and begin with one reporting cycle. Review the first month’s entries with the quality team, correct unclear fields, and use the resulting data to drive documented actions that protect testing quality and patient care.