Skip to content
Sesklo

Blog · October 16, 2026

Scheduling a 3-person crew: dispatch, drive time, and what contractor scheduling software actually fixes

Three people is the size where scheduling stops being a memory problem and starts being a math problem. One truck and you already know where you’re going. Three trucks, three or four stops each, two different skill sets, and a callback that lands at 11:40 — and the thing that quietly disappears is the afternoon. Contractor scheduling software is sold as the fix for that, and it does fix part of it. Here is which part, where the hours actually leak on a small crew, and what to look at before you pay for a field service app you’ll be living in every morning.

What does contractor scheduling software actually do for a small crew?

It replaces three things at once: the whiteboard that says who’s going where, the text thread that tells them, and the mental arithmetic that decides whether the day fits. A dispatch board puts every tech’s day on one grid, assigns work by dragging or tapping it onto a time slot, and — the part a whiteboard genuinely cannot do — accounts for the drive between stops.

That last clause is most of the value. Everything else on the feature list is a nicer whiteboard, and a nicer whiteboard is worth something, but it won’t tell you that the 7:30 you just promised on the far side of town turns a four-job day into a three-job day.

It’s also worth being clear about what it doesn’t do. Software won’t set your priorities, won’t make a ten-hour day fit into eight, and won’t rescue a job you underestimated at quote time. If your estimates are wrong, a dispatch board will show you the wrongness faster and in color. That’s an improvement, not a cure.

The four calendar mistakes that eat afternoons

These show up in almost every shop between one truck and five.

1. Counting jobs instead of counting hours

“Four jobs” is not a day. Four jobs is somewhere between five and nine hours depending on what they are, and crews who schedule by count find out which at two in the afternoon. The fix isn’t a tool — it’s putting a duration on the work at quote time rather than at dispatch time, and treating that number as something a person is accountable for.

Then close the loop: for a month, log hours actually worked against hours estimated, by job type. You’ll come out with a multiplier — “our two-hour service calls are 2.6 hours door-to-door” — and that multiplier is worth more than any scheduling feature you can buy. Sesklo carries a total-estimated-hours figure on the quote, and the schedule optimizer plans against what’s left of it, so the draft of your day starts from the number the estimator wrote. Time tracking, on the Pro and Team plans, records the hours each person actually spent on the job. Comparing the two is the whole exercise.

2. Treating drive time as free

Drive is the only item on a crew’s day that nobody writes down, and on a three-person crew it is routinely the largest single block of unbilled time. Two cross-town hops per tech per day is real money, and it’s invisible because it never appears on the calendar.

So put it on the calendar. When an owner or admin calculates drive times, Sesklo inserts drive-time blocks between stops using traffic-aware Google Maps drive times, labeled with the actual from → to addresses — plus the first leg out and the last leg back when you’ve set a starting point for your routes: your shop, home, or another address you choose. Once drive is a visible block rather than a vague assumption, two things change immediately: your arrival windows get more honest, and you can see which jobs are geographically expensive before you commit to them.

A workable ordering rule for three people: cluster by geography first, then by skill, then by customer preference — in that order, unless the customer preference is an appointment you actually promised, in which case it’s a fixed point and everything routes around it.

3. Keeping the schedule in one person’s head

At three people the owner is usually the dispatcher, and the schedule lives half in a tool and half in their memory. That works until they’re under a house with no signal, and it’s the single point of failure that turns a sick day into a lost day.

The low-drama fix is a shared board where each tech sees their own day without being able to rearrange everyone else’s. On a Sesklo team account, the scope picker switches between your own schedule, one technician, or the whole team at once, and on the website an owner or admin can “view as” a specific tech to see that person’s calendar, read-only, before a confusing phone call happens. If two of the three always ride together, tag them as a crew and schedule the pair in one step on the website instead of assigning them twice.

4. Booking to one hundred percent

A calendar with no gaps has no room for the callback, and the callback is the job you can’t decline. Book to capacity and every emergency becomes a rescheduling cascade that costs you two phone calls per moved appointment.

Leave a deliberate hole. The patterns that hold up are a standing block at the end of each day, or one afternoon a week kept clear for carry-over and warranty work. Then set a weekly hours cap per person, so that whatever automation you turn on cannot quietly schedule your crew into overtime you didn’t approve — in Sesklo an owner or admin sets that cap per member, and neither the optimizer nor customer self-booking will push anyone’s week past it.

How much does a lost afternoon actually cost?

Enough that it should outrank most software decisions. Per Sesklo’s cost guides, which track typical prices across the 50 largest US metros, a roof repair runs from roughly $300 to about $3,400 depending on scope — with the typical job landing around $800 in Houston and around $1,200 in San Jose, a gap of about 50% between the cheapest and priciest metros in that set. HVAC installs and repairs span roughly $3,500 to $21,600 by the same dataset.

Run your own version of that arithmetic. In repair-and-service work, half a lost day is one to three billable calls. If that happens three times a month across a three-person crew, you are looking at a number well into the thousands a year — typically past what any scheduling tool costs, which is why “we’ll fix the calendar later” is usually the most expensive item on the list.

How do you dispatch three people without a full-time dispatcher?

You batch it. Set working hours once per person, mark which appointments are allowed to move, and let the software draft the day — then approve or reject the draft. Reviewing a proposed plan takes a fraction of the time that building one from an empty grid does, which is what makes a ten-minute morning routine possible at three people.

Sesklo’s schedule optimization is deliberately propose-then-apply. An owner or admin runs it; it drafts placements inside each person’s working hours, respects the weekly cap, reserves the drive time between neighboring stops, and then shows you what it placed, what it moved, and what it couldn’t fit and why. Nothing on the live calendar changes until you apply it, and when you do, customers whose appointments moved get an in-app and push notification rather than discovering it on arrival day.

On the website there’s also a whole-team mode for open work. It hands each job that isn’t on anyone’s calendar yet to an eligible tech — one who covers that trade and that service area — whose route it fits best, rather than to whoever would get it by default. That call is hard to make by eye across three routes, and it’s the main argument for letting software draft the day at all.

Firm vs. flexible: the field that makes automatic scheduling safe

The reason owners distrust auto-scheduling is simple and correct — they’re afraid it will move the one appointment they personally promised. Any tool you adopt needs a per-appointment answer to that, not a global setting.

In Sesklo every scheduled visit is firm by default, and you mark the ones the optimizer is allowed to move. Manual blocks, service requests, and drive blocks are always firm. (Accepted jobs that aren’t on the calendar yet are fair game — placing those is what the optimizer is for.) That inversion matters: the safe state is the default, so the worst case of forgetting to configure something is a schedule that doesn’t improve, not a customer who got moved without being asked.

You can also write timing preferences in plain English in a project’s scheduling notes — mornings only, afternoons are better, get this one in soon — and the draft treats them as soft preferences, with a written explanation of what it honored. A hard rule it can’t apply, like “must be a Tuesday,” is named in that explanation rather than silently dropped. Nothing replaces the knowledge in your head here; the point is to get it out of your head and into the thing building the day.

What to check before you pay for contractor scheduling software

Most field service software demos well. These are the questions that separate the ones you’ll still be using in a year:

Scheduling three people well is mostly discipline: honest durations, visible drive time, a shared board, and a deliberate gap for the work you can’t predict. Software’s job is to make those four things cheap enough that you actually keep doing them in August.

See how the dispatch board, drive-time blocks, crews, and propose-then-apply scheduling work together on Sesklo’s scheduling page for contractors.