AV ground services are the physical between-trip jobs an autonomous fleet still needs once the driver is gone: staging, storage, charging-adjacent queueing, recovery holding, cleaning, inspection, and service coordination, plus the records that prove each happened.
AV ground services are the between-trip physical operations a robotaxi fleet still needs after the driver is removed: staging vehicles near demand, storing them overnight, queuing them for charging, holding disabled units for recovery, cleaning and inspecting them, and coordinating who does the work. Removing the driver removes the person who used to absorb these tasks invisibly. The vehicle still has to be put somewhere, prepared, and proven ready. AV ground services is the category name for that work, and for the reservation, access, workflow, and evidence records that make it auditable across distributed private sites.
Key takeaways before you scroll
| Question | Short answer |
|---|---|
| What are AV ground services? | The between-trip physical jobs an AV still needs: stage, store, charge-queue, recover, clean, inspect, coordinate, prove. |
| Why now? | The driver used to absorb these tasks. Driverless fleets have no one in the seat to do them. |
| Is this parking? | No. Parking ends when a car stops. Ground services is the work and the proof while it sits. |
| Is this charging? | No. XoomPark coordinates queueing and access near chargers; it does not own chargers or run a network. |
| What does XoomPark do? | Coordinates reservation, access, workflow, SLA, evidence, and audit across private-site capacity. |
What "ground services" means once the driver is gone
Ground services is the set of physical, non-driving tasks a vehicle needs between revenue trips. With a human driver, these were never a separate line item: the driver parked the car, found a spot to wait, drove to a charger or gas station, wiped down the seats, noticed the warning light, and pulled over when something broke. The labor was bundled into the seat.
A driverless vehicle cannot do any of that on its own. It can navigate, but it cannot decide where it is permitted to wait, negotiate access to a private lot, judge whether a bay is free, or prove to an operator that it was cleaned and inspected. Ground services is the name for that unbundled work, surfaced as an explicit operational category instead of an invisible assumption.
XoomPark is the AV ground-services layer for autonomous fleets. It turns private sites into AV-ready ground-service nodes for staging, overnight storage, charging-adjacent queueing, PUDO access, recovery holding, light cleaning, visual inspection, service coordination, and SLA evidence.
Why robotaxi fleets need this
Robotaxi fleets need ground services because depots alone cannot cover a city. A central depot solves storage and heavy maintenance, but it does not solve the dozens of small location problems a vehicle hits every hour: where to idle between fares without blocking a curb, where to wait for a charger when the depot is across town, where to be held after a fault until a recovery crew arrives. The further a vehicle is from its depot, the more these gaps cost in deadhead miles and downtime.
Commercial robotaxi operations are now running real volume. Waymo crossed roughly 450,000-500,000 paid autonomous rides per week across its operating markets by late 2025, up from about 250,000 per week in April 2025 (CNBC, Dec 2025; Waymo disclosures). At that scale, every minute a vehicle spends deadheading to a distant depot, or sitting idle because it has nowhere permitted to wait, is a direct hit to utilization. Distributed ground-service capacity shortens those trips.
The driver disappears, but the ground work does not. Fleets need trusted places to stage, store, charge, queue, clean, inspect, recover, and reset between trips, distributed across the service area rather than concentrated at one site.
How the ground-services layer works
XoomPark works by coordinating six things across a network of private sites: reservation, access, workflow, SLA, evidence, and audit. It does not own the sites, the chargers, or the labor. It is the coordination and record layer that sits between a fleet and the physical capacity it borrows.
The model rests on a permission-versus-capability distinction. HD mapping tells an AV where it may be able to drive. It does not tell a fleet whether a given private lot will allow that vehicle in tonight, what it is allowed to do there, whether a bay is actually free, what rules apply, or what evidence proves the session happened correctly.
The property defines permission. The fleet validates capability. XoomPark coordinates reservation, access, workflow, SLA, evidence, and audit. A site owner sets the rules of their lot. The fleet confirms its vehicle can physically operate there. XoomPark holds the reservation, governs access, runs the check-in/check-out workflow, tracks the SLA, captures the evidence, and produces the billing and audit record.
Who needs AV ground services
The audience for AV ground services is anyone responsible for keeping driverless vehicles available, or anyone who owns space those vehicles could use.
| Who | What they get from a ground-services layer |
|---|---|
| AV fleet operators | Distributed places to stage, queue, and recover without building depots everywhere. |
| Fleet-ops partners (e.g., Moove, ABM, Transdev type roles) | A workflow and evidence system for the off-depot work they are contracted to deliver. |
| eMobility teams | Charging-adjacent queueing and access coordination near existing charging assets. |
| Parking operators and real-estate owners | A way to turn underused private sites into revenue-generating AV-ready ground nodes. |
| Investors | A defensible coordination layer in a category that scales with every fleet, not one fleet. |
Example workflow: one vehicle, one between-trip session
A robotaxi finishes a fare three miles from its depot and needs to wait near demand for the evening peak. Instead of deadheading back, the fleet's system requests a staging session at a nearby qualified node.
- Reserve. The fleet requests a staging slot at an AV-ready node. XoomPark confirms availability and holds the reservation record.
- Access. The vehicle arrives. XoomPark applies the private-site access rules the property defined and grants entry.
- Workflow. Check-in is logged. The session runs: the vehicle stages, and if the node offers it, gets a light clean and visual inspection.
- Exception handling. If the vehicle faults, the session converts to recovery holding and the fleet is notified to dispatch a crew.
- Evidence and audit. Check-out is logged with timestamps and evidence. XoomPark produces the SLA and billing record proving the session happened correctly.
The vehicle never went back to the depot. The fleet got a between-trip reset, the site owner got paid for capacity, and both sides have an auditable record.
What XoomPark does and does not do
| XoomPark IS | XoomPark is NOT |
|---|---|
| Site discovery and qualification | A consumer parking app |
| Private-site access rules and reservation records | A generic parking marketplace |
| Session records and check-in/check-out workflow | A charger owner or EV charging network |
| Exception handling and SLA tracking | A maintenance provider or car-wash service |
| Evidence capture and billing/audit records | An autonomy or HD-mapping company |
| The coordination layer across distributed capacity | A dispatch system or a replacement for fleet operators |
XoomPark does not replace Moove, Avis Budget Group, Transdev, ABM, or a Waymo operations team. It gives the people doing that work a shared system for reservation, access, workflow, SLA, evidence, and audit.
Original research: the eight ground-service jobs a robotaxi needs between trips
We mapped the distinct ground-service jobs a robotaxi has to complete between revenue trips, because the category is usually discussed as one undifferentiated lump ("parking" or "charging"). Decomposing it shows why a single depot cannot cover all eight, and where distributed nodes earn their place. This decomposition is XoomPark's framework, offered as an analytical model rather than an operating result.
| # | Ground-service job | What it solves | Why a depot alone falls short |
|---|---|---|---|
| 1 | Staging | Idle near demand between fares | Demand is distributed; one depot is not |
| 2 | Overnight storage | Park the fleet off-shift safely | Capacity caps; long deadhead from edge of service area |
| 3 | Charging-adjacent queueing | Wait for a charger without blocking it | Chargers are sited where land allows, not where depots are |
| 4 | PUDO access | Permitted pick-up/drop-off on private ground | Curb access is contested and often off-limits |
| 5 | Recovery holding | Hold a faulted vehicle until a crew arrives | Incidents happen far from the depot, on someone's lot |
| 6 | Light cleaning | Reset cabin condition between riders | No driver to wipe down; needs a place and a record |
| 7 | Visual inspection | Catch damage and readiness issues | No driver to notice; needs structured evidence |
| 8 | Service coordination | Schedule who does the above, where | Multiple parties, multiple sites, no shared system |
Two of these jobs are time-sensitive in ways depots make worse. Charging-adjacent queueing matters because charging dwell is not instant: a fast charge to usable range still takes a meaningful block of time, typically about 20-45 minutes to reach 80% on a DC fast charger for current robotaxi-class EVs (US DOT EV charging toolkit; J.D. Power), during which the vehicle must wait somewhere it is permitted to sit. Recovery holding matters because driverless incidents need a human-staffed place to hold a vehicle until a crew arrives. The further both are from a depot, the more they cost.
When XoomPark is not for you
If you run a single fixed depot, operate only inside it, and never need a vehicle to wait, charge, recover, or reset anywhere off-site, you do not need a distributed node network yet. A self-contained depot operation already has its own ground.
XoomPark also is not for you if you want someone to own the chargers, perform the maintenance, certify AV safety, or dispatch your fleet. It coordinates and records the ground-service session. It does not do the autonomy, the wrenching, or the power.
Frequently asked questions
What are AV ground services?
AV ground services are the physical between-trip jobs an autonomous fleet still needs after the driver is removed: staging, overnight storage, charging-adjacent queueing, recovery holding, light cleaning, visual inspection, and service coordination. They include the reservation, access, workflow, and evidence records that prove each job happened.
Are AV ground services the same as parking?
No. Parking ends the moment a car stops moving. Ground services covers the work performed while the vehicle sits and the proof that it happened: access rules, cleaning, inspection, recovery, and an auditable session record. A parking space is one input; ground services is the coordinated job.
Are AV ground services the same as charging?
No. XoomPark coordinates charging-adjacent queueing and access near charging assets, but it is not a charger owner or an EV charging network. It handles where a vehicle is permitted to wait for a charger and proves the session, while the energy and hardware stay with the charging provider.
Why are depots not enough for robotaxi fleets?
A depot solves centralized storage and heavy maintenance, but it cannot be everywhere a vehicle needs to wait, charge, recover, or reset. Distributed demand creates distributed ground-service needs, and deadheading back to one depot wastes utilization. Distributed nodes shorten those trips.
Related pages
Pressure-test a pilot market
Bring a city and a fleet profile, and we will pressure-test whether a distributed ground-service node network fits your operation: where vehicles deadhead, where they wait, and where private-site capacity could shorten the gaps. Pressure-test a pilot market with XoomPark.