GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building a Reliable TB Laboratory Document Review System

A tuberculosis laboratory depends on controlled information as much as it depends on instruments, reagents and skilled staff. Procedures, forms, registers, policies and reports guide decisions that affect patients, clinicians and public health teams. If a document is outdated, unapproved or difficult to find, even a capable laboratory can produce inconsistent work.

A practical approval and review system gives every document a clear owner, an authorised version and a defined review date. It also creates evidence that staff were trained when a procedure changed. This supports safe testing, reliable results and a quality management system that can withstand internal reviews, external assessment and accreditation checks.

For Australian laboratories, the system should fit state and territory health structures, NATA expectations and the requirements of ISO 15189. A metropolitan service in Sydney or Melbourne may manage hundreds of controlled documents, while a regional facility in Townsville or a remote service in the Northern Territory may rely on a smaller team with limited back-up. The process must work in both settings.

The GLI Quality Tool offers a useful framework because it connects documentation with laboratory safety, personnel, equipment, assessment and continual improvement. A document control process should be practical enough for daily use, clear enough for new staff and robust enough to demonstrate that the laboratory is in control of its work.

Define The Purpose And Scope

Begin by writing a short document control policy. It should explain which records and documents are controlled, who may approve them, how changes are managed, where the current version is stored and how obsolete copies are removed. Keep the policy direct. Staff should be able to understand the rules without decoding quality jargon.

Include all documents that influence testing, reporting, safety or management decisions. These may include standard operating procedures, work instructions, forms, worksheets, equipment manuals, validation reports, quality indicators, emergency plans, training records and referral laboratory instructions. External documents, such as manufacturer instructions or national guidance, also need an owner and review method.

A good scope prevents gaps. For example, a laboratory may control its extraction procedure but overlook the form used to record extraction failures. It may approve a biosafety procedure but fail to control a laminated copy kept beside a cabinet. Mapping the full document set exposes these weak points before they cause confusion.

Assign Ownership And Approval Authority

Each controlled document needs a named document owner. This person is accountable for technical accuracy and for starting a review when practice, equipment, legislation or evidence changes. The owner does not have to write every update, but they must coordinate the process and confirm that the content remains fit for purpose.

Approval should match the level of risk. A senior scientist or section lead may approve a minor formatting change, while a change to a molecular testing method may require review by the laboratory director, quality manager and biosafety representative. Documents affecting clinical interpretation, referral pathways or public health reporting may also need endorsement from a medical microbiologist or relevant state health authority.

Avoid relying on job titles alone. Record the role and delegate as well as the person’s name, because staff move between services. A simple responsibility matrix can show who drafts, checks, approves, releases and trains. In a small regional laboratory, one person may hold several roles, but the same individual should not routinely approve their own unreviewed work.

Create A Risk-Based Approval Workflow

Use a consistent workflow from draft to release. The author prepares the document using an approved template, then sends it for technical review. A second reviewer checks scientific accuracy, practical usability, safety implications and alignment with related documents. The quality manager checks document control features before the authorised approver signs off the release.

Classify changes as minor, significant or urgent. Correcting a spelling error may not require a full technical review, although it should still be logged. Changing a decontamination step, specimen acceptance rule or result interpretation requires a documented impact assessment. An urgent change may be released quickly to protect staff or patients, but it still needs retrospective review and formal incorporation into the document set.

The workflow should show what happens when reviewers disagree. Set a timeframe for comments, identify who resolves technical disputes and define when a draft is returned to the author. Digital approval can be recorded through a quality management platform, while a controlled paper process may use signed approval pages and a document register. Either approach can work if the evidence is legible and retrievable.

Set Review Cycles That Reflect Risk

A fixed annual review date for every document sounds tidy but may create unnecessary work and still miss important changes. Use a risk-based cycle. High-risk procedures, such as drug susceptibility testing, biosafety and result reporting, may need review every 12 months. Stable administrative forms may be reviewed every two or three years, provided they are checked sooner when circumstances change.

