Key takeaways
- Requires Caltrans, with input from transit operators, to create a statewide California Transit Stop Registry by June 1, 2027, with each stop's name, location, available seating, a unique identifier and whether it is sheltered.
- By January 1, 2028, each defined transit operator must conform its stop names and locations to the registry, use the registry identifier in published datasets, and report seating and shelter for each stop.
- This is a state-mandated local program.
AB 1599 — Ch. 269, Stats. 2026. This guide is written for California local government staff and distinguishes the law's direct requirements from source commentary and possible local implications.
At a glance
| Bill and chapter | AB 1599 · Ch. 269, Stats. 2026 |
|---|---|
| Subject area | Transportation, Public Works & Contracting |
| Local impact | Required: administrative action |
| Action class | Operational only |
| Workbook priority | 3.0 (scale: 5 highest) |
| Effective date | Jan 1, 2027 (no urgency clause stated); Caltrans registry due on or before June 1, 2027; operator duties due on or before Jan 1, 2028 |
| Who is affected | Transit operators under the Transportation Development Act (cities, counties and transit agencies that run service) |
What the measure changes
Requires Caltrans, with input from transit operators, to create a statewide California Transit Stop Registry by June 1, 2027, with each stop's name, location, available seating, a unique identifier and whether it is sheltered. By January 1, 2028, each defined transit operator must conform its stop names and locations to the registry, use the registry identifier in published datasets, and report seating and shelter for each stop. This is a state-mandated local program.
The chaptered bill text controls; the Legislative Counsel’s Digest is a summary of the statute. This article translates the workbook’s findings into an implementation-focused overview and does not replace the statute or jurisdiction-specific legal advice.
Who this matters to in city or county government
Covered entities and scope: Transit operators under the Transportation Development Act (cities, counties and transit agencies that run service)
Population or other scope limit: Transit operators as defined in the bill
Departments and roles identified in the workbook:
- Transportation/Traffic
- Public Works/Engineering
- IT/Cybersecurity
Charter-city note: N/A
What local governments need to know
No council action; transit operators should make stop names and locations match the Caltrans registry, use the registry's unique stop identifiers whenever they publish datasets with stop information, and report whether each stop has seating and shelter, all by Jan 1, 2028.
Operational change: Transit operator staff align stop names and locations with the Caltrans registry, use registry stop identifiers in published datasets, and report seating and shelter for each stop by Jan 1, 2028.
Code review: No
Potentially affected code or policy areas: Transit stop inventories; Open data publication practices
Preemption or local authority: No
New local requirement: Yes
Implementation roadmap
- Confirm the agency is covered: Transit operators under the Transportation Development Act (cities, counties and transit agencies that run service) Scope limits: Transit operators as defined in the bill
- Assign a lead and supporting roles from the affected departments: Transportation/Traffic, Public Works/Engineering, IT/Cybersecurity.
- Update staff workflow, forms, notices, contracting, reporting, or training as applicable: Transit operator staff align stop names and locations with the Caltrans registry, use registry stop identifiers in published datasets, and report seating and shelter for each stop by Jan 1, 2028.
- Calendar and verify the applicable dates: Jan 1, 2027 (no urgency clause stated); Caltrans registry due on or before June 1, 2027; operator duties due on or before Jan 1, 2028
Key dates and deadlines
- General effective date and deadlines: Jan 1, 2027 (no urgency clause stated); Caltrans registry due on or before June 1, 2027; operator duties due on or before Jan 1, 2028
- Code change deadline: Not applicable
Implementation and compliance considerations
| Implementation area | Review | What staff should verify |
|---|---|---|
| Local impact classification | Required: administrative action | Workbook action class: Operational only. |
| Scope and coverage | Confirm | Transit operators as defined in the bill |
| Effective dates | Calendar | Jan 1, 2027 (no urgency clause stated); Caltrans registry due on or before June 1, 2027; operator duties due on or before Jan 1, 2028 |
Enforcement and reimbursement
State-mandated local program; reimbursement only if Commission on State Mandates finds costs
Issues to confirm with agency counsel
Digest key shows a local program. The digest ties the operator duties to the Transportation Development Act definition of transit operator, so confirm which operators are covered in the bill text.
Source guidance for local agencies
Streetsblog California (pro safe streets) welcomes the standardized stop identifiers; Cal Cities does not appear to have taken a position in this packet.
Sources and provenance
This overview organizes findings supplied in the California 2026 localities workbook. Source links and commentary were carried over from that workbook; they have not been independently verified for this article. Association and law-firm summaries are secondary commentary, not controlling law. Consult the official text before relying on an interpretation.
- California Legislative Information — chaptered bill text and digestOfficial
- Governor of California (gov.ca.gov)Official · 2026-09-18
California Transit Stop Registry. - Streetsblog CaliforniaPolicy/news · 2026-10-01
Creates a statewide Transit Stop Registry giving every transit stop a unique identifier in shared transit datasets.
Frequently asked questions
What does AB 1599 do?
Requires Caltrans, with input from transit operators, to create a statewide California Transit Stop Registry by June 1, 2027, with each stop's name, location, available seating, a unique identifier and whether it is sheltered. By January 1, 2028, each defined transit operator must conform its stop names and locations to the registry, use the registry identifier in published datasets, and report seating and shelter for each stop. This is a state-mandated local program.
Which local agencies or staff are affected?
Transit operators under the Transportation Development Act (cities, counties and transit agencies that run service)
What should local government staff do next?
No council action; transit operators should make stop names and locations match the Caltrans registry, use the registry's unique stop identifiers whenever they publish datasets with stop information, and report whether each stop has seating and shelter, all by Jan 1, 2028.
Prepared as an informational guide for local government professionals. Confirm statutory requirements, local applicability, and current law with qualified agency counsel.
Published by Legislaide Editorial Team. Workbook-based legislative overview. Sources, review, and corrections policy. Source reference record (JSON).