Every new CEAR lands on the dashboard (CE → Action Requests) unprocessed. Routing it walks
you through a 3-step dialog: confirm the property, pick a route, then execute that route.
Click Process this request on any card (or re-route this request on an already-routed
one) to open the dialog. As of September 2026, every request type starts here — including
municipal-general requests. If the request has no property, you'll see "No property linked"
along with the property search box.
Pick a route from the list. Which routes you see depends on the request:
| Request shape | Routes offered |
|---|---|
| Muni-general | Action underway, Action completed, Invalid request, Referred to another department |
| Not at a known address | Invalid request, Referred to another department |
| Property-linked, property already has open cases | Attach to existing case, Attach to new case, Attach to occupancy period, Invalid request, Referred to another department |
| Property-linked, no open cases yet | Attach to new case, Attach to occupancy period, Invalid request, Referred to another department |
Click Continue to execution to move to step 3, or Back to property to return to step 1.
What you see depends on the route you picked:
"No violation found" has been retired as a routing option. You may still see it on older
requests that were already closed out this way, and it's still available as a re-route target
if you need to match old behavior, but it's no longer offered for new routing decisions. A
genuine "no violation" finding should now go through a real code enforcement case (attach to
new/existing case) so the determination is properly logged with an inspection, rather than a
one-click dashboard closeout.
Any already-routed (terminal) request can be re-routed — an UNPROCESSED option appears in
step 2 as an escape hatch, resetting it back to the top of your queue. As of September 2026,
re-routing a request that was already terminal automatically leaves an internal note recording
the change (which route it moved from and to, and who did it) — you don't need to write that
note yourself.
Depending on your municipality's configuration, committing a route (or several other
case-lifecycle actions later on) can send an automatic status-update email to the requestor
and/or the staff member who logged the request. Whenever that's possible, you'll see an
inline notice right above the commit button — something like "A status update email may be
sent to N recipient(s) for this action" — with a one-click "Don't send this time" option.
This is not configurable by your municipality and has no exceptions: you always get to make the
final call on that one action, regardless of what's been enabled behind the scenes.
Back to: CEAR user guide · hub page