Post-enforcement compliance monitor

A post-enforcement compliance monitor earns its place when it returns one of two products: a cited escalation, or an empty result.

The cited escalation restates facts that already exist on the file. It names the ordered action in the words of the enforcement order. It names the deadline printed on that order. It names the evidence the log still lacks after that deadline has passed. Those three cites are the quality bar. An escalation that says a target is "behind" without pointing to the action, the date, and the missing proof is not ready for an officer.

Empty is the right product when the target is on track. If the deadline has not arrived, if the required proof is already in the log, or if the ordered action is complete, the monitor stays silent. A queue of all-clear flags is not a quality outcome. Officers learn to ignore it.

The monitor does not close the case, does not assess a new penalty, and does not grant more time. The compliance follow-up officer still reads the flag, still checks the live file, and still records the escalation if the gap is real.

This check starts after the order is already issued. If the ordered action and its deadline are still being written, finish that work with the enforcement notice drafter. The monitor cannot cite language that is not on the order.

Do not start from a score that a target is "likely noncompliant." Start from two sources.

Load the order. For each discrete ordered action, capture the bound person or entity and the deadline printed for that action. Split a three-action order into three rows when the dates differ. If an action has no deadline on the order, do not invent one. Hold that row for a human to repair the order or to confirm that a different legal clock applies. An escalation with no deadline cannot tell the officer whether the target is late. It is a broken cite, not a finding.

Load the evidence log the agency already uses: inspection photos, contractor certificates, lab results, affidavits, and any other proof the order itself treated as sufficient. Permitting, licensing, and code case files often sit in systems from vendors such as Accela, Tyler, Salesforce Government Cloud, and Microsoft. Treat those platforms as the class of systems of record. The monitor reads them. It does not replace them, and it does not become a second case file.

Match each ordered action to the evidence the order named. A grease-interceptor installation that required a licensed plumber's completion certificate is not proved by a supply invoice. Two rounds of sampling are not proved by one round. Stay conservative. If the order named a document, look for that document. Do not accept a near-miss and then write that the target "substantially complied."

Here is one illustrative pass, not a measured program result. A food facility is ordered to install a grease interceptor and file a licensed plumber's completion certificate by 15 March. On 16 March the evidence log holds a purchase invoice dated 8 March and a contractor email that the unit is "on order." There is no certificate and no inspector observation of the installed unit. The monitor escalates with the ordered action as written, the 15 March deadline from the order, and the missing certificate and observation. It lists the invoice and the email as reviewed and insufficient. It does not calculate a percent complete, and it does not propose a new date.

If the same log already holds the certificate and an inspector photo on 14 March, the monitor returns empty for that row. The officer does not need a flag that the file is fine.

Write the escalation as a citation block.

Identify the order. Quote the ordered action. Quote the deadline as it appears on the order. State what the evidence log lacks, and point to the log entries that were reviewed so the officer can see they were considered. Stamp the as-of time of the check.

Do not attach a recommended penalty. Sizing a sanction belongs in a separate charging or settlement step. If the officer later needs a dollar figure, that work goes to the penalty calibration engine after the miss is confirmed. Mixing a missed-deadline flag with a proposed fine trains staff to treat the flag as a new penalty. The flag is a prompt that the ordered cure has not been shown. It is not an assessment.

Do not invent a cure window. If the order said 15 March, do not add days for mailing, for weekend overflow, or for a vendor batch job unless that grace period is already written in the order, the statute, or a published procedure that applies to this class of orders. Two clocks on one file, the legal one and the unofficial one, are how follow-up either fires too early or not at all.

Leave on-track rows empty. A certificate filed on time should not enter the escalation queue. A deadline that is still weeks away should not enter it either, unless a separate early-warning rule exists in writing. That rule is not this monitor. Silence means no follow-up is due today.

Run the match on a cadence that matches how the evidence log is updated. If inspectors post photos at the end of the field day, a nightly pass is enough. Hourly reruns will raise the same miss without new proof.

Open the cited escalation and check it against the live file. Proof can land after the model ran. A certificate uploaded late in the afternoon can make an evening flag stale. If the proof is now present, dismiss the flag and leave the case on track. Do not send a follow-up notice because a queue item existed.

If the gap is real, escalate in the form your procedures already require: a follow-up notice, a show-cause listing, a referral for inspection, or a recommendation to amend the order. When the next step is a written notice that must restate the original ordered action and the missed deadline, use the enforcement notice drafter. The citation block is source material. It is not the notice.

If the miss means the site may still be in the unlawful condition, send it to inspection planning instead of inventing a desk-only cure. The risk-based inspection scheduler is where a missed remediation competes with other inspection demand. The monitor should not auto-create an inspection.

Write what you did into the case file. The useful chain is order, deadline, missing evidence, officer action. If that chain exists only in the model output, the next reviewer cannot tell a machine flag from a human finding.

Use this monitor on open enforcement files with outstanding ordered actions. After the case is closed, remaining duties such as reporting, financial assurance, or land-use restrictions belong on a different clock. Hand those to the post-closure obligation monitor. One queue for both will hide both kinds of miss.