Drafting a protocol for periodic review of TB laboratory SOPs

Australia records one of the lowest tuberculosis incidence rates in the world, yet every diagnostic laboratory from Perth to Cairns still needs robust procedures to keep that record intact. Tuberculosis remains a notifiable disease under state and territory public health acts, and outbreaks in remote communities of the Northern Territory have repeatedly shown how quickly complacency can unravel hard-won progress. Standard operating procedures are the backbone of any quality management system, but they only stay useful if they are reviewed and refreshed on a regular cycle. A written protocol for that cycle gives laboratories a predictable, auditable way to keep documentation current, aligned with the GLI Quality Tool Phase 1 framework, and fit for purpose as methods evolve.

In a country where TB services operate across vast distances, from the central Australian outback to metropolitan hubs like Sydney and Melbourne, consistency of practice is more than a bureaucratic goal. It is the only practical way to ensure that a sputum smear examined in Broome is interpreted with the same rigour as one processed in Brisbane. A periodic review protocol is the instrument that makes that consistency possible, defining how often each standard operating procedure is checked, who carries out the review, and how findings are fed back into the working document.

This article outlines a practical approach to drafting such a protocol, drawing on the twelve Quality Systems Essentials that underpin the GLI roadmap. It is intended for laboratory managers, quality officers, and senior scientists who are responsible for keeping TB standard operating procedures alive in facilities of every size, from major reference centres to small regional laboratories that may handle only a handful of mycobacteriology samples each year.

Why periodic review matters in the Australian context

Australia's TB rate sits at roughly five to six cases per 100,000 people, far below the World Health Organization threshold for a high-burden country. That statistic, however, masks important nuances. Notifications remain higher among people born overseas, particularly those from high-incidence regions of the Asia-Pacific, and among Aboriginal and Torres Strait Islander communities in some parts of the Northern Territory and Far Western New South Wales. Laboratories serving these populations often face higher sample throughput and a broader case mix, which places additional pressure on their standard operating procedures to remain accurate and clinically meaningful.

Australia's regulatory landscape reinforces the need for vigilance. The National Association of Testing Authorities, commonly known as NATA, accredits medical laboratories against ISO 15189, and the Royal College of Pathologists of Australasia sets expectations for professional practice. Both bodies expect documented evidence that procedures are reviewed at defined intervals, not simply when something goes wrong. A scheduled, periodic SOP review therefore supports accreditation audits and demonstrates organisational maturity to external assessors.

Resource variability is another local reality. A metropolitan laboratory in Melbourne may have a team of dedicated mycobacteriologists, while a regional service in Tasmania might rely on general microbiology staff who handle the workload alongside many other duties. A well-written protocol accommodates both scenarios by clearly assigning review responsibilities and providing templates that can be completed without extensive subject-matter expertise. It also allows a small laboratory to benchmark its procedures against a national reference framework, rather than reinventing the wheel each time a document is updated.

Defining the scope and governance of the protocol

Before the first paragraph of the SOP review protocol is written, the laboratory should decide what the document will and will not cover. A typical scope statement specifies the categories of standard operating procedures subject to scheduled review, such as specimen reception, microscopy, culture, drug susceptibility testing, molecular methods like Xpert MTB/RIF, and biosafety procedures. It also names the documentation that sits outside the periodic cycle, for example emergency contingency plans triggered by specific incidents, which are reviewed through a separate process.

Governance arrangements need to be equally explicit. In many Australian laboratories, the quality manager or quality officer holds the pen, but technical review is performed by senior scientists or section heads. The protocol should spell out who approves each revised version, who retains master documents, and how changes are communicated to bench staff. Naming a single accountable individual for the entire SOP library, often the laboratory director or chief scientist, prevents the protocol from drifting into ambiguity. For laboratories operating across multiple sites, such as a network serving both Adelaide and Darwin, the governance section is the place to clarify whether reviews are centralised or performed locally with central oversight.

