hackathon

What's holding up the next departure?

For the hour before a truck leaves: what's blocking it, and who to call.

A truck parked at the depot. Driver cover needed for the 10:00 departure to Stuttgart.

My role: Sole product designer
Team: 3 people · 24-hour hackathon
Scope: Hackathon: MAN stakeholder interviews and dispatch flow design
After: 13 screens
Recognition: MAN hackathon finalist

A truck can be ready.
Its shift can still be at risk.

Problem

No driver or no handover keeps a healthy truck in the yard.

Workspace

Every departure gets a blocker, an owner and a follow-up time.

Outcome

Hackathon finalist. Not yet tested with dispatchers.

All operational data is fictional.

Munich depot,
09:00.

24 departures. 4 records available. Which one needs a call first?

Dispatch board with four open shifts, their blockers, owners and contact actions

What does dispatch
actually know?

Known

Depot check 08:35
Driver hours
Customer deadline

Still unknown

20 shift records
018 since 07:10
031 release time

Confirmed by a person

Who checked, and when
The driver's answer
Next owner

Follow the 10:00 to Stuttgart.

01Spot the gap02Compare drivers03Ask the driver04Prepare handover05Pass it on

The 10:00 departure still needs a driver.

Dispatch board screen for the shift walkthrough

Sofia clears the driving and rest checks.

Shift workspace screen for the shift walkthrough

Sofia Keller · Rules check Clear. Tachograph download 06:50.

Sofia can accept or decline this shift.

Driver mobile screen for the shift walkthrough

Her acceptance unlocks the handover.

Driver handover screen for the shift walkthrough

The next dispatcher picks up open work.

Team changeover screen for the shift walkthrough

Where the details matter.

Keep the missing records visible.

Four records can't support a fleet-wide percentage.

Fleet uptimeUnavailable4 of 24 records

Keep the last signal and the last check separate.

A 07:10 signal is not a check. The depot check records who and when.

Vehicle evidence form with Call Munich depot, verifier, time and observed status

Let the driver say yes.

Handover unlocks only after she accepts.

Sofia’s shift offer with accept, decline and call dispatch options

Show why a driver is excluded.

52 h + 5 h 10 min > 56 h weekly limit. The rule is shown; the data can be corrected.

Expanded driver rules table with exclusion reasons, tachograph sources and correction links

How I checked
the handoffs.

I prototyped in MagicPath and cross-checked the screens with Claude.

Earlier: The board said "agreement pending". The app already said "Your shift".
Revised: Leon gets an offer first. Accepting unlocks handover.

What I'd test next.

Can 3–5 dispatchers find the first call to make?
Time to confirmed cover.
An on-time baseline before comparing results.