Work  ›  Logistics

Concept case study

Dispatch ran onone spreadsheet

Concept brief: A fictional freight operator schedules daily runs from a shared workbook that only two people fully understand. The concept explores a portal the whole dispatch team could use.

Relay / Dispatch
Status
Concept case study
Sector
Logistics
Services
Web application, integration
Illustrative timeline
7 weeks
Proposed stack
Next.js, PostgreSQL, REST

The scenario

Everything depended on one file

In the brief, runs, drivers, vehicles and customer bookings live in a single shared workbook. Two people know its quirks. Everyone else phones them.

The scenario assumes recurring file failures, no reliable change history and slow onboarding for new dispatchers.

Design and engineering direction

Model the work, then build around it

The discovery plan begins by observing how dispatch actually schedules a day, then modelling that workflow before selecting screens or database structure.

The concept uses role-based access, a complete change history and an interface that mirrors the team’s run-sheet mental model.

Screens

What the concept demonstrates

Relay / Dispatch
Relay / Dispatch

Success measures

Testable requirements, defined up front

3 d
Target · dispatcher onboarding
100%
Target · changes logged
0
Tolerance · untracked edits
2 min
Target · booking visibility

Concept targets only. They are testable product requirements, not measured client results.

Project enquiries

Tell us what you need to build

Share the goal, budget and timing. We will reply within one business day with the next practical step.