The Crater Register: A Pembury Rider's Two-Minute Habit That Gets Kent Lanes Fixed

There's a particular noise a Kent lane makes when it's about to bite. A hollow clunk, a bottle launching itself out of a cage, and the sudden collective intake of breath from everyone behind you. We've all done the swerve: the last-second twitch around a crater that turns a pleasant Pembury loop into a game of kerb roulette. It keeps you upright today, but it does nothing for the rider who comes through tomorrow.

This is the case for reporting instead of just dodging. Not because cyclists love council forms — nobody does — but because a properly logged pothole is a small favour to every rider behind you. The repair queue is not a mystery. It responds to clear evidence, precise locations and a reference number that someone can chase. That's a habit worth building into the Saturday ride.

First, stop calling it a moan

Reporting road damage isn't a complaint about the state of the world. It's maintenance by another route. Kent County Council is responsible for most of the lanes around Pembury, Tonbridge and Tunbridge Wells, and its highways team works from reports. A vague social media post saying 'the roads are terrible' gives them nothing to inspect. A photo of a sharp-edged hole, pinned to a lane name and a direction of travel, gives them a job.

There's a useful distinction to make before you fire off a report. Most local lanes and residential roads sit with KCC. Trunk roads and some larger strategic routes may be managed by National Highways, so the A21 is a different conversation from the lane behind the pub. If you're not sure, KCC's own reporting tool usually makes it clear when a road isn't theirs. The important thing is to send it to the right inbox rather than letting it bounce around while the hole gets deeper.

What KCC actually needs from you

A good pothole report is short, specific and visual. KCC's online highways reporting service will ask for the location, a description and usually a photo. The more precise you are, the less time an inspector spends playing detective.

What works:

• A proper location. Name the road, the nearest junction, farm gate or house, and the direction you were travelling. 'The left-hand edge heading east towards Matfield' is useful. 'Near Pembury' is not.
• A scale reference. A close-up with a tyre, bottle or pump beside the hole tells the inspector more than a photo of anonymous tarmac. Keep your hands out of the traffic while you do it.
• Two photos. One wide shot showing where the hole sits in the lane, and one close-up showing the edge and depth. If it's full of water, say so — that's often when the damage is worse than it looks.
• Plain description. 'Sharp-edged, roughly 60mm deep, across the left wheel line' is the kind of detail that gets prioritised. Mention if it's on a bend, a descent or a narrow section where riders can't easily avoid it.

You don't need to write an essay. You need to make the defect easy to find and hard to ignore.

The two-minute report

Once you're home and the kettle's on, open KCC's report a pothole page, drop the pin or type the location, add your photos and send it. Save the confirmation email. That reference number is the whole game: it turns a grumble into a case.

A sensible follow-up diary note is about ten working days. If nothing has changed, reply politely with the reference and ask for an inspection update. If the hole is on a busy lane or a known descent, say so again. Keep it factual. 'Reference 123456 — has this been inspected yet? The defect is on the wheel line just after the bend and is being avoided by riders into oncoming traffic' is far more effective than a rant about the council.

If the defect is genuinely dangerous — a missing drain cover, a deep trench, something that could put a rider under a car — ring it through rather than relying on a web form. For ordinary craters, the online route leaves a paper trail, and paper trails get chased.

Riding the damaged stretch meanwhile

Repairs take time. Until the tar gang arrives, the lane still has to be ridden. The trick is to be predictable rather than brave.

Scan further ahead than usual, especially on the shaded stretches where water sits and edges crumble. If you're in a group, call the hazard early — 'hole left' or 'crater middle' — and point it out rather than swerving silently. Leave a bigger gap so you've got room to move without crossing the centre line. When you do have to cross a bad edge, keep the bars straight, unweight the front slightly and don't grab a handful of brake halfway over it. A pothole is usually survivable; a panic brake in a bunch is not.

If a lane is genuinely awful, it's fine to choose a different route for a few weeks. That's not defeat. It's just sensible route planning while the paperwork does its thing.

Build a crater register

This is where the local bit matters. One rider reporting one hole is useful. Ten riders reporting the same stretch, with references, is a pattern. Share the reference number in your club chat or with your regular riding mates. Note when it's been inspected, when it's been filled and when it's already crumbling again. Over a winter, that little log becomes a decent map of which lanes are holding up and which need chasing.

It also changes the tone. Instead of arriving at the café stop with another story about nearly losing a wheel, you arrive with a reference number and a photo. That's a much better contribution to the table.

The payoff is smoother than you think

Every properly logged crater is a nudge towards a better lane for the next rider. It won't fix the roads overnight, and some reports will disappear into the system for longer than anyone would like. But the alternative — swerving, shrugging and hoping — leaves the hole exactly where it was, getting wider with every wet week.

So next time a Kent lane bites, don't just dodge it. Photograph it, pin it, report it, and keep the reference. Two minutes at the kitchen table is a lot cheaper than a new wheel, and it makes the lanes better for everyone who follows.