A Practical Framework for Reporting Road Conditions

FixMyRoad · 2026-09-01

The purpose of the framework

Poor road conditions become easier to ignore when every complaint sounds different. One person reports “a bad pothole.” Another reports “flooding near the school.” A third says “the shoulder is crumbling again.” Each may be right, but the authority receiving the reports has to translate scattered descriptions into maintenance priorities.

This framework is meant to make that translation easier. It gives residents, community groups, and civic platforms a practical way to classify six common road-condition problems: potholes, flooding, erosion, broken or missing signage, unsafe shoulders, and repeated failure points.

It is not an engineering inspection standard. It does not assign legal fault. It is a reporting language — a way to describe what can be seen, document why it matters, and help public agencies route the right repair at the right level of urgency.

The backbone is simple:

1. Name the condition.
2. Record its location and evidence.
3. Score severity by observable risk.
4. Score priority by exposure and recurrence.
5. Escalate only when the condition creates immediate danger.

This follows the spirit of established transportation practice. FHWA’s pavement distress manual says a shared distress language helps agencies collect condition data consistently and avoid having each agency invent its own definitions and measurement methods. FHWA’s Local Road Safety Plan guidance similarly frames local safety work as a process of identifying, analyzing, and prioritizing issues, risks, actions, and improvements.

The reporting unit

Each report should describe one “condition instance.” A condition instance is a visible defect or hazard at a specific place during a specific time window.

Minimum fields:

• Condition type: pothole, flooding, erosion, signage, shoulder, repeated failure point, or other.
• Exact location: street name, cross street, direction of travel, nearest landmark, and GPS if available.
• Date and time observed.
• Evidence: at least one clear photo or video, taken safely and without standing in traffic.
• Size or extent: depth, length, width, lane coverage, or affected distance where a safe estimate is possible.
• Exposure: traffic speed, lane count, nearby school, bus stop, bike route, pedestrian crossing, driveway, bridge, curve, or intersection.
• Immediate danger: whether vehicles, cyclists, or pedestrians must swerve, stop suddenly, enter opposing traffic, or pass through water.
• History: whether this location has failed before, been patched before, flooded before, or already been reported.

A report does not need perfect measurement to be useful. But it should distinguish “annoying,” “damaging,” and “dangerous.”

Severity scale

Use four severity levels.

Severity 1 — Minor: visible defect, low immediate risk.

The condition is present but does not force evasive movement. It may worsen if left untreated. Report it for routine maintenance or monitoring.

Severity 2 — Moderate: likely damage or discomfort, manageable at normal caution.

The condition can damage tires, wheels, alignments, drainage, signs, or road edges, especially for smaller vehicles, cyclists, or at night. It deserves planned maintenance, not just monitoring.

Severity 3 — Serious: active safety risk.

The condition can cause loss of control, sudden braking, swerving, lane departure, pedestrian exposure, or blocked sight guidance. It deserves prompt inspection and interim risk reduction.

Severity 4 — Critical: immediate hazard.

The condition creates a realistic risk of serious injury, vehicle disablement in traffic, road washout, hidden depth water, missing stop control, blocked emergency access, or a hazard that drivers cannot reasonably see in time. It should be routed to the road authority’s emergency or after-hours channel, not only to an ordinary complaint queue.

Priority scale

Severity asks, “How bad is the condition?” Priority asks, “How quickly should it move?”

Priority A — Emergency: act now.

Use for critical hazards: missing or knocked-down stop signs, water covering the travel lane with unknown depth, road collapse, washout, sinkhole, live debris field, blocked lane on a high-speed road, or a shoulder/drop-off hazard forcing vehicles into unsafe recovery.

Priority B — Prompt: inspect and reduce risk soon.

Use for serious hazards with meaningful exposure: a deep pothole in a wheel path, recurring standing water at an intersection, edge drop-off on a curve, missing curve warning sign, eroded shoulder near a school route, or repeat patch failure after rain.

Priority C — Planned maintenance: schedule repair.

Use for moderate hazards that are not yet forcing dangerous maneuvers: shallow-to-medium potholes outside the main wheel path, damaged but legible signs, minor shoulder rutting, clogged drainage with no standing water during observation, or erosion starting at the road edge.

