A difficult hour still needs people
Imagine a hypothetical driverless fleet with several cars needing help at once. More vehicles would not automatically supply more people to recover them. If support falls behind, cars might stop earning revenue while waiting. The operating question is how much help the service needs during a difficult hour, not just a quiet one.
Removing an onboard driver could move some work to remote support and local response. That does not by itself defeat the business case. Fleet operators would need to compare staff time, response capacity and vehicle downtime per completed trip. Emergency officials and other road users also have a stake in how quickly an obstruction clears.
What changes in July 2028
California approved SB1246 on September 30, 2026. Its new autonomous-vehicle operations chapter becomes operative July 1, 2028. Approval establishes the future framework, not a report that operators have already changed staffing or achieved better response times. [1]
The law directs the Department of Motor Vehicles to adopt reasonable response-time guidelines for local incident technicians by July 1, 2028. These technicians respond onsite. Guidelines are not one fixed arrival deadline for every location and incident; they set a future standard against which response capacity can be planned. [1]
A separate provision, also operative July 1, 2028, requires remote drivers to be in the United States with a license valid for California driving, including the appropriate class and endorsements. The law distinguishes remote drivers from remote assistants. The driver-license requirement should not be applied to both as if they were interchangeable. [1]
The public needs rates, not a league table
The new chapter requires the department to publish quarterly summary statistics broken down by manufacturer. That could give the public an operating record to examine. The statute itself is not evidence of compliance, faster recovery or improved safety. [1]
Raw incident counts would be a poor ranking of operators. More trips could bring more incidents even with a lower incident rate. Compare responses with trips or other operating exposure and with local conditions. Long waits during simultaneous incidents would matter even if an average response time looked reassuring.
Existing support could change the bill
The strongest counterargument to a large new staffing bill is that operators may already provide much of this support. Incremental costs could be modest, and rare incidents could allow efficient shared coverage. The law supplies no added-cost estimate. A written requirement also cannot demonstrate a working response system under pressure.
Watch the guidelines due by July 2028, readiness when the provisions start, and the subsequent manufacturer summaries. Pair response times with operating exposure, staff hours and downtime where available. Low support use with reliable recovery would weaken the cost-burden interpretation; persistent delays would strengthen it. Neither result can be read from the approval alone.
Source limits and remaining unknowns
- New provisions become operative July 1, 2028. The statute distinguishes remote drivers from remote assistants and calls for reasonable response-time guidelines rather than one universal arrival deadline.
What remains uncertain
- The new operations chapter and remote-driver provision start in July 2028. Approval alone establishes neither extra staffing costs nor improved safety or compliance.
- Existing support may make added costs modest. Raw incident counts and average waits can mislead without operating exposure, local context and simultaneous-incident performance.
Watch the brief
52 seconds · AI-generated narration and artwork. The article and sources provide the full context.
Read the video transcript
Imagine several driverless cars needing help together. More vehicles don’t automatically mean more response capacity. Cars waiting for help could lose earning time. California’s new operations chapter starts in July twenty twenty-eight. It calls for local response-time guidelines and quarterly manufacturer summaries, alongside a separate remote-driver location and licensing rule. The business question is support hours and downtime per completed trip. Removing an onboard driver could shift work elsewhere, rather than remove every human cost. Operators may already provide much of that support, so added costs could be modest. The law doesn’t estimate them, and written obligations don’t demonstrate recovery under pressure. Watch the guidelines and eventual operating data. Compare waits with fleet activity and simultaneous incidents. Raw counts or a good average alone can hide the strain.
Sources
- Bill Text - SB-1246 Autonomous vehicles.SB1246:v92#DOCUMENT California Legislative Information · accessed 02 Oct 2026
Supporting excerpt
38807. This chapter shall become operative July 1, 2028.
Supporting excerpt
A remote driver shall be located within the United States and hold a driver’s license that is valid for operation in California, is of the appropriate class, and includes any required endorsements.
Supporting excerpt
This section shall become operative on July 1, 2028.
Supporting excerpt
summary statistics, broken down by manufacturer, quarterly on its internet website.
Supporting excerpt
On or before July 1, 2028, the department shall adopt guidelines establishing reasonable response time standards for local incident technicians
Supporting excerpt
who responds onsite
This article distinguishes sourced information from interpretation and scenarios. It may contain errors and is not individual investment, legal or tax advice. No return is guaranteed. Corrections: hello@priag.com.
