Clarity Value/ Solutions/ 311 / Citizen Services

From “there’s a pothole” to a closed work order.

One intake surface — web, phone, mobile — and one queue your public-works team actually wants to open. Every request lands as a typed, geocoded, routable record. Every closure is a status update the reporter can see.

SOC 2 Type II·CJIS- and FedRAMP-aligned·US-only on Google Cloud·Built in Miami
Workflow

Report. Route. Resolve. Close the loop.

Four phases. The reporter sees status updates the whole way through — and a photo when the crew finishes.

01Report

Web, phone, or app

Map-pinned, geocoded, photo-attached. Auto-deduped against open work orders nearby.

02Route

Department-aware dispatch

The right crew gets the right ticket. Public works, parks, code enforcement, sanitation — typed at intake.

03Resolve

Field-app closure

Crews close from a phone with photo evidence. The record updates in real time.

04Notify

Reporter gets confirmation

Status update with the closure photo. The reporter knows it's actually fixed.

Capabilities

Three things this module is actually good at.

Three core capabilities — intake, dispatch, closure — built around the reality that the front desk, the dispatcher, and the field crew are three different people with three different tools.

01  /  Intake

Map-pinned reports. Auto-deduped at the door.

Citizens drop a pin, snap a photo, pick a category. The system checks for nearby open tickets and merges duplicates so the same pothole isn't dispatched three times.

  • PinMap-first reporting with reverse-geocoding and neighborhood routing.
  • PhotoPhoto + description — required for categories that need visual confirmation.
  • DedupeAuto-dedup against open tickets within a configurable radius.
CITIZEN APP · REPORT 01
DISPATCH · MAP 02
02  /  Dispatch

A queue your dispatcher actually wants to open.

List view, map view, kanban view — same data, three angles. Filter by district, category, age, priority. Drag a ticket onto a crew. Done.

  • TriagePriority by category, age, repeat-offender. The 3-day pothole sorts to the top automatically.
  • AssignDrag-to-assign onto crews; crew accepts on their phone before they're moving.
  • SLAPer-category SLAs visible on every ticket — graffiti 5 days, pothole 3, downed tree same-day.
03  /  Field & closure

Closed in the field. Confirmed for the reporter.

The crew gets the ticket on their phone. They close it from the truck — photo of the patched pavement, a one-line note. The reporter gets a notification with the closure photo. Loop closed.

  • FieldMobile crew app with offline mode, route optimization, and same-day reassignment.
  • EvidenceClosure photo required by category — required-field amber, not error red.
  • NotifyAuto-notify the reporter with closure photo and a one-tap "still broken?" reopen.
CREW · TODAY 03
Configuration

Your categories, your crews, your SLAs.

Every city's 311 catalog is different. Sanitation here is two divisions; parks there is one crew. Configure categories, routing, SLAs, and notification templates to your operations.

Categories
Your service catalog
Categorize at the granularity your operations need. New category live in minutes — no vendor ticket.
Routing
By district, category, geofence
A pothole on Main Street routes to Public Works North. Graffiti in District 4 routes to Code. The clerk reroutes without a ticket.
SLAs
Per-category response targets
Tree limb same-day. Pothole 3 days. Graffiti 5 days. Tracked, reported, escalated.
Notifications
Templates the reporter trusts
SMS + email templates per category. Reporter sees received → assigned → resolved with photo evidence.