Staff Tuberculosis Screening and Clearance Tracking Log

Use it for staff and volunteers whose roles require tuberculosis screening before or during placement, especially in childcare, schools, and similar settings. It is designed for HR, compliance, or site administrators who need a clear record of screening basis, results, clearance, and follow-up. If your organization does not require TB documentation, you may not need this log at all.

This template tracks the person’s identification, the basis for screening, the test or risk assessment details, the clearance decision, and any restrictions or follow-up actions. It also includes consent, PII notice acknowledgment, and an audit trail so you can show who submitted the record and when. It is meant to document the workflow, not to replace the underlying medical record.

That depends on your policy, local requirements, and the person’s role or exposure risk. Many organizations review clearance at hire, before placement, and again when a renewal or next review date comes due. Use the next_review_date field to avoid ad-hoc tracking and to keep renewals from slipping through.

Yes, the structure supports both staff and volunteers through the role_type field. That makes it easier to apply one process across onboarding paths while still distinguishing who the record belongs to. If volunteers have a lighter screening path, use conditional logic so you only show the fields that apply.

A common mistake is collecting more medical detail than the organization needs, which can create unnecessary PII exposure. Another is marking every field required, even when some items should be optional or only shown after a positive risk assessment or incomplete result. Teams also forget to record the clearance decision and next review date, which makes the log less useful for follow-up.

Customize the department_or_program and worksite fields to match your actual organizational structure, and adjust screening_basis options to reflect your policy. If some sites accept documentation from an external provider while others require internal review, make that distinction explicit in the documentation_received field. You can also add conditional logic for restrictions_or_notes when follow-up is needed.

Yes, it is structured to support an audit trail through submitted_by and submission_date, and it can be paired with document upload or workflow tools if your process uses them. If you integrate it with onboarding or HR systems, keep the fields limited to what you actually need for clearance decisions. That helps preserve data minimization and makes the log easier to maintain.

A dedicated log gives you consistent fields, clearer validation, and a single place to review status and follow-up. Email threads and freeform spreadsheets often lose the screening basis, the date of clearance, or the next review date, which creates gaps during audits or onboarding. This template also makes it easier to apply progressive disclosure so users only see the fields relevant to their case.