A Code Enforcement Action Request (CEAR) is a concern or complaint about a property or
general municipal issue. Most come in through the public online form, but you can also log one
yourself on behalf of a caller. Every CEAR lands on your dashboard unprocessed, and it's your
job to review it and route it somewhere — a new or existing code enforcement case, an
occupancy period, or a closeout decision like "invalid" or "referred to another department."
The CEAR dashboard (CE → Action Requests) is your home base — it lists every unprocessed
request as a card, with a search/table view underneath for finding anything, routed or not.
Depending on how your municipality has things configured, routing a request — or almost any
later action on the case it becomes — can trigger an automatic status-update email to the
person who submitted it and/or whichever staff member logged it. The actions that can possibly
trigger one are:
Not every municipality has every one of these turned on — see the
CEAR admin overview for how that's configured. Whichever
ones are enabled, you will always see a visible notice and a one-click "don't send this time"
option before any of them go out — there is no configuration, anywhere, that lets one fire
without you seeing it first. If you don't want an email sent for a particular action, just check
that box; it only skips that one instance.
Back to: hub page · subsystem registry entry #20