Use case

Vehicle collection and delivery, on one record.

Post the movement, connect with a transporter, and keep collection, transit and handover in the same place.

The problem

Collection and delivery fails when the request, the status and the proof live in different channels. Coordinators end up reconstructing the job from messages instead of reading it.

How VMove runs the movement

A dealer posts collection and delivery details as a vehicle movement. Transporters quote or accept. Assigned drivers collect and deliver against that job, with photographs for proof of collection and proof of delivery.

This is the core VMove workflow. Auction collections, stock transfers and customer deliveries are the same underlying job with different locations and receivers.

Process

01
Specify the movement
From, to, vehicles, dates, method and access notes.
02
Award the work
Transporters quote. The dealer chooses who completes it.
03
Collect
Proof of collection records condition before the vehicle moves.
04
Deliver
Proof of delivery closes the handover at the destination.

Why this belongs on a platform

One brief

Stop rewriting collection details for every operator you call.

One status

Collected, in transit and delivered sit on the job.

One evidence trail

POC and POD are operations documents, not chat attachments.

UK coverage in the product

Post movements across England, Scotland, Wales and Northern Ireland. Fulfilment depends on who quotes.

Common questions

What is vehicle collection and delivery on VMove?

A posted movement with a pickup location, a drop-off location, vehicle details and a transporter who completes the job with proof of collection and delivery.

Can I choose driven or transported?

Yes. Jobs can request driven, transported, or no preference.

Who completes the collection?

A registered transporter. They may assign a professional driver from their team to each vehicle.

Get Started