Portfolio Demo · Community services
311 Service Requests
A civic engagement tool showing how residents can report municipal issues and track their resolution from a single dashboard.
Demo uses simulated data — not a live municipal system.
- React
- TypeScript
- Tailwind CSS
- Accessibility
Interactive demo
10
Total Requests
3
Open
3.5d
Avg. Resolution
4
Resolved This Month
Categories reflect actual city service request systems as of March 2026. Individual requests are sample data for demonstration purposes.
Case study overview
The problem
Most cities still route 311 calls through phone and email. Staff manually log issues, assign them by hand, and send status updates one at a time. Residents who report a pothole have no idea if it was received, so they call again. Or give up. The result is call volume that drowns dispatch teams and visible community frustration that's entirely avoidable.
The approach
A structured intake system that captures issue type, location, urgency, and contact info from the start. Tickets move through a status lifecycle (Open → In Progress → Resolved) with optional email notifications at each stage. The staff view lets teams filter, assign, and update without a separate CMS. Accessible throughout: keyboard navigation, ARIA roles, and WCAG 2.1 AA contrast baked in from the start, not added after.
Why it matters
A 311 system residents actually use is a force multiplier for public works teams. Fewer repeat calls, less manual logging, and a visible record of resolved issues that builds community trust. Staff time saved on intake translates directly to faster response times — the metric residents and city councils actually track.
Have something similar in mind?
Need a civic tool with this shape?
Stoa designs and ships resident-facing tools, internal workflows, and public service interfaces that stay fast, legible, and accessible from day one.