Compliance

Regulatory obligations tracked against the PM schedules that fulfill them - what's required, what's actually being done, and the paper to prove it.

Compliance tracks the obligations with someone else's clock on them: fire inspections, elevator licenses, boiler certificates, backflow tests, playground audits. The module's job is that nothing lapses quietly.

The model: items, linked schedules, computed status

A compliance item is the obligation - "Annual fire alarm inspection". It carries a name, description, a regulation reference (the code section or standard), what it applies to (a system or an infrastructure network), and a compliance period in months.

The item then links to the PM schedules that fulfill it - each link with a required frequency and a weight for how much it contributes to the item's score. Status is not something you set: it computes from the completed work orders those schedules have actually generated. If the quarterly inspections are being completed on rhythm, the item is compliant; if they stop, it degrades - no one has to remember to update a status field.

Status at a glance

The compliance list and its dashboard tab show every item as compliant, warning, or non-compliant, with a gauge summarizing the portfolio. An item with no linked schedules scores as non-compliant - an obligation with nothing fulfilling it is exactly the situation the module exists to surface. Check the list as part of your routine; the module computes status but does not send due-soon notifications.

Evidence

Attach the certificate, report, or sign-off on the item's detail page Documents tab. When the authority, insurer, or auditor asks, the answer is the item with its paper hanging off it and the completed work order history behind it.

Compliance and the work loop

The inspection itself is often work you dispatch - a work order to a vendor or staff, optionally with an inspection form. The pattern that works:

1. The compliance item defines the obligation and its rhythm.
2. A PM schedule, linked to the item, generates the work orders that get it done. Associate it with the system rather than individual assets where the obligation covers a whole plant - "Refrigeration Monthly Inspection" on the Refrigeration system inspects every related asset under one work order, so nothing under the system escapes the audit trail.
3. Completing those work orders is what moves the item's computed status - and the certificate they produce attaches to the item's Documents tab.

Deficiencies found during a compliance inspection become their own corrective work orders, linked to the asset - so the finding, the fix, and the cost all stay connected.

Programmatic access

compliance:read / compliance:write on the REST API; compliance item/record tools via MCP.