Call-prep brief · checked 2026-10-15

York Region Transit (YRT)

Grade F · 56.4 / 100

Down 2.1 points since 2026-10-14 (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 down 4.0
Freshness down 1.6
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 16 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
This one is about the feed as a whole, so there is no share of it to count.
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: Usually an export-tool fix, not hand editing.

Riders and need behind these fixes

Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
No need reading for this feed was on hand when this was built, so transit need is not known.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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 16 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

Agency: York Region Transit (YRT)
Finding: scorecard_feed_expiring_soon
Feed evidence: Service data runs out in 16 day(s).
Why it matters: When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/york-region-transit/?finding=scorecard_feed_expiring_soon#finding-handoff

Ready to send to the agency

Hi York Region Transit (YRT) team, Service data runs out in 16 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/

Copy this note from the full scorecard.

Key facts

Feed URL: https://www.yrt.ca/google/google_transit.zip
Last checked: 2026-10-15
Service window: 16 days of service data remain. Last service date 2026-10-31.
Feed version: 2026.09.06_September_20260810
Location: Ontario, Canada

Part of the Canada portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.