GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building a Reliable TB SOP Review Tracking System

A controlled document review process helps tuberculosis laboratories keep standard operating procedures (SOPs) accurate, approved and usable at the bench. A simple time-tracking mechanism shows when an SOP was issued, when it must be reviewed, who is responsible and whether the review was completed on time.

For Australian laboratories, this process needs to work across public hospital networks, private providers, regional services and remote facilities. It should support NATA assessment expectations, align with ISO 15189 quality principles and remain practical for teams in places such as Darwin, Cairns, Perth and rural New South Wales.

Why SOP Review Timing Matters

TB testing depends on consistent procedures for specimen reception, biosafety, microscopy, culture, molecular testing, antimicrobial susceptibility testing, reporting and referral. An outdated SOP can leave staff using incorrect instrument settings, superseded interpretation criteria or unsafe handling instructions. The risk is greater when a procedure is copied across several sites and local changes are recorded informally.

A review date alone is not enough. The laboratory needs evidence that the review happened, that relevant staff considered changes and that the approved version reached users. A tracking mechanism creates an auditable link between the document owner, review activity, approval decision and implementation date.

The GLI Quality Tool provides a useful quality management framework for laboratories developing this type of control. Its phased approach and Quality Systems Essentials can help a TB service connect document control with personnel, equipment, assessment, safety and continual improvement activities.

Define The Review Workflow

Start by writing a short procedure for document control. It should state which documents are controlled, who may draft or revise them, who performs the technical review, who grants final approval and how obsolete copies are removed. Include SOPs, work instructions, forms, worksheets, algorithms, job aids and critical manufacturer instructions where they affect testing quality.

Assign each document a unique identifier, title, version number, owner, approval authority, effective date and scheduled review date. A standard review interval might be every two years, but a fixed interval should not override risk. A major assay change, instrument replacement, incident, audit finding, new regulation or revised national guideline may require an earlier review.

Set clear status categories, such as “current”, “under review”, “approved pending release”, “overdue” and “retired”. Avoid vague labels like “in progress”. They make it difficult for a quality manager to see whether a document is waiting for a reviewer, authorisation or publication.

In a large state health service, the workflow may involve a central quality team and several laboratory managers. In a smaller regional service, one person may hold several roles. Separating the author, technical reviewer and approver where possible provides a stronger check without creating an impractical administrative burden.

Build A Usable Review Register

A spreadsheet can be sufficient when it is protected, version-controlled and reviewed regularly. A document management system may be preferable for a multi-site network, particularly where staff need controlled access, electronic approval and automatic reminders. The technology matters less than having one authoritative register.

Useful fields include document ID, document title, department, site, document owner, risk level, current version, approval date, effective date, review due date, actual review date, reviewer, approval date, next due date and current status. Add fields for change summary, related records, staff training required and the location of the released copy.

Calculate the review status automatically. For example, a document may be “Due soon” when its review date is within 60 days and “Overdue” when the date has passed without an approved decision. Conditional formatting can highlight urgent items, while a dashboard can show the percentage reviewed within the required period.

The register should track time at meaningful points rather than recording every email. Record the date the review was assigned, the date the reviewer began or accepted it, the date comments were returned, the date approval was granted and the date the revised SOP became effective. This makes delays visible and supports a fair workload discussion.

Use a shared Australian Eastern, Central or Western time setting according to the laboratory’s location, particularly when sites operate across state borders. A clear date format such as 15 Mar 2026 avoids the confusion that can arise with numerical dates in a national network.

Use Review Data For Risk Control

Review timeliness should be measured alongside document risk. A high-risk SOP for opening potentially infectious specimens, operating a biological safety cabinet or reporting a critical TB result deserves tighter monitoring than a low-risk administrative instruction. A risk field allows the laboratory to prioritise overdue reviews rather than treating every document identically.

A practical monthly report might show the total number of controlled SOPs, reviews due, reviews completed on time, overdue documents, average days late and documents awaiting approval. Break the results down by site, department and owner. Trends are more informative than a single monthly percentage; repeated delays in one area may point to insufficient staffing, unclear delegation or an overcomplicated approval path.

Link the register to change control. If a new GeneXpert or other molecular platform is introduced, the change record should identify all affected SOPs and create review tasks with owners and due dates. The same approach applies after a nonconformity, internal audit, external quality assessment issue or biosafety event.

Environmental monitoring is another useful trigger. Guidance on environmental monitoring checklists can help a laboratory identify when revised cleaning, ventilation, temperature or contamination-control procedures need document review. This is especially relevant to facilities managing seasonal heat, cyclone preparation or older buildings in northern Australia.

Make The Mechanism Work For Staff

A tracking system will fail if it becomes a separate clerical task that staff update only before an audit. Give each document a named owner with enough subject knowledge and protected time to review it. The owner should confirm whether the SOP remains technically valid, operationally realistic and consistent with current equipment, forms and reporting pathways.

Use a short review checklist. It might ask whether the purpose and scope remain accurate, hazards and controls are current, references have changed, competency requirements are clear, records are retrievable, and the procedure matches what staff actually do. Include a field for “no change required”, because a documented review may correctly conclude that an SOP remains suitable.

Before release, check that the new version is available where staff work. Remove printed superseded copies from benches, specimen reception areas and instrument folders. If a paper copy must remain in a remote site or after-hours area, mark it as controlled and define how replacement copies are distributed.

Hold a brief monthly quality meeting to review exceptions. In Australian teams, a practical “no dramas” approach means focusing on removing bottlenecks rather than blaming individuals. A laboratory in Brisbane may use an electronic workflow, while a small service in regional Queensland may rely on a protected spreadsheet and scheduled reminders. Both can provide strong evidence when responsibilities and records are clear.

Recommended Controls For A Sustainable System

Keep the process proportionate. A TB laboratory does not need an expensive platform before it has agreed on document ownership, review intervals and escalation rules. Begin with a controlled register, test it for one section, then expand it across the quality management system.

The following controls provide a practical baseline:

A review register should support decisions, not simply produce an attractive dashboard. If the report shows that reviews are late because one senior scientist approves every document, the corrective action may be delegated authority or a revised approval matrix. If delays occur because SOPs are too broad, divide them into clearer procedures with manageable ownership.

Control approach Suitable setting Strength Watch point
Protected spreadsheet Small or single-site laboratory Low cost and quick to implement Requires disciplined access and backups
Shared document register Regional service with several teams Provides common visibility Permissions and version control need attention
Electronic document management system Large public or private network Strong audit trail, reminders and approvals Requires configuration, training and support
Paper register with scanned evidence Low-connectivity or temporary setting Works when digital access is limited Higher risk of delay, duplication and lost records
Hybrid register Sites with mixed connectivity Flexible for metropolitan and remote locations Requires one agreed source of truth

A well-run SOP review time tracking mechanism gives laboratory leaders early warning before a document becomes a quality or safety problem. It also gives staff confidence that the procedure at the bench is the approved procedure, not an old printout or an emailed draft.

Adopt the register, assign owners and review the first set of TB procedures this month. Use the results to refine your workflow, strengthen audit evidence and keep every critical SOP current across your Australian laboratory service.