GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building Reliable TB Laboratory Document Control

A tuberculosis laboratory depends on accurate, current information at every stage of testing. Procedures for specimen reception, microscopy, culture, molecular testing, biosafety, equipment maintenance, result reporting, and waste management must be available to staff in a controlled form. When documents are outdated, incomplete, or difficult to locate, the risk of errors increases even when trained personnel are working carefully.

A document control system provides the structure needed to create, review, approve, distribute, use, and retire laboratory documents. It also creates a traceable history of changes, allowing staff and assessors to see which version was authorized at a particular time. The system should be practical for the laboratory’s staffing, workload, technology, and connectivity.

The GLI Quality Tool’s phased approach can help laboratories build this system progressively. A facility may begin with essential policies and procedures, then expand into stronger records management, internal assessment, and continual improvement. The objective is a working quality management process rather than a collection of documents that staff rarely use.

Define The Document Control Scope

Begin by identifying which information must be controlled. This usually includes the quality manual, standard operating procedures, work instructions, forms, registers, logs, policies, safety materials, job aids, equipment instructions, and externally supplied documents. Records such as completed worksheets, maintenance logs, temperature charts, quality control results, and training records should also be covered, although records are managed differently from active procedures.

Create a master document register before rewriting every procedure. Useful fields include document title, document code, department, document type, current version, effective date, review date, owner, approver, storage location, and status. The register becomes the central index for the quality system and helps reveal duplicate or missing documents.

Set clear responsibilities. A document author understands the technical process, a reviewer checks accuracy and usability, an authorized approver accepts the document for implementation, and a document controller maintains the register and distribution records. In a small TB laboratory, one person may perform several roles, but the approval decision should still be independent enough to prevent unchecked changes.

Create A Consistent Numbering Scheme

Version numbering should be predictable, visible, and simple enough for every staff member to understand. A laboratory can use a document identifier such as SOP-MOL-004, where “SOP” identifies the document type, “MOL” identifies the section, and “004” is the sequential number. The identifier should remain stable throughout the document’s life; the version number changes when the content changes.

A practical numbering format is Version 01, Version 02, and so forth. Some laboratories prefer a major and minor format such as 1.0, 1.1, and 2.0. Either approach can work if the rules are written down and applied consistently. For example, a major revision may indicate a significant change to the testing method, while a minor revision may correct wording, update a contact detail, or clarify a step without changing the technical process.

Avoid embedding dates into the version number as the primary identifier. Dates are useful as separate fields because they show when a document became effective, but a date alone does not clearly show the sequence of revisions. Also avoid restarting numbering when a document moves to another department. Stable identifiers make cross-references, audit trails, and electronic searches easier.

Every controlled document should display key identification details in a header or footer. Include the title, document code, version, effective date, page number, total number of pages, document owner, and approval status. A statement such as “Uncontrolled when printed” can remind staff that paper copies may become outdated and should be checked against the master copy.

Control Drafting, Review, And Approval

Use a standard template for procedures and work instructions. The template might include purpose, scope, responsibilities, definitions, safety requirements, materials, step-by-step instructions, quality control, troubleshooting, records, references, and revision history. Consistent structure helps staff find critical information quickly, especially during high workload or urgent testing.

Drafting should involve the people who perform the work. A technically correct procedure may still fail if it does not reflect the laboratory’s actual equipment, staffing pattern, specimen flow, or biosafety controls. Before approval, test the draft at the bench or during a simulated workflow. This can identify unclear instructions, missing decision points, or steps that cannot be completed with available resources.

The review process should verify technical accuracy, regulatory alignment, biosafety, clarity, and compatibility with related procedures. Reviewers should check whether forms, equipment references, acceptance criteria, and reporting instructions match the proposed text. The approval record should include names, roles, signatures or secure electronic approvals, and dates.