Priority D — Monitor: record and revisit.

Use for minor defects and early warning signs: hairline cracks, small depressions, fading sign visibility that is not yet unreadable, light shoulder wear, or drainage stains without current ponding.

Priority can rise even when severity is unchanged. A moderate pothole near a school crossing may be more urgent than the same pothole on a low-speed dead-end road. A shallow flood that appears after every rain may be more important than a deeper puddle that formed once after an exceptional storm.

Condition class 1: potholes

A pothole report should record the number of potholes, approximate size, depth if safely estimated, lane position, and whether drivers are swerving or braking.

FHWA’s Distress Identification Manual defines asphalt potholes as bowl-shaped holes in the pavement surface, with a minimum plan dimension of 150 mm. It classifies pothole severity by depth: low at about 25 mm, moderate at 25 to 50 mm, and high at more than 50 mm. That is a useful measurement anchor, but a public report should also include road context.

Reporting severity:

• Minor: small shallow hole, outside wheel path, visible in daylight, no observed evasive movement.
• Moderate: shallow-to-medium hole in the wheel path; likely tire, wheel, bicycle, or motorcycle risk; drivers slow or adjust line.
• Serious: deep, sharp-edged, clustered, hidden by shade or water, or located where swerving creates conflict.
• Critical: deep enough to disable vehicles or throw a cyclist; located in fast traffic, on a bridge, curve, intersection, or night-unlit section; or already causing crashes or near misses.

Evidence to capture: photo from shoulder or sidewalk; object for scale only if safe; direction of travel; close-up and wider context; whether water conceals the hole.

Condition class 2: flooding and standing water

Flooding reports should distinguish nuisance ponding from a roadway safety hazard. The important questions are depth, coverage, speed environment, recurrence, and whether the water hides pavement damage.

Reporting severity:

• Minor: small curbside ponding; travel lane remains passable; drains slowly but does not redirect traffic.
• Moderate: water intrudes into a lane, bike lane, shoulder, crossing, or bus stop; splashing reaches pedestrians; likely hydroplaning risk at speed.
• Serious: water covers a substantial part of a travel lane, forces vehicles across lane lines, blocks a pedestrian route, hides potholes, or occurs at an intersection, underpass, curve, or school approach.
• Critical: moving water, unknown depth, water across the full roadway, stalled vehicles, undermined pavement, blocked emergency access, or any condition where a driver may enter floodwater without a clear escape.

Evidence to capture: water extent from a safe distance; nearby drain or culvert if visible; rainfall timing; whether the same place floods after ordinary rain; and whether sediment, debris, or pavement breakup remains after water drains.

Flooding should be tagged as a drainage issue, not only as a “wet road” complaint. FHWA’s hydraulics program exists because culverts, waterways, headwater conditions, and roadway data all matter to road safety and resilience. A resident cannot solve that design question, but a good report can point inspectors toward the drainage system rather than only the pavement surface.

Condition class 3: erosion and washout

Erosion is the loss of soil, gravel, shoulder material, ditch stability, or road-edge support. It may look less dramatic than a pothole, but it can weaken the road from the side or beneath.

Reporting severity:

• Minor: small rills, exposed soil, or early edge wear with no travel-lane effect.
• Moderate: shoulder material loss, ditch scouring, exposed aggregate, clogged outlet, sediment fan, or water cutting a channel beside the road.
• Serious: road edge unsupported, pavement cracking near the edge, culvert inlet/outlet erosion, shoulder drop, or erosion near a curve, bridge, steep grade, or pedestrian path.
• Critical: active washout, undermined pavement, sinkhole, collapsed shoulder, water cutting through the road base, or any visible void beneath pavement.

Evidence to capture: before-and-after if available; photos along the direction water flows; nearby culvert, ditch, drain, or outfall; recent rain; and whether prior repairs failed at the same location.

Condition class 4: broken, missing, obscured, or unreadable signage

Signage reports should classify both the physical condition of the sign and the safety role it serves. A faded street-name sign and a missing stop sign are not the same kind of risk.

