SOP Library
Approved procedures for Remote-On, 12V, tires, charging, smoke tests and escalation have not been supplied.
Approved document missingField proof ranges are demo rules. No procedure is represented as approved.
Fleet Control
⌘K
R2 · DemoSample snapshot
Live
Vehicles 0 attention
Fleet states Status, not bookability
100%
Las Vegas fleet map
Sample vehicle positions0 visibleSample · not live
!P0 / P1!Other attentionDashed edge: stale locationBlue outline: selected
Overview
What needs us now priority · impact · owner · next action · clear condition
| Priority | Type | Resource | What happened | Why now | Owner | Next action | Clear when | Age | State |
|---|
Supporting context Patterns, handoff and customer impact
Patterns
Shift handoff
Customer recovery
Nothing important should reset when the shift changes.
Open work stays attached to the vehicle, customer, RD or Field mission until verified and resolved.
Carryover requiring action priority · owner · current state · next action · clear condition
| Priority | Resource | What is open | Owner | State | Next action | Clear when | Age |
|---|
Customer updates due
Field evidence & verification
RD capacity watch
Can we serve more trips with the fleet, RDs and Field capacity we already pay for?Make avoidable waiting and downtime visible before adding more complexity or headcount.
Bookable fleet+RD utilization+Verified Field work→Lower ATA→More trips
Where capacity is leaking turn operational friction into measurable work
Customer experience symptoms the customer actually feels
Scale readiness
Can we serve more trips with the fleet and people we already pay for?
Mission Control should make the answer visible: usable fleet, RD capacity, Field completion, queue aging and customer recovery.
Utilization→Lower ATA→More trips→Revenue
Estimated revenue impactConnect Finance / Pricing modelDo not guess the dollars. Use the real economics when available.
Verified work
RD Overview
PM Shift · 09 Sep 2026Las Vegas · sample snapshot
!1 Remote Driver calling for help · 1 job stuck
Included job records · sample snapshot
0Queue
0Pending
0In progress
—Completed
Remote Drivers
0On shift
0Idle / available
0Busy
0On break
1Need help
Telestation inventory 36 stations · not a physical floor plan
Warnings
Roster (0)
Queue requiring attention
Session & station health
Fleet State Fleet not globally grounded
Full Fleet Ground / Unground
This controls the market-wide operational ground state. Every action requires a reason, confirmation phrase, actor and audit entry. Individual restrictions are preserved when ungrounding.
Recent Control Actions actor · scope · reason · outcome
| Time | Actor | Scope | Action | Reason | Outcome |
|---|
Operational Accountability open work must have ownership
Operational Safeguards
Remote Driving ODDNot connected
Fleet telemetrySample · not live
DispatchNot connected
Map dataStreet map loading · sample positions
Open Waiting Vehicle Jobs
| Vehicle ID | Needs Attention | Battery | LV Battery | Aggregated Ops Status | Current Mission Type | Remote Driver | Is Grounded? | Serviceable | Bookable | Location | Issue | Owner | Resolution | SLA | Last Changed By | Updated | Age |
|---|
Operations / Vehicles / Individual VehicleSlide-out vehicle drawer · keeps your list context
Vehicle
1 / 1
Vehicle identity
Current Vehicle State
Operational Controls reason + actor logged
Issue Resolution & Accountability owner → action → verify → close
Trips · included records—
Redispatches · unavailable—
Field tasks · included records—
Location
Battery & charging
Diagnostics & Attention
Current / Recent Missions
| Mission | Type | Status | RD | Started |
|---|
Trips
| Trip | Pickup | Customer | Duration | Result |
|---|
Remote Driving Sessions
Remote Driving Health
Field Jobs
| Job | Type | Priority | Owner | Status | Age |
|---|
Maintenance State
Recent Maintenance
Diagnostics
Repeat Issues · 30d
Command history Simulation only
Event Timeline
Audit Trail actor · action · reason · source
Time & utilizationOnline, offline and verified driving time
Use behavior + context, not assumptions. Slow acceptance or available-idle time should be reviewed alongside demand, break state, telestation/session health and repeated patterns before coaching or escalation.
Remote Drivers · capacity & accountability
| Name | Online | Status | Telestation | Current Job | Accept p50 | Offers | Expired | Available Idle | Utilization | Context |
|---|
RD exceptions · review the reason, not just the number
Sample Job Queue
Sample Remote Driving Sessions
| Health | Session | Remote Driver | Telestation | Station State | Station Updated | Vehicle | Mission / Job | Mode | Connected | Duration | Latency | Jitter | Packet Loss | Video | Audio | Controls | Handover | Ops Owner |
|---|
Selected Session / Station
Select an active session to inspect the Remote Driver, telestation and vehicle connection.
Telestation Occupancy
| Priority | Job | Type | Vehicle | Area | Wait | Assigned RD | State |
|---|
| Rider name | Status | Booked at (PT) | Vehicle | Pickup type | Delivery RD | Takeback RD | Driving | Stopover | Distance | End time |
|---|
The customer should not have to understand our internal handoffs.
One current status, one recovery owner, one next update.
Customers needing recovery customer-facing state · internal cause · owner · next communication
| Priority | Customer | Trip | Vehicle | Customer sees | Internal cause | Recovery owner | Next update | Recovery action | Contact |
|---|
Customer recovery principles
No silent waitingIf the service is delayed, surface when the next customer update is due.
Customer-safe languageCS sees the operational truth but communicates a clear customer-facing status, not internal jargon.
Keep the existing call workflowLaunch the customer contact tool from the customer context instead of making CS search twice.
Customer
Sample customer
Customer promiseSample records only. Customer services are not connected.Next update · recovery owner · call / message action
Source:
Total spent with Vay$176.61
Total Completed Trip Count3
Trips type share
remote-driven
78%
78%
Trips daily
Trips
| Trip | Date | Vehicle | Pickup | Status | Spend |
|---|
Emails
Email history unavailable. No customer communication service is connected.
Calls
Call history unavailable. No call records or customer service notes are connected.
KYC Funnel
Identity verificationUnknown · not connected
Driver eligibilityUnknown · not connected
Fraud & T&C
Account stateUnknown · not connected
Risk flagsNot reported
Payment History
Payment history unavailable. No payment, refund or payment-method records are connected.
Available Promotions
Promotion eligibility unavailable. No promotion or redemption service is connected.
| Customer | Current Trip | Vehicle | Status | Remote Valet | Customer Impact | Case |
|---|
| Customer | Review / access | Reason / reviewer | Queued · PT |
|---|
| Telestation | Status | Remote Driver | Current Vehicle | Session | Latency | Audio | Controls |
|---|
RESOURCE ALLOCATION
Tenants
Dedicated spaces for demos, testing and internal operations.
Local planning workspaceAssignments are saved in this browser. Live dispatch, account permissions and backend isolation are not connected.
A SEPARATE SPACE, A CLEAR PURPOSE
Build the allocation you need.
Create a tenant by name, then add any combination of vehicles, telestations, drivers and rider email references. An empty tenant is a valid starting point.
01Name the tenant02Assign resources independently03Review and release
TENANT ALLOCATION
| Resource | Reported state | Allocation / restriction |
|---|
Allocation history Local demo operator · timestamps in PT
Sample team data Workforce + Snowflake · not connectedChanges stay in this browser
| Team member | Availability | Current context | Next break / lunch | Actions |
|---|
Team availability
Demo workflow. Durations are planning inputs, not an approved break policy.
Data sources
Fleet and sessionsSample snapshot
Team availabilityInteractive demo
Workforce.comPlanned · not connected
Workforce will provide clock-in, clock-out and recorded break attendance. Connected and busy states come from operational systems. Clocked in does not automatically mean available.
Lunch will appear only when the source identifies it. Missing or delayed information will show Unknown.
SnowflakeNot connected
A live roster needs a backend connection to approved workforce and presence data. Workforce API access and attendance fields still need verification. Neither service is connected.
Demo changes are saved only in this browser. They do not update team schedules or control real vehicles.
Stale data marks availability as unknown and prevents new break or lunch actions.
Operations Wallboard
Las Vegas · Demo day · Sample snapshot
Sample data · Workforce and operational feeds are not connected.
Who's doing what
Current queue
Incoming jobs
Simulated arrivalsOpenFreeMap · sample FSA locations
| Priority | Vehicle | Mission | Area | Customer Impact | Assigned FSA | Age | Status | Completion Gate | Proof |
|---|
Shift Handoff
Review open issues, ownership, next actions, recovery deadlines and evidence.
Vehicle State Guide
View current demo rules
Grounded: a market hold or an independent vehicle hold remains active.
Bookable: Available status, serviceable, score below 70, and no active hold.
Available: a reported status; it does not by itself mean bookable.
Unknown: a source has not reported a measurement. No healthy status is inferred.
These preserve the existing prototype rules; production approval is outstanding.
Escalation Matrix
The approved contact roster, authorities, response thresholds and procedure versions are missing.
Owner review required