Call-prep brief · checked 2026-08-31
York Region Transit (YRT)
Grade F · 55.3 / 100
Down 0.4 points since 2026-08-30 (F to F).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
Top three things to fix
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 5 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Effort: One export setting.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Effort: Often a bulk fix in your scheduling software.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Effort: Usually an export-tool fix, not hand editing.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data runs out in 5 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Ready to send to the agency
Hi York Region Transit (YRT) team, Service data runs out in 5 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/york-region-transit/
Key facts
- Feed URL
- https://www.yrt.ca/google/google_transit.zip
- Last checked
- 2026-08-31
- Service window
- 5 days of service data remain. Last service date 2026-09-05.
- Feed version
- 2026.06.28_June_20260611
- Location
- Ontario, Canada
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.