Field service schedule

A field service schedule has a ceiling and most businesses have never worked out where it is. The ceiling is technicians multiplied by the jobs one of them genuinely completes in a day, and booking past it does not produce more work, it produces the phone calls that move the work. This worksheet puts a number on the ceiling, on what the month invoices when you hit it, and on the part of the day that goes on driving.

Count jobs completed, not jobs booked

The input is what a technician actually finishes, and the two numbers differ by exactly the amount this worksheet exists to expose. 6 technicians at 5.2 jobs is 31.2 a day and 655 a month, and if your board is carrying more than that then the surplus is not work, it is a queue that will be rebooked at somebody's expense.

Put your own invoice value in, including the small jobs

$285 is the worked example and it is an average, which means it has to include the twenty minute call that billed $95 as well as the install that billed $1,400. Averaging only the good jobs is the commonest way to make this worksheet flatter you, and the flattering version is no use in a budget conversation.

Read the travel line, then look at your map

$41,081 a month of capacity sitting in the van is the argument for clustering jobs by area before clustering them by urgency. It is also a payroll fact rather than a metaphor: travel inside the working day is hours worked, and the Department of Labor is specific about that, so the time is paid whether or not it is billed.