GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Establishing a document control system for TB lab policies

A reliable document control system gives tuberculosis laboratories a consistent way to create, approve, distribute, revise, and retire policies. It ensures that staff use the current instructions for testing, biosafety, equipment operation, reporting, and quality assurance, rather than relying on outdated files or informal workarounds.

For laboratories handling smear microscopy, culture, molecular testing, drug susceptibility testing, or specimen referral, uncontrolled documents can create serious risks. A superseded procedure may lead to incorrect testing steps, incomplete records, unsafe practices, or results that cannot be defended during an assessment. Document control therefore supports both technical accuracy and patient safety.

The system does not need to depend on expensive software. A well-designed register, clear responsibilities, standardized templates, and disciplined review practices can work in laboratories with limited infrastructure. The GLI Quality Tool provides a practical framework for building these controls alongside the broader quality management system.

Define what must be controlled

Begin by identifying the documents that influence laboratory quality, safety, and service delivery. These include policies, standard operating procedures, work instructions, forms, logbooks, job aids, quality manuals, equipment manuals, emergency plans, external standards, and records generated during testing. Documents from partner facilities or national programs may also need control when they affect local activities.

Separate controlled documents from quality records. A procedure explains how work should be performed, while a completed worksheet, temperature log, maintenance record, or corrective action report demonstrates what happened. Procedures require version review and approval; records require secure storage, retention, and protection from unauthorized alteration.

Create a document hierarchy that staff can understand. For example, a quality manual can describe the management system, policies can state required principles, procedures can define processes, and work instructions can explain specific technical steps. This structure reduces duplication and makes it easier to locate the authoritative instruction for each activity.

Assign ownership and approval authority

Each controlled document should have an owner who understands the process and can coordinate technical updates. The owner may be the laboratory manager, biosafety officer, quality officer, section supervisor, or another person designated in writing. Ownership means more than writing the document: it includes monitoring its use, collecting feedback, initiating revisions, and confirming that changes remain technically sound.

Approval should be independent enough to prevent unverified instructions from entering routine use. A technical specialist may draft a molecular testing procedure, while the quality manager checks formatting, document status, and references. The laboratory director or authorized senior person can then approve the document for implementation. Where national guidance applies, the laboratory should also verify alignment with program requirements.

Use a consistent approval record. It should show the document title, identification code, version, effective date, author, reviewer, approver, and signatures or electronic authorization. An approval page is useful, but the same information should also appear in the document control register so that staff can confirm status without opening every file.

Build a clear document lifecycle

A controlled document follows a defined lifecycle: drafting, review, approval, release, distribution, use, revision, withdrawal, and archiving. Establishing these stages prevents a document from being treated as permanently valid simply because it is stored in a shared folder or printed in a binder.

Every document needs a unique identifier and revision number. A code might include the laboratory abbreviation, process area, document type, and sequence number. Version 1.0 can identify the first approved issue, while 1.1 may indicate a minor correction and 2.0 a substantial change. The exact convention matters less than using it consistently.

The document control register should record current status and location. It can include the title, code, version, owner, approval date, effective date, review due date, storage location, distribution points, and withdrawal date. A simple spreadsheet may be sufficient if access is restricted, backups are maintained, and one person is responsible for keeping it current.

Document element Purpose Minimum control
Title and identifier Distinguishes the document from similar materials Unique code and clear name
Version and dates Shows which issue is valid Version number, approval date, effective date
Owner and approver Establishes accountability Named roles and authorization
Change history Explains what was modified Brief description of each revision
Distribution record Shows where controlled copies are used Location, recipient, or access group
Archive status Prevents obsolete use Withdrawal date and secure archive

The starting phase of the GLI Quality Tool can help laboratories establish foundational practices, including the basic organization and responsibilities needed before document control becomes fully operational.

Control printed and electronic copies

A document is not controlled merely because it has a version number. The laboratory must know where authorized copies exist and how staff can distinguish them from obsolete or unofficial versions. Printed copies should display a controlled-copy status, location, issue date, or another visible indicator. Uncontrolled reference copies should be marked clearly so that they cannot be mistaken for instructions in force.

Limit the number of printed copies when possible. Assign each controlled copy to a specific work area, such as the specimen reception desk, microscopy bench, culture room, or equipment station. When a revision is released, the document owner or quality officer should replace all controlled copies and record the action. Old copies must be removed from points of use immediately.

Electronic files require equivalent safeguards. Store current versions in a designated folder with controlled permissions, rather than allowing multiple editable copies to circulate by email or personal devices. Use read-only access for routine users, maintain backups, and apply file names that include the document code and version. If internet or network access is unreliable, maintain a locally synchronized official repository with a defined update process.

Link document changes to laboratory risk

Review documents at planned intervals, but do not wait for the review date when a change is needed. A new test platform, revised national algorithm, equipment failure, biosafety incident, audit finding, supplier change, or corrective action may require an immediate update. The quality system should provide a way for any staff member to report a needed correction.

Assess the effect of each proposed change before approval. A revision to a sample rejection procedure may affect reception staff, clinicians, reporting practices, and referral transport. A change to a decontamination instruction may require new supplies, competency assessment, or biosafety review. Documenting these effects helps managers allocate resources and prevents partial implementation.

The change history should summarize what changed, why it changed, and when the new version became effective. Where the revision is substantial, the laboratory should record related training, competency checks, equipment verification, or quality indicators. This creates a traceable connection between document revision and actual service improvement.

Verify that staff use current policies

Document control succeeds only when staff can find, understand, and apply the approved instruction. During orientation and refresher training, explain where current procedures are stored, how document identifiers work, and how staff should report errors or unclear language. Training records should identify the document version used, since staff may need retraining after a significant revision.

Supervisors can verify implementation through observation, internal audits, record review, and interviews. Look for outdated photocopies, handwritten changes, missing pages, conflicting instructions, or completed forms that do not match the current procedure. Findings should lead to corrective action, such as replacing copies, clarifying wording, or improving access at the point of work.

Document availability should be considered during routine quality indicators and management reviews. Delayed reviews, repeated use of obsolete forms, or frequent staff questions may indicate weaknesses in the system. The continual improvement phase of the GLI Quality Tool is relevant when the laboratory is using assessment findings and corrective actions to strengthen document management over time.

Priorities for implementation

A laboratory can introduce document control progressively rather than attempting to revise every file at once. Start with high-risk and frequently used policies, establish one register, and test the workflow in a single section. Once responsibilities and version practices are working, extend them to other testing areas and support functions.

Use these priorities to create a manageable first cycle:

A practical system should match the laboratory’s staffing, connectivity, storage capacity, and regulatory obligations. Paper-based control can be effective when registers and distribution records are maintained carefully, while electronic control can improve access when permissions and backups are reliable. In both settings, clarity of responsibility is more important than the technology used.

Begin by selecting one critical TB laboratory policy, documenting its full lifecycle, and using the lessons learned to refine the process. Then expand the register, train staff, and review evidence of use during internal assessments. With consistent application, document control becomes a working part of laboratory quality management rather than an administrative file-keeping exercise.