Platform concept

A decision and memory layer — not another driver application.

Deliverd is designed to sit beside the tools an operation already uses. Drivers should not be asked to learn another application, and platforms should not be asked to hand over their workflow.

See it in the demonstration Pilot and research enquiries

Concept

Before the job

An authorised platform requests a delivery-readiness decision and any available last-metre knowledge.

Concept

During the job

The driver receives only the authorised information necessary to complete that delivery.

Concept

After the job

The outcome confirms, corrects or disputes the existing record.

Conceptual interfaces

Platform job-card component

Prototype

Manchester → Castle Farm Workshops

Today · 10:30–11:00 · Medium van

Last-metre knowledge available · 1 conflict

Driver mobile component

Prototype

Second gate after the stone wall

Blue workshop door beside Unit 4 · photograph available

Previously confirmed — not guaranteed current.

Recipient approval link

Prototype

Six items, each approved for future deliveries, approved until a date, restricted to one delivery, rejected or corrected.

Change-history record

Prototype

Who supplied each item, who confirmed it, when, its permission state, whether it is disputed, and when it expires.

Conceptual API

Illustrative only — no real address, API key or live endpoint is shown. Not currently a production API.

Dispatch decision
Principal issue
Required checks
Vehicle suitability
Crew requirement
Handling equipment
Memory available
Evidence state
Unresolved conflicts
Recipient confirmation required

Non-functional exampleNot live

GET /v1/locations/{authorised-location-id}/delivery-memory

{
  "location_id": "authorised-location-reference",
  "access_point": {
    "description": "Second gate after the stone wall",
    "coordinates": "ordinary latitude and longitude"
  },
  "handover_point": "Blue workshop door beside Unit 4",
  "vehicle_constraints": {
    "medium_van": "access confirmed",
    "larger_vehicle": "restricted turning space",
    "state": "unresolved_conflict"
  },
  "evidence": [
    { "type": "photograph", "subject": "entrance", "supplied_by": "recipient" }
  ],
  "provenance": [
    { "date": "12 July", "actor": "recipient", "action": "supplied" },
    { "date": "18 July", "actor": "driver", "action": "confirmed" }
  ],
  "last_confirmed_at": "18 days ago",
  "expires_at": "04 February",
  "permission_scope": "authorised_future_deliveries",
  "unresolved_conflicts": ["vehicle_turning_space"]
}

One product, four layers

Deliverd Check

Can I accept and complete the job?

Mission feasibility

Distance, energy, operational time, charging and reserve.

ChargeWise CX evidence

Will the required charging stop actually work for this commercial vehicle?

Deliverd Memory

What was verified at the collection, charging stop and destination?

Deliverd decides whether the job is realistically achievable — not merely whether the route exists.

Mission feasibility outputs

Mission feasibility
Direct drive time
Collection operational time
Charging required
Preferred charging stop
Alternative charging stop
Charger fit state
Charger status state
Occupancy evidence state
Charging minutes required
Planned break minutes
Overlapping minutes
Effective charging delay
Realistic arrival window
Disrupted arrival window
Expected delivery charge
Expected return charge
Required reserve
Principal uncertainty
Required action

Operational stop evidence

Where a mission may require charging, Deliverd assesses whether the stop is usable by the described vehicle rather than whether a charger exists. ChargeWise CX is a specialist evidence source inside Deliverd — not a separate product or consumer charging application.

Charging stop decision
Bay length fit
Cable reach state
Current status source

Charging evidence and suitability decisions →

The prospective moat

The software interface can be reproduced. The difficult asset is an authorised history of what was expected, who confirmed it, what happened during the delivery and whether the information remained useful.

Boundaries, compliance and sources+

Deliverd does not calculate statutory driving-hours compliance. A user-entered planned break is a planning input only, never a compliance determination.

Delivery Memory would store ordinary geographic coordinates as the underlying location. Human-readable systems such as three-word references could be displayed optionally where appropriately licensed and supported. No partnership or endorsement is implied.

Deliverd does not yet claim a proprietary location dataset. The proposed pilot exists to determine whether a governed evidence network can be created responsibly and whether it produces measurable operational value.

Mapping and fleet platform teams: platform integration concept · commercial model