Transit system planning
Explain a proposed transit change in terms of real journeys
Help riders understand what would change, what is still undecided, and how their feedback can inform the proposal.

Original editorial illustration; not a photograph of Cathay operations.
A proposed route or timetable change is easier to discuss when riders can understand its effect on an actual journey. A map alone may not explain a longer walk, a different transfer, or an earlier last departure. Prepare clear examples alongside the technical proposal, and make the status of the decision explicit. This is a communication framework to use alongside the agency's applicable public-participation and review requirements.
State the problem and what is proposed
Explain the service problem using plain language and the evidence the agency has reviewed. Distinguish the objective from the proposed solution. For example, improving access to a destination is an objective; changing a route segment is one possible way to pursue it.
Label the material as a proposal when decisions remain open. Identify which elements can still change, what information is being sought, and how the next decision will be made. Avoid presenting an implementation date as settled when it has not been approved.
Compare complete journeys
Choose representative trip examples that show the current and proposed experience from origin to destination. Include the walk to the stop, the relevant departure, any transfer, and the return journey. Make assumptions visible so an example is not mistaken for a guaranteed trip time.
Show tradeoffs as clearly as benefits. Some riders may gain a more direct journey while others face a different stop or connection. Include evenings and weekends where the proposal affects them, rather than illustrating only the easiest weekday trip.
- Current stop, route, and service period.
- Proposed stop, route, and service period.
- Change in walking or transfer arrangements.
- Effect on the return trip and final available departure.
Make feedback specific and usable
Ask riders which journeys the proposal would help or make harder, and invite concrete origins, destinations, and travel periods through appropriate channels. Offer ways to respond that fit the communities served, and have the responsible staff review communication and accessibility needs.
Avoid collecting unnecessary personal information just to understand a travel pattern. If a comment requires an individual response, explain how the agency will handle that contact information through its established process. Keep feedback about a proposal distinguishable from requests for immediate trip assistance.
Show how the proposal developed
Maintain a clear version history and a record of recurring concerns. When the agency revises the proposal, explain the practical effect of the revision and which earlier materials it replaces. Riders should not have to compare several undated maps to find the current option.
After a decision, communicate the approved arrangement separately from the consultation materials. Confirm the implementation details through the agency's process and identify where riders can obtain current information. Closing that loop helps people move from discussing a possible change to planning a real journey.
Your next step
Discuss transit service planning and rider communication
Connect with our team to discuss your needs and the available arrangements.


