Gathering Public Input on a Bus Route Change
Service changes generate more public comment than anything else an agency does, and almost none of it arrives in a form you can plot. The fix is to ask the question on a map, and to ask it where the affected riders actually are.
Why route-change comment is usually unusable
An agency announces a proposed change, opens a comment inbox, and receives four hundred emails. Two months later somebody has to summarize them for a board packet. The summary says most commenters opposed the change — which was always going to be the finding, because people who are fine with a change don't write in. Nothing in the record says which segment each commenter actually rides, so nothing in it can distinguish a genuine coverage problem from generalized dislike of change.
A structured, spatial survey fixes both halves of that. It samples riders on the affected segments rather than waiting for the motivated to self-select, and it records where each respondent is speaking from.
The five questions that earn their place.
A route-change survey is read on a phone, often on the vehicle. Keep it to about five questions and put the map first — it establishes immediately that this survey is about a specific thing, which is what stops the abandon.
Show the proposal
A Route Display question renders the proposed alignment on a map with the current one for contrast, and collects a reaction to it specifically.
Locate the respondent
A Route Creator question asks them to draw the trip they take today. This is what lets you separate affected riders from interested observers.
Ask what would fix it
"What would need to be true for this to work for you?" produces actionable specifics — a stop, a transfer, a first-trip time — instead of a support score.
Rank the alternatives
If there's more than one option on the table, a Route Ranker question puts them in preference order — far more useful than approve/disapprove on each.
Capture frequency
How often they ride the affected segment. Weighting comment by exposure is the single most defensible cut you can make in the board presentation.
Then, optionally, who
The profile step goes last and stays optional. Email enables deduplication and verification; zip code alone still plots on the coverage map.
Choosing the right map question type → · Building surveys that get completed →
Post the survey on the segment you're asking about.
This is the part that determines whether the study is worth running. A link on the agency homepage reaches advocates. A QR code on the stanchion of the run being changed reaches the person whose commute is about to change.
- Vehicles serving the affected runs — seat backs and stanchions
- Stops being moved, added, or removed — shelter panels and pole signage
- Rider alerts and the agency app — direct link, for riders already subscribed
- Email lists — for stakeholders, committees, and prior commenters
- A tablet kiosk at the open house — so walk-ins land in the same dataset
One count, not five
Every channel feeds the same survey and the same dataset. Where an email address is collected, TIPS deduplicates across all of them — so the totals you put in front of the board are people, not submissions, and nobody can argue the open house attendees were counted twice.
What you bring to the hearing
The deliverable is a branded PDF plus the live Report page for anyone who wants to dig. What actually moves the room, in order: the density map showing where respondents were concentrated and where they weren't; the cross-tab of reaction by ride frequency, which separates the people who use the segment daily from those who don't; and the verified-response count, which is your answer when somebody suggests the survey was brigaded.
Keep the raw CSV and GeoJSON too. Drawn trips from the Route Creator question are genuinely useful downstream — they show the trips the proposed alignment would break, which is often a better argument than any of the survey's scored questions.
Common questions
- When should input collection start?
- Before the alignment is final, and early enough that the answer can still change something. Input gathered after the decision is made reads as a formality to everybody involved, and riders can tell. Practically that means opening the survey when you have two or three viable options rather than one preferred alternative.
- How do we reach riders on the affected segments specifically?
- Posted QR codes on the vehicles serving those runs and at the stops being changed. This is the whole advantage of intercept collection for a route change — the poster is physically located on the segment you are asking about, so the sample self-selects toward exactly the people affected, which is the opposite of what happens with a website announcement.
- What do we do about the people who just want to say no?
- Give them a place to say it, and then ask a question that produces usable information anyway. "What would need to be true for this change to work for you?" gets a specific answer — an earlier first trip, a preserved stop, a maintained transfer — where "do you support this change?" gets a number that surprises nobody. Both belong in the instrument.
- How do we handle the person who submits fifty responses?
- Enable the pre-survey profile step and collect an email address; TIPS then deduplicates on it across every channel. For an anonymous QR-only survey there is no way to identify a repeat respondent, which is why route-change surveys generally should ask for an email even when the response itself stays effectively anonymous in reporting.
- What goes in front of the board?
- The branded PDF export covers the standard package: response counts, per-question charts, the respondent-density map, and the demographic cross-tabs. The density map is usually what carries the meeting, because it answers the question a board member will ask first — "did you actually hear from the people on that street?"
- Can we run it in more than one language?
- Yes, and for a route change through a linguistically diverse corridor you should. Add the languages to the survey, translate the questions and the invitation email, and every response aggregates into the same dataset regardless of the language it was answered in.
Start from the route-realignment template
TIPS includes a route-realignment template that becomes a working survey in one click. Load your alignment, adjust the wording, and it's ready to post.
Start free 14-day trial Public involvement software