The moment everything stops
You pull into Isaac Newton Centre car park on a Tuesday morning — a quick errand, twenty minutes, maybe half an hour. You find a space, look around for a machine, and spot a sign. It says RingGo. There is no coin slot. There is no card reader built into a meter. There is a QR code, a phone number, and an instruction to download an app.
For some people, this takes thirty seconds. For others, it stops the journey entirely.
Before a single minute of parking is bought, the process asks for an account, a phone number, a vehicle registration, and payment details — a sequence of steps that assumes you have arrived not just with a car but with a smartphone, a data signal, sufficient battery, and enough familiarity with app stores to move through registration without hesitation. The transaction you expected to take ten seconds now has a form to fill in.
That gap — between what a service assumes about you and what you actually are — is where trust in public institutions quietly begins to erode. The car park is just the place it becomes visible.
What SKDC changed in 2025, and what paying now involves
South Kesteven District Council revised car parking charges across Grantham's town-centre sites — including Westgate, St Peter's Hill, Wharf Road, Isaac Newton Centre, and Guildhall Street — as part of its 2025/26 budget. The tariff changes were approved through the council's standard budget-setting process.
Alongside the revised charges came a near-total shift in how payment works. Cash is effectively gone. The council's guidance routes users primarily through RingGo, a cashless parking platform, with phone payment retained as a secondary option. On-site signage for alternatives to the app is limited.
For a first-time RingGo user, the payment sequence runs roughly as follows: scan the QR code or find the app in an app store; create an account with a phone number and password; enter a vehicle registration; add a payment card; then, finally, start a parking session. A returning user with a saved account moves faster — but that efficiency exists only on the far side of registration.
The council's interest in reducing cash-handling costs is legitimate: coin collection, machine maintenance, and cash security are real operational expenses that app-based systems can reduce. The question the 2025 change raises is not whether cashless parking makes sense as a direction, but whether the transition was designed with the full range of Grantham's actual car park users in mind.
Who actually parks in Grantham
Market-town car parks do not serve a digital-native crowd. The mid-morning footfall at Westgate or St Peter's Hill on a weekday includes retired residents, carers bringing relatives into town for appointments, people travelling in from surrounding villages, and shoppers who are not necessarily carrying a smartphone with a data signal and a ready-configured app-store account.
The national figures put a rough scale on that observation. Ofcom's 2024 Connected Nations data shows that around 6% of UK adults own no smartphone at all — a figure that rises to approximately 20% among those aged 75 and over. Lloyds Bank's 2024 Consumer Digital Index found that 5 million UK adults lack essential digital skills entirely, and a further 7.5 million have very limited skills; older people, disabled people, and those on lower incomes are disproportionately represented across both groups. Lincolnshire sits below national averages on both internet use and digital skills, which means those proportions are likely higher in the Grantham catchment than headline figures suggest.
What the RingGo flow requires — smartphone ownership, a live data connection at the machine, confidence navigating app stores, and a payment card to save — is a combination that cannot simply be assumed across that population. Individually, each assumption is plausible for many users. Applied together, they describe a narrower profile than the one that actually pulls into a Grantham car park on a Tuesday morning.
The mismatch is structural. It does not require exceptional circumstances to produce failure; it only requires a user who does not match the design's assumptions — and in Grantham, on any given morning, that is a predictable and significant share of the people paying to park.
Good services are verbs — what design principles say about this
'Start with user needs' is the first Government Digital Service design principle, and its instruction is blunt: 'Don't make assumptions. Have empathy for users.' A payment system built around RingGo as the primary option, with limited on-site alternatives, proceeds from an assumption — that the person arriving in Isaac Newton Centre car park owns a smartphone, has a data signal, and is ready to register an account. Whether SKDC researched who actually uses its car parks before making that the primary route is not visible in its published guidance.
The second relevant principle — 'do the hard work to make it simple' — was demonstrated in practice by a GDS team at the Ministry of Justice, going through every word of a form to strip unnecessary complexity. The logic applies directly here. Each extra step in the RingGo flow — app store, account creation, vehicle entry, payment card — is a point at which a user may abandon the transaction. That hard work was not done; it was redirected to the user, at the machine, in real time.
Lou Downe's insight that 'good services are verbs, bad services are nouns' is the most vivid frame. 'Pay for parking' is a verb — legible and purposeful. 'RingGo' is a noun: an unfamiliar proper name that must be decoded before the task can begin. For a 70-year-old standing in Isaac Newton car park, 'download RingGo' is not an instruction — it is a barrier wearing the costume of one.
The Government Service Manual is explicit that a good service must work across every channel — 'phone, post and face to face as well as digital' — not treat digital as the default from which alternatives are grudgingly carved. These are not aspirational ideals. For public sector bodies, they are the published standard against which services should be assessed.
Why friction at the payment moment damages trust
Parking machines occupy a particular moment in a person's relationship with a public authority — low-stakes, transactional, expected to work without introduction. When they don't, and when the obstacle is an unexplained mandatory step the user did not anticipate, the response is calibrated not to the parking task but to the institution that designed it.
Nesta and Reform's research on public digital services finds that unexpected barriers at a payment moment — account creation, app download, personal data entry — significantly increase abandonment rates and damage trust in the delivering institution, disproportionately to the inconvenience itself. The gap between what a user expected (pay, receive a ticket) and what they encountered (register, verify, configure) does not register as a technical hiccup. It registers as evidence about who the service was built for.
The UK-wide complaint record supports this. Councils that removed cash from car parks between 2022 and 2025 saw complaints concentrated not on the principle of change but on confusing sign-up flows, absent signage, and the unexamined assumption of smartphone ownership — patterns consistent enough to be documented in local government reporting and Which? consumer research.
For residents who cannot complete the payment, the consequences are specific: a penalty charge notice, a decision to avoid the town centre, or dependence on another person to pay on their behalf. None is trivial. And each compounds the trust cost — because the problem is not simply that the system failed, but that it evidently was not built with them in mind. That sense of being designed around, rather than designed for, is difficult for a public body to recover from.
What better actually looks like here
Better design here is not complicated to describe. At the machine itself, signage should name every available payment route in plain language — app, phone number, any card terminal — with the alternatives given equal visual weight, not buried in small print. A person who cannot use the app should not have to discover that a phone option exists by chance.
Under the Public Sector Equality Duty, a council implementing a significant change to a public-facing payment method is expected to carry out an equalities impact assessment before that change goes live — to identify, in advance, the populations most likely to be excluded. SKDC has not published such an assessment for its 2025 parking changes. That absence is itself informative: if one was completed, it should be accessible; if it was not completed, the transition proceeded without the legal groundwork that could have surfaced the problem before a single resident encountered it.
The 2018 Public Sector Bodies Accessibility Regulations require any guidance page and linked app to meet WCAG 2.1 AA standards. The RingGo sign-up flow and SKDC's 'how to pay' guidance fall within scope and should be audited against that standard — this is a legal obligation, not a design preference.
Even lightweight user research — observing who uses Isaac Newton Centre car park on a typical Tuesday morning — would have made the mismatch visible before the system went live. The case for reducing cash handling is legitimate; no one is disputing that. But the design burden of that efficiency was transferred to the user rather than absorbed by the service. The saving in coin collection does not offset the trust spent each time a machine becomes a barrier rather than a transaction.