From report to resolution, with an owner and a deadline at every step
A report on Avisa Aí never enters an invisible queue: it moves through well-defined steps, each with who can act, the deadline to act and a record of what was done.
The six steps of a report
Every transition records who acted, when, with what justification and what evidence.
- 1
The citizen reports
CitizenLong-press on the map, pick a category, add a title, a description (typed or dictated) and at least one photo or video. The spot must be within 100 m of the reporter, and the app warns if an active report already exists within 50 m, suggesting support for it instead of a duplicate.
- 2
AI takes a first look
AI agent secondsThe photo (or video frames) is analyzed: what it actually shows, whether the chosen category matches, whether the image is blurry or dark, and whether the text contains offensive language. When the evidence clearly shows a different problem, the category is corrected instead of the report being rejected.
- 3
The community approves
Another citizen 7 daysA citizen other than the author, within 100 m of the spot, confirms the problem is real. Authors with a strong track record (high reputation and previously approved reports) are approved automatically. Managers and officers do not approve: they only act afterwards.
- 4
The team starts the work
Maintenance officer or manager per categoryOnly someone responsible for the report’s city and category can start it, and they must be on site. Unassigned reports go automatically to the officer with the shortest queue. The AI suggests a risk priority and a clearer description for the team.
- 5
The team closes with evidence
Maintenance officer or manager per categoryCompletion requires a justification and may include photos of the repair. Every step is recorded on the report’s timeline and reviewed by the AI and by moderation, which can reverse invalid evidence.
- 6
The author validates the fix
Reporting citizen 7 daysOnly the person who opened the report declares the problem truly solved. If they disagree, the report goes back to “in progress”. With no answer in 7 days, the case closes automatically and the author loses reputation points.
The statuses citizens follow
Each status has a fixed color in the app and the dashboard, so it is recognized at a glance on the map.
- Pending
Awaiting community approval.
- Awaiting resolution
Approved; the team has not started yet.
- In progress
Repair underway.
- Awaiting validation
The team finished; the author still has to confirm.
- Resolved
Confirmed by the author or closed after the deadline.
- Rejected
Not a real problem, offensive, or rejected in review.
Deadlines based on risk
There is no federal law setting a deadline for each kind of urban problem, so Avisa Aí uses deadlines tiered by safety and health risk. If the AI spots immediate risk in the image, any category moves to the shortest deadline (1 and 3 days).
| Category | First response | Resolution | Basis |
|---|---|---|---|
| Structural damageBridges, walls, sinking sidewalks | 1 day | 3 days | Safety risk (civil defense) |
| Water leakBurst pipe, water gushing onto the street | 2 days | 5 days | Sanitary risk |
| SewageOpen sewage, broken manhole cover | 2 days | 5 days | Sanitary risk |
| Street lightingStreetlight out or flickering | 3 days | 7 days | ANEEL (energy regulator) reference |
| SignageFallen sign, faded markings, traffic light | 5 days | 10 days | Road safety |
| DrainageClogged storm drain, flooding | 5 days | 10 days | Flood prevention |
| PotholePotholes and damaged asphalt | 5 days | 14 days | Road maintenance |
| AccessibilityDamaged ramp or tactile paving | 7 days | 15 days | Brazilian Inclusion Law |
| TrashPiles and illegal dumping | 7 days | 15 days | Urban upkeep |
| VegetationFallen tree, overgrown weeds | 7 days | 15 days | Urban upkeep |
Community approval and author validation are human-response steps with a fixed 7-day deadline for any category. When a deadline passes, city management is alerted and the city loses points in the upkeep ranking.
Rules that keep the process trustworthy
The safeguards below are enforced by the server; the app only reflects what is allowed.
Nobody approves their own report
Authors never approve or reject what they created, and managers or officers only act after approval. The check runs on the server, inside a transaction, before anything is written.
You have to be on site
Creating a report requires being within 100 m of the spot. Approving, starting, completing and validating also require being within 100 m of the problem.
The reporter closes the case
The team declares it is done, but only the author declares it “resolved”. That stops tickets from being closed just to hit a target.
Similar reports are flagged
The app warns about active reports within 50 m before sending; the map clusters nearby markers; and the dashboard shows possible same-category duplicates within 100 m. Nothing is merged automatically.
Abuse limits
At most 20 reports a day, at least 60 seconds apart, and automatic censoring of offensive language in titles, descriptions and comments.
No case gets stuck
Periodic automatic routines assign owners, alert management when a deadline passes and close forgotten validations; moderation can take over overdue cases.
Points and reputation
Gamification rewards quality contributions and penalizes fake or abandoned reports.
- Creating a report: +10 points. Report approved: +15. Resolution validated: +20.
- Whoever completes the repair gets +30; whoever started the work and whoever approved also score.
- Rejected report or evidence: −10 reputation for the author.
- Resolution not validated within 7 days: the case closes and the author loses 10 reputation.
- There are 14 score levels; authors with high reputation and an approval track record get their reports approved automatically.
See what citizens get in the app
A map, reporting in a few taps, deadline tracking and notifications on every change.