How to Report a Pothole to Your City (and Get It Fixed)

When you report a pothole, your message lands in a queue managed by a roads, highways, or public works department. Before anyone fills anything, someone has to confirm exactly where the defect is, decide whether it's on a road the city is responsible for, judge how urgent it is, and assign it to a crew with the right materials. Every one of those steps depends on the quality of the information you gave them. A report that says "corner of 5th and Main" still leaves a question — which corner, which lane, which side of the junction?

Vague reports don't get ignored out of laziness; they get parked because they can't be actioned. An inspector may have to drive out just to locate the defect before any repair is scheduled, which adds days. If the description is ambiguous, the report can bounce between departments — a pothole on a state highway running through town isn't the city's to fix, and a report on the wrong authority's desk goes nowhere until someone reroutes it.

The fix is to give the people on the other end everything they need in one pass. A report they can act on without a single follow-up question is a report that moves to the front of the queue. The rest of this guide is about exactly what that looks like.

Start with a precise location. A street name alone is rarely enough — a road can run for miles. The most useful pinpoint is the nearest property number, the closest intersection plus a direction ("on Elm Street, about 30 metres north of the junction with Park Road"), or, best of all, exact coordinates. Add which lane or which side of the road the pothole sits in, because a defect in the centre of a busy carriageway is a different repair job from one at the kerb.

Next, describe the defect itself. Rough size matters — a hole the width of a dinner plate is routine, while one that spans half a lane and is deep enough to damage a wheel is a safety priority. Note the depth if you can, whether it's in a vehicle lane, a cycle lane, or a pedestrian crossing, and whether water is pooling in it, which accelerates the damage and hides the depth from drivers. If it has already caused a flat tyre, a bent rim, or a near miss, say so plainly; cities triage by risk, and a defect linked to actual harm jumps the line.

Finally, give context that helps routing and scheduling. Is the road a main arterial route or a quiet residential street? Is it near a school, a hospital, or a bus stop? Has the same spot been reported before? None of this is busywork — each detail helps the department decide how fast to respond and which crew to send. The more you answer up front, the fewer reasons there are to delay.

A photo does in one second what a paragraph of description struggles to do: it shows the actual size, shape, and severity of the pothole, and it removes any argument about whether the defect is genuinely a hazard. An assessor can look at the image and triage it without leaving their desk. A wide shot that includes a recognisable landmark — a house number, a road sign, a shopfront — lets them place it on a map, and a closer shot conveys the depth and the broken edges that decide how serious it is.

Pairing that photo with a map pin is what really compresses the timeline. A pin carries exact coordinates, so there's no guessing from a street description and no inspector dispatched just to find the hole. When a crew is sent out, they can navigate straight to the spot and arrive with the right materials, because they already know what they're dealing with. That's the difference between a defect that's located, assessed, and scheduled from a single report, and one that needs a site visit before any work can even be planned.

Timestamped, geotagged photos add one more layer that matters more than people expect. The timestamp records when the defect was in that condition, and the location data confirms where the photo was taken. For the reporter, that's evidence the hazard existed and was flagged on a given date. For the city, it's part of the record that shows when an issue was raised and how quickly it was handled — which matters if the pothole later causes damage and the response time is questioned.

Most cities and councils offer more than one channel. Many run a dedicated online form or a 311-style public reporting service — by phone, web, or app — designed specifically for issues like potholes, broken streetlights, and fly-tipping. These tend to be the fastest route because they drop your report straight into the system that schedules the work, often with a reference number you can track. Map-based reporting tools, where you drop a pin on the exact spot, are ideal for road defects because location is the hardest thing to convey in words.

The catch is responsibility. Not every road belongs to your city. Highways, motorways, and major trunk routes are often managed by a regional or national roads authority, while private roads and car parks aren't a public matter at all. If you report a pothole on the wrong authority's road, it won't get fixed — it'll sit until someone redirects it, if they do at all. When you're not sure, a quick look at the city's roads or highways page usually clarifies which roads they maintain, and a good public reporting tool will route the report to the correct department automatically based on where the pin lands.

Whichever channel you use, keep a copy of what you sent and any reference number you get back. That reference is how you follow up, and it's your proof that the issue was reported on a specific date — which is exactly the kind of record that matters if the defect causes damage before it's repaired.

A reference number turns a report from a message into the void into something you can chase. Most reporting systems will tell you the status — received, assessed, scheduled, or closed — and some send updates automatically. If you don't hear anything within the timeframe the city publishes for road defects (many commit to inspecting reported hazards within a set number of working days), follow up with the reference and a calm, factual note: when you reported it, where it is, and that it's still there.

If the same pothole keeps getting patched and reopening, or a temporary fill has worn away, report it again rather than assuming the city already knows. Repeat reports on the same spot are useful data — they tell the department the repair isn't holding and the location may need a proper resurface rather than another quick patch. Reference the earlier report if you have it, so the history is connected rather than starting from scratch.

The reporters who get results aren't the loudest; they're the most organised. A clear original report, a saved reference, and one well-timed follow-up will move a pothole faster than a dozen frustrated calls with no detail behind them. Persistence works best when it's backed by a record.

SnagGrid is built for exactly this kind of report, whether you're a resident flagging a hazard or a public works team fielding hundreds of them. You snap a photo and drop a map pin — the address auto-fills, so the location is precise without anyone typing a street description. You add a few rough notes about the size and severity, and AI drafts a clear, factual report from what you wrote. It never invents facts, and you approve every word before it sends, so the report describes the actual defect and nothing more.

From there SnagGrid emails the right recipient, with per-category routing that can send pothole reports to the roads team and other issues elsewhere automatically. Every item is logged to an audit trail with timestamped, geotagged photos, so there's a defensible record of when a hazard was raised and how it was handled. One-tap follow-up reminders stop reports from stalling, and a public no-login report form — with its own QR code you can put on a sign or a noticeboard — lets anyone report a pothole without an account. For teams, a dashboard with roles, case tracking, CSV export, and a scoped REST API with webhooks keep everything in one place.

Pricing is $29 per month per organization for one seat, plus $15 per month for each extra seat — so a pothole report stops being a vague message that gets parked and becomes a precise, photo-backed item the right department can action straight away.