Guide
Dispatch Schedule:Technician Capacity, Arrival Windows, Buffers, Same-Day Adds and Paid Travel Rules
Dispatch schedule guide: daily capacity per technician, arrival windows, buffers, same-day adds and the DOL travel rules, with a sample four-technician day.
A dispatch schedule is the dispatcher's plan for one working day: each technician's paid hours, the jobs assigned to each arrival window, the drive time between them, the buffer held for overruns, and the open capacity reserved for same-day calls. It is set the evening before and revised through the day as jobs run long or new calls arrive.
The errors in a dispatch schedule sit in minutes the plan never counted. A technician who loads the truck at the shop before the first call is paid for that drive, and a schedule that ignores it books one stop too many. A day with no buffer passes every overrun into the next customer's window. A same-day call placed on the nearest technician becomes overtime by Friday. FieldRanger, which makes field service software that runs inside HubSpot, publishes this guide among its dispatching and scheduling guides. It covers the columns of the schedule, daily capacity in paid hours, the start of the paid day, arrival windows, buffers and same-day adds, then the order for dispatching technicians to jobs and the federal hours-of-service rules for heavier service trucks. A four-technician pest control day is scheduled with sourced rates, followed by the measures that improve the dispatch process, a checklist and the software record.
A dispatch schedule differs from the documents beside it. A service schedule books jobs into days and windows ahead of time, as set out in service scheduling; the dispatch schedule takes one booked day and assigns its minutes. A dispatch board is the display on which the dispatcher moves jobs; the schedule is the plan the board shows. A panel schedule shares the word and nothing else: it is the circuit directory inside an electrical panel. Within the schedule, capacity is the paid minutes a technician has left for jobs and the drives between them, a buffer is time added to a job for overruns and parts runs, and a float is a block of capacity held empty for same-day calls.
Dispatch schedule columns and rows
The schedule has one row per technician and one column per attribute of the day, so the dispatcher can read a technician's whole day across one line at 7 a.m. and again at 2 p.m.
| Column | What it holds |
|---|---|
| Technician | Name, truck number, and the skills or licenses that limit which jobs the technician can take |
| Paid-day start | The time and place paid time begins: the shop, or the first job for a take-home truck |
| Paid hours | The hours scheduled for the day and the running total for the workweek |
| Rest breaks | Short paid breaks, counted as hours worked |
| Meal period | The unpaid meal period and its start time |
| Jobs by window | Each job in its arrival window, with address, job type and estimated minutes on site |
| Drive minutes | The estimated drive before each job after the first |
| Buffer | Minutes added to each job, or held at the end of a window |
| Open capacity | Paid minutes left after jobs, drives, buffers and breaks |
| Float | Capacity held empty for same-day calls, and the time it is released |
| Status | Booked, en route, on site, complete or carried over, updated through the day |
The weekly total in the paid-hours column matters because the Fair Labor Standards Act requires pay of "not less than one and one-half times the regular rate" for hours in a "workweek longer than forty hours" (29 U.S.C. 207(a)(1), via Cornell LII, checked November 12, 2026). A call that fits Thursday's open capacity can therefore cost more on one technician than on another.
Daily capacity per technician in paid hours
Capacity starts from paid minutes and subtracts the paid minutes that produce no job. Federal regulations set three rules that decide the arithmetic. Rest periods "running from 5 minutes to about 20 minutes" must be counted as hours worked (29 CFR 785.18). Bona fide meal periods are not worktime: the employee must be "completely relieved from duty", and "ordinarily 30 minutes or more" is long enough (29 CFR 785.19). Travel that is part of the principal activity, such as travel from job site to job site during the workday, counts as hours worked (29 CFR 785.38, via Cornell LII, checked November 12, 2026).
The capacity test for one technician follows from those rules. A day with a given number of jobs fits when the on-site minutes and buffers of every job, plus one drive before each job after the first, add up to no more than the paid minutes less the rest breaks. The meal period sits outside the paid day and moves the clock, not the capacity. A dispatcher who plans in job slots without the drive minutes plans a day the technician cannot work inside paid time.
Paid-day start: shop, first job and take-home trucks
The place the paid day begins is a dispatch decision with a measurable cost. Under 29 CFR 785.38, an employee required to report at a meeting place to receive instructions, to perform other work there, or to pick up and carry tools is working from that point, so the drive from the shop to the first job is hours worked. Ordinary travel from home to the place of the principal activity is not compensable under the Portal-to-Portal Act. Its 1996 amendment adds a condition for company vehicles. Commuting in an employer's vehicle is not part of the principal activities "if the use of such vehicle for travel is within the normal commuting area" and the use is "subject to an agreement" between the employer and the employee or the employee's representative (29 U.S.C. 254(a), via Cornell LII, checked November 12, 2026).
Three start rules follow, and the schedule records which one applies to each technician:
- Shop start. Paid time begins at the shop; loading time and the drive to the first job are paid and come out of capacity.
- Take-home truck under a written agreement. Paid time begins at the first job, provided the first job is within the normal commuting area.
- First job outside the normal commuting area. The 1996 amendment covers vehicle commuting only inside the normal commuting area, so the pay treatment of a longer first drive is settled in writing before the schedule assumes it is unpaid.
The end of the day has its own rule. The example in 785.38 treats travel after the last job as home-to-work travel when the employee goes home rather than back to the employer's premises; a technician required to return the truck to the shop is working until arrival there. The sample day below shows the start rule moving capacity by one job per technician.
Arrival windows in the dispatch schedule
The arrival window is promised at booking, and the dispatch schedule decides which technician keeps it. Each window on a technician's row holds the jobs whose on-site minutes, buffers and drives fit between its start and end, and the dispatcher sequences jobs inside a window by location so that the drive minutes in the row are the drives the technician will make. The meal period is placed between windows, never inside one, so that it cannot push a promised arrival.
The first window of the day is the only one that no earlier job can overrun, so its arrival time depends on the paid-day start. A technician on a shop start with 55 minutes of loading and driving cannot reach an 8:00 first call; one on a take-home truck can. On the day, the window promised at booking can be narrowed to an estimated arrival time sent when the technician leaves the previous job, which keeps the promise and the plan separate.
Buffers for overruns and parts runs
A buffer is unsold capacity bought on purpose, and the schedule states where it sits. Two methods exist. A per-job buffer adds a fixed number of minutes to every job, which protects each following customer a little. A window buffer holds a block at the end of each window, which protects the next window fully and leaves the jobs inside the window exposed to each other.
Buffers are sized from the company's own records: logged on-site minutes against estimated minutes by job type, and the number of parts runs per week. A buffer has a price. In the sample below, ten minutes on each of seven jobs is 70 minutes a day per technician, or $32.99 at the loaded rate of $28.28 an hour, so a buffer larger than the overruns it absorbs is a cost with nothing on the other side.
Same-day adds and the float
A same-day add is accepted only where four checks pass, in this order:
- Skill. The technician holds the license, certification or equipment the call needs.
- Capacity. The row has open minutes for the job, its buffer and the drive to it.
- Workweek. The addition does not take the technician over 40 hours, or the overtime is accepted knowingly.
- Later windows. The jobs after the insertion still arrive inside their promised windows.
The float makes the second check pass by design. A float is a block of one technician's afternoon, or a slice of several technicians' days, left empty for same-day calls and released at a fixed time, such as 1 p.m., to callbacks or the next day's backlog if no call claims it. Its size comes from the company's record of same-day calls by weekday and season. A call that fails every check is offered the first window with capacity the next day, which is a promise the schedule can keep.
Technician-to-job assignment order
Dispatching technicians to jobs follows a fixed order, because each step narrows the choices for the next. The procedure below builds a day from an empty schedule.
- Record each technician's paid-day start, scheduled hours and workweek total.
- Place the jobs that only certain technicians can do: licensed work, certified repairs, jobs that need specific equipment.
- Place fixed-time appointments: first-window promises, commercial sites with access times, return visits booked to a time.
- Group the remaining jobs by area and assign each group to the technician whose earlier stops are nearest.
- Add drive minutes and buffers to each row and compute open capacity.
- Hold the float, and set its release time.
- Send each technician the day, with addresses, windows and job notes.
- Verify after the last job: compare each arrival with its window and each logged on-site time with its estimate, and carry the differences into tomorrow's estimates.
The verification step is what improves the schedule over time; a dispatch schedule that is never compared with the day it planned keeps the same errors.
Service trucks under federal hours-of-service rules
Dispatching trucks in a service business adds one more constraint where the trucks are heavy and cross state lines. A commercial motor vehicle includes a vehicle used on a highway in interstate commerce to transport property with a gross vehicle weight rating or actual gross weight "of 4,536 kg (10,001 pounds) or more" (49 CFR 390.5T, via Cornell LII). A box truck, jetter truck or crane truck of that rating that crosses a state line is one; a light van that stays in town is not.
For property-carrying drivers, 49 CFR 395.3 allows 11 hours of driving within the 14 consecutive hours after 10 hours off duty, requires a 30-minute interruption after 8 hours of driving, and stops driving after 60 hours on duty in 7 days or 70 in 8 (49 CFR 395.3). The short-haul exception in 395.1(e)(1) applies to drivers who stay within "a 150 air-mile radius (172.6 statute miles)" of their normal work reporting location and are released within 14 consecutive hours. The carrier then keeps time records for 6 months showing when each driver reported, the total hours on duty and when each driver was released (49 CFR 395.1, checked November 12, 2026). A dispatch schedule for such a truck therefore records the report time and the release time, and treats the 14-hour release as a hard end of the row. The federal rules reach vehicles in interstate commerce; a truck that never leaves one state falls under that state's motor carrier rules. Freight dispatching for owner-operators, built on load boards and brokers, is a different job outside this guide.
Pest control dispatch schedule: a sample four-technician day
The day below is a sample for a hypothetical pest control company with four technicians on take-home trucks under a written agreement, all first jobs inside the normal commuting area. Job lengths, drive times and buffers are sample inputs, labelled as such; the wage, the compensation ratio, the overtime rule and the mileage rate are published figures.
Each technician has an 8-hour paid day from 8:00 to 4:30 with a 30-minute unpaid lunch and two paid 10-minute breaks, so 460 minutes remain for jobs, buffers and drives. A quarterly exterior service takes 40 minutes on site, an initial service 90, and every job carries a 10-minute buffer. Drives between jobs average 18 minutes and 9 miles. The median wage for pest control workers was $21.75 an hour in May 2025 (BLS Occupational Outlook Handbook, pest control workers, modified September 14, 2026). Wages and salaries were 76.9% of total compensation for private industry service occupations in June 2026 (BLS Employer Costs for Employee Compensation, Table 4, modified September 9, 2026), so the loaded rate is $21.75 ÷ 0.769 = $28.28 an hour.
| Technician | Jobs | Minutes used | Open minutes |
|---|---|---|---|
| A | 7 quarterly services | 7 × 50 + 6 drives × 18 = 458 | 2 |
| B | 7 quarterly services | 458 | 2 |
| C | 1 initial service, 5 quarterly services | 100 + 5 × 50 + 5 drives × 18 = 440 | 20 |
| D | 5 quarterly services, afternoon float | 5 × 50 + 4 drives × 18 = 322 | 138 |
| Team | 25 jobs | 1,678 of 1,840 | 162 |
The day carries 21 paid drives of 18 minutes, or 6.3 hours, which cost 6.3 × $28.28 = $178.16 in loaded wages. The 189 miles cost $143.64 at the IRS business rate of 76 cents a mile from July 1, 2026 (IRS standard mileage rates, updated July 28, 2026).
The shop-start version. If the same technicians report to the shop at 7:30, load for 30 minutes and drive 25 minutes to the first job, 55 paid minutes come out of each row before the first arrival.
| Measure | Take-home trucks, paid from the first job | Shop start at 7:30 |
|---|---|---|
| Paid minutes before the first job | 0 | 55 |
| Minutes left for jobs, buffers and drives | 460 | 405 |
| Quarterly services one technician can hold | 7 | 6 |
| Initial service plus quarterly services | 6 | 5 |
| Team jobs on the sample day | 25 | 22 |
| Float left on technician D | 138 minutes | 83 minutes |
The same-day add. At 10:40 a customer calls about a wasp nest at the front door: 30 minutes on site, a 10-minute buffer and an 18-minute drive, 58 minutes in all. Technician D's float holds it, and 80 minutes of float remain. Technician A is nearer, but A has 2 open minutes and, in the sample, reaches 40 hours on Friday. Placed on A, the call uses A's 2 open minutes and runs 56 minutes beyond the paid day, paid at the overtime rate of 1.5 × $21.75 = $32.63 an hour, or $30.45 in wages before payroll taxes. It also moves every later customer on A's route 58 minutes later, the last of them to an arrival after 4:30, when A's paid day was planned to end.
Dispatch process improvements measured from the schedule
Improving the dispatch process means changing the inputs the schedule is built from, and each input is measured by comparing the plan with the day. The table lists the measures, the records each comes from and the change it supports.
| Measure | Computed from | Change it supports |
|---|---|---|
| On-time arrival by window and technician | Arrival times against promised windows | Window width, sequence, first-window start rule |
| Estimate accuracy by job type | Logged on-site minutes against estimated minutes | Job lengths used at booking |
| Buffer use | Minutes of buffer consumed against minutes held | Buffer size and method |
| Float use | Same-day calls placed in the float, and float released unused | Float size by weekday and season |
| Overtime minutes by cause | Hours over 40 traced to the job that caused them | Same-day add rules, weekly hours column |
| Carry-overs | Jobs moved to another day, with the reason | Capacity per technician, parts on trucks |
Dispatch schedule checklist
- Each technician's paid-day start is recorded as shop, first job or outside the commuting area, and take-home trucks have a written agreement.
- Rest breaks are counted inside paid minutes; the meal period is unpaid only when the technician is completely relieved of duty.
- Every job after the first carries a drive estimate, and open capacity is computed per row.
- Buffers are sized from logged overruns, and their cost at the loaded rate is known.
- A float is held, with a stated release time.
- Same-day adds pass the skill, capacity, workweek and later-window checks in that order.
- Heavy trucks crossing state lines carry report and release times against the 14-hour limit.
- At day's end, arrivals are compared with windows and logged minutes with estimates, and tomorrow's estimates are corrected.
Dispatch schedules in FieldRanger
FieldRanger keeps the dispatch schedule on the same HubSpot records as the sale. A won HubSpot deal becomes a job with its context carried over. The dispatcher assigns and reschedules jobs by dragging them on the calendar, with every technician side by side, their availability and current assignments shown. Skill-based assignment matches jobs to technicians by certification and expertise, capacity planning prevents overbooking with workload balancing, and conflict detection warns of double-bookings. Arrival windows are set on each job and on-time performance is tracked, and real-time notifications alert technicians to schedule changes and new assignments. FieldRanger builds each technician's route for the day automatically, and technicians clock in and out with time logged against each job, which supplies the logged minutes the end-of-day check compares.
Job status changes can trigger HubSpot workflows. HubSpot lists up to 50 workflows with restricted triggers and actions on Sales Hub Starter and up to 300 fully customizable workflows on Sales Hub Professional (HubSpot Sales Hub pricing, checked November 12, 2026). The scheduling and dispatch page shows the calendar step by step, the dispatch software page covers the dispatcher's day, and the dispatch board template lays out the board's fields for a team still working on paper or a spreadsheet.
Frequently asked questions
What is a dispatch schedule?
The dispatcher's plan for one working day: each technician's paid hours, the jobs in each arrival window, the drives between them, the buffers held for overruns and the float kept for same-day calls. It is set the evening before and revised through the day.
How to dispatch technicians to jobs?
Record each technician's paid-day start and weekly hours, place jobs that need a specific skill first, then fixed-time appointments, then group the rest by area. Add drives and buffers, hold a float for same-day calls, send each technician the day, and compare arrivals and logged minutes with the plan at day's end.
How to improve the dispatch process?
Measure the plan against the day: on-time arrival by window, logged minutes against estimates by job type, buffer and float use, overtime minutes by cause and carry-overs. Each measure changes one input, such as a job length or the size of the float.
How to dispatch trucks in a service business?
Treat each truck's day as a row with a start time, jobs, drives and an end time. A truck rated 10,001 pounds or more that crosses a state line is a commercial motor vehicle, so its row also respects the 11-hour driving and 14-hour limits, or the short-haul exception's 150 air-mile radius and 14-hour release.
Is the drive to the first job paid?
It depends on where the day starts. Travel from a shop where the technician must report or pick up tools to the first job is hours worked under 29 CFR 785.38. Commuting in a company vehicle to the first job is not, when it is within the normal commuting area and covered by an agreement under 29 U.S.C. 254(a).
How much buffer should a dispatch schedule hold?
Enough to absorb the overruns the company's own logged times show, and no more, because buffer minutes are paid and unsold. In this guide's sample, 10 minutes on each of seven jobs costs $32.99 a day per technician at a $28.28 loaded rate.
On the sample Tuesday, the rule for where a technician starts work removed three jobs and 55 minutes of float from the day before the dispatcher had assigned a single call. The dispatching and scheduling guides continue with booking and routing, service scheduling sets the windows this schedule fills, and the per-technician plans are on pricing, where Start free trial runs 14 days and needs no card.
Run field service on HubSpot with FieldRanger
Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.
Book a demo