Research Note: Remote Assistance, Remote Driving, and Fleet Support

Research Note: Remote Assistance, Remote Driving, and Fleet Support

Question

E073 used teleoperation as a catch-all. The public explainer needs a role and authority model that shows who observes, who communicates, who advises, who authorizes, and who can directly control the vehicle.

What current federal sources establish

At its 2026 National AV Safety Forum, NHTSA described remote interaction as a spectrum. It can include confirming a proposed action, providing guidance or permission to deviate from a programmed norm, or fully remote manual driving. NHTSA identified latency, cybersecurity, communications, and remote-operator situation awareness as different safety concerns across that spectrum.

NHTSA's forum remarks add passive monitoring, passenger and road-user communication, binary contextual confirmation, directional guidance, and remote manual controls. These are discussion inputs for emerging federal guidance, not a final mandatory taxonomy.

A 2026 US Department of Transportation Volpe Center review distinguishes remote driving, where the human is responsible for the dynamic driving task, from remote assistance, where the ADS maintains vehicle control and object-and-event response while the human supplies decision support or path planning.

An earlier FHWA-sponsored dispatch study shows that monitoring, passenger service, incident coordination, maintenance dispatch, and workload management are fleet functions even when no one remotely drives a vehicle.

The role and authority model

The roles can be described through four questions.

A company may use more than one role. One person may handle passenger support while another function evaluates road context. A direct remote driver may exist only for a defined recovery mode. The system design, not the job title, determines the authority.

What the Tesla record does not establish

Tesla's current Robotaxi support page says riders can request support and ask the vehicle to pull over or stop. It does not disclose whether a remote person observes every trip, how often support is requested, whether guidance changes a planned path, whether anyone can directly steer or brake, how communications failures are handled, or how many vehicles one person may support.

The E073 transcript's statement that the Austin service was continuously tele-operated is therefore not cleared. The updated story can say Dalton made that assumption and explain why the evidence requires a narrower statement.

Editorial use

The public explainer should avoid treating any human involvement as proof that an ADS is not performing the driving task. It should also avoid treating remote assistance as a harmless call-center function. Authority, latency, staffing, cybersecurity, communications loss, training, logs, escalation, and minimal-risk behavior all matter.