This is an example proposal built by Nagenthiran — see more examples or get one like it
Placeholder photo: distribution depot

Proposal · Q4 2026

Faster routes,
fewer delays.

A proposal to rebuild dispatch planning at Brightwater Logistics, prepared for the operations leadership team.

Prepared forOperations leadership
Prepared byNagenthiran

The challenge

Dispatch still runs on spreadsheets.

Every morning, planners rebuild routes by hand, and the day starts with three versions of the truth.

  • i.Route plans are built by hand each morning, taking three to four hours per shift.
  • ii.Late deliveries cost an estimated 6% of revenue in penalties and re-routing.
  • iii.Drivers and warehouse teams see different versions of the same schedule.

The approach

One live plan, shared by everyone.

i.

Route planner

Generates daily routes from orders, vehicles, and time windows, then flags conflicts before they happen.

ii.

Driver app

A clear mobile view of each route, with stop order, delivery notes, and proof of delivery.

iii.

Live dashboard

One screen for dispatch to spot late risks and reassign work in a single click.

Expected impact

Targets for the first six months.

Based on the pilot depot's data from Q2 2026. We'll review progress together at month three.

−70%Time spent building daily routes
−40%Late deliveries, measured monthly
+15%Stops completed per driver per shift

Delivery plan

Four phases, live in twelve weeks.

Weeks 1–2

Discovery

Map current routes, interview dispatchers, and agree on success measures.

Weeks 3–6

Planner pilot

Build the planner and run a pilot with one depot.

Weeks 7–9

Driver app

Release the driver app and proof of delivery, tested on live shifts.

Weeks 10–12

Roll-out

Extend to all depots, train teams, and hand over documentation.

Who delivers, and what could go wrong

A small team, with you involved.

  • i.Delivery lead, full-time for twelve weeks. Owns the plan, the pilot and the handover.
  • ii.Two developers, from week three. Build the planner, the driver app and the dashboard.
  • iii.Your dispatch champion, around four hours a week. Signs off routes and tests every release on live shifts.

Risks we plan for

  • 1Drivers don't adopt the app. A champion per shift, in-depot training, and a two-week shadow period before the old sheets are retired.
  • 2Order data is messy. A two-week clean-up sprint before build, with validation rules on address and time-window fields.
  • 3Scope grows. A fixed fee for the agreed scope, and a monthly review of any change request with its cost stated first.

Investment

Two ways to begin.

Recommended

Full build

£38,000fixed fee

  • Planner, driver app, and dashboard
  • Twelve-week delivery with training
  • Thirty days of post-launch support
Lighter start

Planner only

£18,500fixed fee

  • Route planner for one depot
  • Six-week delivery
  • Upgrade path to the full build

In their words

“

The pilot took three weeks to build, and our dispatchers stopped asking for the old spreadsheet by the second day.

Operations Manager, pilot depot · placeholder testimonial

Next steps

Shall we start
with a pilot?

Approve the scope this week, and discovery begins the following Monday.

01 / 09 ← → keys to move