Operations & management
What belongs in a monthly transportation service review?
A practical meeting structure for agencies and operating partners reviewing service delivery, recurring issues, and agreed follow-up actions.
A monthly service review should lead to decisions, not just a stack of charts. For an agency working with an operating partner, the useful questions are straightforward: what service was delivered, where did the plan break down, what did passengers experience, and who will act before the next review? Start with the contract’s reporting requirements and build a discussion around them.
Agree on definitions before comparing results
Define each measure so both parties interpret it the same way. If the report includes on-time performance, state the relevant timing standard and which trips are counted. If it includes missed service, distinguish operator-caused events from other categories without using classifications to hide the passenger impact.
Record exclusions and missing information. A percentage without a denominator can be difficult to evaluate, especially when service volume changes. Keep definitions consistent between months and explain any revisions before treating a change as improvement or deterioration.
Show the service behind the totals
Compare planned and delivered service using the measures appropriate to the program. Discuss where results vary by route, time period, location, or service type. A systemwide average may conceal a recurring problem affecting one group of passengers.
Use a small number of examples drawn from verified records to explain a pattern. Keep personally identifying passenger information out of general meeting materials when it is not needed. Separate evidence from a proposed explanation that still requires investigation.
Include the passenger’s experience
Review complaints, commendations, and recurring information requests alongside operating results. Ask whether riders received clear updates during disruptions and whether an issue has appeared more than once. A complaint count alone does not explain its severity or whether the underlying problem was resolved.
Where a matter requires an immediate safety or service response, use the program’s escalation process promptly; do not wait for the monthly meeting. The review is a place to examine patterns and completed actions, not a substitute for timely operational response.
Connect resources with service outcomes
Discuss staffing coverage, vehicle availability, maintenance coordination, and dispatch capacity according to the responsibilities established in the agreement. Identify dependencies that the agency or another party must resolve, rather than assigning every issue to the same owner.
FTA’s National Transit Database provides public operating, financial, and asset information for transit systems. It can support context, but a local monthly review still needs the program’s own definitions and records. Peer comparisons should acknowledge differences in geography, service design, and reporting.
Further readingFTA: The National Transit Database (opens in a new tab)End with a short action register
For each agreed action, record the issue, responsible owner, due date, and evidence that will show whether the action worked. Carry unresolved items into the next review, and distinguish an action that was completed from a problem that was actually resolved.
A useful meeting closes with a few clear commitments. Cathay’s transportation operations and management service can be discussed in the context of an agency’s fleet, operating scope, and reporting expectations. Define that scope early so the review measures the service the parties actually agreed to deliver.
Your next step
Discuss your transportation operating program
Connect with our team to discuss your needs and the available arrangements.