Feed status · checked 2026-08-02
Eau Claire Transit
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Wisconsin.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 214 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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 ended 214 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- 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
- Foreign key violation (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Stop time with arrival before previous departure time (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date was 214 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 8 kinds of issue across 65 instances (51 error, 14 warning, 0 informational).
Service data ended 214 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 20, 21).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
60 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Mall Dr and E. Hamilton", "Oakwood Mall Dr and Monk's", "Starr and Somona Pkwy", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 492 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- E1 (black)
- 21 (teal)
- 1 (green)
- 6 (yellow)
- 5 (purple)
- 7 (purple)
- 3/4 (green)
- 8 (red)
- 3 (brown)
- 15 (purple)
- 17 (orange)
- 7 (orange)
- E10 (black)
- 15 (purple)
- 20 (teal)
- 15 (purple)
- 12 (teal)
| Route | Type | Line color |
|---|---|---|
| E1 Express 1 | Bus | black |
| 21 Shopko Plaza | Bus | teal |
| 18 Memorial | Bus | red (no shape in feed) |
| 1 Margaret and Mall | Bus | green |
| 6 Putnam Heights and Mall | Bus | yellow |
| 5 Rudolph Road | Bus | purple |
| 7 West Clairemont 6:45AM | Bus | purple |
| 4 Locust Lane | Bus | gray (no shape in feed) |
| 3/4 North High/Locust Lane Combination | Bus | green |
| 8 Folsom and Vine | Bus | red |
| 3 North High | Bus | brown |
| 15 West MacArthur Daytime | Bus | purple |
| 17 Altoona | Bus | orange |
| 7 West Clairemont | Bus | orange |
| E10 Express 10 | Bus | black |
| 15 West MacArthur Evenings | Bus | purple |
| 20 Westridge Center | Bus | teal |
| 2 Mt. Washington | Bus | teal (no shape in feed) |
| 15 West MacArthur 7:45AM | Bus | purple |
| 12 Delong | Bus | teal |
List every stop
- Abbe Hill and Eddy
- Forest and Huyssen
- Runway and Robin
- W Hamilton and Stein
- Robert Rd and W Moholt Dr
- Rudolph and Benton
- Golf and Clover
- Menomonie and Michigan
- MIller and Brian
- Forest and Elm
- 5th and West Grand
- Starr and Eddy Ln
- Birch and Holm
- Main and McGraw
- Seymour and Zepher
- Seymour and Morningside
- Rudolph and Webster
- State and Lincoln
- West MacArthur and Augusta
- Farwell and Earl
- Cameron and Nicholas
- E. Lexington and Fairfax
- 14th and Folsom
- Fairfax and Skeels
- Ferry and Menomonie
- North Lane and Anderson
- Germania and Division NE
- Starr and Seymour
- White and Hogarth
- W Moholt Dr and Mercantle Dr
- Fenwick and Keith
- 5th and Chestnut
- Bellinger and Randall
- Main and McGraw
- North Hastings Way at Dairy Queen
- E. Lexington and Trimble
- Oakwood Mall - Scheels
- Hamilton and Harlem
- Western and Marquette
- Craig and Oakridge
- Heights and Lasker
- Sunset and Fairmont
- Mall Dr and Festival Foods
- Starr and Lasalle
- Water and 8th
- 14th and Truax
- La Salle and Abby Hill
- Water St. and Fine Arts
- White and Runway
- 3rd and Walnut
- Birch and Putnam
- 14th and Wilson Dr
- Westover and Stein
- State and Roosevelt
- Water St. and Subway
- Margaret and Hoover
- Highland and Enterprise
- Wellington E and Eddy
- E. Hamilton and Trimble
- Craig and Clairemont
- Craig Road and Fahrman Center Driveway
- Chauncey and Belmont
- Division and Lynn
- State and Lincoln
- Putnam and Wisconsin
- Menomonie and 10th
- Birch and Germania
- 4th and Water
- Vine and Delong Middle School
- Addison and Sheridan
- Rudolph and Mitcher
- Western and Peebles
- Western and Conrad
- Oakwood Hill Pkwy and SSI Office
- Addison and Sheridan
- Oak and Barstow
- Folsom and Amstad
- Lark and Louis
- E. Lexington and Keith
- Truax and Folsom
- North Lane and Monroe
- E. Lexington and May
- Warden and Heimstead
- Oxford and Madison
- N Hastings Way Service Road and Melby
- Rudolph and Goff
- Birch St. & Mt. Nemo
- E. Hamilton and Gateway
- 9th and James
- Starr and Dellview
- Patton and E. Lexington
- Main and Our Savior Lutheran Church
- Pershing and Dulaney
- White and Anderson
- Hastings Way Service Road and La Salle
- Chauncey and Hogeboom
- Seventh and Fountain
- Birch and Mt Nemo
- Putnam and Summit
- Abbe Hill and Abbe Hill Ct
- W Hamilton and Xcel Energy
- Eddy and Cliff
- Craig Road and International Dr
- Cameron and 11th
- Miller and E Hamilton
- E. Hamilton and Miller
- Menomonie and Carson Park Dr
- Mitcher and Fairfax
- Kirk and Gloede
- Stein and Kenny
- Menomonie and Michigan St
- Cameron and 6th
- Riverfront Terrace and Barstow
- Cameron and Bellinger
- Graham and Emery
- Putnam and Madison
- Transfer Center
- Chauncey and Altoona
- Main and Our Savior Lutheran Church
- Hastings Way Service Road and Jackson
- Birch and Putnam
- Brian and Lever
- Forest and Sara
- Margaret and Highland
- Lake and Oxford
- Oak and Forest
- Fairfax and Ridgeview
- Spooner and 10th W
- Fairfax and Laurel
- Highland and Margaret
- Main and Dodge
- Highland and Lee
- Farwell and Eau Claire
- Chapin and Main
- Clairemont and Fairfax
- Keystone and Gateway
- London and Golf
- Woodman's
- Madison and McDonough
- Skeels and Fairfax
- E. Hamilton and Cypress
- Margaret and Main
- Abbe Hill and Leslie
- Stein and Kenney
- Barstow and Madison SE
- White and Melby
- Birch St and Erin St SE
- Rudolph and Lehman
- Starr and Omaha
- State and McKinley
- Spooner and Sports Center
- E. Lexington and Keith
- 10 ST W at Golden Acres
- E. Lexington and Grant
- Forest and Huyssen
- Washington and S Dewey
- Fall and Birch
- Anderson and Delbert
- Keith and Memorial High School
- Starr and Hallie
- Starr and La Salle
- 3rd and Lake
- Skeels and Rudolph
- Starr and North Lane
- Festival Foods lot S
- HIghland and Keith
- Farwell and Earl
- Pershing and Dulaney
- Western and Eddy
- Redwood and Starr
- Abbe Hill and Abbe Hill Ct
- Starr and Somona Pkwy
- Starr and Omaha
- Westover and Ellis
- Barstow and Eau Claire
- 5th and Chestnut
- Eddy and Cliff
- Lake and 4th
- Abbe Hill and LaSalle
- N. Clairemont Frontage Rd and Frank St
- Starr and Marquette
- Margaret and Main
- Galloway St & Putnam SW
- Bolles and Seventh
- Lake and Oxford
- Menomonie and Carson Park Ave
- London and Damon
- Festival Foods lot N
- Barstow and Marston
- Fairfax and Tony
- Oakwood Mall Micon Cinema
- Starr and Regional Airport
- Eddy and Mercury
- Margaret and Altoona
- E. Hamilton and Family Dollar
- Folsom and Mercantile
- Anderson and Edgewood
- Candell and Ferry
- Starr and Redwood
- 10 St W and Bartlett NW
- McIntyre and Melby
- W Hamilton and State
- Skeels and Blakely
- Pershing and Gleason
- Galloway at Walk Bridge
- Runway and Cardinal
- Seymour and Western
- Gateway and Goodwill Driveway
- Water and 8th
- Mercury and Piedmont Rd
- Eddy and Northland
- Barstow and Oak
- Anderson and Mitchell
- Piedmont and Mercury
- Eldorado and Imperial Circle
- Bellevue and Spring
- Barstow and Grand
- Zephyr Hill and Seymour
- Cleveland and LaMans Ln
- Main and Grove
- Jodi Dr and Moholt Dr
- Crescent and Fisher
- Main and Grove
- Birch and Holm
- Damon and Boardwalk
- Mitcher and Fairfax
- 5th and Union
- Platt and 2nd St
- 3rd and Water
- Eddy and Uranus
- North Hastings Way Frontage Road and Drylock
- 1st and Hudson
- Rudolph and E Lexington
- Golf and Oakwood Hills Pkwy
- Golf and Royal
- Barland and Summer
- Ferry and Short
- Vine and Fourth
- Golf and Keystone
- Skeels and Blakely
- Piedmont and Wellington E
- Fairfax and Sessions
- Riverfront Terrace and Barstow
- Fenwick and Donnellan
- Westover and State
- Vine and Delong Middle School Driveway
- Ferry and Short
- Birch and Dewey
- Seymour and Morningside
- Piedmont and Wellington E
- and 242 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error49 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Stop time with arrival before previous departure time (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 214 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning492 instances
492 of 492 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning361 instances
361 of 361 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning361 instances
361 of 361 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning6 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 214 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 214 days ago, so FTA would find the link out of date.
- 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 your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Needs attention
- 284 of 361 trips have a shape; 77 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 2 validator errors to resolve. Service data expired 214 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 214 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 51 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 44 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 0 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/eau-claire-transit/2026-08-02.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-02. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.