GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building a TB Lab Staff Communication Log for Smooth Shift Handovers

In a busy tuberculosis laboratory, the gap between one shift ending and the next beginning is where critical information either travels safely or gets lost. Whether you are working out of a reference facility in Sydney's Westmead precinct, a regional hospital lab in Cairns, or a pathology service supporting remote communities across the Northern Territory, the moments around handover carry real clinical weight. A well-built staff communication log helps bridge those moments with something better than memory or hurried corridor conversations.

The idea is straightforward: create a written record that captures what happened, what is pending, and what the incoming team needs to know. Done properly, it protects patient samples, supports continuity of testing, and gives supervisors a clear trail to follow during audits. For laboratories working through the GLI Quality Tool roadmap, this kind of log sits naturally inside several of the twelve Quality Systems Essentials, especially those covering documentation, personnel, and continual improvement.

What a Communication Log Actually Does in a TB Lab

A communication log is more than a notebook on the bench. It is a controlled record that captures events, decisions, and unresolved matters during a shift. For TB laboratories, this can include anything from a delayed GeneXpert run and a contaminated MGIT tube to a power fluctuation in a BSL-3 cabinet or a courier delay from a remote collection point serviced by the Royal Flying Doctor Service.

Across Australia, TB laboratory work often stretches across multiple time zones. A lab in Perth might finish processing samples before sunrise, while a team in Brisbane is only just starting. Without a reliable handover record, context can vanish in the two-hour gap between Perth AWST and Queensland AEST. The log becomes the single point of truth that both shifts trust.

It also supports the documentation expectations found in NATA accreditation and aligns with the safety culture encouraged by the National Tuberculosis Advisory Committee. When something goes wrong, supervisors need to reconstruct what happened, who knew what, and which samples were affected. The log is the backbone of that reconstruction.

Designing a Structure That Works on a Busy Bench

A log that is too elaborate will sit unused. A log that is too sparse will not protect the laboratory when it matters. The structure needs to balance completeness with speed, so a scientist finishing a 12-hour shift can fill it in within five to ten minutes.

Most Australian TB laboratories find that a simple tabbed format works well, often mirrored from existing quality documents already in use. The log typically includes sections for date and shift, names of outgoing and incoming staff, samples received, samples in progress, samples referred out, instrument status, safety observations, and any follow-up actions. Some teams add a small section for stock or reagent concerns, particularly relevant for labs managing tight supplies in remote settings.

For laboratories running multiple platforms such as smear microscopy, culture, and molecular methods, the resource on managing several diagnostic methods under one quality system offers useful framing. The same logic applies to the handover log: it should reflect the real workflow, not an idealised version of it.

Capturing the Right Details During Handover

The hardest part of any communication log is knowing what to write. Staff often wonder whether a detail is important enough to record, and the honest answer is usually yes. If the incoming scientist would benefit from knowing it, it belongs in the log.

Practically, this means recording the obvious things: pending samples with their unique identifiers, results that need verification, equipment that showed an alarm overnight, and any communication with clinicians or external laboratories. It also means recording the less obvious things, like a partial reagent bottle that might run out mid-shift, a sample that arrived with damaged packaging from a remote collection point, or a member of the public who called the lab with a result enquiry.

Fields Worth Including in the Log

A few habits help capture these details reliably. Writing in real time keeps memory fresh, and using sample IDs rather than patient names keeps the log compliant with privacy expectations. Flagging urgent items with a clear marker helps the incoming team triage quickly, and signing and timing each entry creates a clear chain of accountability.

Linking the Log to the Quality Management System

A standalone document is a fragile document. The communication log earns its place when it connects to the wider quality system the laboratory is building. Within the GLI Quality Tool phases, this means linking entries to nonconformities, corrective actions, training records, and instrument logs wherever appropriate.

For example, if a biosafety cabinet flagged a pressure drop during the night shift, the log entry should reference the equipment record and trigger a follow-up in the maintenance log. If a sample was compromised, the entry should connect to the nonconformity register. This kind of cross-referencing is what auditors from NATA or the RCPA look for during assessments, and it is also what helps laboratories learn from events rather than repeating them.

Teams that want a ready-made starting point can explore the phase-specific checklists available through the GLI Quality Tool, which cover documentation and personnel essentials across all four phases. Many Australian laboratories adapt these checklists to include a handover log section, then refine it as their workflow matures.

Training Staff and Building the Habit

Even the best-designed log will fail if staff do not see the value of using it. Training is therefore an ongoing conversation, particularly as new scientists rotate through the laboratory or as locum cover arrives from interstate to fill gaps in places like Hobart or Darwin.

Short toolbox sessions at the start of each roster cycle work well in most Australian settings. A senior scientist or quality manager walks through a recent example, showing how a clear handover note helped resolve an issue quickly, or how a missing one caused a delay. The message is simple: the log protects the team, not the paperwork.

Habits That Help the Log Stick

Recognition also matters. Teams in labs across Melbourne, Adelaide, and Brisbane have found that a quick mention in a staff meeting reinforces the habit more effectively than a policy memo. Australian workplace culture tends to respond well to that direct, fair-go approach: tell people why it matters, show them what good looks like, and trust them to get on with it.

Reviewing the Log and Improving It Over Time

A communication log should never be set and forgotten. Like any quality tool, it needs periodic review to stay relevant, especially as testing platforms change or as the laboratory takes on new responsibilities, including work supporting Aboriginal and Torres Strait Islander health services where sample logistics can be more complex.

Quarterly reviews are a sensible rhythm for most Australian TB laboratories. The quality manager pulls a sample of recent entries and looks for patterns: are staff missing certain fields, are urgent items being flagged appropriately, or are there recurring issues that point to a deeper problem, such as a bottleneck in sample reception or a recurring instrument fault?

Where the log needs improvement, the change should follow the laboratory's document control process. Staff should be told what changed and why, and old versions should be archived. The downloadable communication log template available through the GLI Quality Tool can serve as a useful reference point for teams building or refreshing their own format.

Over time, the log becomes a quiet record of how the laboratory handles the ordinary pressures of TB diagnostics, and a reliable guide when something out of the ordinary happens. For laboratories working through the GLI Quality Tool roadmap, it is one of the simplest ways to strengthen the people side of the quality system.

If your team is ready to start building or refining a handover log, the GLI Quality Tool checklists and downloadable resources offer a practical starting point. Sit down with two or three colleagues from different shifts, sketch what the log needs to capture, and commit to a trial period. The first version will not be perfect, but the second version will be close, and the laboratory will be stronger for it.