Respiratory protection training under OSHA 1910.134: written program, medical evaluation, fit testing, required training, and tracking it across sites.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
How to track OSHA training in an LMS so an inspector's records request takes minutes, not a panicked week of spreadsheets.
How to deliver consistent safety training across multiple plants without ignoring shift work, languages, and site-specific hazards.
How to automate training recertification so certifications never lapse silently — and nobody works on an expired credential.
Respiratory protection training is one of the most sequence-dependent programs in occupational safety: an employee cannot simply take a course and be cleared. Under OSHA's standard, respiratory protection training pairs with medical evaluation and fit testing, and each step has to happen in the right order, be documented, and carry its own trigger for repeating. For a multi-site employer, the hard part is proving, by location and by person, that everyone using a respirator is currently medically cleared, fit-tested, and trained. This guide breaks down what OSHA 1910.134 requires and how an owned platform proves it on demand. It is general guidance, not legal advice; confirm specifics against the current standard and your own program.
Respiratory protection is governed by OSHA standard 29 CFR 1910.134. The standard treats respirator use as a program, not a product — you do not just hand someone a respirator, you run a system around it.
Two foundations sit at the top. First, wherever respirators are required, the employer must establish and maintain a written respiratory protection program with worksite-specific procedures. Second, that program must be administered by a suitably trained program administrator who oversees it and evaluates its effectiveness. Everything else — medical evaluation, fit testing, training, maintenance — hangs off that written program and that named owner. For a multi-site operation, that raises a tracking question immediately: the program is one thing on paper, but its execution is spread across every location, and you have to show it is actually running everywhere.
Respiratory protection training is really three linked obligations that must happen in a fixed order, each documented and each with its own trigger to repeat.
Before an employee is ever fit-tested or allowed to use a respirator, the standard requires a medical evaluation to determine whether the person is physically able to use one. Wearing a respirator places a real physiological burden on the body, and the evaluation exists to catch conditions that make respirator use unsafe for that individual.
The sequence is not negotiable: medical clearance precedes fit testing and use. In tracking terms, medical clearance is a gate. A worker who is not medically cleared should not show as eligible for fit testing, let alone cleared to use a respirator.
A respirator only protects if it seals to the individual wearer's face, which is what fit testing verifies. A fit test is required before an employee first uses a respirator, and then at least annually thereafter. It comes in two forms:
Two details matter for tracking. The fit test is specific to the same make, model, style, and size of respirator the employee will actually wear — a test on one respirator does not clear a different one. And refitting is required not only annually but whenever there is a change in the employee's facial condition that could affect the seal (weight change, dental work, facial scarring) or when a different respirator model is introduced.
Training must be comprehensible to the employee and, at minimum, cover:
Training must happen before use and be repeated when workplace conditions change, when new respirators are introduced, or when a lapse in a worker's knowledge or use indicates retraining is needed. Like fit testing, this is partly event-driven, so a calendar alone will miss it. Capturing it in defensible records is covered in OSHA training tracking in an LMS.
The standard requires the employer to keep records that show the program is real and current. In practice, a defensible record set includes:
The fit-test detail is worth emphasizing: the record is kept until the next fit test, so your system should always hold the most recent test per person and roll it forward at each retest. That is exactly the current-status logic spreadsheets handle badly and a purpose-built platform handles automatically.
Here is where the program becomes a data problem. Respirator users are often spread across plants, yards, and field locations, and the compliance question an inspector asks is local and immediate: for the people using respirators at this site, right now, is each one medically cleared, fit-tested on the model they wear, and trained?
An owned, centrally managed platform lets a multi-site employer answer that with a filtered view rather than a scramble:
The wider playbook for standardizing safety programs across locations is in multi-site safety training. Respiratory protection is one of the clearest cases for it, because the compliant answer depends on three separate statuses lining up for every user at every site.
Respiratory protection compliance is judged in the moment an inspector points at a respirator user and asks whether that person is cleared, fitted, and trained. Scattered paper and per-seat platforms make that a slow, uncertain answer. An owned platform — bespoke or built on Moodle Workplace and owned outright — lets you model the medical-evaluation gate, track fit tests by make/model/size and roll them to the next test, deliver and record the required training, and prove all three by site and role on demand. Because you own it, the cost is fixed rather than charged per respirator user across every location, and the program logic is yours to adapt as the standard or your operations change.