Follow-up insight
When we first ran the numbers on how residents in the Eastern Cape townships reach their workplaces, the picture looked straightforward. The second pass told a different story, and it is that difference worth writing about.
The initial review, published in the February edition, focused on minibus taxi routes and their schedules. We spoke to drivers, queue marshals, and commuters at three ranks in Makhanda and King William's Town. The feedback was clear: people wanted more than a list of departure times. They wanted to understand why some routes run smoothly while others collapse under pressure.
What changed after that first round of interviews is the way we approached the municipal records. Instead of taking the published timetable at face value, we started comparing it with the actual vehicle logs submitted to the local transport office. The gaps were not small. On the route between Mdantsane and East London's CBD, the official schedule promised a taxi every twelve minutes during peak hours. The logs showed intervals stretching to twenty-five minutes on most weekdays.
Commuters we spoke to were not surprised. A woman who travels from NU2 to the city centre each morning put it plainly: "We know the times printed on the board are a wish. The real clock is the one at the rank." Her comment, and others like it, pushed us to look at the reasons behind the delays rather than just reporting them.
The deeper issue turned out to be maintenance. Several vehicles were being pulled off the road for brake checks and suspension work, and there was no spare fleet to cover the gap. The provincial department acknowledged the shortage in a written response but said new vehicles were only expected in the next financial year. That leaves commuters with a system that works, but barely.
There is also a quieter change worth noting. After our first article ran, the local taxi association invited us to their monthly meeting. It was the first time they had opened the floor to the press in over a year. The chairperson said the coverage helped them make the case to the municipality for better rank facilities. Whether that translates into action remains to be seen, but the door is now open.
For readers who followed the original piece, the practical takeaway is this: the schedule on the wall is a starting point, not a promise. Plan for the delay, and if you can, travel outside the sharpest peak. The associations are aware of the strain, and some are testing a staggered departure system on the busiest routes. We will report on how that experiment goes in the coming months.
This is the third piece in our series looking at how public transport systems actually function. The earlier articles approached the topic from different angles, and together they give a fuller picture of what commuters face.
Byline
A grounded post that adds a different angle without repeating the others.
Three months ago, the editorial team sat down with a stack of reader letters and a list of recurring complaints about municipal services in the Eastern Cape. The first review produced a set of promises. This piece looks at what actually shifted since then, and what stayed stubbornly the same.
The initial review focused on water outages in the northern suburbs of Gqeberha and the slow response times reported by residents in Kariega. We published the findings, listed the contact numbers for the relevant ward councillors, and promised to track the follow-up. That tracking turned out to be more revealing than the original complaints.
The most obvious shift was in communication. Where residents previously waited days for a response to logged faults, the municipal call centre now sends a confirmation SMS within two hours. It is a small thing, but it changed how people described the process. Instead of feeling ignored, callers knew their report had landed somewhere.
A second change was the introduction of a shared spreadsheet between the ward office and the neighbourhood association in Westering. Every Monday morning, the list of open cases is updated and circulated. It is not a fancy system, but it gave both sides a single source of truth. Disputes about whether a complaint was logged, or when a team last visited, became easier to settle.
The original document did not anticipate how much of the delay was caused by a shortage of specialised vehicles. The review assumed that once the workflow was clearer, the work would happen faster. In practice, the bottleneck was not paperwork. It was the fact that only two teams were available to cover a district that needed at least four.
Residents noticed this gap quickly. One woman in Kabega Park kept a handwritten log of every visit she saw from the water department over a six-week period. Her count came to three. She brought the log to a public meeting and read it aloud. That single act did more for accountability than any formal report we had produced.
The ward councillor has requested an additional vehicle from the provincial department, and the request is still in the approval queue. In the meantime, the neighbourhood association has started coordinating with a private borehole company to provide temporary water points during extended outages. It is a stopgap, not a solution, but it has reduced the number of days families go without water.
What the follow-up review made clear is that public systems improve when residents keep records and show up to meetings. The spreadsheet works because people update it. The call centre responds because callers follow up. None of this is glamorous, but it is how change happens in a provincial town.
"The review gave us a starting point. The real work began when residents started keeping their own notes and holding everyone to them."
For readers who want to see the original findings or the updated action list, the full documents are available at the ward office on Cape Road. The next public meeting is scheduled for the first Thursday of next month at the community hall. Bring your own logbook if you have one.