Abstract
Field Computer-implemented systems for triggering employee requalification based on regulatory calendar expiration rather than document change detection, applicable to compliance domains where periodic recertification is mandated regardless of whether reference content has changed. Background Many compliance regimes mandate periodic employee retraining on fixed schedules: annual harassment training, biennial OSHA refresher courses, quarterly anti-money-laundering updates. These requirements are triggered by the passage of time, not by changes to authoritative documents. The approach described here manages requalification purely through calendar logic, with no document ingestion, versioning, or analysis of any kind. Technical Description The system maintains a regulatory_calendar table mapping each compliance domain to its mandated recertification parameters. Each entry contains: domain_id, jurisdiction_id, recertification_interval_days, new_hire_deadline_days, recordkeeping_retention_days, and penalty_severity_weight. Multiple entries can exist for the same domain across different jurisdictions, reflecting overlapping regulatory requirements. Employees are mapped to applicable compliance domains based on their work location and role classification. The mapping is computed at enrollment time and updated when an employee's location or role changes. The system evaluates each employee against all applicable jurisdictions simultaneously, applying the union of all required content tracks with the most restrictive deadline and retention period enforced across overlapping jurisdictions. A compliance status state machine tracks each employee-domain pair through four states: compliant (certification current), approaching_deadline (within configurable warning window, default: 30 days), overdue (past deadline, not yet non-compliant), and non_compliant (past grace period). Transitions are driven purely by elapsed time relative to the employee's last certification date for that domain plus the jurisdiction-specific recertification interval. When an employee's status transitions to approaching_deadline, the system generates a requalification_obligation record containing: employee_id, domain_id, jurisdiction_id, last_certification_date, deadline_date, and assigned_content_ids. Manager alert priority is weighted by the jurisdiction-specific penalty_severity_weight, so a jurisdiction imposing per-offense-per-day penalties generates higher-priority alerts than one with flat penalty structures. The system computes an organizational compliance risk score by aggregating per-employee compliance states across all active domains, weighted by penalty severity and deadline proximity. Distinguishing Characteristics This system is triggered by calendar expiration, not by document change events. It does not ingest, version, or analyze reference documents. It does not compute section-level differentials between document versions. It does not maintain source-attribution records binding assessments to document sections. It does not perform reverse-index traversal. The requalification mechanism is purely temporal: time elapsed since last certification compared against jurisdiction-specific intervals. This is a fundamentally different trigger model.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Davis, Kenneth, "Regulatory Calendar-Driven Periodic Requalification Without Document Change Analysis", Technical Disclosure Commons, (March 25, 2026)
https://www.tdcommons.org/dpubs_series/9640