AV-ready SLA evidence is timestamped, signed proof that a site, vehicle, vendor, or task met the agreed operational standard during an autonomous fleet ground-service session. It is the audit and billing record, not the parking spot.
AV-ready SLA evidence is the timestamped, attributable record that proves a ground-service session happened correctly: the right vehicle entered the right site, the agreed task was performed, the service level was met, and an exception (if any) was handled. It is the difference between a fleet operator believing a site staged or charged-queued its vehicles and being able to prove and bill it. For autonomous fleets, where no driver is present to confirm anything, this evidence record is the operational substrate, not a nice-to-have.
What is AV-ready SLA evidence?
AV-ready SLA evidence is a structured, time-stamped record that confirms a ground-service session met its service-level agreement. It answers four questions an autonomous fleet cannot answer from telemetry alone: was this the authorized vehicle, was it at an authorized site, was the agreed task completed to standard, and what proves it. The record combines identity, location, timing, task outcome, and exception handling into one auditable artifact a fleet operator, a site owner, and a billing system can all trust.
| Question | What the evidence record answers | Why a driverless fleet needs it |
|---|---|---|
| Who | Which vehicle (VIN/fleet ID), which fleet, which authorization | No human to confirm the vehicle's identity on site |
| Where | Which authorized site, which stall or zone | Mapping shows where an AV may go, not where it is allowed to be |
| What | The contracted task: stage, store, queue, clean, inspect, recover, reset | The job between trips still has to be proven done |
| Proof | Timestamps, check-in/check-out, photos, signatures, exceptions | Billing and dispute resolution need an artifact, not a claim |
Why ground-service proof matters more once the driver is gone
When a human driver was present, the driver was the evidence layer. They confirmed the vehicle reached the lot, noted damage, signed for a wash, escalated a problem, and stood as the witness to every ground-service event. Remove the driver and that entire informal proof layer disappears, but the obligations do not. The site still has to be the right site, the task still has to be done, and someone still has to be billed.
Autonomous fleets are capital-intensive and contractually dense. Operators like Waymo, Zoox, and fleet-financing players such as Moove run vehicles that represent serious per-unit investment, with autonomy hardware adding around $100,000 and total fifth-generation Waymo vehicle cost estimated near $175,000 (Waymo co-CEO Dmitri Dolgov, via TechCrunch), and they coordinate ground work across many third parties. Without a session-level evidence record, a fleet operator cannot tell a clean handoff from a disputed one, cannot reconcile a vendor invoice against work actually performed, and cannot prove to an insurer or regulator that a vehicle was held, inspected, or recovered correctly. SLA evidence is what makes distributed, off-depot ground operations auditable instead of trust-based.
How AV-ready SLA evidence is captured
XoomPark captures SLA evidence as a session record that opens at check-in and closes at check-out, with structured events in between. A session begins when an authorized vehicle arrives at an authorized site against a valid reservation, and the system writes an identity-and-location record. As the contracted task runs, the workflow captures task-specific evidence: a charging-adjacent queue position, a light-cleaning completion photo, a visual-inspection note, a recovery-hold confirmation. Exceptions (wrong vehicle, occupied stall, blocked task, overstay) are logged as first-class events, not silent failures. At check-out, the session closes with a final state and an SLA result, producing a billable, auditable record.
This is the operational expression of XoomPark's core split: the property defines permission, the fleet validates capability, and XoomPark coordinates reservation, access, workflow, SLA, evidence, and audit. The evidence record is where that coordination becomes provable.
Who needs AV-ready SLA evidence
The buyers who need this are the parties who are accountable when a ground-service session goes wrong and have to settle money against it.
- Fleet operators and fleet-ops partners (the teams running Waymo-style operations, or operators like Transdev and ABM taking on AV ground work) need proof that contracted off-depot sites performed, so they can pay correctly and escalate exceptions.
- eMobility and charging-adjacent operators need queue and dwell evidence to reconcile staging against charging windows without owning the parking layer.
- Fleet financiers and asset owners (Moove-type players, Avis Budget Group-style fleet holders) need an audit trail proving their assets were handled to standard between trips.
- Site and real-estate owners offering AV-ready capacity need evidence that protects them in a dispute: proof they delivered the access and service they contracted to.
- Investors and risk/insurance functions need a defensible audit trail before underwriting distributed AV ground operations at scale.
Example workflow: an overnight-storage session with one exception
A robotaxi finishes its service window and is routed to a XoomPark AV-ready ground node for overnight storage and a light visual inspection.
- Reservation check. The fleet holds a reservation for vehicle FLT-2231 at Site 14, stall block B, for an overnight hold plus visual inspection.
- Check-in. Vehicle arrives. The session opens with a timestamped identity-and-location record: authorized vehicle, authorized site, reservation matched.
- Task execution. Overnight hold runs. A visual inspection captures two photos and a "no new damage" note against the contracted standard.
- Exception. At 04:12 the vehicle is found one stall outside its assigned block. The system logs an access exception, not a silent overstay, and flags it for the site owner.
- Check-out. Vehicle departs at 05:30. The session closes with an SLA result: hold met, inspection met, one access exception resolved.
- Audit/billing record. The closed session becomes one auditable artifact the fleet, the site, and billing all reference. The exception is visible, attributed, and timestamped, so the dispute (if any) is settled on evidence, not memory.
Original research: the anatomy of a ground-service evidence record
Because XoomPark is defining this category rather than reporting an operating history, we built the evidence model from first principles by decomposing what each accountable party must be able to prove in a dispute. We mapped the eight ground-service jobs an autonomous vehicle needs between trips (staging, overnight storage, charging-adjacent queueing, PUDO access, recovery holding, light cleaning, visual inspection, service coordination) against the question "what artifact would let a fleet operator win an audit or a billing dispute about this job?" The result is the field schema below: the minimum a defensible session/SLA record must contain.
| Record field | What it captures | Failure it prevents |
|---|---|---|
| Session ID | Unique handle for one ground-service session | Untraceable events; no anchor for billing |
| Vehicle identity | VIN / fleet ID + the authorization it arrived under | Wrong or unauthorized vehicle on site |
| Site + zone identity | Authorized site, stall/zone, access rule applied | Vehicle in a place it had no permission to be |
| Reservation reference | The booking the session was opened against | Unreserved use; capacity conflicts |
| Check-in timestamp | Authoritative session start | Disputed arrival time; overstay ambiguity |
| Task + standard | Contracted job and the SLA it must meet | "Done" with no definition of done |
| Task evidence | Photos, sensor notes, completion confirmation | Unprovable work; vendor invoice disputes |
| Exception events | Wrong vehicle, blocked task, overstay, recovery flag | Silent failures that surface only at invoice time |
| Check-out timestamp + state | Authoritative session close and final condition | Open-ended liability; no clean handoff |
| SLA result | Met / partial / missed, per task | No measurable service level to enforce |
| Attribution / signature | Who or what system attests to each event | Unaccountable, repudiable records |
Two structural points fall out of this decomposition. First, a record missing any one of these fields is not a weaker record, it is a non-defensible one: drop attribution and the whole artifact becomes repudiable; drop the task standard and "met" is meaningless. Second, the evidence chain has four record types that must reconcile to each other: a site record (permission), a reservation record (intent), a session record (what happened), and a billing/audit record (what is owed). When all four reconcile, you have AV-ready SLA evidence. When they diverge, you have an exception, and the exception is itself evidence. Industry framing for why this matters: depot-grounded operations can lean on a fixed, staffed, camera-covered facility, where technicians charge, clean, and inspect vehicles on site (Waymo; understandingai.org, 2025), but distributed off-depot capacity has no such default witness, which is exactly the gap a structured session record closes.
What XoomPark does and does not do for SLA evidence
| XoomPark provides | XoomPark does not provide |
|---|---|
| Session records (check-in to check-out) | The autonomy stack or the drive itself |
| SLA tracking and SLA results per task | HD maps or localization |
| Evidence capture and the audit trail | Vehicle maintenance or repair work |
| Reservation, access, and exception records | AV safety certification |
| Billing/audit records that reconcile the chain | Charger ownership or an EV charging network |
| Coordination across distributed private sites | Replacing the fleet operator's own ops team |
XoomPark is the ground-services layer that records and proves the session. It does not perform the autonomy, the charging, or the maintenance, and it is not a consumer parking app.
Not for you (when SLA evidence is the wrong purchase)
If you run a single fixed depot, all your ground work happens inside one staffed facility you control, and you never stage, store, queue, or recover vehicles off-site, you do not need a distributed SLA-evidence layer yet. Your cameras, your badge logs, and your on-site staff already function as your evidence layer. XoomPark earns its place the moment ground operations go distributed across private sites you do not own and cannot directly witness. If you are pre-revenue on AV operations entirely, this is a roadmap concept, not a today purchase.
Frequently asked questions
What is AV-ready SLA evidence?
It is timestamped, attributable proof that a ground-service session met its service-level agreement: the right vehicle, at the right site, performing the contracted task to standard, with exceptions logged. It is the auditable record a fleet operator can bill and dispute against, not the physical space itself.
How is SLA evidence different from a parking record?
A parking record proves a vehicle occupied a spot. SLA evidence proves a service was performed to a standard during a session, with identity, task outcome, exceptions, and attribution. Parking is a subset of the data; the SLA record is the auditable artifact that ties permission, reservation, session, and billing together.
Does AV-ready SLA evidence certify vehicle safety?
No. XoomPark records that a contracted ground-service task was performed and met its SLA. It does not certify autonomous-driving safety, inspect roadworthiness, or replace the fleet operator's or regulator's safety processes. The evidence is operational proof of a session, not a safety attestation.
Who is accountable for the evidence record?
Each event in the session carries attribution, so the site owner, the fleet operator, and any service vendor are each accountable for the parts they touch. XoomPark coordinates and stores the record; it does not assume the fleet operator's operational liability.
Related pages
Explore the pilot
Explore the AV-Ready Staging Evidence Pilot to see how XoomPark turns a ground-service session into a defensible, billable evidence record.