Call-prep brief · checked 2026-08-02

Embark

Grade B · 83.6 / 100

Up 0.2 points since 2026-08-01 (B to B).

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 up 0.6
Freshness no change
Rider experience no change

No longer reported since the last check (1 finding):

Some service dates fall outside the date window set in feed_info.txt. (service_window_outside_feed_period)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing bike allowance (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
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.
Turn on 'remove unused shapes' (or the like) in your export tool.
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
Effort: One setting.

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: Missing bike allowance (flagged by the MobilityData validator).
Next action: Review the rule documentation for 'missing_bike_allowance' 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

Agency: Embark
Finding: missing_bike_allowance
Feed evidence: Missing bike allowance (flagged by the MobilityData validator).
Why it matters: See the linked rule for what this affects.
Requested change: Review the rule documentation for 'missing_bike_allowance' 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.
Evidence: https://gtfsscorecard.org/agency/embark-2062/?finding=missing_bike_allowance#finding-handoff

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Ready: Service data covers the next 365 days.
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): 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.

Key facts

Feed URL: https://mna.mecatran.com/utw/ws/gtfsfeed/static/okc?apiKey=6a3b186a334d1e3e064f42782f6002520e60394c
Last checked: 2026-08-02
Service window: 365 days of service data remain. Last service date 2027-08-02.
Feed version: 01/08/2026-22:30
Location: Oklahoma

Part of the Oklahoma portfolio: see where this agency sits among the state's feeds 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.