The Promises Register: Keeping Consultation Feedback Live Through 2026 Delivery
Photo by Photo by Josh Mills on Unsplash on Unsplash
Transport consultations are designed to end. A statutory notice period closes, responses are analysed, a decision is taken, and a report is published. For many local transport authorities and operators, that is the point at which the consultation is considered complete. In practice, however, the most useful work often begins afterwards. The period between a decision and the first bus, the first works compound or the first revised timetable is where public trust is either reinforced or quietly eroded.
The risk is familiar. Residents remember a specific concern raised at a public meeting: a stop that seemed unsafe, a connection that appeared unworkable, a loading arrangement that would affect a high street. The decision report records that concerns were considered. The delivery team inherits a scheme but not always the reasoning behind it. A year later, the same concern resurfaces as a complaint or a local campaign, and the authority has to reconstruct why a particular choice was made. That is not a failure of consultation. It is a failure to carry consultation evidence into delivery.
Why the feedback trail loses its way
Most consultation exercises generate more material than can reasonably be read by a delivery team. Responses arrive as emails, online forms, letters, workshop notes and petition signatures. Analysts group them into themes. The final report summarises the themes and explains the decision. This is a necessary compression, but it often strips out the practical detail that matters later: which ward raised which issue, which operator offered a workable alternative, which accessibility group asked for a specific change to a crossing point.
There is also an institutional gap. Consultation teams and delivery teams are often different people with different deadlines. The former are judged on the quality of the exercise and the report. The latter are judged on programme, cost and specification. Unless someone deliberately transfers the feedback findings into delivery documents, the scheme proceeds with the decision but without the conversation that shaped it. A promises register closes that gap without creating a new bureaucracy.
A register with three columns
The most effective tool is also the least glamorous: a spreadsheet, maintained in the open, with three columns. The first records the concern or proposal as it was raised. The second records the authority's response: accepted, adapted, or not taken forward. The third records the delivery consequence: what will change in the scheme, who owns that change, and at which milestone it will be checked. A fourth column can record the evidence source, such as a consultation reference number or a workshop theme.
The register should distinguish between a concern that has been noted and a concern that has changed the scheme. Not every response can alter a design, and it is dishonest to imply otherwise. What matters is that the distinction is visible. If a requested bus stop is not provided because the carriageway width is insufficient, the register should say so, cite the relevant assessment, and record the date on which that judgement was made. If a requested connection is added to a timetable, the register should identify the operator and the service change that will deliver it. This is not about creating a permanent record of grievances. It is about creating a practical link between what people asked for and what delivery teams are actually building.
Publishing the reasoning, not just the outcome
Many authorities already publish a consultation report and a decision notice. Fewer publish a feedback trail that shows how specific themes influenced specific parts of a scheme. In 2026, with public scrutiny of transport spending as sharp as it has been for years, that trail is a credibility asset. It allows councillors, scrutiny committees and community groups to follow the argument from response to decision to delivery.
Publishing the register need not mean publishing every respondent's personal details. It means publishing the categories of concern, the response, and the delivery consequence in plain English. Authorities should link it from the scheme page, keep it updated at agreed milestones, and provide it in accessible formats. Where a concern has been rejected, the reason should be stated without defensiveness. A short explanation is more useful than a long justification. The aim is not to win every argument but to show that the argument was heard and that the scheme changed where it could.
Putting the register into delivery governance
A register only matters if it is used. The practical step is to make it a standing item at scheme stage gates: preliminary design, procurement, construction readiness and service start. At each gate, the project lead should confirm that every open commitment has either been delivered, is on track, or has been formally changed with a recorded reason. This should sit alongside the risk register rather than replace it. The risk register asks what might go wrong. The promises register asks what was said would happen.
Operators can use the same discipline for service change consultations, particularly where bus partnerships or enhanced partnerships are in place. A partnership that asks passengers for views on a revised network should be able to show, at the next review, which responses led to which timetable adjustments. Smaller operators may not have a consultation team, but they can keep a simple log of commitments made at public meetings and member forums. The discipline is proportionate to the scale of the change.
Revisiting at milestones, not just at the end
The most common failure is to revisit consultation promises only when a scheme is complete. By then, changes are expensive and explanations sound like excuses. Revisiting at milestones gives authorities room to adjust. If a promised shelter cannot be delivered within budget, the register should record the constraint early and set out the alternative, whether that is a different location, a phased installation or a contribution to a future scheme. Early disclosure is not an admission of failure. It is evidence that delivery is being managed honestly.
This routine also protects institutional memory when staff move on. Transport teams change, particularly in smaller authorities. A register that records the reasoning behind a decision is a handover document as much as an accountability tool. It tells a new project manager why a particular junction was chosen, why a stop was relocated, and which community group is expecting a follow-up call. That is valuable in any year, but it is especially valuable in 2026, when many authorities are managing multiple funding streams and stretched delivery capacity.
A regional habit, not a one-off
Consultation is often treated as a hurdle before delivery. A promises register treats it as part of delivery. It costs little to maintain, it improves scrutiny, and it gives regional authorities a defensible answer when residents ask what happened to their feedback. The best time to start is before the next consultation closes, not after the next complaint arrives.
