How it works
From published request to released payout
Eight phases, each with a responsible party and a completion requirement. Nothing advances on trust alone.
- 01
Onboarding
DriveVia review teamFleets, provider companies and drivers submit an application with documents. A reviewer approves or returns it with reasons. No work is offered before approval.
- 02
Request
Fleet dispatcherThe fleet records the vehicle, both locations, the date window and the amount it will pay, then publishes the request to the network.
- 03
Offer and acceptance
Provider, then fleetApproved providers respond. The fleet accepts one. Acceptance locks the price and creates a mission with a named responsible party on each side.
- 04
Pickup
Assigned driverThe driver confirms the vehicle, captures the required photo set, records odometer and fuel or charge level, and notes any pre-existing damage.
- 05
Transit
Assigned driverStatus updates are posted to the mission. Any incident is reported immediately and attached to the record.
- 06
Delivery
Assigned driverThe same evidence set is captured at the destination. The mission cannot be closed until it is complete.
- 07
Settlement
PlatformDelivery triggers settlement against the locked price. The provider amount and the DriveVia fee post to a balanced ledger.
- 08
Payout release
DriveVia operationsAfter the standard post-delivery verification hold, the payout is released to the provider's connected account.
What stops a mission from advancing
- Missing or incomplete photo evidence at pickup or delivery.
- A provider whose compliance records have lapsed.
- An unfunded movement β funding is required before work is released.
- An open incident that has not been triaged.
Questions about a specific step?
Read trust and safety