More than a week after route alternatives were sent, residents still have no answer and no relief.
On Sunday evening, 7 June 2026, a resident again wrote to Checkers after sitting in an otherwise quiet home while noisy Sixty60 delivery bikes continued passing through the affected residential route. The resident reports that the practical issue remains unchanged: a simple instruction to avoid the street as a through-route could reduce the noise immediately, yet no such instruction has been confirmed.
- Route alternatives with screenshots were sent on 31 May 2026.
- The resident reports more than a week passed with no response or confirmation of action.
- On 7 June 2026, the resident reported another Sunday evening of noisy bike passes every few minutes.
- The resident again asked whether GPS or route data can be used to monitor and enforce main-road routing.
Date: 7 June 2026
Privacy note: exact residential street names, staff names, and private email details have been removed. The purpose is to document the unresolved operational issue and the continued lack of practical mitigation.
More than a week has now passed since residents sent Checkers Sixty60 mapped route alternatives with screenshots and direct questions. As of Sunday evening, 7 June 2026, residents report no response, no confirmation of action, and no visible change on the street.
That is the part that is so hard to accept: the noise is continuing while a simple mitigation remains available.
A quiet Sunday evening, except for the bikes
On 7 June 2026, a resident wrote again while sitting at home on what should have been a quiet Sunday evening. Instead, they reported being forced to listen to repeated Sixty60 delivery-bike passes through the residential street, with noisy bikes passing every few minutes.
The resident also reported another week of heavy delivery-bike traffic, describing daily pass volumes in the hundreds and even higher weekend-day volumes. Those numbers are presented here as the resident's report, because the point of this update is the escalation email and the continued lack of mitigation.
The lived experience is not abstract. It is repeated noise in the home, throughout the day, again on a Sunday evening, after months of complaints and more than a week after the latest route proposal was sent.
The solution being asked for is not complicated
The email again asked for a direct answer: why has nothing practical been done?
The requested instruction is simple: if a rider is not delivering in the affected residential street, do not use that street as a through-route. Use the main-road alternatives instead.
That is not a fleet replacement programme. It is not a long-term electric-bike strategy. It is not a citywide transport study. It is a route instruction that could be communicated now, monitored now, and adjusted now if there is a legitimate operational issue.
Residents have already shown that main-road alternatives appear to involve little or no meaningful difference in travel time. If Checkers disagrees, it should explain why in specific operational terms.
Route data should make this enforceable
The resident also asked a direct question about tracking and route data. If Checkers or its delivery partners have access to GPS, route, speed, braking, or similar operational data for delivery bikes, why is that not being used to prevent repeated shortcut use through affected residential streets?
This matters because the issue is not invisible. The same residential route is reportedly being used over and over again. The same pattern has been raised repeatedly. The same practical request has been made repeatedly.
If route data exists, then the company should be able to see the problem. If the company can see the problem and still does not act, then affected residents are entitled to ask whether the continued noise is being treated as acceptable collateral damage.
The human impact has been stated again
The 7 June email again explained that residents are dealing with repeated motorbike noise in their own homes for much of the day. The resident described severe stress, anxiety, unhappiness, exhaustion, and physical anxiety symptoms caused by the ongoing noise.
This is not a minor inconvenience. It is a daily residential nuisance that residents say has continued for more than 18 months while the company says it is looking into the matter.
There is a point where repeated assurances stop sounding like care and start sounding like delay. Residents are at that point.
The questions now need specific answers
The resident asked again for specific answers, not generic assurance:
- Will riders be instructed not to use the affected residential streets as through-routes unless they are delivering there?
- Will available GPS or route data be used to monitor and enforce that instruction?
- Will Checkers trial the main-road alternatives already provided?
- By what date will practical mitigation be implemented?
Those are reasonable questions. After the route screenshots, the repeated emails, the stated mental-health impact, and the continuing Sunday evening noise, silence is not acceptable.
This is why residents are angry
Residents are not angry because delivery services exist. They are angry because the same avoidable noise keeps being pushed through homes while the obvious mitigation is left undone.
They are angry because an apparently simple route instruction could reduce the impact now.
They are angry because they have supplied alternatives, explained the harm, asked direct questions, and still sit at home listening to the same bikes pass again and again.
Checkers Sixty60 can no longer credibly treat this as a vague future issue. There is an immediate operational choice in front of it: keep allowing the affected residential street to be used as a shortcut, or stop it.