Everett Transit

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).

   1098 of 1098 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. Populate trip_headsign to match what the bus displays.

   1098 of 1098 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

   Estimated effort: Usually a bulk edit in your scheduling software.

3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Estimated effort: A small file for most flat-fare systems.

Where this agency stands

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