Skip to main content

Market-neutral small-business guide

Field-Service Economics: Travel, Labour and Capacity

Reconcile call-out work with travel, loaded labour, recovery and daily capacity on one job basis.

Set one comparable decision contract

Record these assumptions before calculating

  • Dispatch-to-return time, not only on-site time. (not complete)
  • Loaded labour cost and vehicle/equipment cost on compatible units. (not complete)
  • Direct materials and subcontractors for the job. (not complete)
  • Schedule utilisation and gaps across the planning period. (not complete)
  • Failed-access, callback and collection boundary. (not complete)
Core comparison

field-job contribution = customer price - mobilisation cost - travel cost - on-site labour cost - direct job cost - expected failure/callback cost

mobilisation cost
Dispatch, preparation, loading, setup and minimum diagnostic resource (CU per visit) โ€” time and cost record
travel cost
Travel labour plus vehicle and route-specific cost included in scope (CU per visit) โ€” route, payroll and vehicle record
expected failure/callback cost
Explicit scenario for failed access, repeat travel or warranty callback (CU per job) โ€” comparable job record or scenario

Keep one currency, indirect-tax basis, time horizon and cost boundary throughout. Scenario values below are invented currency units (CU), not benchmarks.

Worked example: Field-Service Economics: Travel, Labour and Capacity

Invented tax-exclusive visit: 260 CU customer price; 35 CU mobilisation, 50 CU travel, 80 CU on-site labour, 40 CU materials and 15 CU expected callback cost.

Reproducible base-case calculation
LineCalculationResult
Included job cost35 + 50 + 80 + 40 + 15(220 CU)
Job contribution260 - 22040 CU
Contribution margin40 รท 26015.4%
Price at zero contributionincluded cost220 CU
Recalculate from the displayed inputs. Parentheses indicate a cost or adverse result.
Sensitivity while all unlisted assumptions stay fixed
CaseChanged inputDecision result
Dense routeTravel cost 30 CU60 CU contribution
BaseTravel cost 50 CU40 CU contribution
Long routeTravel cost 90 CU0 CU contribution

Reconcile the day-capacity waterfall before setting recovery

Paid time to productive service time on one declared day
Capacity layerUnit and recordTreatmentRecovery decision
Paid or owner timeHours per day from the roster or owner-time recordStarting capacity; not automatically sellableKeep the same day and labour-cost basis
Travel and setupRecorded route, dispatch, loading and setup hoursSubtract once from paid timeEnter vehicle cost separately on the same route scenario
Productive service timeCompleted on-site hours after travel and setupCapacity available to recover service costTest call-out, travel and service recovery without double counting
Schedule gaps and failed visitsObserved or labelled hours per daySeparate from completed productive timeStress the day before setting the quote structure
Hours per day, CU per hour and CU per route stay separate. Vehicle cost is a user-entered scenario, not a default.

Use the exact calculation owner

Turn the calculation into an operating decision

  1. Measure the whole visit cycle.
  2. Separate mobilisation, travel, on-site labour and materials.
  3. Allocate vehicle and equipment on a supportable driver.
  4. Add observed failed-access and callback scenarios.
  5. Test route density and daily capacity.
  6. Quote transparently and reconcile the completed job.
  • Pricing only billable on-site time.
  • Counting travel labour but not vehicle cost, or vice versa.
  • Dividing daily cost by a fully booked day that rarely occurs.
  • Hiding callback and failed-access cost.
  • Using revenue per visit without contribution or capacity.

Questions to settle before acting

Should travel be a separate customer line?
That is a commercial decision. Keep it separate in the internal model even if the customer sees one bundled price.
How should schedule gaps be treated?
Model realistic sellable visits or hours for the period. Do not spread cost over theoretical full utilisation.
What if a callback is chargeable?
Separate expected recovery from expected callback cost and apply the reviewed service terms.

Sources and methodology

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.