Research note
How often does training completion evidence lag the due date?
A local method for measuring how often required training has reviewed completion evidence by the due date, with a clear rule for what counts as proof.
Published

Table of contents
Question and scope
The question covers training that the employer requires for a role, a task, or a compliance duty. It includes safety, security, privacy, and role-specific modules. It excludes optional courses that carry no completion requirement. The review covers one employer, one review window, and the roles that commonly receive required training.
A case enters the sample when the training appears in the written requirement list and a due date exists. A course without a due date enters as an undated case. Record the source of the requirement and the date it was issued. If the due date was extended, record both dates and the reason for the extension.
The stop point is the date a named reviewer accepted the evidence, not the date the employee clicked through the last screen. A completion screen can show activity without proof of understanding. The accepted evidence may be a quiz score, a work sample, or a signed checklist. Report the two dates separately so a fast click does not look like a completed review.
Definitions and evidence standard
Define accepted evidence before reviewing any case. The definition must name the training, the proof, and the reviewer. A record with no reviewer does not meet the standard. Record the definition with the case so a later reader can apply the same rule.
Use the learning system, the review note, and the employment record as the primary evidence. A manager's memory can support context but cannot replace a dated entry. Mark a case as unverified when the only evidence is a verbal report. Report the share of unverified cases with the result.
Separate the employee's completion from the reviewer's acceptance. A module can be finished on time and still wait for a review. Measure both steps so a slow reviewer does not look like a slow employee. The two numbers answer different questions about the process.
Sampling and measurement
Freeze the list of required training cases before reviewing any of them. Include more than one manager, more than one module, and more than one due month. Record the export date and the filter used. Do not remove a case because the record is incomplete; incomplete cases are part of the finding.
If the list is large, take a random sample and record the selection method. Keep the full count beside the sample so a reader can see coverage. A replaced case should be reported as a deviation. The sample should be large enough to compare at least two teams.
Measure the number of cases, the share with accepted evidence by the due date, the median and longest lag, and the share with no recorded evidence. Add the number with no reviewer and the number with an unclear due date. Report the counts by module and manager. A single percentage hides which module drives the delay.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of late evidence under one manager may mean the reviewer never received the files. A cluster on one module may mean the due date fell during a busy period. Read the cases behind the largest cluster before naming a reason.
Compare the lag with the review method. A work sample may take longer to review than a quiz score. Record the evidence type and the number of cases assigned to each reviewer. The comparison can show whether the problem is capacity or the standard.
Check whether late cases were eventually accepted and whether the employee was told what was missing. A late acceptance with an explanation is different from a case that was forgotten. Record the date of any update and the reason given. The quality of the delay matters alongside its length.
Limitations
The review measures evidence timing, not whether the employee can apply the training. A fast review can still accept weak proof. The result describes the record clock, not the skill outcome. Report it beside a sample work check so a reader does not overread the number.
The requirement list may change during the window, and an older case may follow a rule that was appropriate at the time. Record the requirement version rather than applying the current rule retroactively. A case that missed an old standard may not be a current defect. Keep the version note with the case file.
A case that is never recorded is invisible to this method. The count may understate the gap if employees complete training without a review. Pair the review with an anonymous question about whether employees know what proof is accepted. The answer can reveal a gap the record cannot show.
Practical next step
Publish one requirement list per role with the proof and the reviewer named. Send the list at hire and at each role change. Record the due date in the same system as the evidence. A clear standard makes the review measurable.
Set a review window after the due date and an escalation date after that. Tell the employee what is missing and who will review it. Record the message and the response. The window should close the gap rather than only mark it.
Test the process for one quarter and compare the accepted-by-due share with the baseline. Keep the change if it improves the result without turning the review into a race. If one module creates a delay, fix the assignment or the proof standard. The goal is accepted evidence, not a longer file.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| Occupational Safety and Health Administration, Training Requirements | osha.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |