Autonomy levels from teleoperation to supervised operation
Autonomy levels for unmanned platforms are a statement about driving, not about judgement. Reading it as a statement about judgement is the single most common error in coverage of these systems.
The scale for unmanned platforms, and the problem with quoting it
Autonomy levels describe how much of the control loop a machine closes on its own. Several scales exist, they were written for different purposes, and they divide the same continuum at different points. The consequence is practical rather than academic: a level quoted without naming its scale tells a reader nothing, and two systems described at the same level may differ more than two systems described at different ones.
Underneath the scales the useful question is narrower and always the same. What does the platform do when the link drops, when the ground turns out to be softer than expected, and when something is detected? The first two are engineering. The third is not an autonomy question at all, and treating it as one is where public accounts go wrong.
Teleoperation: a person is driving
At the low end an operator drives the unmanned platform continuously from a console, seeing what its cameras see. It is simple, it is predictable, and responsibility is unambiguous — somebody is holding the controls. Its costs are equally clear. It occupies one person per platform, so it does not scale. It needs a continuous, low-latency link, so terrain that breaks radio breaks the mission. And it is tiring in a way that degrades quietly: an operator four hours into a shift drives worse and does not know it.
Teleoperation remains the fallback mode on almost every platform in the European record, because it is the mode that works when the clever parts do not.
Supervised autonomy: a person is watching
Here the platform handles the driving between points and the operator sets intent — go to this location, hold this corridor, return if the link fails. The link becomes intermittent rather than continuous, which is what makes broken terrain workable, and one person can hold several platforms because they are supervising rather than steering.
The trade is predictability. A supervised platform makes decisions the operator did not watch it make, and when it behaves unexpectedly the reason has to be reconstructed afterwards. That is tolerable for driving. It is the reason the same programmes stop short of extending it to what happens on a detection.
| Mode | Link requirement | Operators per platform | On link loss |
|---|---|---|---|
| Teleoperation | continuous, low latency | 1 : 1 | stops |
| Waypoint following | intermittent | 1 : few | continues to next point |
| Supervised autonomy | intermittent, tolerant | 1 : several | continues or returns, by rule |
The ratios are directional, not measurements: published figures vary by programme, terrain and how much of the maintenance burden was counted. What transfers between programmes is the direction — as the operator moves back, the link requirement falls and the need to explain the platform's behaviour afterwards rises.
Nothing in this table addresses detection. In every documented European programme the decision about what a detection means, and what follows from it, stays with a person.
Why the autonomy level matters outside engineering
Two things change as autonomy levels for unmanned platforms rise and the operator moves back from the controls, and only the first is technical. The system becomes harder to account for: a supervised platform's behaviour has to be reconstructed from logs rather than remembered by the person who caused it, which puts weight on logging that is rarely specified as carefully as the autonomy itself.
The second consequence of higher autonomy levels is legal and sits outside this section. Responsibility for an action on a border attaches to a person, and the further a machine's behaviour is from a person's direct input, the more work the surrounding procedure has to do to keep that attribution intact. That is why the research programmes drew their line where they did, and why the line is examined separately under observing or acting.
Questions about autonomy levels
What do autonomy levels actually describe?
Which parts of the loop a machine closes without a person. In practice that means driving: keeping to a corridor, avoiding obstacles, judging whether ground is passable, returning to a point if the link drops. It does not mean deciding what a detection is or what should follow from it, and the published European scales do not claim that it does.
Are autonomy levels comparable between programmes?
Not reliably. Several scales are in circulation, they divide the same continuum at different points, and a "level 3" in one programme is not a "level 3" in another. When two systems are compared by level without naming the scale, the comparison carries no information. This site names the scale wherever a level is quoted.
Does higher autonomy mean fewer people?
It changes the ratio, not the requirement. One operator may supervise several unmanned platforms rather than driving one, but maintenance, recovery when a platform fails on soft ground, and the person empowered to act on a report all remain. Published ratios vary widely enough that no single figure describes the field.
What is the difference between teleoperation and supervised autonomy?
In teleoperation a person is driving continuously and the link is a hard dependency: lose it and the platform stops. Under supervised autonomy the platform drives itself between points and the person sets intent and watches, so a dropped link degrades the mission instead of ending it. The trade is bandwidth and attention against predictability.