A review is not complete simply because the date has been extended. The owner should confirm that the procedure matches current equipment, consumables, staffing, workload and referral arrangements. Review triggers should include a nonconformity, audit finding, incident, amended standard, new test platform, supplier change, revised public health requirement or feedback from staff.

Build a forward-looking review calendar with reminders at least 60 and 30 days before a document expires. Escalate overdue reviews to the quality manager and laboratory director. In a busy service, a fortnightly review meeting can deal with upcoming due dates, outstanding approvals and documents waiting for training or implementation.

Control Versions And Access

Every document should have a unique identifier, title, version number, effective date, review date, owner and approval record. Add a change history that briefly explains what changed and why. Version numbering should be consistent; for example, a major method change might move from version 2.3 to 3.0, while a minor wording correction might become 2.4.

Store the current approved version in one authoritative location. A shared drive can be suitable if permissions, naming conventions and backups are controlled. Larger Australian health services may use an enterprise document management system, but a sophisticated platform will not fix unclear ownership or poor housekeeping. Make the approved copy easy to find at the bench, including for staff working after hours.

Remove obsolete paper copies from work areas and clearly mark retained historical versions as superseded. Do not destroy records that must be retained for legal, accreditation or operational reasons. Instead, move them to a restricted archive. Access should be based on role: staff need to read current procedures, while only authorised users should edit or release them.

Link Changes To Training And Evidence

A newly approved document is not effective merely because it has been uploaded. The laboratory must show that affected staff were informed, trained and assessed where necessary. Record the document version, training date, participants, trainer and any competency check. For a high-risk method, supervised practice or observation may be more meaningful than an email acknowledgement.

Connect document changes with nonconformities, corrective actions and quality indicators. If an amended procedure follows repeated specimen rejection, the laboratory should be able to show the reason for the change and whether rejection rates improved. This creates a useful feedback loop between document control and continual improvement.

The GLI Quality Tool can help laboratories place document control within the wider quality management system rather than treating it as an isolated filing task. Its approach encourages evidence across several Quality Systems Essentials, including assessment, personnel, equipment and process improvement.

Use A Practical Control Checklist

Before releasing a document, use a short checklist that confirms both content and administration. It should be completed by the author, reviewer or quality officer and retained with the approval evidence. The checklist can be electronic, printed or built into a document management workflow, provided it is consistently applied.

The GLI Quality Tool’s phase checklists can be adapted to help identify gaps in document control, review evidence, responsibilities and implementation. Adaptation matters: a remote service may need a resilient paper fallback, while a large tertiary laboratory may need integration with an enterprise platform and single sign-on.

Useful checks include:

Run a sample check each quarter. Select documents from different sections, such as culture, molecular testing, biosafety and administration. Confirm that the copy at the point of use matches the master record and that staff can explain how they know it is current. This small audit often reveals practical issues faster than reviewing the register alone.

Make The System Sustainable

Assign one person to maintain the master document register, but make document control a shared responsibility. Section leads should monitor technical content, supervisors should watch for outdated bench copies and all staff should have a simple way to report errors or needed changes. A “speak up early” culture is especially important when staff work across multiple campuses or rotate through regional services.

Measure a few useful indicators rather than collecting data for its own sake. Track the percentage of documents reviewed on time, overdue approvals, training completion, obsolete copies found during audits and the time taken to close a document change. Trend the results by section and discuss them at management review.

For Australian services, include local operating realities in the process. Consider public holidays, interstate referral delays, procurement changes, workforce shortages and the logistics of supporting sites in places such as Alice Springs, Port Hedland or far north Queensland. The best system is one that works when the quality manager is away, the internet is unreliable or a method must change quickly during an outbreak.

Start by inventorying the documents used in one TB testing section and piloting the workflow for a month. Record what takes too long, where approvals stall and which documents staff struggle to locate. Then refine the templates, clarify responsibilities and expand the system across the laboratory.

Use the pilot evidence to establish a review calendar, train document owners and report progress at the next quality meeting. A controlled, visible and reviewable document system will make daily work safer and give the laboratory stronger evidence of reliable practice. Begin with the highest-risk procedures, release only authorised versions and keep improving the process as the service evolves.