The MUTCD is the national standard used by road managers for signs, signals, markings, and other traffic control devices on roads open to public travel. Its current edition page says the manual defines standards to install and maintain traffic control devices nationwide. The 2023 Chapter 2A material also states that signs and other traffic control devices should be installed and maintained from a systematic standpoint rather than only one by one, and includes maintained retroreflectivity levels.

Reporting severity:

• Minor: sign dirty, slightly bent, partly faded, or beginning to lose nighttime visibility, but still legible and correctly positioned.
• Moderate: sign hard to read at normal approach speed; vegetation partially blocks it; reflective surface degraded; sign is bent or rotated but still understandable.
• Serious: warning, speed, school, pedestrian, curve, railroad, lane-use, or detour sign is missing, hidden, unreadable, facing wrong direction, or placed where drivers cannot react in time.
• Critical: stop, yield, do-not-enter, one-way, railroad crossing, lane closure, bridge/weight restriction, or flood closure sign is missing, knocked down, reversed, or misleading.

Evidence to capture: daytime and, if safe, nighttime visibility; approach direction; the sign’s face and its context; vegetation blockage; post damage; and whether a temporary sign is present.

Condition class 5: unsafe shoulders and pavement edge drop-offs

Shoulder reports should record the usable shoulder width, drop-off height if safely estimated, slope, loose material, edge cracking, and whether recovery from the shoulder back to the lane appears difficult.

FHWA’s Safety Edge material notes that pavement edge drop-off has been linked to serious crashes, including fatal collisions, and that roadway departures account for over half of fatal crashes. It describes edge drop-offs as height differences between the paved road and adjacent graded material, and explains that exposed vertical edges can make it difficult for a driver to return safely to the paved lane.

Reporting severity:

• Minor: narrow or rough shoulder with no clear drop and no forced movement.
• Moderate: loose gravel, rutting, edge cracking, vegetation, or small drop-off that reduces recovery room.
• Serious: drop-off, soft shoulder, erosion, or obstruction that could cause loss of control, especially on curves, hills, bridges, high-speed roads, or roads used by cyclists and pedestrians.
• Critical: abrupt edge drop-off, collapsed shoulder, no recovery space beside a high-speed lane, shoulder failure near a bridge/culvert, or condition forcing disabled vehicles or pedestrians into the travel lane.

Evidence to capture: wide shot showing lane and shoulder; close-up of edge; approximate drop; curve/hill/intersection context; and whether there is any safe pedestrian or cyclist refuge.

Condition class 6: repeated failure points

A repeated failure point is a location where the same or related problem returns after repair, rainfall, freeze-thaw cycles, heavy traffic, or seasonal use. This category matters because repeat failure often points to a root cause: drainage, base failure, utility cuts, heavy vehicles, poor materials, shade/ice, slope, or design.

Reporting severity uses the underlying hazard, but priority rises with recurrence.

• Minor repeat: same small defect returns slowly, with no safety exposure.
• Moderate repeat: repeated patching, ponding, sign damage, shoulder rutting, or erosion within months.
• Serious repeat: the same location repeatedly causes swerving, flooding, vehicle damage, near misses, or emergency complaints.
• Critical repeat: prior temporary repairs fail quickly and expose people to immediate risk, such as washout, missing control signs, or deep concealed potholes.

Evidence to capture: old report numbers, dates of prior repairs, photos from previous incidents, rainfall or freeze timing, and nearby features such as drains, utility covers, bus stops, driveways, loading zones, steep grades, or tree roots.

Repeated failure points should not be treated as “another pothole.” They should be tagged for diagnosis. A patch may be necessary, but the report should ask the agency to inspect the cause.

Cross-cutting modifiers

After assigning a condition and severity level, apply priority modifiers. These do not change what the condition is. They change how quickly it should be reviewed.

Raise priority when the condition is:

• In a wheel path, bike lane, crosswalk, bus stop, school zone, bridge, underpass, curve, hill, intersection, railroad crossing, or emergency route.
• Hard to see at night, in rain, in glare, under shade, or at normal approach speed.
• Forcing drivers to swerve, brake suddenly, enter opposing lanes, or leave too little room for pedestrians and cyclists.
• Near people with less protection: children, older adults, wheelchair users, cyclists, motorcyclists, transit riders, roadside workers.
• Recurrent after previous repair.
• Worsening quickly.
• Associated with water, loose debris, edge support failure, or missing traffic control.

