Writing a quality manual for a TB diagnostic facility
A quality manual gives a tuberculosis diagnostic laboratory a clear description of how its quality management system works. It explains responsibilities, defines controlled processes, and shows how the facility protects patients, staff, specimens, results, and data. For a TB laboratory, the document must support reliable testing across the full pathway, from specimen collection and transport to reporting, referral, and follow-up.
The manual should be practical rather than decorative. It is not a collection of broad promises or copied accreditation language. It is the facility’s operating map: a concise explanation of what the laboratory does, who performs each activity, which procedures apply, and how the team verifies that requirements are being met.
A strong document can support laboratories at different stages of development. It can establish basic control in a small microscopy service, organize molecular testing in a district facility, or help a national reference laboratory prepare for assessment. The content should reflect the laboratory’s actual scope, available resources, testing platforms, biosafety arrangements, and public health responsibilities.
Define the manual’s purpose and scope
Begin with a controlled title page containing the laboratory name, document identification number, version, effective date, approving authority, and review date. Include a revision history so staff can see what changed and why. The approval page should identify the laboratory director or quality manager responsible for authorizing the manual.
The scope statement should specify the services covered. It may include sputum reception, smear microscopy, culture, nucleic acid amplification testing, drug-resistance testing, specimen referral, result interpretation, and reporting to surveillance programs. If a service is excluded, state that clearly. A precise scope prevents the manual from making claims about activities the facility does not perform.
Describe the laboratory’s role within the TB diagnostic network. Explain referral relationships, public health reporting obligations, communication with clinicians, and escalation routes for urgent or unusual findings. Include the physical location, operating hours, testing population, and relevant regulatory or accreditation requirements. This context helps assessors and staff understand how individual procedures fit into patient care.
Organize the content around quality essentials
A logical structure makes the manual easier to use and easier to maintain. Organize major sections around the twelve Quality Systems Essentials, while adapting the wording to the facility’s size and operating model. The twelve essentials provide a useful framework for connecting leadership, personnel, equipment, purchasing, process control, assessment, and continual improvement.
The manual does not need to reproduce every standard operating procedure. Instead, it should explain the system that governs those procedures. For example, the personnel section can describe competency assessment, authorization, training records, and continuing education, while individual methods remain in approved SOPs.
Useful sections commonly include organization and leadership, personnel, equipment, purchasing and inventory, process management, information management, documents and records, customer service, assessment, nonconforming events, and improvement. Safety should be visible throughout the document, with specific attention to biological hazards, aerosols, waste, spills, exposure response, personal protective equipment, and emergency communication.
Create a cross-reference between each quality system area and the documents or records that demonstrate implementation. This may include an equipment maintenance log, temperature chart, internal quality control record, occurrence report, staff competency form, or corrective action file. Cross-referencing prevents gaps and makes the manual an effective navigation tool.
Write operational content people can use
Use direct language that describes actual practice. “The section supervisor reviews internal quality control results before releasing patient results” is more useful than “Quality shall be assured at all times.” Responsibilities should be assigned to roles rather than individuals wherever possible, so the system remains stable when staff change.
Explain how work moves through the laboratory. A specimen pathway might cover ordering, collection, labeling, packaging, transport, accessioning, acceptance or rejection, testing, review, reporting, storage, and disposal. Identify control points where errors are most likely and state what happens when a requirement is not met.
TB testing requires particular attention to specimen integrity and contamination control. The manual should address criteria for unsuitable specimens, delayed transport, missing identifiers, leaking containers, repeat collection, and referral to another laboratory. It should also explain how critical results, detected resistance, contamination, or instrument failures are communicated and documented.
Distinguish between policy, process, and procedure. A policy establishes the required principle, a process explains the sequence and responsibility, and an SOP provides detailed technical instructions. A quality manual should link to these controlled documents without becoming so detailed that it duplicates them. Include document identifiers and locations so staff can quickly find the current version.
The writing should accommodate varied literacy, language, and staffing conditions. Define technical abbreviations, use consistent terms, and include diagrams or flowcharts when they clarify specimen movement or decision points. If the laboratory works with limited connectivity, describe how staff access controlled copies and how obsolete printed documents are removed.
Show how the system develops over time
A manual should reflect the laboratory’s current maturity while showing a credible route toward stronger performance. The GLI Quality Tool’s phased approach can help leaders decide which controls must be established first and which activities can be developed as capacity grows. The downloadable quality resources can support gap reviews, action planning, and discussions with laboratory teams.
| Development focus | What the manual should describe | Typical evidence |
|---|---|---|
| Establish control | Roles, scope, safety rules, document control, basic process requirements | Approved manual, organization chart, controlled SOP list |
| Implement routines | Training, equipment checks, stock management, internal quality control, reporting | Logs, forms, competency records, inventory records |
| Assess performance | Audits, indicators, external quality assessment, incident review, management review | Audit reports, EQA results, meeting minutes, action plans |
| Sustain improvement | Risk-based planning, trend analysis, corrective action verification, periodic revision | Quality dashboard, completed actions, revised documents |
This progression prevents the manual from becoming an unrealistic statement of intent. If a facility has not yet implemented a formal management review, the manual can describe the planned process, assign ownership, and set a target for implementation. However, it should distinguish established practice from future development.
Use measurable objectives wherever possible. Examples include reducing rejected specimens, improving turnaround time for molecular results, maintaining equipment uptime, increasing completion of competency assessments, or closing corrective actions within an agreed period. Indicators should have defined data sources, calculation methods, reporting frequency, and responsible reviewers.
Control documents, records, and evidence
Document control is central to a dependable quality system. State how documents are drafted, technically reviewed, approved, issued, updated, archived, and withdrawn. Define the format for identifiers, version numbers, revision dates, and page numbering. Printed copies should have a clear status, while electronic access should protect approved documents from accidental alteration.
Records require a separate approach because they provide evidence that an activity occurred. Explain how records are completed, corrected, stored, protected, retrieved, and retained. For a TB laboratory, records may include worksheets, instrument output, quality control data, environmental monitoring, result authorization, referral forms, maintenance reports, incident records, and staff training files.
Good recordkeeping supports traceability. A result should be linked to the specimen, testing method, operator or analyzer, quality control status, reviewer, and report issued. Where laboratory information systems are used, the manual should identify access controls, backup arrangements, downtime procedures, data validation, and confidentiality safeguards.
Clear documentation also supports corrective action. The documentation guidance can help laboratory leaders explain why records are operational evidence rather than administrative paperwork. When a deviation occurs, the record should show what happened, the immediate containment, the investigation, the root cause, the action taken, and how effectiveness was checked.
Review risks and improve performance
The manual should describe how the laboratory identifies and manages risks. Consider pre-examination risks such as incorrect patient identification or poor specimen collection, examination risks such as contamination or failed controls, and post-examination risks such as transcription errors or delayed notification of resistance results.
Internal audits should test whether the documented system matches actual practice. Auditors can review records, observe work, interview staff, and trace a specimen through the process. Findings should be categorized consistently, assigned to responsible staff, given due dates, and reviewed for completion. Repeated findings may indicate that a process, training approach, resource allocation, or procedure needs redesign.
Management review provides a regular opportunity to examine quality indicators, complaints, incidents, EQA performance, audit findings, staffing, workload, equipment, supplies, and improvement projects. The manual should state who participates, how often the review occurs, what inputs are required, and how decisions are recorded and communicated.
Keep the manual current through scheduled review and event-driven revision. Major changes in testing technology, staffing, facility layout, regulation, referral arrangements, or biosafety requirements should trigger an earlier review. A change-control process should assess the effect on training, validation, forms, inventory, information systems, and related SOPs.
Make the manual useful at the bench
- Write the scope around real TB services, referral pathways, and patient needs.
- Assign every critical activity to a defined role and identify the required record.
- Link quality manual sections to current SOPs, forms, logs, and policies.
- Use indicators and review dates to turn quality objectives into monitored work.
- Test the document with staff during routine activities, audits, and emergency situations.
A manual earns its value when staff can use it during ordinary work and when leaders can use it to make decisions. Before approval, compare its statements with observed practice, interview personnel from different shifts, and trace several specimens through the documented pathway. Correct contradictions, remove obsolete references, and confirm that every cited form or procedure is available.
Once approved, launch the manual through a controlled briefing and role-specific training. Place the current version where authorized users can access it, monitor whether staff follow the described processes, and review evidence during internal audits and management meetings. Begin drafting or revising the quality manual now, using the laboratory’s actual workflow as the foundation for a safer, more reliable TB diagnostic service.