GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Designing A TB Lab Document Numbering System For Easy Retrieval

A tuberculosis laboratory can produce hundreds of controlled documents over a year: standard operating procedures, bench worksheets, equipment logs, forms, policies, risk assessments, training records and corrective action reports. If each file uses a different naming habit, staff spend valuable time searching, checking versions and deciding whether a document is current.

A clear numbering system gives every document a predictable identity. It supports filing in paper folders, shared drives and laboratory information systems, while making it easier to trace who approved a procedure, which test it covers and when it must be reviewed. The system should be simple enough for busy staff to use consistently, including people working in regional or remote services.

For Australian laboratories, the system should sit comfortably alongside NATA assessment expectations, ISO 15189 principles and local health-service governance. A public hospital laboratory in Sydney may have a dedicated quality manager and electronic document control platform, while a smaller service in regional Queensland may rely on shared folders and printed controlled copies. The numbering approach needs to work in both environments.

The GLI Quality Tool provides a useful framework because its quality systems approach covers documentation, personnel, equipment, assessment, safety and continual improvement. A numbering scheme should reflect those management needs without becoming so elaborate that staff avoid using it.

Define The Purpose Before The Format

Begin by deciding what the document number must tell a user. At minimum, it should identify the document family, the subject or process, the individual document and its current revision. The number is an identifier, not a substitute for the document title, so it should remain short and stable.

A practical pattern might be:

TB-SOP-03-02-04

In this example, “TB” identifies the tuberculosis laboratory, “SOP” identifies the document type, “03” identifies the process group, “02” identifies the specific procedure and “04” is the revision. A separate field should show the title, owner, approval date, next review date and status.

Avoid embedding information that will change frequently. A document number should not contain a staff member’s name, room number, instrument serial number or year of approval. When a laboratory moves equipment or changes its organisational structure, those details can make old documents confusing and force unnecessary renumbering.

Create A Controlled Document Taxonomy

Before assigning numbers, create a small list of document categories. Useful categories include policies, procedures, work instructions, forms, registers, templates, records and external documents. Use consistent abbreviations, such as POL, SOP, WI, FRM, REG, TMP and EXT, and record them in a master register.

The process code can follow the Quality Systems Essentials used by the laboratory. For example, one code might cover organisation and leadership, another personnel, another equipment, another purchasing and inventory, and another assessment and improvement. The exact coding is less important than making the categories logical and documenting their meaning.

A TB testing procedure could therefore be recorded as TB-SOP-06-01-02, while a specimen rejection form associated with the same process might be TB-FRM-06-01-01. The shared process code helps users find related material, while the document-type code distinguishes an instruction from the form used to record evidence.

Keep the taxonomy limited. Six or seven document types are usually easier to remember than a long list of specialised labels. If every small variation receives a new category, staff may file documents inconsistently and the master register becomes difficult to maintain.

Separate Document Numbers From Revision Numbers

The document number identifies the document itself; the revision number identifies its approved version. When a procedure changes, retain the document number and increase its revision. For example, TB-SOP-06-01-02 may become revision 03 after a change to decontamination instructions.

Show the revision in a clearly labelled field rather than changing the core identifier. A full filename could be:

TB-SOP-06-01-02_R03_Sputum-Digestion-and-Decontamination

This arrangement makes sorting and visual checking easier. It also helps prevent a common error in which staff create a new number for every update, leaving multiple apparently current procedures in circulation.

Set rules for major and minor changes. A revision may increase by one for any approved change, or the laboratory may use a format such as R03.1 for an administrative correction and R04.0 for a substantive technical revision. Either approach can work, provided the rule is documented and applied consistently.

Retired documents should remain traceable but clearly marked as obsolete. Move them to a restricted archive, add an obsolete status and retain them according to the laboratory’s record-retention requirements. Never delete an old procedure simply because a newer version has been issued; historical evidence may be needed during an incident review, internal audit or NATA assessment.

Design Filenames And Filing Locations Together

The number should work across both electronic and paper systems. Use the same core number on the document header, filename, printed footer and master register. A controlled PDF might be named TB-SOP-06-01-02_R03_Sputum-Digestion-and-Decontamination.pdf, while the editable source file is held in a restricted authoring folder.

Use plain English, predictable separators and a consistent date format where dates are needed. Avoid slashes, excessive punctuation and very long filenames, since they can cause problems when files are moved between systems. Include the document title after the identifier, but do not rely on title wording alone because titles often change during review.

Create a folder structure that mirrors the document taxonomy. For example, a top-level folder may contain Controlled Documents, Forms, Records, Archived Versions and External References. Within Controlled Documents, folders can be arranged by document type or process. The master register should remain the authoritative index, showing the approved location and status of every item.

Australian health services often use Microsoft 365, network drives or enterprise document-management platforms alongside printed bench copies. A regional laboratory may need an offline or synchronised copy when connectivity is unreliable. In either setting, access permissions should ensure that staff can read current procedures but only authorised document controllers can approve, replace or archive them.

Build The Master Register And Retrieval Rules

The master document register is the control centre for the numbering system. Recommended fields include document number, title, type, process area, owner, author, approver, revision, effective date, review date, status, storage location and related documents. Add a field for superseded numbers when documents are merged or split.

Decide how users will search. They may know the number, a keyword, the test method, the specimen type or the equipment involved. Include useful keywords in the title and register, such as “smear microscopy”, “Xpert MTB/RIF”, “culture”, “drug susceptibility testing”, “biosafety cabinet” or “external quality assessment”.

The register should be checked whenever a new document is drafted, revised or withdrawn. A document controller can reserve the next available identifier and prevent duplicate numbers. Where a laboratory uses a quality-management platform, configure mandatory fields so that an item cannot be released without an owner, approval date and revision status.

Use retrieval exercises to test the system. Ask a new staff member to locate the current procedure for a defined task, then ask another person to find the previous revision and its approval record. If either task takes too long, simplify the naming convention, improve keywords or adjust the folder structure. The GLI checklists can help laboratories review documentation and implementation activities in a structured way.

Control Changes, Training And Local Use

Numbering is effective only when it is linked to document control. Every proposed change should record the reason, affected documents, risk assessment, approver, implementation date and required training. If a new assay, analyser or specimen pathway is introduced, check related forms, worksheets, competency records and equipment instructions before releasing the revised procedure.

For example, a change to a TB molecular testing protocol may require updates to the SOP, result interpretation guide, worksheet, quality-control record and staff competency assessment. The GLI guidance on managing protocol changes offers practical context for maintaining quality while procedures evolve.

After approval, remove obsolete copies from benches, shared folders and local downloads. Replace printed copies through a controlled distribution list and record where copies are held. Australian laboratories operating across Melbourne, Perth or remote Northern Territory services may need a named local contact at each site to confirm that replacement pages or revised files have reached staff.

Train staff on the small number of rules that matter: never create an unapproved local number, check the master register before use, report missing or damaged documents and save records in the designated location. Include document-numbering practice in induction and competency activities. Periodically review retrieval times, duplicate files, overdue reviews and obsolete copies as indicators of whether the system remains usable.

Choose a numbering convention, document it in a short control procedure and pilot it with real TB laboratory documents. Register the existing procedures, assign stable identifiers, archive superseded versions and test retrieval with staff from different roles. Share implementation experience through the GLI feedback form so the wider quality community can continue refining practical approaches.

A reliable system should make the correct document obvious within seconds. When document numbers, filenames, registers, approvals and training records use the same logic, the laboratory gains a dependable audit trail and staff spend less time searching. The result is safer work, clearer accountability and a quality management system that can grow with the service.