Lower priority only with care. A low-volume road still deserves safe passage. The question is not whether many people are affected; it is whether the risk is immediate, predictable, and preventable.

A practical scoring method

For platforms or community groups that need a simple numeric sort, use a 0–12 score.

Base severity:

• Minor: 1
• Moderate: 2
• Serious: 3
• Critical: 4

Add exposure points:

• High-speed road, bridge, curve, hill, intersection, school area, transit stop, bike/pedestrian route, or emergency route: +1 each, maximum +3.
• Evidence of evasive movement, near misses, stalled vehicles, blocked access, or prior crash: +2.
• Repeated failure at same location: +2.
• Hidden hazard: water-covered pothole, nighttime visibility problem, blind curve, obscured sign, or concealed edge drop: +1.

Priority bands:

• 9–12: Priority A — emergency or same-day routing.
• 6–8: Priority B — prompt inspection and interim control.
• 3–5: Priority C — planned maintenance.
• 1–2: Priority D — monitor.

The score should never override judgment. A missing stop sign is Priority A even if the numeric score looks lower because few modifiers were recorded. A resident report is a triage aid, not a substitute for a road authority’s duty to inspect.

How to write the complaint or service request

A clear report can be short:

“On September 1, 2026 at about 8:10 a.m., I observed a deep pothole in the northbound wheel path on Maple Avenue, about 30 meters before Oak Street. It appears more than 50 mm deep and roughly 0.4 m wide. Drivers were crossing the center line to avoid it during school drop-off. This seems like a Serious pothole with Prompt priority because of depth, wheel-path location, school-hour exposure, and evasive movement. Photos attached.”

For flooding:

“After ordinary rain, water covers most of the westbound lane under the Pine Street rail bridge. This has happened at least three times in the past two months. Today the water hid the pavement edge and cars entered the opposing lane to pass. Please inspect the drainage system and consider temporary warning or closure control if depth is unsafe.”

For signage:

“The stop sign on the southeast corner of 4th and Cedar is rotated away from approaching eastbound drivers. It is not readable until the intersection. This appears Critical because it affects stop control. Photo attached.”

What the evidence does not support

A public report should avoid three overclaims.

First, it should not say a road is illegal, negligent, or noncompliant unless a qualified authority has made that finding. Residents can document conditions and risk; liability is a separate question.

Second, it should not treat every visible defect as an emergency. Over-escalation weakens the signal and can delay the truly dangerous cases.

Third, it should not treat a recent patch as proof the agency acted well or badly. A repeated patch failure may reveal a deeper problem, but the public record should describe the recurrence before assigning motive.

The least-harm path

The least-harm path is steady documentation with clear routing.

For residents: report what is visible, attach safe evidence, identify exposure, and keep the tone factual.

For community groups: aggregate repeat locations, separate emergency hazards from routine defects, and publish maps that help agencies see patterns rather than only criticism.

For agencies: accept public reports as early-warning data, publish status where possible, and distinguish temporary make-safe work from permanent correction.

For platforms like FixMyRoad: make reporting simple, but make classification disciplined. The goal is not to shame every crew or flood every inbox. The goal is to make preventable road risk visible enough that repair, drainage, signage, and design decisions can be prioritized with less delay and less guesswork.

What I am uncertain about

This framework is designed for broad public use. Local laws, agency response categories, climate, pavement type, rural geometry, and maintenance budgets vary. A city may define emergency potholes differently from a county or state department of transportation.

The severity thresholds for pothole depth are anchored in FHWA’s pavement distress manual, but the flooding, erosion, signage, shoulder, and recurrence categories are practical reporting translations, not legal standards.

The largest uncertainty is operational: whether an agency receiving reports will preserve the distinction between severity, exposure, and recurrence. If those fields are kept separate, the reports can support better triage. If they are collapsed into a single complaint label, much of the value is lost.