Call-prep brief · checked 2026-09-13
Regional Transportation District (RTD)
Grade D · 60.8 / 100
Down 0.4 points since 2026-09-12 (D to D).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
- Realtime quality down 0.7
Top three things to fix
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 13 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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
21567 of 21567 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
Effort: A default or per-trip field in your export.
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.
Effort: A small file for most flat-fare systems.
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 13 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
- 21567 of 21567 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- The feed contains no fare information.
- Next action
- 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.
- 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 Regional Transportation District (RTD) team, Service data runs out in 13 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/regional-transportation-district-rtd-178/
NTD GTFS readiness: Needs attention
This feed is close to NTD-ready. Service data runs out in 13 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 13 days; renew before you certify.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals NTD ID (optional): Different (allowed). Your feed's agency_id is RTD; your National Transit Database ID is 80006. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id RTD to NTD ID 80006, and keep the feed value stable. Do not change it solely to make the two values equal.
The bar this score answers to
A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers.
Key facts
- Feed URL
- https://www.rtd-denver.com/files/gtfs/google_transit.zip
- Last checked
- 2026-09-13
- Service window
- 13 days of service data remain. Last service date 2026-09-26.
- Feed version
- Jun26-36973-20-27-20260819-030145
- Location
- Colorado
Part of the Colorado 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.3, validator 8.0.1.