Peer Review of TB Laboratory SOPs for Consistency
Standard operating procedures (SOPs) are the working memory of a tuberculosis laboratory. They translate validated methods, safety requirements, and quality policies into repeatable actions that different staff members can perform with comparable results. When SOPs use conflicting terminology, omit critical controls, or describe the same process in different ways, variation can enter the testing pathway before anyone recognizes it.
A peer review provides an independent, practical check of those documents. Colleagues who understand TB diagnostics, laboratory workflow, biosafety, and quality management can identify gaps that the original authors may overlook. The goal is not to rewrite every document in the same voice. It is to make procedures technically aligned, easy to follow, and consistent with the laboratory’s actual resources.
The review works best as a structured comparison rather than a line-by-line editing exercise. Reviewers should examine how related SOPs connect, whether instructions match equipment and forms, and whether the documents support the laboratory’s quality objectives. A clear process also helps laboratories record decisions and track revisions through the GLI Quality Tool roadmap.
Define the purpose and boundaries
Begin by stating what the peer review must achieve. A review may focus on all TB testing SOPs, a single testing pathway, or documents associated with a new platform. Define whether the review will assess technical accuracy, document control, safety, usability, or all of these areas. A precise scope keeps reviewers from spending time on unrelated formatting preferences.
Create an inventory before opening individual files. Record each SOP title, identification code, current version, approval date, owner, related forms, and location of the controlled copy. Group documents by process, such as specimen reception, sputum processing, smear microscopy, liquid culture, identification, drug susceptibility testing, result reporting, decontamination, and waste management. This inventory often reveals duplicate or obsolete procedures.
The review should include the interfaces between procedures. For example, specimen acceptance criteria in a reception SOP must agree with rejection rules in the culture SOP and reporting requirements in the information system. A method can be technically correct in isolation while still creating confusion when staff move from one workflow to another.
Select reviewers and agree on criteria
Use at least two reviewers with complementary knowledge. One may be experienced in TB laboratory methods, while another brings quality management, biosafety, or document-control expertise. Including a staff member who performs the procedure regularly adds an operational perspective. Reviewers should be independent enough to question established habits but familiar with local constraints.
Before the meeting, agree on a scoring approach and evidence requirements. Reviewers can classify observations as compliant, minor inconsistency, major gap, or critical risk. They should cite the exact SOP section, form, record, equipment manual, standard, or policy that supports each observation. This prevents discussions from becoming subjective debates about writing style.
Use the user instructions to orient reviewers to the GLI Quality Tool materials and phase-specific quality activities. The review criteria can then be linked to relevant Quality Systems Essentials, including personnel, equipment, documents and records, assessment, process management, and continual improvement. This creates a common language for teams working in different resource settings.
Compare structure, terminology, and technical content
Start with the document framework. Related SOPs should generally contain compatible sections for purpose, scope, responsibilities, safety, materials, equipment, procedure, quality control, interpretation, records, references, and document history. The exact layout may vary, but missing information should be intentional rather than accidental. A consistent structure allows staff to locate critical instructions quickly during routine or urgent work.
Next, check terminology across the SOP set. Confirm that specimen types, test names, units, abbreviations, biosafety terms, instrument names, and result categories are used consistently. A laboratory should decide whether it uses terms such as “sample” or “specimen,” “positive control” or “external control,” and “invalid” or “indeterminate” in particular contexts. Define accepted abbreviations and avoid alternate terms that could lead to incorrect selection or reporting.
Technical comparison requires more than matching sentences. Check that incubation conditions, reagent preparation, quality control frequency, contamination responses, control acceptance limits, result interpretation, and referral procedures agree across documents. Verify that each instruction reflects the current manufacturer’s instructions, national algorithm, and laboratory validation. For drug susceptibility testing, reviewers can use the practical guidance on TB DST SOP writing as a reference point while preserving locally approved requirements.
| Review dimension | Questions for peer reviewers | Evidence to check |
|---|---|---|
| Document control | Is the current version identifiable and approved? | Master list, approval page, revision history |
| Terminology | Are test names, specimen types, units, and result terms consistent? | SOP set, reporting forms, LIS fields |
| Workflow | Do steps follow the actual sequence of work? | Direct observation, process map, staff interviews |
| Safety | Are hazards, PPE, containment, spills, and waste actions explicit? | Risk assessment, safety manual, incident records |
| Quality control | Are controls, acceptance criteria, and corrective actions defined? | QC logs, worksheets, control policies |
| Equipment and reagents | Do instructions match available models, supplies, and maintenance plans? | Equipment files, inventory, manufacturer instructions |
| Records | Are required entries, forms, and retention periods clear? | Worksheets, registers, electronic records |
| Results | Are interpretation and reporting rules aligned across procedures? | Result templates, referral criteria, amended reports |
Test the SOP against real laboratory work
A document review should be followed by a practical walk-through. Ask a staff member who was not involved in writing the SOP to explain or perform the process using only the controlled document. Observe where the person pauses, interprets ambiguous wording, searches for information, or relies on undocumented local knowledge. These points are strong indicators of usability problems.
Check whether the SOP accurately describes the laboratory’s resources. An instruction that refers to an unavailable centrifuge, a different cabinet model, a reagent concentration that is not stocked, or a software feature the laboratory does not use can create immediate inconsistency. Record such findings separately from editorial issues because they may require validation, procurement, training, or a change to the workflow itself.
Trace the records produced at each stage. Every critical action should generate an appropriate record, such as a temperature log, equipment check, culture worksheet, QC result, incident report, or authorization entry. Confirm that the SOP identifies who completes the record, when it is completed, what must be reviewed, and how errors are corrected. A procedure is incomplete when staff can perform the test but cannot demonstrate that it was controlled.
Resolve differences through documented decisions
After individual reviews, hold a consensus meeting with the SOP owners and relevant technical staff. Begin with safety and patient-impact risks, then address workflow conflicts, quality control gaps, and terminology. Keep personal writing preferences separate from requirements that affect test validity, traceability, or staff protection.
Use a finding log with a unique reference number, description, risk classification, agreed action, responsible person, due date, and verification method. When two SOPs differ, determine which source has authority. The decision may be based on a validated local method, a current national guideline, a manufacturer’s instructions, or an approved quality policy. Record the rationale rather than silently changing one document.
For liquid culture procedures, cross-check linked instructions for preparation, inoculation, incubation, contamination assessment, instrument use, and result interpretation. The guidance on liquid culture SOPs can help reviewers identify the operational details that should be explicit. Any local adaptation should be reviewed, approved, and connected to validation or verification evidence.
Control revisions and maintain alignment
Revise related SOPs as a coordinated set. Changing a specimen acceptance rule may require updates to reception, testing, referral, reporting, and nonconforming work procedures. The document controller should check cross-references, forms, abbreviations, appendices, and electronic copies before releasing a new version. Withdraw obsolete copies from work areas and shared folders.
Training should reflect the revised workflow rather than consist only of a signature sheet. Use demonstrations, supervised practice, competency assessment, or case-based exercises according to the risk and complexity of the procedure. Staff should know where the controlled SOP is located, how to report an error or ambiguity, and what to do when equipment or reagents differ from the documented conditions.
Actions after the review
- Maintain a master SOP register with owners, review dates, approval status, and linked forms.
- Schedule focused consistency checks after major method, equipment, guideline, or staffing changes.
- Compare SOP instructions with completed records during internal audits and supervisory visits.
- Track recurring deviations as evidence for corrective action, retraining, or process redesign.
- Include document consistency in management review and continual improvement activities.
A peer review becomes valuable when its findings change daily practice and remain visible in the quality system. Laboratories should preserve the review report, evidence used, decisions made, and verification results. Repeating the exercise at planned intervals helps detect drift between written procedures and actual work, especially when staff, instruments, or testing algorithms change.
Use the GLI Quality Tool materials to organize the review within a practical quality management cycle. Assemble the SOP inventory, involve reviewers from technical and quality functions, document each decision, and verify that revised procedures work at the bench. Consistent, controlled SOPs give TB laboratory teams a stronger basis for safe testing, reliable results, and measurable improvement.