Inspection / testing (ITM) overdue.

Trigger, action plan, and escalation criteria.

Related metric

fire_system_readiness

Trigger

itm_due_date within itm_lead OR itm_due_date passed (raises ITM overdue)

Value drivers

Operational continuity

Preconditions

The ITM cycle and its due dates per building are recorded, with a configurable itm_lead window for the approaching reminder. Inspection records are captured as they are completed.

Human role

Primary — Keedian tracks the ITM cycle dates and raises the reminder / overdue alarm; the inspection itself is the licensed provider's. Operators refer the due inspection and retain the record as compliance evidence.

Action plan

(1) Raise a reminder as the ITM cycle enters the itm_lead window; raise an overdue alarm once the due date passes. (2) Refer the due / overdue inspection to the customer's licensed fire / life-safety provider. (3) Capture the completed inspection record and retain it as audit-ready compliance evidence.

Escalation

(1) An inspection passes overdue without a scheduled visit → escalate to the customer, since an out-of-certification life-safety system is a liability exposure. (2) Repeated overdue cycles on the same building → flag the ITM program for a standing schedule.

Prevention

(1) Load the ITM regime and due dates per building at onboarding and keep them current. (2) Set itm_lead so the reminder gives the provider enough runway to schedule before the due date.