COTA Audio Briefing — 6 minutes
Under six minutes on where COTA sits in the cohort. Two analysts walk the review, from the LinkUS capital build to the rider-trust project the public record shows no owner for, and what New Jersey Transit did when it made rider trust its own project. The audio companion to your booklet.
Read the transcript
ANALYST "It will show your bus coming and that it has gone. Passengers are standing there confused. Never saw it." That is a rider in Oakland, posting on Reddit in twenty twenty-five about A-C Transit. It is the first voice in COTA's booklet, and the booklet is honest about why. It is not a COTA rider. It is a rider from a peer agency in the same friction cluster, describing the experience the review found across that whole cluster. HOST: A bus that arrives on the screen and never arrives at the curb. That is about as basic as rider trust gets. ANALYST: And it is not one agency's story. The review behind this episode studied sixty U.S. transit agencies, and roughly three of every four are losing rider trust in real-time arrivals. COTA is among them. This episode is about what the review found here. HOST: This is edition twelve of a sixty-agency review of digital rider experience in U.S. transit. Let's get into it. HOST: Come back to that quote. Why does a booklet about Columbus open with a rider from Oakland? ANALYST: Because it describes the exact shape COTA lives inside. The booklet calls it the LinkUS capital window. A voter-approved half-percent sales tax from April of twenty twenty-four is funding a multi-year build-out. B-R-T corridors are in active planning. Microtransit zones keep expanding. And the rider-facing surfaces, the website, the app, the trip planner, are being asked to absorb all of that change at once. The booklet's essay argues that surfaces designed for steady state struggle to render change, and that real-time data that worked on existing routes lags on the new ones. HOST: Did the review see the same complaint at other agencies in that window? ANALYST: Cleveland's R-T-A, a same-state peer at adjacent scale, where a rider wrote, "Delays are bad, but the poor passenger information, ghost trains, no service announcements, makes it even worse." ANALYST: And Charlotte, the cohort's closest funding parallel, with its own new voter-approved sales tax. A rider there wrote, "The app presents info like real time bus arrival and departure info. It isn't. It will show your bus coming and that it has gone." Nearly word for word the voice that opened this episode. ANALYST: That repetition is the point. The booklet's argument is that this kind of capital-build-versus-digital-readiness gap is durable. Riders learn not to trust the screen, and that lesson outlives the technical fix that should make it unnecessary. HOST: So what did the review actually observe about COTA? ANALYST: The first observation is about ownership. Three of every four agencies in the study show documented real-time trust friction, and the booklet calls COTA's instance the cohort's clearest case of a capital build without a customer-experience owner. The data feed publishes. The surfaces are in service. But the review found no named customer-experience function in COTA's public org structure carrying the rider-trust project alongside the build. ANALYST: The second is timing. Thirty-five of the sixty agencies are in an active service-change window, and LinkUS sits inside one of the cohort's larger capital windows. Across the cohort, the public communication of service changes and the public measurement of rider response are running on different timelines. HOST: And where does that put COTA on the review's maturity arc? ANALYST: In the Operational cluster, alongside roughly forty-eight other agencies. Functional rider tooling, an active data feed, a clear capital runway through LinkUS. One tier up is Integrated, where eight of the sixty sit. And zero agencies have reached the top tier, where rider experience is treated as continuously measured and actionable in real time. HOST: Has any of the sixty treated this trust gap as its own project? ANALYST: New Jersey Transit. A twenty-nine day study there found that seventy-three percent of riders planning trips during active service advisories didn't know those advisories existed. And here is the uncomfortable part. The data was accurate. The alerts were live. The gap was entirely in whether riders saw them at the moment of decision. HOST: So what did they actually do? ANALYST: One question. The trip planner asks, "Did you know there is a travel advisory for your trip?" It surfaces only when a rider's searched route has an active advisory, never otherwise. The technical footprint is one tag in the page header. Everything else runs server-side. HOST: And the result? ANALYST: Seven in ten trip planners the agent reaches discover an alert they didn't know existed, and choose to see it in context, at the moment they're planning the affected trip. In the first weeks of full production it guided tens of thousands of riders to alerts they would have missed. And modeled at the floor of measurable value, the conservative case cleared the program cost inside the pilot window. HOST: So what happens next? ANALYST: The review used open record only. Strategic plans, board minutes, app store reviews, rider forums. No interviews, and that is the next step. This fall, Pulse Insights publishes the first cross-agency report on rider digital experience in U.S. transit, and COTA is on the shortlist for the conversations that will shape it. Thirty minutes. Participating agencies receive the report ahead of public release, along with a deeper readout on what the review found here. HOST: And if the person listening isn't the right person? ANALYST: They almost certainly know who is. Everything cited today is in the COTA booklet. HOST: Thanks for riding with us.
HELP IF YOU WANT IT
Want to talk through any of this?
No pitch, just a short working session to see what this could look like on your own site.