Determine which requirements cover the process
Start with the process roles, assigned tasks and procedures that apply at the site. Identify which rules govern the work before selecting records or review dates. Keep unresolved coverage questions visible. This is an editorial recordkeeping workflow, not a complete chemical-safety checklist or instructions for operating a process.
US examples: establish coverage first
Check the thresholds and exceptions in 29 CFR 1910.119(a) before applying the process safety management examples below. They concern covered US processes, not every chemical plant or jurisdiction. A generic industry label does not establish that the rule applies.
Keep process training and hazard communication distinct
For the US hazardous-chemical example, OSHA requires effective information and training concerning hazardous chemicals in the work area at initial assignment and when a chemical hazard not previously covered is introduced. See 29 CFR 1910.1200(b) and (h)(1)-(3). Preserve that work-area and hazard scope.
Keep the relevant training event connected to its own requirement. Do not combine different obligations into one assumed renewal date. The separate WHMIS training records guide addresses its Canadian scope; it does not replace the applicability review for a US process.
Record understanding as well as attendance
For covered US processes, 29 CFR 1910.119(g)(3) requires a record identifying the employee, training date and means used to verify understanding. That is a scoped legal example. Attendance and the means of checking understanding answer different questions; keep them distinguishable when reviewing the evidence.
The editorial handoff table below is separate from that legal example. It suggests record relationships, not an official form or a blanket retention period. Use the operator records guide to frame a task-level evidence review without treating a completion label as operating authorization.
Review training before a covered process change
Within the US PSM scope, affected operating, maintenance and contract employees must be informed of and trained in the change before startup of the affected process or part. See 29 CFR 1910.119(l)(3). Keep this training requirement distinct from the separate decisions and requirements governing startup.
The covered-process refresher provision requires training at least every three years and more often if necessary: 29 CFR 1910.119(g)(2). It is not a three-year rule for every chemical training topic. Use the procedure-change training guide to consider evidence when a requirement changes, without confusing course versioning with process-change approval.
What TrainGrid records
TrainGrid records training and evidence; it does not deliver or grade e-learning courses.
TrainGrid supports course versions and retraining assignments while keeping completed evidence tied to the version used.
A completed TrainGrid assignment has fields for completion date, grade, hours and instructor.
TrainGrid attachment types include Certificate, Attendance sheet, Competency evidence and Other.
Import .xlsx or .csv training history as a matrix with one row per person or a log with one row per completion. Check matches and row errors in a preview before saving. An Administrator can undo an import for 30 days. The import does not complete existing open assignments. Before importing, tick Repeats to set Repeat every (days) for recurring courses. For expiring certificates, tick Requires certificate to set Valid for (days).
Use an evidence handoff checklist
This original recording aid connects the questions a reviewer may need to resolve. It is not a statutory form or a promised set of product fields. Select the detail needed for the applicable process and evidence review.
| Process or task | Applicable procedure/version | Training event | Understanding check | Change reference | Outstanding follow-up |
|---|---|---|---|---|---|
| The assigned work being reviewed | The instruction taught and its revision | Date and source evidence for the event | The means used and supporting result | The relevant change, if any | Unresolved question, owner and review date |
Trace the training event to its source, then check that the understanding evidence concerns the same requirement. Record missing information without replacing the original evidence. A completed handoff documents the review; it does not authorize operation or establish that every applicable obligation has been met.
For distinct follow-up questions, use the scoped lockout/tagout training records guide and the training matrix audit checklist. Keep the task-specific requirements separate from the editorial review structure.
Read the product guide for the documented workflow and compare the published plans against your requirements.
