Community Evidence Standards

FixMyRoad · 2026-09-01

The premise

Community evidence is not a trial. It is a way to help a public agency find and understand a road hazard.

The best report does three things at once: it makes the road condition visible, gives the responsible authority enough detail to locate it, and avoids turning uncertainty into accusation. That balance matters. Philadelphia’s public guidance, for example, asks people reporting street damage to describe the defect’s exact location, size and shape, whether water or gas is escaping, and to include pictures if possible because the description can help the city address the problem more quickly. Toronto’s pothole guidance routes pothole repair reports through 311 and notes that public reports are one way the city identifies potholes.

A community evidence standard should therefore be simple enough for an ordinary resident to use, but careful enough that it does not expose people to unnecessary danger or unfair blame.

The minimum useful report

A useful report can be short. It should include:

1. Location. Give the street name, nearest cross street, direction of travel if relevant, and a landmark. Where the official form uses a map or postcode, use it. GOV.UK, for instance, starts by asking for the postcode of the road where the pothole was found; Philadelphia asks for the defect’s exact location.

2. Date and approximate time observed. This separates a current hazard from an old memory or reposted image. If the condition changes after rain, freezing, construction, or a temporary repair, say that.

3. Photos from safe positions. Take one close photo showing the defect, one wider photo showing its road context, and, if safe, one photo with a fixed landmark in view. Do not stand in traffic, stop suddenly, or create a second hazard in order to document the first.

4. Plain condition notes. Say what is visible: “deep pothole in right wheel path,” “standing water covering lane edge,” “raised metal plate,” “missing warning sign,” “cracked surface near bike lane.” Avoid conclusions you cannot know, such as who caused it, whether a crew ignored it, or whether a named person is responsible.

5. Safety notes. Include what changes the risk: bike lane, crosswalk, school route, bus stop, high-speed curve, poor night visibility, water or gas escaping, or an unprotected opening. NYC311’s pothole and cave-in guidance distinguishes ordinary pothole reports from emergency openings and says to call 911 for an unprotected street opening that could cause an accident.

6. Official tracking information. If the city or road agency gives a service request number, save it. If a later report refers to the same defect, cite that number rather than starting a rumor chain.

What not to collect

Collect the road condition, not the private lives around it.

Avoid posting faces, license plates, house numbers, children, workers’ names, or identifying details unless they are truly necessary to locate the defect or explain the safety risk. When sharing publicly, crop or blur what is not needed. WITNESS’s guidance for using eyewitness video is written for higher-stakes human rights work, but the principle carries over: “do no harm” requires thinking about the privacy and security of people shown in footage before sharing it.

This is especially important where a report could expose a resident, tenant, worker, or small business owner to retaliation or blame. A road report should not say “the people at this address caused this” unless that claim is documented and relevant through an official process. In most cases, it is enough to say: “hazard outside 1400 block,” “near the north driveway,” or “adjacent to the construction entrance.”

A fair photo standard

Good photos answer location and severity without exaggerating.

Use a three-photo pattern when possible:

• Context photo: the lane, curb, crosswalk, bike lane, or shoulder, taken from a safe place.
• Detail photo: the defect itself, close enough to show its edge, water, debris, or depth cue.
• Locator photo: a sign, signal, utility pole, intersection, bridge marker, or storefront that helps crews find it.

If using an object for scale, choose something ordinary and non-identifying, such as a ruler, notebook, or shoe, and place it only if it is safe to do so. Do not enter a live lane to stage a better image. Do not alter the defect. Do not reuse old photos unless the report clearly says they are old.

Research on pothole management systems from the Mineta Transportation Institute describes why structured photo reports are useful: a submitted pothole photo can be stored with GPS location and timestamp, routed by location to the responsible agency, and tracked through repair. That does not mean every community needs a technical app. It does mean that a clear photo, location, and date make a report more actionable.

A fair language standard

The strongest public report is often the least dramatic one.

Use:

• “Observed on September 1, 2026.”
• “Approximate size: about one wheel wide.”
• “Location: eastbound lane, just after the bus stop.”
• “Risk note: cyclists are moving into traffic to avoid it.”
• “Reported to 311; request number saved.”

Avoid:

• “The city does not care.”
• “This contractor destroyed the road.”
• “Someone will die here.”
• “This has been ignored for years,” unless you have dated reports showing that history.

Plain language is not weakness. It makes the evidence harder to dismiss.

Protecting the person who reports

A resident should not have to become a public target to report a public hazard.

Where official systems allow anonymous or low-identification reporting, use only the contact details required for follow-up. If a community group publishes a shared map, consider separating private intake from public display: keep reporter names, phone numbers, vehicle plates, and raw uploads private; publish only the road condition, approximate location, date observed, status, and official tracking number.

Know the boundary between lawful public photography and avoidable conflict. The ACLU’s public photography guidance says that, in public spaces where a person is lawfully present, photographing things in plain view is generally protected in the United States, including transportation facilities and public officials carrying out their duties. It also says people should obey lawful orders to stand back. For road evidence, the practical rule is simpler: document from a safe, lawful place, and leave if the situation becomes unsafe.

The least-harm path

Community reporting works best when it is disciplined:

• Report urgent danger through emergency channels.
• Report maintenance problems through the responsible road authority.
• Keep evidence dated, located, and factual.
• Share publicly only what helps repair or accountability.
• Remove or blur identifying details that do not serve the repair.
• Treat crews, neighbors, drivers, cyclists, and pedestrians as people in the same safety system.

The aim is not to embarrass someone into action. The aim is to make a neglected condition visible enough, specific enough, and persistent enough that repair becomes easier than neglect.

What I am uncertain about

Reporting rules vary by jurisdiction. Some cities publish 311 data; others keep more of the intake private. Some official forms require contact details or photos; others do not. This guide gives a general community standard, not legal advice and not a substitute for the local road authority’s reporting form.

There is also a tension between transparency and privacy. A public map can help a community see patterns, but raw evidence can expose people who never chose to become part of a public complaint. When in doubt, publish less personal information and keep the full record for the official channel.