GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Why documentation supports reliable TB laboratory quality

Documentation is the practical memory of a tuberculosis laboratory. It records what the laboratory has agreed to do, how work is performed, what results were produced, and how problems were addressed. Without that record, quality depends too heavily on individual experience, informal reminders, and staff who may not be available every day.

For TB laboratories, reliable documentation is especially important because testing often involves complex workflows, biosafety controls, specialized equipment, and results that influence treatment and public health decisions. A clear document system connects these activities, making it easier to prevent errors, demonstrate competence, and maintain continuity when personnel, instruments, or testing volumes change.

Documentation is also more than filing forms. It is a controlled system of policies, standard operating procedures, job aids, logs, reports, records, and improvement plans. When these materials are accurate, accessible, and routinely used, they turn quality management principles into consistent laboratory practice.

Documentation turns expectations into routine work

A quality management system defines what a laboratory must control. Documentation explains how those controls operate in daily work. A standard operating procedure can specify specimen acceptance criteria, decontamination steps, instrument checks, result verification, and reporting requirements. A related form or electronic record then provides evidence that each step took place.

This connection reduces variation between staff members and shifts. Experienced personnel may complete a process correctly from memory, but less experienced colleagues need clear instructions and defined decision points. Written procedures also help supervisors identify whether a problem resulted from inadequate training, an unclear instruction, a missing resource, or failure to follow an established process.

Good documents are designed for use at the point of work. They should use precise language, logical sequencing, appropriate terminology, and only the level of detail needed for the task. A long procedure that is difficult to navigate may be less useful than a concise procedure supported by a flowchart, checklist, or bench-level job aid.

Controlled documents protect laboratory consistency

A document can become a quality risk when staff are unsure which version is current. Document control establishes ownership, approval, review dates, version numbers, distribution methods, and withdrawal of obsolete copies. These controls apply to both paper and electronic materials.

The document lifecycle should be visible. A procedure may begin as a draft, undergo technical review, receive authorization, enter active use, and later be revised or retired. Each change should have a reason, an effective date, and a record of who approved it. This is important when a test platform changes, national guidance is updated, or an internal assessment identifies a weakness.

Access also matters. Staff need to find current instructions quickly, especially during specimen reception, testing, maintenance, or result reporting. At the same time, uncontrolled copies should not circulate indefinitely. A practical system may use a master electronic repository, controlled printed copies in defined work areas, and a simple method for confirming that obsolete versions have been removed.

Records make quality visible

Procedures describe intended practice; records show what actually happened. Temperature logs, equipment maintenance records, training files, quality control charts, incident reports, corrective action forms, and internal assessment findings all create an evidence trail. Together, they help a laboratory demonstrate that processes are monitored and that deviations receive appropriate attention.

Records support traceability from specimen to reported result. If a result is questioned, the laboratory should be able to identify relevant sample information, testing dates, personnel, reagent or kit details, instrument status, quality control findings, and review actions. This traceability is essential for investigating errors and determining whether other patient results may be affected.

Retention rules should be defined rather than improvised. The laboratory can identify which records are critical, how long they must be kept, where they are stored, and who may access them. Confidentiality and data protection are part of this decision, particularly where patient identifiers and clinical information are recorded. A record that is complete but inaccessible, damaged, or exposed to unauthorized use cannot fully support quality.

Documentation element What it controls Evidence of effective use
Quality manual or system description The laboratory’s quality objectives, responsibilities, and scope Staff can explain key responsibilities and quality priorities
Standard operating procedure The correct method for a test or supporting activity Staff follow the approved process and deviations are documented
Job aid or workflow chart Critical steps and decisions at the point of work Users can complete tasks consistently without relying on memory
Equipment file Installation, maintenance, calibration, faults, and service history Instrument status is known before use and failures are traceable
Training and competency record Authorization and ongoing competence of personnel Staff have documented training, assessment, and reassessment
Quality control record Validity and stability of testing processes Trends are reviewed and unacceptable runs trigger action
Incident or nonconformity report Events that may affect safety, specimens, results, or service Causes, immediate corrections, and follow-up are recorded
Corrective action record Response to identified problems and prevention of recurrence Actions have owners, deadlines, and effectiveness checks
Internal assessment report Review of conformity with procedures and requirements Findings are prioritized and used to strengthen the system

