Definition
CMR measures the average number of days between the actual completion date of regulatory maintenance tasks and their compliance deadline, providing a forward-looking risk indicator where shrinking margins signal that AI scheduling is eroding the buffer between when compliance work gets done and when it must be done.
The Measurement Gap
On-time rate metrics measure binary compliance (done before deadline or not) but provide no signal about how close to the deadline work is being completed. A facility completing all regulatory tasks on the day of the deadline looks identical to one completing them two weeks early in any on-time rate dashboard, but these represent very different risk profiles. When AI scheduling optimizes for overall throughput, it may gradually compress the lead time between completion and deadline, eroding the operational buffer that provides protection against unexpected delays without ever triggering an on-time rate alert. This quiet erosion of margin is undetectable until a schedule disruption causes a breach, at which point the buffer that should have absorbed the disruption is no longer there.
Decision Supported:
CMR determines whether the operational buffer between regulatory task completion and compliance deadlines is adequate to absorb realistic schedule disruptions, or whether AI scheduling is systematically using up that buffer in ways that will eventually cause compliance breaches.
Formula
Plain language: For each regulatory task completed in the measurement period, subtract the completion date from the compliance deadline. A positive number means the task was done early; a negative number means it was done late. Average all of these across the R tasks in the period. Also count the Deadline Breach Rate: tasks completed after their deadline as a percentage of all regulatory tasks.
Notation:
CMR = (1/R) × Σ_r (Deadline_r − Completion_date_r)
DBR = (Tasks_past_deadline / Total_regulatory_tasks) × 100
Variables:
| Variable | Definition | Unit |
|---|---|---|
| Deadline_r | The regulatory compliance deadline for task r (the legally required completion date, not any internal target) | Days (as a date for individual calculation, converted to day-difference) |
| Completion_date_r | Actual date task r was completed and documented | Days |
| R | Total number of regulatory tasks due in the measurement period | Count |
| Tasks_past_deadline | Count of tasks where Completion_date_r > Deadline_r | Count |
| Total_regulatory_tasks | Same as R | Count |
Cap early completions at +90 days to prevent tasks completed far in advance from inflating the average margin and obscuring current near-deadline risk. For open tasks that have not yet been completed, compute projected margin based on current schedule: open tasks represent real-time risk visibility. Track CMR separately by compliance deadline frequency: monthly tasks (generator testing), quarterly tasks, and annual tasks have different risk profiles.
Proposed formula, pending validation pilots.