The national proposition

DCS delivers the operation.
DRIVR opens up the capacity.
InPost gets visibility and control.

DRIVR is the owner-driver access and engagement platform within the DCS operating model. It connects drivers’ genuinely available days with delivery opportunities, supported by DCS onboarding, allocation, operational coordination and payment workflows.

For InPost, the proposition combines planned DCS capacity with a wider pool of owner-drivers who can take additional days, recurring commitments or peak work. DCS retains operational and commercial responsibility; DRIVR is the brand and platform through which that flexible pool is reached.

“We can help InPost access experienced owner-drivers who do not need to leave their existing work to support you—and give your depots a clearer view of what they need, what is booked and what has been delivered.”

Why it matters to InPost

These are operating benefits and intended outcomes, not quantified savings, guaranteed fill rates or a promise of immediate nationwide supply.

Why drivers choose it

The owner-driver parcel rate is adjusted to the applicable InPost ring, with the low-margin approach carried throughout. The previously discussed £2.25 figure is an illustrative rate, not a universal ring tariff. Weekly payment is two weeks in hand; eligibility, units, VAT treatment and accepted terms govern each engagement. Availability or interest is not a confirmed booking.

Candidate to Client introduction

Review the person.
Check the evidence.
Control access to the pack.

Before mobilisation, DCS can introduce selected drivers through a recipient-specific client compliance pack. The client sees the shared evidence, its review status and relevant expiry dates, with PIN access and a time-limited link.

What the compliance overview covers

The shared evidence may include identity, right-to-work, driving-licence, insurance and vehicle documents, according to the driver’s pathway and applicable requirements. An owner-driver and a renter do not have identical document requirements. The overview shows review dates, expiry dates or indefinite status where recorded, and saved MOT / tax check information where available.

The client reviews the evidence as at the displayed check time. A driver being active or signed off is not a substitute for inspecting the applicable evidence, and a missing or expired item must remain visible rather than being counted as approved.

Screengrab evidence · the client journey

These are browser screengrabs of the application’s client-introduction page template, rendered with an isolated synthetic candidate and demo responses. They show the PIN, compliance and expired states without publishing anyone’s real documents. They are not screenshots of a real candidate pack or proof of production security enforcement.

The demonstration supplies no real compliance files. Its controls are browser-only examples; live document access and expiry require the application’s server-side checks.

Try the synthetic introduction screens ↗ · Demo PIN: 2468 (demonstration only).

From depot demand to delivered work

Demand, applications, confirmed bookings, completed work, client validation and financial acceptance are separate stages. A change in one does not silently prove the others.

The client workspace

One place to plan.
One place to see the work.
One place to review the evidence.

The indexed walkthrough below describes the client experience from the reviewed portal source. It is a presentation guide, with a small offline demonstration—not a production login or a replica connected to live systems.

Roster & demand: a guided demonstration

The portal separates the client’s editable forecast from confirmed Roster bookings. Its planning view displays two weeks at a time; future forecast entry and driver availability have separate permitted windows. Missing requirements remain “not set”.

Allocated drivers & profiles

Open a driver name from the allocation table to inspect the available client-facing profile. The table associates the driver with the depot, allocation status, start wave and route reference where recorded.

Profile access does not mean unrestricted access to identity documents, internal assessments or private staff notes. Driver selfies and richer profile presentation depend on the released view and available data; this guide does not promise every row contains them.

Performance & operational visibility

The reviewed client workflow combines operational figures for the selected end date with submitted work and validation history for the selected period. Today, last 7 days, last 14 days and previous/next-period controls support review. Individual queries are bounded to periods of up to 14 days.

EOD evidence, queries & validation

The review queue brings overdue work, outstanding evidence and queries into view by depot. The client selects a site to inspect individual EOD lines and the available screenshots before recording an authorised decision.

Client work access and validation are separately enabled. Staff review can remain read-only. Client validation does not unlock payroll, establish payment or override the agreed financial reconciliation.

Parcel pricing by ring.
Low margin throughout.

The parcel rate follows the ring.
The low-margin model stays consistent.

Parcel pricing is structured around the applicable InPost ring. The client parcel rate is agreed for that ring, and the corresponding DRIVR owner-driver rate is adjusted with it. A deliberately low retained margin is carried throughout the ring structure, keeping the driver proposition attractive across the work being offered.

Agree ring coverage, rates, qualifying parcel units, service scope, VAT basis, effective dates and reconciliation before mobilisation. This guide does not assign unconfirmed ring boundaries or publish a new ring tariff.

Where configured, the client view can surface the applicable charging basis and supporting operational measures. Chargeable parcels, stops and days remain distinct. DCS retains the existing client invoicing/self-billing and driver-payment ownership.

Commercial presentation only. This guide does not amend rate cards, accepted bookings or financial records.

A controlled national rollout

A national framework.
Mobilised depot by depot.

Agree a common operating model with InPost, then prioritise the depots and dates where additional supply creates the greatest value. Build from established relationships and evidenced local reach.

Capability boundaries

This guide is based on the reviewed portal source and recorded release evidence available on 5 November 2026. It does not certify a signed-in production journey. Access and enabled features vary by reviewed account and site.

The discussion with InPost

Where would additional
capacity make the
biggest difference?

“Our proposal is to bring DCS operational accountability and DRIVR’s flexible driver proposition together under one national framework—then prove and expand it locally.”

Gareth Hulme · DCS Group / DRIVR
gareth.hulme@dcsgroup.uk.com
www.getdrivr.co.uk