Skip to main content

Market-neutral small-business guide

Last-Mile Delivery: Route, Time and Failure

Connect route cost, stop density, time and failed delivery on one completed-delivery basis.

Define a comparable operating contract

Inputs and assumptions to record

  • Attempted, completed and failed stops under one success definition. (not complete)
  • Dispatch-to-return time and loaded driver cost. (not complete)
  • Route distance, vehicle resource boundary and toll/parking costs. (not complete)
  • Revenue and variable order/stop cost on one tax basis. (not complete)
  • Repeat, return and recovery rules for each failure class. (not complete)
Core calculation

route contribution = completed-stop revenue - dispatch cost - driver cost - vehicle cost - stop-variable cost - failed-delivery cost

completed-stop revenue
Revenue earned under the defined successful-delivery event (CU per route) — order and delivery record
vehicle cost
Fuel/energy, maintenance, lease/depreciation and included route resources (CU per route) — vehicle record or labelled scenario
failed-delivery cost
Handling, repeat travel, return, collection and loss caused by failed attempts (CU per route) — failed-stop record or scenario

Use one currency, indirect-tax basis, attribution rule and time horizon. All numbers below are invented currency units (CU), not forecasts or benchmarks.

Worked example: Last-Mile Delivery: Route, Time and Failure

Invented route: 24 attempts, 21 completed at 18 CU revenue; 55 CU dispatch, 120 CU driver, 70 CU vehicle, 42 CU completed-stop handling and 36 CU failed-delivery cost.

Reproducible base case
LineCalculationResult
Completed-stop revenue21 × 18378 CU
Included route cost55 + 120 + 70 + 42 + 36(323 CU)
Route contribution378 - 32355 CU
Contribution per completed stop55 ÷ 212.62 CU
Sensitivity with unlisted assumptions held fixed
CaseChanged inputResult
18 completions324 revenue - (245 fixed + 36 handling + 72 failure)(29 CU)
21 completionsBase55 CU
23 completions414 revenue - (245 fixed + 46 handling + 12 failure)111 CU

Bridge the denominator from route to successful delivery

One route cost viewed across attempted and successful stops
MeasureBase caseMore-failure caseInterpretation
Route cost323 CU for 24 attempts and 21 successes353 CU for 24 attempts and 18 successesRoute total remains the first reconciliation
Cost per attempted stop323 ÷ 24 = 13.46 CU353 ÷ 24 = 14.71 CUShows the attempted-stop workload only
Cost per successful delivery323 ÷ 21 = 15.38 CU353 ÷ 18 = 19.61 CUFailure changes the denominator and adds failure cost
The more-failure case uses the existing sensitivity assumptions: 18 completions, six failures, 2 CU handling per completion and 12 CU per failure. It is a scenario, not a failure-rate benchmark.

Use the exact calculation owner

Use the result without hiding uncertainty

  1. Define success, failure and route horizon.
  2. Reconcile attempted stops to outcomes.
  3. Cost dispatch, driver, vehicle and handling separately.
  4. Attach repeat/return cost to failure classes.
  5. Stress completion, density and route time.
  6. Pilot one change and reconcile actual route contribution.
  • Dividing route cost by attempted stops.
  • Using revenue per stop without order contribution.
  • Ignoring dispatch and return-to-base time.
  • Counting redelivery revenue twice.
  • Treating one dense route as a network benchmark.

Questions before committing

Should failed stops receive revenue?
Only if the commercial contract actually earns it under the defined event; keep collected cash, recognised revenue and contribution separate.
How should redelivery be treated?
Attach its time, vehicle, handling and any recovery to the original failure cohort or a clearly linked route record.
Is contribution per stop enough?
No. Retain route total, completion rate, time-window and capacity views.

Sources and methodology

Model the next decision

Change history

  1. Expanded the existing canonical owner with a bounded decision workflow, clearer interpretation boundaries and exact tool or methodology hand-offs without creating a competing article intent.
  2. Initial public release of the article after pre-launch factual, editorial, source and presentation review.