Readiness
Know what is ready, what is blocked, and who owns the next step.
Readiness review helps operators prepare GTFS, GTFS Realtime, license/contact metadata, validation, vehicle data, connectors, and maintenance work without overclaiming the result.
What Readiness Should Answer
| Area | Question | Next owner |
|---|---|---|
| GTFS Schedule | Is there an active schedule with required files and reviewable validation state? | Operator or administrator |
| Vehicle Positions | Are fresh vehicles publishing safely, and are stale or unmatched rows understood? | Operator |
| Trip Updates | Is output available, withheld, blocked, or waiting on prediction configuration? | Administrator or integrator |
| Alerts | Is the Alerts feed available and tied to an operator-owned alert lifecycle? | Operator |
| Validation | Are validator tools configured, current, and understandable? | Administrator |
| License and contact | Are public metadata fields present before URLs are shared? | Agency and deployment owner |
| Maintenance | Are backup, restore, support, update, and monitoring responsibilities assigned? | Deployment owner |
Before You Share Feed URLs
- Confirm the five feedsDiscovery, schedule, Vehicle Positions, Trip Updates, and Alerts should each have a clear status.
- Confirm public metadataLicense, contact, provider identity, and feed URLs need agency and deployment-owner review.
- Confirm operations ownershipAssign who handles validators, backups, telemetry sources, secrets, monitoring, and updates.
- Decide what can be saidOnly make external claims that are supported by authorized deployment-specific records.
Limits
Readiness review is preparation. It is not compliance approval, agency adoption, consumer submission or acceptance, final public root proof, production readiness, hosted service availability, vendor compatibility, SLA coverage, production AVL reliability, or ETA-quality proof.