Pick, pack & dispatch — Summary

Warehouse & Dispatch · Dispatch Supervisor · Runs daily91% complete

5 waiting for a decision

Biggest wins in this workflow

SimplifyWave-picking by zone (step 2)≈ 125h/yr · ~30m/run
SimplifyOne booking screen for three carriers (step 4)≈ 63h/yr · ~15m/run
SimplifyManifest built from the bookings (step 5)≈ 50h/yr · ~12m/run

Team time per run

7.6h

Counts everyone: 2 steps are done by a group

≈ 1,896 h a year

Planned to free (accepted)

0m per run

≈ 0 hours a year back to the team once done

Still open (recommendations to review)

1.2h per run

0m planned + 1.2h open + 6.4h untouched = 7.6h per run

≈ 304 hours a year if all adopted. Accepted ones sit under Planned to free; nothing here counts more than its step costs

Already automated today

0 of 7 steps

0m of hands-on time is on partly systematised steps — honest baseline, not opportunity

Top friction points

Worst first — how much a step hurts, multiplied by how long it takes. So a long mildly annoying step can outrank a short painful one.

Step	Who does it	Kind of pain	Hurts	Time	Why it hurts
Rank 1, step 4, Book couriers across the three carrier portals	Dispatch Supervisor	—	a lot	20m	Three logins, three interfaces, same data keyed into each

Recommendations

Start here

The biggest wins your team can start without waiting on anyone.

Manifest built from the bookings

Step 5 · needs setting up · ~12m/run

Pick lists allocated and sent on their own

Step 1 · needs setting up · ~8m/run

Tracking numbers sent back automatically

Step 6 · needs setting up · ~8m/run

To review5

🔧 Change how these are done (5)~73m/run

Step 2Simplifyneeds other teams

Wave-picking by zone

~30m per run of the step's 270m team time

How ▾

Three people walk the whole floor for every order. A build groups the day's orders into waves and gives each picker a route through one zone, so the same orders are picked with less walking. The floor layout and the wave times are agreed with the warehouse team first.

Step 4Simplifyneeds other teams

One booking screen for three carriers

~15m per run of the step's 20m

How ▾

The same consignment data is keyed into three courier portals. A build takes the day's manifest once and books all three via their APIs, returning labels together.

Step 5Simplifyneeds setting up

Manifest built from the bookings

~12m per run of the step's 15m

How ▾

Once the couriers are booked in one place, the manifest already exists. A build assembles it per carrier and prints it for the drivers, so the supervisor checks it instead of compiling it.

Step 1Simplifyneeds setting up

Pick lists allocated and sent on their own

~8m per run of the step's 10m

How ▾

The 6am order batch is already in the ERP. A build splits it into pick lists by zone and sends each list to the picker's handheld, so the supervisor stops printing and allocating by hand and only steps in when stock runs short.

Step 6Simplifyneeds setting up

Tracking numbers sent back automatically

~8m per run of the step's 10m

How ▾

The courier labels carry the tracking numbers. A build posts each one to the online store as the label prints, so nobody copies them across at the end of the day.

Accepted0

None

Not now0

None

Manual hand-offs between systems

5 → 6Data moves from Courier portals to Ecommerce platform by hand here.
6 → 7Data moves from Ecommerce platform to Courier portals by hand here.

Worked out from the systems named on each step, so check it against how the work really goes. No time or cost is counted for these.