RTS Rochester Audio Briefing — 6 minutes

ANALYST "R-T-S is so incredibly inefficient. It would take ninety minutes each way for a twenty-five-minute drive." That's an R-T-S Rochester rider, posting on the Rochester subreddit in twenty twenty-five. HOST: Ninety minutes against twenty-five. That's not a review of an app. That's a rider doing the math in public. ANALYST: And it isn't only Rochester's story. Pulse Insights studied sixty U.S. transit agencies this year, and roughly three in four show the same pattern: riders losing trust in what the agency's digital surfaces tell them. This episode is about what the review found at R-T-S. HOST: This is edition twenty-two of a sixty-agency review of digital rider experience in U.S. transit. Let's get into it. HOST: Come back to that quote for a second. What's the phrase that matters? ANALYST: "A twenty-five-minute drive." The rider isn't naming the app. The rider is naming the comparison. Ninety minutes by bus against twenty-five by car, and the arithmetic is the story. Across the cohort, real-time trust friction shows up in three shapes: information that's wrong, information that misleads, and information that's simply absent. R-T-S Rochester's documented pattern lives one step earlier, at the planning surface. The trip planner returns routes the rider judges too long to use, and the transfer with the University of Rochester shuttle gets flagged as a specific seam. HOST: Did the review see this shape anywhere else? ANALYST: It did. In Buffalo, an N-F-T-A rider wrote in the App Store that the MetGo app force closes constantly, and password entry fails six times before it succeeds. Same regional scale as Rochester, both heavy bus networks with a light-rail spine in a mid-sized northeastern metro. Different surface, same rider response. HOST: Where else? ANALYST: A Cleveland R-T-A rider put it this way. "Delays are bad, but the poor passenger information, ghost trains, no service announcements, makes it even worse." In every case the rider compares the agency's surface to a more reliable alternative and reports the gap publicly. And that comparison is durable. It outlives the schedule refinement that should make it unnecessary. The grant funds the data work. The trust gap runs on a different surface, where the rider actually sees the ninety-minute result. HOST: So what did the review find about R-T-S specifically? ANALYST: Two observations stand out. First, R-T-S sits inside the cohort's largest friction pattern. Three of every four agencies studied have documented real-time trust friction. What distinguishes Rochester is that the public friction surface is the trip planner itself, not the real-time tracker. Riders compare the planner's recommended route to the drive they'd take instead, and the comparison drives the complaint. HOST: And the second? ANALYST: Thirty-five of the sixty agencies are in an active service-change window. SEPTA's Bus Revolution, MARTA's NextGen, Pace's ReVision, C-D-T-A's Vision Refresh. R-T-S has a Service Performance Monitoring grant that funds ridership-data work and schedule refinement, and that places Rochester in the same window. Across the cohort, the public communication of service changes and the public measurement of rider response are running on different timelines. HOST: Where does that put the agency overall? ANALYST: The review sorts the sixty onto a maturity arc. Eight agencies are at what it calls Integrated: multi-modal trip planning, single-app architectures, documented real-time fallback handling, structured rider feedback. R-G-R-T-A sits one tier below, in the Operational cluster, alongside roughly forty-eight others. Functional rider tooling, documented reliability gaps, and the multi-app pattern visible across the cluster. Two agencies are at Foundational. And zero of the sixty have reached the top tier, Leading. HOST: Has any agency treated the trust gap as its own project, rather than waiting on the data fix? ANALYST: New Jersey Transit. A twenty-nine day study found that seventy-three percent of riders planning trips during active service advisories didn't know those advisories existed. And here's the part that matters for Rochester. The data was accurate. The alerts were live, timely, and complete. The friction was riders unaware at the moment of decision. HOST: So what did they do about it? ANALYST: One question. It surfaces only when a rider's searched route has an active advisory, and it asks, did you know there's a travel advisory for your trip? The agent matches each searched route against the live advisory feed, runs across rail, bus, and multi-modal trips, and scales on its own during disruptions. The technical surface 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. 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: What happens next? ANALYST: The review used the open record only. Strategic plans, board minutes, app store reviews, rider forums, grants. No interviews. That's the next step. This fall Pulse Insights publishes the first cross-agency report on rider digital experience in U.S. transit, and R-G-R-T-A is on the shortlist. Thirty minutes. Participating agencies get the report ahead of public release, along with a deeper readout on what the review found in Rochester. HOST: And if the person listening isn't the right person? ANALYST: They almost certainly know who is. Everything cited today is in the R-G-R-T-A booklet. HOST: Thanks for riding with us.