Crew Scheduling and Dispatch Basics for Small Field Businesses
How to plan a week of jobs across crews, route them to cut paid drive time, dispatch each day, and handle rain days and no-shows without chaos.
Key Takeaways
- Schedule the week, dispatch the day. Plan the week on Thursday or Friday. Confirm tomorrow’s plan at a fixed time each afternoon. Handle same-day changes through one person.
- Driving between jobs is paid time. Under federal rules, site-to-site travel during the day is hours worked, so clustering jobs by area cuts payroll, not just fuel.
- Every job needs the same five facts before it’s scheduled. Duration estimate, crew size and skills, equipment, materials and site access. Missing one is how crews end up waiting.
- Leave slack on purpose. A schedule that’s 100 percent full on Monday is wrong by Tuesday. Hold time for overruns, callbacks and weather.
- One channel for changes. If the schedule lives in three places, crews will follow the wrong one.
Quick-Start Prioritization Framework
| When | What happens | Who |
|---|---|---|
| Thursday or Friday | Build next week: assign jobs to crews and days, check materials and equipment | Owner or scheduler |
| Daily, 2–3 p.m. | Confirm tomorrow: weather, materials, customer confirmation, crew availability | Scheduler |
| Daily, by 5 p.m. | Send each crew tomorrow’s jobs, order and site notes | Scheduler |
| Morning | Crew confirms start; foreman flags problems | Foreman |
| During the day | All changes go through one person, sent to the affected crew only | Dispatcher |
| End of day | Crew marks jobs done or not done, with reason | Foreman |
Scheduling is deciding who does which job on which day. Dispatch is getting the right people, tools and materials to the right place this morning, and fixing it when something changes at 9:15. Small field businesses usually do both in the owner’s head and a group text, which works until the third crew or the second rainy week. This guide lays out a simple system that works on a whiteboard, a spreadsheet or an app: how to build the week, how to route jobs so you aren’t paying for unnecessary driving, what each crew should get the night before, and how to handle the changes that always come. The wage rules referenced are US federal rules; it’s general information, not legal advice.
Scheduling and dispatch are different jobs
Mixing them up is the root of most crew chaos. Scheduling is a planning job you do with a clear head, away from the phone. Dispatch is a live job: answering calls, moving people, fixing the plan.
In a small business one person often does both, and that’s fine. But do them at different times. Build next week’s schedule on Thursday afternoon with the door closed. Dispatch from 6:30 to 9 in the morning and whenever the phone rings. If you try to plan next week while dispatching today, both get worse.
Before a job goes on the schedule
A job is ready to schedule when you can answer five questions. If you can’t, it goes on a “not ready” list, not on a crew’s day.
| Question | Example answer | What goes wrong without it |
|---|---|---|
| How long will it take? | 2 days, 3 people | Crews leave jobs half done or sit idle by noon |
| What skills does it need? | One person who can set a sump pump | Wrong crew shows up |
| What equipment? | Mini excavator, trailer | Two crews need the same machine on the same day |
| Are materials on hand or ordered? | Pavers delivered Tuesday | Crew arrives to an empty driveway |
| Can we get in? | Gate code 4471, homeowner home after 9 | Crew waits in the truck, on the clock |
Estimate durations from history
If your crews log time against jobs, you have the best duration data you’ll ever get. Look at the last ten similar jobs and use the typical figure, not the best one. If you don’t have history, estimate, then compare to actuals every week until you do.
Confirm with the customer
A short confirmation a day or two ahead, with the arrival window and anything the customer needs to do (move the car, unlock the gate, clear the garage), prevents a lot of wasted mornings.
Building the week
Start with what’s fixed, then fill around it.
Order of operations
First, place jobs with fixed dates: inspections, deliveries, customer deadlines, jobs following another trade. Second, place multi-day jobs so the same crew stays on them. Third, fill remaining days with flexible work, grouped by area. Last, leave a buffer: many crews hold Friday afternoon or a half day per crew for overruns and callbacks.
Keep crews on their jobs
Moving a crew off a half-finished job to start another one feels efficient. It usually isn’t. Every handoff costs setup, travel and context, and the customer on the first job notices the empty driveway.
A worked week
Three crews, one week. Crew A (3 people) has a two-day patio Monday and Tuesday, a fence repair Wednesday morning, and a retaining wall Thursday and Friday. Crew B (2 people) runs maintenance: Monday and Wednesday in the north part of town, Tuesday and Thursday in the south, Friday as a catch-up day. Crew C (2 people) does a three-day bathroom demo and rough-in Monday to Wednesday, then an inspection Thursday morning with punch list in the afternoon, Friday held open. Two and a half of fifteen crew-days are open buffer (Crew A’s Wednesday afternoon, and both Fridays for Crews B and C). When it rains on Tuesday, Crew B’s Friday absorbs it, and Crew C’s open Friday takes any overflow.
Routing: why drive time is a payroll question
Routing isn’t just about fuel. The Department of Labor’s Fact Sheet 22 says travel from job site to job site during the workday is work time, and 29 CFR 785.38 says the same of travel from a required meeting place, like the shop, to the first site. Every minute a crew drives between jobs is paid.
The arithmetic
A two-person maintenance crew does four stops a day. Scheduled in the order customers called, the three drives between stops average 30 minutes: 90 minutes of driving per person, 180 paid minutes for the crew. Grouped by neighborhood, those drives average 10 minutes: 60 paid minutes for the crew. That’s two hours of paid time saved per day, ten per week, for one crew, before counting fuel. At 25 dollars an hour, that’s 250 dollars a week of payroll, which is your own example arithmetic, not an industry figure.
Zones and days
For recurring work, split your area into zones and give each zone fixed days. Customers learn that “north side is Monday and Wednesday,” and new jobs slot in naturally. For project work, try to keep a crew’s small jobs near its main job.
Order within the day
Put the job with a fixed time window or the most uncertainty first, while there’s still time to recover. Put flexible, short jobs last, so they can slide to tomorrow if the day runs long.
Daily dispatch: what each crew needs the night before
Crews should never learn their first job at 7 a.m. Pick a time, say 5 p.m., and send each crew tomorrow’s plan every day, even when nothing changed.
- Start time and meeting place (shop or first site).
- Jobs in order, each with the address as a tap-to-navigate link.
- Scope in one or two lines, and a checklist if the job type has one.
- Site notes: gate code, parking, pets, where the water shutoff is, customer’s hours.
- Materials: what’s on site, what to pick up and where.
- Equipment: what to bring, what is being delivered.
- Who to call: foreman, office, site contact.
Each crew sees only its own day
Send the full company schedule to everyone and people will read the wrong line. Each crew should see its own jobs. The foreman can see the crew’s week; the office sees everything.
When the plan changes
It will. The point of a system is to change one thing without breaking five others.
Rain days
Decide the call time the night before or at a fixed time in the morning, and make it before crews leave home when you can. Have indoor or rain-tolerant work ready to swap in. If you send people home after they’ve reported, check your state: California, for example, requires reporting time pay of half the scheduled day, at least 2 and at most 4 hours, when an employee reports and gets less than half the scheduled work, with exceptions such as acts of God and utility failures, according to the state Labor Commissioner. Whether a given weather call falls under an exception is a question for your state’s rules or an attorney.
Waiting
Under Fact Sheet 22, workers who are “engaged to wait,” such as a crew told to stand by on site until the inspector shows up, are working. If a crew will be waiting, either give them something to do or reschedule. Waiting is the most expensive thing a crew can do.
No-shows and sick calls
Have a rule for which crew gives up a person when another crew is short, and which jobs get pushed first. Usually that’s flexible maintenance before fixed-date project work.
Emergencies and add-ons
An emergency call goes to the crew nearest it with the most flexible next job. The dispatcher moves the bumped job and tells that customer the same day. Never let a crew reshuffle its own day without telling the office; the next customer will call the office, not the crew.
Overtime and capacity
Schedules quietly create overtime. A crew scheduled for five 9-hour days with shop and travel time is past 40 hours before anything goes wrong.
Plan in paid hours, not job hours
Count shop time, travel and waiting when you load a crew’s week. Federal overtime is owed for hours over 40 in a workweek, and 29 CFR 778.104 says each week stands alone: a light rain week doesn’t offset a heavy one. Some states, like California, add daily overtime.
Watch the week as it happens
Look at week-to-date hours by person on Wednesday or Thursday. That’s when you can still move a job or a person. On Monday it’s just a payroll number.
Common mistakes
These are the scheduling habits that cost crews the most.
- Scheduling jobs that aren’t ready: materials not ordered, customer not confirmed, access unknown.
- Building the schedule in the order customers called, which maximizes paid drive time.
- No buffer, so every overrun becomes a cascade of late jobs and apologies.
- Sending tomorrow’s plan at 6:45 tomorrow morning.
- Changes going out through three channels, so crews follow the wrong one.
- Pulling crews off half-finished jobs.
- Counting only on-site hours when planning a crew’s week, then being surprised by overtime.
- Leaving a crew on site waiting instead of rescheduling.
Tools for scheduling and dispatch
A whiteboard and a group text work for one or two crews. Past that, most businesses move to a shared calendar, a spreadsheet, or field service software that sends each crew its own day and records changes. Whatever you use, the system above matters more than the tool.
If you’d rather not bend your process to a packaged product, Floot can build a crew scheduling app from a plain-English description of your crews, zones and job types, with each crew seeing only its own jobs and push notifications when a job moves. It is free to start.
Frequently Asked Questions
What is the difference between scheduling and dispatching?
Scheduling is planning which crew does which job on which day, usually a week ahead. Dispatching is the day-of work of sending crews out, tracking where they are in the plan and handling changes.
How far ahead should I schedule crews?
Most small field businesses plan one to two weeks ahead and lock the next day by mid-afternoon. Recurring service work can be scheduled much further out by zone and day.
Is drive time between jobs paid?
Yes, under federal rules. The Department of Labor treats travel from job site to job site during the workday as hours worked, which is why clustering jobs by area saves payroll as well as fuel.
What should I do on rain days?
Make the call at a fixed time, ideally before crews leave home, and have rain-tolerant work ready. Check your state’s rules on reporting time pay; California, for example, requires it in some cases when workers report and are sent home.
How much buffer should a crew schedule have?
There’s no single right number. Many businesses hold a half day per crew per week, or keep Friday afternoon flexible, then adjust based on how often their jobs actually overrun.
How do I reduce crew drive time?
Group jobs by area, give recurring work fixed zone days, keep each crew’s small jobs near its main job, and schedule in route order instead of call order.
Sources
- U.S. Department of Labor, Fact Sheet #22: Hours Worked under the FLSA, 2008 https://www.dol.gov/agencies/whd/fact-sheets/22-flsa-hours-worked
- 29 CFR 785.38, Travel that is all in the day’s work (Cornell LII) https://www.law.cornell.edu/cfr/text/29/785.38
- 29 CFR 778.104, Each workweek stands alone (Cornell LII) https://www.law.cornell.edu/cfr/text/29/778.104
- California Labor Commissioner, Reporting Time Pay FAQ https://www.dir.ca.gov/dlse/faq_reportingtimepay.htm
- California Labor Commissioner, Overtime FAQ https://www.dir.ca.gov/dlse/faq_overtime.htm