We spend a lot of time talking about technology. But the honest answer to “what makes a car park run well” has less to do with any single product and more to do with habits we have seen the best-run operations share, whether a city council, a train operator, a university estates team or a leisure site in a forest.
This post collects some of those lessons. Where they draw on client work, we have kept the detail general. We would rather publish something accurate than something impressive.
Lesson one: the back office matters more than the front
One council client came to us with a familiar picture: solid on-street enforcement, but off-street car parks running on ageing machines, spreadsheets and a permit system that did not talk to anything else. The cameras and kiosks were the visible change; the shift that mattered was putting payments, permits and enforcement on one record.
Why does that matter to a driver? Because when a Blue Badge, a resident permit and a pay-by-phone session live in the same place, fewer people get a charge they should not have received. Fewer wrong charges means fewer appeals, less officer time and happier residents.
Lesson two: rail passengers do not want to think about parking
Station car parks are unusual: demand is brutally peaked, most users are regulars, and the customer is already anxious about a train. Our work with a rail operator taught us that the ideal experience is one the passenger barely notices: drive in, park, pay when convenient, drive out, no barrier queue at 08:10.
ANPR freeflow suits this pattern, but only if the pay-later window and season-ticket whitelist are set up properly. Get that wrong and you create the friction you were trying to remove.
Lesson three: seasonality is a design input, not a surprise
A car park serving a forest or leisure destination we work with sees visitor numbers swing enormously between a wet February Tuesday and an August bank holiday. The lesson: tariffs, patrols and even payment channels should flex with the season, and the system must make those changes easy enough that a small team will actually do them. Kit that survives a woodland site through winter is also not the kit you would specify for a multi-storey.
Lesson four: universities are really small towns
A campus has residents, commuters, contractors, visitors, open days and a population that changes every September. Our higher education work, including with the University of Leicester (the case study is on our site), reinforced that permit administration is where most of the pain lives. Digital permits linked to vehicle registrations, with ANPR doing the checking, take the burden off the estates team.
Lesson five: scale needs standards
Working alongside London-wide bodies has shown us what happens when many authorities need consistent data. Shared definitions, clean vehicle records and borough-comparable reporting matter as much as any camera. The same applies nationally as the National Parking Platform brings interoperable payment to more councils: your data has to be clean enough to share.
Lesson six: accessibility complaints are early warnings
Across every sector, the first complaints after a change come from drivers who cannot use the new route to pay or apply. Treat those as signals about your design, not noise. A cash option on selected machines, a phone line and a no-download web payment page cost little and protect the whole scheme’s reputation.
Lesson seven: measure what you changed
The operations that improve year on year look at their data monthly: occupancy by hour, payment mix, appeal rates, permit churn. Blink was built to make that routine, and every lesson above came from a client willing to look at the numbers with us.
If any of this sounds like your estate, our case studies go into more depth, and we would be happy to talk through what has worked across 3,000+ locations. Get in touch.