Stop Attending, Start Escalating: A Ten-Day Rule for Town-Centre Problems

There's a particular sound a room full of business owners makes when a council officer says "we'll take that away and come back to you". It's a sort of collective exhale. Relief, mixed with the knowledge that everyone will be back in the same church hall in eight weeks, discussing the same three potholes.

I've sat in a lot of these meetings. Parish-hall forums, BID briefings, chamber lunches, the town-centre partnership that meets quarterly and has never once published minutes anyone can find. The people are decent. The problems are real. The format is the problem.

The passive update problem

Most local forums are built around information flow in one direction. An officer reads an update. A highways contractor shows a slide of a phased programme. Someone raises parking charges. Someone else raises the empty unit next to the bank. The chair says it's noted, and it is — in a notebook, in a folder, in a filing cabinet nobody opens.

Two structural flaws sit underneath this.

First, there's no clock. Nothing in the agenda establishes when an answer is due, so nothing is ever late. A question without a due date is a question that has been politely declined.

Second, there's no single artefact. Every issue gets re-explained from scratch each meeting, by a different person, with slightly different facts. The council officer isn't being obstructive when they say they'll look into it — they genuinely can't tell which version of the parking complaint is the one that matters, because there are six and none of them have a photograph attached.

Fix those two things and a forum stops being a complaint circle.

The ten-day rule

Here's the rule, and it's deliberately blunt:

Any issue raised at a meeting is either answered, or formally escalated to a named person with a dated request, within ten working days. If it isn't, it goes on the open register at the next meeting and the chair writes to the relevant cabinet member.

Ten working days is roughly two clear weeks. Long enough for a highways officer to check a schedule. Short enough that the issue doesn't evaporate. Crucially, it's a deadline the forum sets for itself, not one it pleads for from anyone else. That distinction matters — it means you're never waiting on someone else's diary to look organised.

In practice, a forum that adopts this needs three roles, and they can all be volunteers:

• An issue lead — the person who raised it, who owns the written record. Not the chair.
• A tracker — someone who keeps the list and, once a month, chases anything past its date. One hour a month.
• A chair who writes the letter. The escalation step has to be someone with a title on the letterhead, or it gets ignored.

The escalation ladder itself is usually shorter than people think: highways or parking team first, then the relevant ward councillor, then the cabinet member for regeneration or highways, then a formal freedom of information request if the question is really about data, and only then the local paper. Most things get sorted at step two. The trick is knowing which step you're on and when you moved.

The one-page issue sheet

One A4 page per issue. Not a spreadsheet row — a page, because it has to be readable by a councillor in ninety seconds.

What goes on it:

1. Location. Street name, and a photograph or a marked-up map crop. Photographs decide more arguments than paragraphs do.
2. The issue in one sentence. "Loading bay suspended since 14 September with no notice to traders."
3. Who it affects and how many. Six businesses, roughly forty staff, two delivery slots a day. Numbers turn an anecdote into a case.
4. What's been tried. Phone calls, emails, reference numbers, dates. This is the bit that stops you being fobbed off, because it shows you've already done the polite route.
5. The specific ask. Not "please review parking" but "reinstate the two loading bays by 30 November or confirm in writing why not".
6. The date the answer is due. Ten working days from the meeting.

Six fields. Half a page if you're disciplined. Circulate it to the whole forum before it goes anywhere, so nobody's surprised and nobody contradicts it later.

The template does something subtle to the room. Once issues are written down in a consistent shape, the meeting stops relitigating them and starts working through a list. Arguments about whose fault it is give way to arguments about dates, which are far more productive.

Where it gets awkward

Two warnings, from watching this go wrong.

Don't let the tracker become a grievance log. If the register grows past about fifteen open items, the forum is raising problems faster than it's closing them, and the meetings become a reading of the list. Cap it. Each meeting, three new issues maximum, and the oldest three get escalated whether they're ready or not.

And keep it public. Publish the register — on the forum's own site, a PDF, a page on the town council's noticeboard, wherever. Officers behave differently when the deadline is visible, and members behave differently when their issue sheet might be read by a rival trader.

The bit nobody says out loud

A town centre doesn't decline because the council is incompetent or because the BID is useless. It declines because problems sit unowned for long enough that everyone stops believing anything will change, and once that belief goes, the good operators leave.

Forums are the cheapest tool we have for stopping that slide. They just need a clock and a piece of paper. Not another strategy document — a deadline and a form.

If you're on a forum committee, put the ten-day rule on the next agenda as an item to adopt, and bring the template with you. If it gets voted down, you've learned something useful about the forum, and you can get on with your own business knowing exactly where the limit sits.