GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Managing TB laboratory document revision histories for audit readiness

Reliable document control is a foundation of a tuberculosis (TB) laboratory quality management system. Procedures for specimen handling, testing, equipment use, biosafety, reporting, and waste management must remain current, approved, and available to the people who use them. An auditor should be able to see what changed, why it changed, who authorized it, and when the new version became effective.

A revision history provides that evidence. It turns a static SOP into a traceable record of quality improvement. When managed consistently, it also prevents staff from following obsolete instructions, supports investigation of errors, and shows that the laboratory evaluates its processes over time.

The GLI Quality Tool offers a practical framework for this work through its four-phase roadmap and twelve Quality Systems Essentials. Document control connects closely with management responsibilities, personnel, equipment, purchasing and inventory, process management, assessment, and continual improvement. The goal is not to create paperwork for its own sake, but to make laboratory decisions visible and defensible.

Establish a controlled document system

Begin by defining which records require formal control. These usually include policies, SOPs, work instructions, forms, logs, quality manuals, equipment procedures, biosafety documents, validation reports, and externally supplied standards. A document register should assign each controlled item a unique identifier, title, owner, version number, approval date, effective date, and review date.

The laboratory should also define where the master copy is held and how authorized users access it. A secure electronic folder can work well when access permissions and backups are reliable. In a paper-based setting, a controlled binder or distribution register may be more appropriate. Either approach needs a clear rule: only the current approved version may be used for routine work.

Document status should be obvious at a glance. Include labels such as “controlled copy,” “uncontrolled copy,” “draft,” or “obsolete,” depending on the system. Withdraw superseded paper copies from work areas, and restrict access to old electronic versions. Archived documents may be retained for traceability, but they should be clearly separated from active procedures.

Design a useful revision history

A revision history should do more than record a new number. Each entry needs enough information to explain the change without forcing an auditor or staff member to compare every line of two documents. At minimum, record the version, date, section affected, description of the change, reason, author, reviewer, approver, and implementation date.

Use consistent version conventions. A simple sequential system such as 1.0, 2.0, and 3.0 is suitable for major approved releases, while minor changes can use 1.1 or 1.2 if the laboratory has defined what those numbers mean. Avoid changing the numbering method from one document to another. Consistency makes the document register easier to search and reduces ambiguity during an audit.

The change description should be specific. “Updated procedure” is weak evidence. “Added a two-hour maximum between specimen decontamination and inoculation in section 6.3 after review of workflow data” explains the operational impact. If a change results from a nonconformity, assessment finding, equipment replacement, amended manufacturer instructions, updated national guidance, or a corrective action, record that source in the history.

A revision history is strongest when it connects the document to its approval record. Keep the completed change request, review comments, training evidence, risk assessment, and authorization with the document or in a linked location. Electronic signatures, approval emails, or signed document-control forms should be protected against alteration and retained according to the laboratory’s record-retention policy.

Connect revisions to risk and evidence

Not every edit carries the same risk. Correcting a typographical error may require document-control approval but no competency reassessment. Changing a decontamination temperature, incubation condition, critical result threshold, or acceptance criterion may require technical review, verification, staff training, and a defined implementation date.

A change-control process helps the laboratory decide what evidence is needed before approval. Consider the effect on patient results, biosafety, turnaround time, equipment performance, supplies, reporting, and regulatory requirements. Where a revision affects a validated or verified method, retain the supporting data and document who assessed its impact.

For example, a change to monitoring rules should be supported by appropriate quality indicators and trend data. Laboratories can use control charts for test performance to identify shifts, trends, or unusual variation that may justify reviewing an SOP. The revision history can then cite the relevant quality event and show how the laboratory responded.

The same principle applies to safety-related documents. If a laboratory revises its autoclave waste procedure, it should preserve the rationale, equipment information, verification records, and staff training associated with the change. A practical autoclave waste protocol guide can support the drafting process, while local risk assessment and approval remain essential.

Make audit evidence easy to follow

Auditors commonly test whether staff use current procedures, whether revisions are authorized, and whether changes were implemented effectively. They may select a document from the register, inspect its history, ask for the previous version, and interview personnel who use it. A well-organized trail allows the laboratory to answer these questions quickly.

The records below show the difference between informal editing and controlled revision:

Document-control element Weak practice Audit-ready practice
Version identification File names such as “final” or “new” Unique document code and defined version number
Change description “Minor update” Specific sections, actions, and technical changes
Approval Verbal agreement or undated email Named reviewer and approver with dated authorization
Effective date Same as editing date by default Clearly stated implementation date
Obsolete copies Left in benches or shared folders Removed, marked obsolete, and archived securely
Staff implementation Informal announcement Training, read-and-understand record, or competency evidence
Related records Stored separately without references Linked change request, risk review, and verification evidence

Conduct periodic document-control checks rather than waiting for an external assessment. Select a sample of SOPs from the document register and verify that the posted copy matches the approved master, the revision history is complete, and staff can locate the document. Record discrepancies as findings and follow them through corrective action.

Manage electronic and paper versions

Electronic systems create convenience but also introduce risks. Multiple local copies, automatic synchronization conflicts, uncontrolled downloads, and shared editing can make it difficult to establish which version was active on a particular date. Use read-only access for approved masters where possible, and limit editing rights to designated document owners or quality personnel.

File names should contain the document code, title, and version, but the file name should not be the only control. The document itself should display its status, version, approval date, and page numbering. Maintain backups and test restoration periodically. If the laboratory uses a document-management platform, preserve an audit trail of edits and approvals.

Paper systems require equally deliberate controls. Number distributed copies, identify their locations, and maintain a distribution list when appropriate. On release of a new version, collect or destroy old copies and document that action. If an uncontrolled printout is allowed for reference, label it clearly and explain that the user must verify the current version before applying it.

Review the system through the quality essentials

A revision history should be part of routine quality management, not an isolated administrative task. Assign a document owner for every controlled procedure and establish a review interval based on risk, usually annually or according to national requirements. A review can confirm that the procedure remains suitable even when no changes are needed; record that decision rather than leaving the history blank.

The quality manager can monitor indicators such as overdue reviews, uncontrolled copies found, approval delays, missing training records, and repeat document-related nonconformities. These measures reveal whether the system works in practice. Findings should feed into management review and continual improvement, consistent with the GLI Quality Tool’s phased approach.

Use these practical controls as a routine checklist:

Turn revision control into daily practice

Staff should know how to report a needed change, locate the current SOP, and identify an obsolete copy. Include these expectations in induction and refresher training. Supervisors can reinforce them during bench observations by checking whether the document in use matches the registered version.

When a procedure changes, communicate the practical effect clearly. State what action is new, when it starts, which forms or instruments are affected, and whether competency must be demonstrated again. A short implementation record is often more useful than a broad message saying that “documents have been updated.”

An audit-ready document system is built through repeated, ordinary actions: accurate records, timely approvals, controlled distribution, and evidence that staff adopted the change. Review the GLI Quality Tool materials, adapt the controls to your laboratory’s available technology, and begin by checking a small sample of high-risk TB procedures. Then use the findings to strengthen the wider quality management system.