The value of these records depends on their quality. Entries should be legible, dated, attributable to a person, and protected from unauthorized alteration. Corrections should preserve the original information and show who made the change and when. Electronic systems should provide suitable access controls and backups, while paper systems need secure storage and protection from water, pests, and loss.

Documentation connects the quality essentials

The twelve Quality Systems Essentials are interdependent, and documentation provides many of the connections between them. Personnel management relies on job descriptions, training plans, competency assessments, and authorization records. Equipment management relies on inventories, maintenance schedules, calibration certificates, and breakdown reports. Purchasing and inventory require specifications, supplier records, stock cards, and expiry monitoring.

Safety procedures, waste management instructions, and exposure reports connect laboratory safety with risk reduction. Process control depends on validated methods, quality control results, environmental monitoring, and review of testing performance. Assessment activities generate findings that must be documented, assigned, tracked, and checked for effectiveness.

This is why quality management guidance is most useful when it is applied as a connected system rather than as isolated paperwork. A laboratory can begin with the documents that control its highest risks, then expand and refine the system as staff gain experience. The goal is useful evidence and consistent practice, not paperwork for its own sake.

Documentation drives learning and continual improvement

A well-maintained record does more than prove compliance. It helps the laboratory recognize patterns. Repeated specimen rejection may point to collection or transport problems. Frequent equipment downtime may indicate inadequate preventive maintenance or a supply issue. Recurring transcription errors may show that result verification or reporting interfaces need attention.

To support improvement, records must be reviewed at defined intervals. Supervisors can examine quality indicators, incident trends, turnaround times, external quality assessment performance, and internal assessment findings. The review should lead to decisions: revise a procedure, retrain staff, change a workflow, obtain a replacement item, or monitor a risk more closely.

Corrective and preventive actions should be specific. “Remind staff to be careful” is difficult to verify and rarely addresses a root cause. A stronger action might assign a person to revise a specimen acceptance job aid, train all relevant staff, introduce a weekly review, and assess rejection data after a stated period. Documentation then shows whether the intervention was completed and whether it worked.

Build documentation into daily practice

A sustainable system makes documentation part of normal work rather than an activity reserved for inspections. Laboratory leaders can reinforce this by reviewing selected records during supervision, discussing findings without blame, and ensuring staff have time, materials, and access to current procedures. When records reveal a weakness, the response should focus on learning and risk control.

Practical steps include:

The system should also fit local conditions. A resource-limited laboratory may rely on registers and controlled binders, while another facility may use a laboratory information system. Both can support quality when responsibilities are clear, information is protected, and records are reviewed. The technology is less important than the discipline of maintaining trustworthy information.

Use practical tools to strengthen the system

Laboratories do not need to design every document from the beginning. Templates, checklists, examples, and phased implementation materials can shorten the time between identifying a need and putting a workable control in place. They also help teams use consistent terminology when several departments or facilities collaborate.

The downloadable resources from the GLI Quality Tool can support this process with practical materials for laboratories working across varied resource settings. Teams can adapt relevant tools to local workflows, testing platforms, staffing arrangements, and regulatory requirements, while retaining control over approval and revision.

A useful starting point is a documentation gap review. List essential activities, identify the procedure or record that supports each one, and mark whether the document is current, available, understood, and actually used. Prioritize gaps that could affect biosafety, result validity, patient management, or continuity of service. This approach turns a broad quality goal into manageable actions.

Reliable documentation gives a TB laboratory a shared way to work, a defensible record of performance, and a foundation for improvement. Begin by reviewing the documents that govern your highest-risk processes, involve the staff who use them, and build a controlled record system that can grow with the laboratory’s quality objectives.