CivicLens

About CivicLens

Complaining to the city shouldn’t feel like shouting into a void.

Every city has potholes nobody fixes and streetlights nobody reports — not because residents don’t care, but because reporting feels pointless. CivicLens makes it effortless to be heard, and makes the city’s response visible: one public map, one status timeline per issue, and a priority score the whole neighborhood can move.

How it works

1. You report

A photo, a pin on the map, and a sentence. Thirty seconds from your phone — no accounts, no forms that feel like tax returns.

2. AI triages

The triage service classifies the issue into one of seven categories, scores its severity from 1 to 5 with a written rationale, and routes it to the right department — Public Works, Sanitation, Water Authority, and so on.

3. Duplicates merge

If your neighbors already reported the same pothole, your report is merged into theirs instead of creating a second ticket. Your backing still counts — it raises the priority score.

4. Everyone watches

Every report lives on the public map with a status timeline: reported → acknowledged → in progress → resolved. Transparency is the whole point.

Three things we’re upfront about

Honest about AI

Triage runs on an AI model when it is available. If the model is unreachable, a transparent keyword-based rules engine takes over — and the app says so on the triage result. We never present a guess as a certainty.

Honest about data

The map ships with clearly labeled sample reports so you can explore the product. They carry a “Sample” badge everywhere they appear — we never pretend they are real resident reports or a live city integration.

Honest about who we are

CivicLens is an independent community tool built for the WarriorHacks 2.0 hackathon. We are not affiliated with, or endorsed by, any city government or municipal body.

See something? Say something.

It takes thirty seconds, and your neighborhood can watch it get fixed.

Report an issue

Built for WarriorHacks 2.0 · Map data © OpenStreetMap contributors