A well-constructed scope also defines the boundaries between the SOP review protocol and related quality documents. It should reference the laboratory's document control procedure, the internal audit schedule, the non-conforming event management process, and the corrective and preventive action system. These cross-references keep the protocol from existing in isolation and help staff understand where the periodic review fits within the broader quality management landscape.

Structuring the review cycle

The heart of any SOP review protocol is the schedule itself. Most Australian laboratories adopt a tiered approach, with high-risk procedures such as those involving live Mycobacterium tuberculosis cultures reviewed annually, and lower-risk administrative or referral procedures reviewed every two to three years. Triggers for out-of-cycle review should also be listed: changes to national or international guidelines, introduction of new equipment, software updates, adverse events, or significant findings from internal audits.

Each standard operating procedure should carry a header block that records the version number, the date of the next scheduled review, the author, the reviewer, and the approver. This metadata turns every SOP into its own reminder system. When the review date approaches, the document essentially raises its hand and asks to be examined. Pairing this with a centrally maintained register, often a simple spreadsheet or a document management module, gives the quality officer a clear view of what is due, what is overdue, and what has just been completed.

The protocol should also describe the review methodology. This typically involves reading the procedure against current best practice, checking that referenced guidelines are still valid, confirming that equipment, consumables, and software mentioned in the text are still in use, and walking through the procedure with bench staff to confirm that it reflects actual practice. Findings are recorded in a standard template that captures what was reviewed, what was changed, what was found to be still appropriate, and any follow-up actions. The phase-specific review checklists available on the GLI Quality Tool platform provide a useful starting point for this template.

Records, version control, and training evidence

Version control is the area where laboratories most often stumble. Australian laboratories are routinely inspected by NATA assessors who expect to see a clean audit trail showing how each standard operating procedure has evolved over time. The protocol should therefore mandate a consistent approach to version numbering, the archiving of superseded copies, and the retention of review records for a period consistent with state or territory regulations and the laboratory's own quality policy.

A practical approach is to keep superseded versions in a clearly labelled archive folder or document management system, marked as "withdrawn" but never deleted, and to maintain a master change log for each SOP. The change log records the date, the nature of the change, the person who made it, and the reason. This log is invaluable when an assessor asks why a particular step was modified, and it is equally useful when training new staff who need to understand how a procedure has developed. For laboratories seeking a structured starting point, the practical guidance on celebrating small quality wins illustrates how routine documentation can become part of a positive quality culture rather than a chore.

Training records linked to each revised SOP complete the picture. The protocol should require that staff are trained on new versions before they begin using them, that training is documented, and that competency is reassessed at appropriate intervals. Linking training records directly to the SOP version ensures that, in the event of an audit, the laboratory can demonstrate not only that procedures are current but that staff are demonstrably competent to perform them.

Turning review findings into improvement

A review that ends with the document being marked as "still current" is not a wasted exercise, but its real value lies in the improvements it generates. The protocol should describe how findings are escalated, how action items are tracked, and how completion is verified. Common actions include rewriting an unclear step, updating a reference to a newer guideline, retiring an obsolete piece of equipment, or adding a safety warning that was previously missing.

Linking SOP review findings to the laboratory's continuous improvement plan is the final and most important step. Many Australian laboratories incorporate review outcomes into their annual quality objectives, tracking indicators such as the proportion of standard operating procedures reviewed on time, the number of corrective actions arising from reviews, and staff feedback on document usability. These indicators transform the SOP review protocol from a compliance obligation into a tool that genuinely shapes the laboratory's performance.

When the cycle is functioning well, staff begin to see the protocol not as an administrative burden but as a routine that protects them, their patients, and the integrity of the TB diagnostic service. That shift in perception is the most reliable indicator that the quality system is working, and it is the outcome that every well-drafted periodic SOP review protocol should aim to produce.

Begin drafting your laboratory's review protocol this week — open a working document, assign accountability for each section, and schedule a first review meeting before the end of the month. The GLI Quality Tool platform offers the templates, checklists, and guidance to make that process straightforward, and your future self will thank you when the next audit or accreditation visit arrives.