Instructions for navigating the GLI Quality Tool and using its resources are available in the user instructions. Laboratories can use this guidance while assigning responsibilities, selecting relevant materials, and aligning document control work with a broader quality improvement roadmap.

Manage Distribution And Access

Once a document is approved, the document controller should release it through defined channels. The master electronic file may be stored in a controlled folder with restricted editing rights, while read-only copies are distributed to designated work areas. If paper copies are necessary, each copy should have a location or copy number so that replacements can be tracked.

Access should be based on need. Staff should be able to reach current procedures where work occurs without relying on a single person’s computer or memory. At the same time, ordinary users should not be able to overwrite the master version. File names should include the document code, title, and version, but the file name should support rather than replace the identification shown inside the document.

When a new version becomes effective, remove obsolete copies from benches, shared folders, binders, and portable devices. Mark archived copies as obsolete and restrict them from routine use. Retaining an archived version can be important for investigations, audits, and determining which instructions were in effect when a result was produced.

Document control element Minimum practice Stronger practice
Identification Title, code, version, and effective date Standard header, page control, owner, and status
Revision history Brief description of changes Detailed change summary linked to review evidence
Approval Named reviewer and approver Dated signatures or secure electronic approval
Distribution Current copy at the point of use Controlled access, copy tracking, and obsolete-copy checks
Archiving Retain superseded versions Protected archive with retention rules and retrieval log
Review Periodic review date Risk-based review plus event-triggered review

Set Review And Revision Triggers

A document should have a planned review date, but calendar review alone is insufficient. Procedures should also be reviewed after a change in test method, instrument, reagent, software, facility layout, safety requirement, reporting rule, or staffing responsibility. An error, nonconformity, complaint, failed quality control event, or audit finding may also show that a document needs revision.

Assign a review interval that reflects risk and change frequency. High-risk procedures involving specimen handling, biosafety, result interpretation, or critical equipment may need more frequent checks than administrative guidance. The review does not always require a new version. If the procedure remains accurate, document the review outcome and retain the current version.

When changes are needed, record what changed, why it changed, who reviewed it, and when it was approved. Update related forms, training materials, job aids, and references at the same time. A revision that changes a critical testing step should trigger an assessment of staff competency before the new version is used independently.

The laboratory should also define how urgent corrections are handled. A temporary controlled notice may be appropriate when an immediate safety or testing issue must be addressed before a full revision is approved. Such notices need an expiry date, responsible owner, distribution record, and clear connection to the permanent document.

Connect Documents With Daily Workflow

Document control works best when it follows the movement of work through the laboratory. Map where staff receive specimens, perform testing, record results, review quality control, authorize reports, maintain equipment, and dispose of materials. Place the relevant procedure or job aid at each point, and remove documents that do not support a current activity.

Workflow analysis can expose practical barriers to document use. A time-motion study guide can help TB laboratories examine delays, repeated steps, and bottlenecks that may be linked to unclear forms or poorly located instructions. The findings can inform both document design and the wider improvement plan.

Train staff whenever a new or revised document affects their duties. Training records should identify the document version, date, participants, trainer, and method used to confirm understanding. For critical procedures, direct observation or a competency assessment provides stronger evidence than attendance alone.

Monitor whether the system is functioning. Useful indicators include the percentage of controlled documents reviewed on time, the number of obsolete copies found during inspections, average approval time, staff access to current procedures, and findings related to document use. Review these indicators during quality meetings and use them to remove unnecessary complexity.

Recommendations For Sustainable Control

A reliable system grows through regular use and small corrections. Begin by controlling the documents that carry the greatest safety and testing risks, then expand coverage as roles, storage, and review practices become established. Use the register during internal assessments, replace outdated copies promptly, and make document performance part of routine laboratory management.

Set a first review meeting, assign document owners, and build the initial register from the procedures already in use. With consistent version numbering and disciplined approval and distribution, a TB laboratory can make its instructions trustworthy, traceable, and available when accurate work matters most.