VerityTrainCustomer wiki Start training

Managing assignments

Assignments are where the statute becomes a calendar. The clocks below are the ones your deadlines run on.

The due-date clock, per state

When you assign training, Verity Train sets the due date from the statutory cycle for that employee's state — not from a company-wide policy you have to research yourself:

JurisdictionStatutory cycleDue-date clock in the app
New York (§201-g)Annual — every employee, every year12 months from assignment
New York City (§8-107(30))Annual, within each calendar year12 months from assignment
Illinois (775 ILCS 5/2-109)Annual12 months from assignment
Chicago (Muni. Code §2-160)Annual, July 1 – June 30 training year12 months from assignment
California (§12950.1)Every two years24 months from assignment
Connecticut (§46a-54(15)(B))Within 6 months of hire; refresher every 10 years6 months from assignment, then the 10-year refresher
Delaware (§711A(g))Within 1 year of hire, then every 2 years12 months from assignment for new hires, 24 months on repeat
Maine (§807)Within 1 year of hire (supervisor add-on: 1 year from role)12 months from assignment

New supervisors and new hires obey their own statutory windows — California's are the strictest that most of our customers juggle: six months from hire for nonsupervisory staff, six months from assuming the role for new supervisors. Change the role and the app resets the window accordingly (see Adding employees).

Anatomy of an assignment

Each assignment tracks four states, and every transition writes to the audit log:

  • Assigned — the employee was invited; the statutory clock is running.
  • In progress — lessons underway. Lesson completion is quiz-gated at 80%, so "in progress" always means genuine work, not a video left playing.
  • Completed — the final lesson passed and the certificate issued, with statute citation and verification ID.
  • Overdue — the due date passed without completion. The clock doesn't stop; the assignment goes red and keeps reminding.

Reminders and overdue work

  • Reminder emails go out ahead of the due date automatically. You don't schedule them; they scale themselves to the clock.
  • An overdue assignment stays open and keeps reminding until it completes. The dashboard totals overdue items separately so the exposure is always visible — never silently buried under a new cycle.
  • When someone finishes late, the record shows the true completion date. Don't ask it to show anything else: an honest late record beats a pretty fake one in every setting that matters.

Re-running annual and two-year cycles

The statutes are recurring by design, so cycles are too:

  • NY / IL / NYC / Chicago: when an employee completes a cycle, the next annual assignment opens on the 12-month clock. You don't re-assign by hand each year.
  • California: the same mechanism on a 24-month clock, measured from each employee's own completion date — which matters, because §12950.1 tracks two years from their last training, not a single company reset day.
  • Content refreshes: when a legislature amends a mandate, the state pack is updated against the new checklist and the next cycle assigns the current version. Your prior-cycle certificates keep the version and citation they were earned under.
The operating rhythm that works: new hires added in their first week, the dashboard scanned once a week for overdue red, exports taken before an audit rather than during one. Ten minutes a week for most companies.