University of Michigan Transit Services

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

   1245 of 1245 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Estimated effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

2. Remove retired stops from the export, or add them back to the trips that should serve them.

   Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

   Estimated effort: A review pass in your scheduling software.

   Agencies here usually clear this within about 1 week (based on 11 observed fixes).

3. Enable 'remove unused shapes' (or similar) in your export tool.

   The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.

   Estimated effort: One setting.

Where this agency stands

Ahead of 64% of all tracked agencies, and ahead of 63% of mid-size agencies nationwide.