Keep the load as the organising record
Customer requests, quotation versions, assignment and delivery evidence relate to the same shipment. Dispatch and accounts can follow that context as the work progresses.
Freight & fleet operations
Project overviewRunwise: Every run, from booking to handoff.
RunwiseProduct videos
Runwise connects booking, dispatch, live tracking and invoicing for hotshot and expedited carriers. Shared shipment records link office teams, drivers and yard operations, carrying trip updates and delivery evidence through to billing and driver pay so teams can follow each run from quote to completion.
The freight operations challenge
A shipment moves between customers, office teams and drivers. Those handoffs need a shared record and clear responsibility.
Who Runwise connects
Office
Plan the request and assignment.
Driver
Update the trip and capture evidence.
Customer
Follow the shipment context available to their role.
What Runwise brings together
Booking and dispatch
Connect the request, quotation and assignment.
Progress and evidence
Keep trip updates and supporting documents with the shipment.
Commercial handoff
Carry completion records into the next paperwork and finance step.
Follow the journey
01
Request
Capture the shipment and its requirements.
02
Assign
Plan the work and responsible driver.
03
Move
Record pickup, progress and delivery evidence.
04
Review
Check the completed record before the commercial handoff.
A separate development initiative explores supervised AI assistance for logistics context and exceptions. It is distinct from the operational workflow described here. Logistics Operations AI · In development
Shipment journey
RW-1042Warehouse 3 → Retail partnerViewing as Driver
PickupRecorded · 09:20
DeliveryRecorded · 10:42
Delivery documentMissing
Explore the workflow
A connected operational journey for shipment planning, dispatch, delivery evidence and commercial follow-through.
Product engineering story
One shipment, several responsibilitiesRelated services
Inside the build
The decisions behind the experience.
Runwise supports hotshot and expedited carriers across the dispatch desk, road, yard, accounts team and customer experience. Booking information, vehicle availability, trip events and delivery paperwork need to remain connected. The design challenge was to make each participant’s next action clear while preserving a shared history of the load.
The design brief
Preserve shipment continuity while preventing conflicting resource commitments.
Freight moves through many hands. The shipment record should stay continuous from the first quote to the final invoice.
The constraint
Availability shown to a dispatcher is not sufficient protection when assignments can overlap. Resource commitments need enforcement in the data model as well as a clear interface.
The tradeoff
Reservations use conservative hourly slots and a unique resource-hour constraint. This can reject a tightly packed pairing, but prevents genuine overlaps across supported database engines.
Product scope
4
AI advisory desks
Financial, Fleet, Customer and Executive
3
Companion mobile apps
Customer, driver and operations
1
Shipment record
Request, dispatch, delivery and finance
Make the driver’s next action explicit
The driver app uses a trip ladder from travelling to pickup through handover and completion. Photos, receiver details, signatures and location evidence attach to the job.
Ground assistance in business data
The AI desks use bounded business queries and present figures with their answers. They analyse and advise; dispatch decisions remain in the operational workflow.
A workflow in practice
From the trigger to the handoff.
A representative scenario through the implemented workflow.
- 01 · The situation
A dispatcher considers a driver and vehicle for a shipment window.
- 02 · The product response
The reservation service checks occupied resource-hour slots; conflicting commitments cannot occupy the same slot.
- 03 · The next step
The accepted assignment remains linked to the shipment as the driver records trip activity and delivery evidence.
How it is built
The structure behind the workflow.
Carrier & customer experiences
A React web application supports operational and customer views. Three Flutter apps serve customers, drivers and operations staff.
Operational services
Django services cover shipments, fleet, tracking, finance, documents and coordination, with permissions applied across the platform.
Advisory layer
Four AI desks use bounded data queries. Their role is to explain the business and surface relevant information rather than autonomously dispatch trucks.
Actual product screens
The product, up close.
Booking and assignment states bring the next operational action into view.
Original product interface captures. Screens use demonstration data; visible figures are not measured customer results.
System map
Connected by design.
SYSTEM BLUEPRINT / Runwise
Select a component to exploreConnected by design.
01 The experiences
02 The shared foundation
03 What it connects
THE COMPLETE PICTURE
Shared shipment record
React web experiences and Flutter apps connect to a Django API. Tracking, paperwork and finance attach to the shipment workflow.
| The work | Problem addressed | With Runwise |
|---|---|---|
| Quotation | Commercial terms separated from operations | Approved quotes connected to the booking |
| Dispatch | Availability coordinated in separate messages | Driver and vehicle window checks during assignment |
| Delivery paperwork | Evidence gathered after the trip | Photos, signatures and documents attached to the job |
| Business questions | Manual searches across operational records | Advisory agents grounded in permitted business queries |
Delivered capability
Inside Runwise.
Runwise connects the customer request, road activity and financial close-out around the shipment. The result is a platform where each participant contributes to a shared operational history without needing the same interface.
Continuity is the design principle: preserve the identity and history of the load while changing the interface to suit the person handling the next step.
Evidence & evaluation
What this case study establishes.
Resource-reservation service and the Runwise capture inventory linking dispatch, driver, proof-of-delivery and invoice screens.
This is a product engineering case study based on source code, project documentation and recorded screens. It describes implemented capabilities; customer performance gains have not been measured for this case study.
What to measure next
Suggested measures for a deployment evaluation, not reported results.
- Conflicting assignments rejected
- Completed trips awaiting delivery evidence
- Elapsed time from delivery evidence to invoice preparation
Discuss the fit
Branding, roles, integrations and support are discussed for the carrier’s operating model. Initial adaptation should be scoped to an isolated carrier deployment.