A Code Enforcement Action Request (CEAR) is a concern or complaint submitted to your
municipality's code enforcement office — either by a member of the public through the
unauthenticated public form, or by staff on a caller's behalf. Officers triage and route every
CEAR from a dashboard, and the system can email the submitter and/or staff as that happens.
As a system administrator, your configuration surface for CEAR is entirely about who gets
emailed, when, and with how much detail. There are two separate, independently-running email
systems layered on top of CEAR — you don't have to choose one; both can be active at once, and
they serve different purposes.
| Legacy routing blast | Update-blast system (recommended) | |
|---|---|---|
| What it covers | Only the moment an officer routes a CEAR | Routing plus every notable event afterward in the CEAR's host case (violation attached, NOV sent, case closed, etc.) — see the task page for the full list of 9 event types |
| Who configures it | Nobody — it's always on by default; an officer can uncheck a box on their own submission form | You, per event type, per municipality |
| Default state | On | Off for every event type until you turn it on |
| Who it emails | The whole municipality's subscribed staff list, plus the requestor | One targeted email per eligible recipient — the requestor and/or the specific staff member who logged the original request, if they opted in |
| Unsubscribe | None | Every email includes a working, no-login-required unsubscribe link |
| Where you manage it | Nothing to manage — it's a fixed behavior | Muni Tools → Municipality Manager → "CEAR Subscriber Update Blasts" panel |
Every blastable action always shows the acting officer a visible notice with a one-click
"don't send this time" option, no matter what you've configured. This is a deliberate,
non-negotiable product guarantee (ratified 2026-09-30) — not a bug and not a setting you can
change. You decide whether an event type is available to send at all; the officer in front
of the specific case always decides whether this one actually goes out. There is no
administrative way to force a blast through without that notice, and no municipality setting
removes it.
CEAR routed by officer) before enabling the full set.STANDARD for one event andMINIMAL for another on the same municipality; there's no single "detail level forBack to: hub page · subsystem registry entry #20