Employee Safety Training Records: How Long to Keep Them

Use a retention schedule organised by record type. Keep the deadline for the next training or evaluation in a separate field from the date on which a record may be reviewed for disposal.

This guide covers selected US federal OSHA examples. It is not an exhaustive retention schedule. Check the rules applying to each worksite, including its OSHA State Plan where applicable. State Plans must be at least as effective as federal OSHA and may differ in their requirements (OSHA State Plans FAQ).

Retention periods and training intervals are different

A training record answers what happened: who attended, what was covered and what evidence supports completion. A training schedule answers what must happen next. Combining the two into one "expiry" date makes it hard to distinguish an overdue evaluation from a record that is no longer needed.

The distinctions matter in the following examples. Where a cited training provision gives no fixed retention period, that does not establish permission to delete the record. Determine the applicable retention policy separately.

Another common mix-up is applying the OSHA injury-log rule to training. OSHA 300 Logs, privacy case lists, annual summaries and OSHA 301 Incident Reports must be saved for five years following the end of the year they cover. That provision addresses those injury and illness records, not every safety-training record (1904.33(a)).

Build a record that another person can understand

Start with the fields required by the applicable standard. Then add the context your team needs to retrieve and interpret the evidence. The following is a recommended operating structure, not a claim that every field is legally required for every course.

Identify the person and work. Record the employee's name or stable identifier, role, worksite and relevant task or equipment. Keep an individual entry for each attendee, even when one session has a shared attendance sheet.

Describe the training. Record the topic, date, trainer, relevant procedure and the version of the material used. Distinguish the training date from the date someone uploaded the evidence.

Link the evidence. Attach or link the attendance record, course content, certificate and assessment where relevant. Identify what each item proves. A certificate or attendance sheet should not silently stand in for a separate practical evaluation. Powered industrial truck training, for example, includes formal instruction, practical training and a workplace evaluation (1910.178(l)(2)).

Record the next decision. Include the next scheduled training or evaluation date where applicable, event-based retraining triggers, record owner and retention-policy reference. Treat "no scheduled renewal" and "renewal not yet checked" as different states.

A shared PDF can remain the original evidence while employee-level entries point to the relevant session or page. This is a practical way to answer both "who attended that session?" and "what training evidence do we have for this person?" without manufacturing new proof.

Set the retention rule before calculating the disposal date

Use a short review for each training category:

1. Identify the work activity, location and applicable standard. Record the exact provision supporting the retention rule.
2. Separate training evidence from related medical, exposure, inspection or incident records. Do not assign them one blanket period because they share a folder.
3. Record the event that starts the retention period: the training date, an employment event or another specified trigger.
4. Have the responsible records owner check other applicable requirements, contractual commitments and any preservation instructions before approving disposal.
5. Test whether the underlying evidence remains readable and retrievable when a person leaves, a document moves or a system contract ends.

This is a recommended records-management process. It does not change a statutory minimum. For the export and migration checks, use the EHS software migration checklist.

Worked example: one session, two separate clocks

Consider a hypothetical US workplace subject to the bloodborne-pathogens standard. An employee completes the required training on 15 October 2026. The source record includes the attendee, trainer, covered content and training date.

The training record must be kept for three years from that date, through 15 October 2029. Annual training is due within one year of the previous training, by 15 October 2027. These dates come from different provisions and serve different purposes. Other applicable retention requirements or preservation instructions still need checking before disposal (1910.1030(g)(2)(iv), (h)(2)(ii)).

In the register, record both dates with their labels. When the employee completes the next session, add the new event and its evidence. Preserve the earlier entry for its required period instead of replacing its date with the latest attendance.

For a different type of training, do not copy these intervals. Start from that activity's requirements.

Keep retraining tied to the work

A calendar alone is insufficient for some training decisions. Lockout/tagout retraining can be triggered by changed job assignments, equipment, processes or procedures, and by identified gaps in knowledge or use of the procedures. Those triggers are explicit in the standard (1910.147(c)(7)(iii)).

As an operating practice, connect changes in equipment and procedures to a review of affected training records. Give the review an owner. Record whether more training was needed, what was completed and where the evidence is stored. Use the register to support that decision, rather than treating a future date as proof that every requirement remains satisfied.

Where SoterAI fits

Soter's public Help Centre describes record creation through typed or spoken conversation. The AI populates the record fields, and the user can switch to form view to review and edit the result. That makes the review step the place to check names, dates and supporting files before saving the record (Creating Records with AI Assistance).

The record-type documentation lists configurable fields, including dates, files and repeating sections, and describes PDF export. Those building blocks can be evaluated against your training-record requirements. They do not establish a retention schedule or verify an employee's competence by themselves (Setting Up and Managing Your Record Types).

Start with Training Records. For short group sessions, also see Toolbox Talks. In your test, create one record, correct an incorrectly extracted date, open the original evidence and retrieve an older entry. Before rollout, confirm your organization's requirements for retention, access and export against the actual configuration.

Check how a training record is built before you set the retention fields. Open Training Records.