Scheduling Two-Technician and Crew Jobs: A 2026 Guide

TL;DR

Some jobs genuinely need two people. Rather more jobs get two people because that is how they were done the first time, and nobody has looked at it since.

As of September 2026 the practical problem is not deciding which is which — most owners can do that in a minute if asked directly. The problem is that a two-technician job consumes two capacity slots and almost every calendar in this industry is built around individual technicians, so the second slot disappears from the plan and reappears as a day that ran late. This guide covers which jobs really need a crew, what a crew slot costs, how to represent one honestly on a calendar, how to sequence two technicians so they are both free at the same time without wrecking two routes, and how to read your own job data to find out whether the second person was needed at all.

Which jobs genuinely need two people

There are four honest categories, and they have one thing in common: a single technician physically cannot complete the job safely or legally on their own.

Equipment lifts and set-downs. Air handlers, condensers, water heaters, commercial kitchen units, safes, gym equipment, anything that has to come down a staircase. The constraint is weight and geometry, and no scheduling cleverness makes a two-hundred-kilogram unit a one-person job.

Ladder, roof and elevated work. Where your safety policy or the site's requires a second person at the base, that person is not optional and is not really a technician for the period — they are a spotter. Treat it honestly rather than pretending the day contains two productive workers.

Confined and hazardous-space entry. Crawl spaces, tanks, vaults, anywhere with an attendant requirement. This is a compliance question rather than a productivity one, and it is where "we usually manage" is the most expensive sentence in the business.

Full install days. Not repairs — installs, where two workstreams run genuinely in parallel. One person running the line while the other sets the unit finishes in half the time rather than the same time, which is the test.

That last test is the useful one for everything else. If two technicians finish in half the elapsed time, you have parallel work and the crew is buying capacity. If they finish in the same elapsed time as one, you have a job with a passenger.

The jobs that are padded by habit

Three patterns account for most unnecessary crew work.

Training that never ended. An apprentice was paired with a licensed technician for six months, the six months became eighteen, and the pairing is now the default for job types the apprentice could run alone.

The difficult-customer premium. A job went badly once, somebody sensibly sent two people next time, and it became a rule about the job type rather than a note about one address.

The estimate nobody revisited. A job was quoted at two technicians because of a specific access problem, the template kept the two, and every similar job since has been booked the same way.

None of these are stupid decisions. They are reasonable decisions that outlived their reason.

What a two-technician slot actually costs

Here is the arithmetic, and it is worth doing out loud because it is the part that gets skipped.

Take a team where realistic capacity is four jobs per technician per day — a figure most small teams land on once travel, parts and write-up are counted honestly, as covered in technician capacity planning. A three-hour job with two technicians assigned, plus a travel leg each way for both, removes something in the region of seven or eight technician-hours from the day. Against a two-person team's total capacity of eight jobs, that single job has consumed roughly a quarter of everything you had to sell.

Which leads to the only rule in this article that matters: a two-technician job must be priced for two technicians. Not at a small premium. At the actual cost of the capacity it removes, plus the margin you expect on that capacity.

This is routinely not done, usually because the price was set when the job was assumed to be one person. The result looks profitable on the invoice and is quietly subsidised by the jobs that got displaced to make room for it.

The second cost is flexibility, and it appears in no arithmetic. A crew job cannot be moved without moving two people, cannot absorb an emergency reroute, and does not happen at all if either technician calls in sick. The triage framework in emergency versus scheduled jobs assumes somebody is free to reassign, and a crew day is a day where nobody is.

One-tech and two-tech jobs side by side

The bottom row is the one to keep. If the answer to the second question is no, the correct response is a staggered start or a repriced job, not a permanent crew.

Putting a crew job on a calendar built around individuals

Most field-service calendars are organised as columns per technician, which is the right primary view and is also exactly why crew jobs get misrepresented.

The single-record principle solves it: one job, two assignments. The job is one row with one customer, one address, one arrival window, one set of notes and photos, one invoice, one completion timestamp — and two technicians attached to it. Both see it in their own day. The board shows both slots occupied. Nothing about the customer relationship is duplicated.

If your calendar can do that, use it. GetTimePad's scheduling and dispatch board are built around this shape: the assignment is a property of the job rather than the job being a property of the technician, so a job can carry more than one person without becoming two jobs.

What breaks when you fake it with two appointments

The workaround everybody tries is entering the job twice, once under each technician. It appears to work and then produces a repeatable set of failures.

You get two arrival windows, and an automated reminder will eventually send the customer the wrong one. You get two sets of notes and photos, so the record of a single visit lives in two places and neither is complete — which matters on the day a dispute needs evidence. You get two invoices, or one invoice and an orphaned record that shows as unbilled work forever.

Worst, you get two independently reschedulable records. Somebody moves one, the other stays, and one technician arrives at a job that needs two. That is not hypothetical; it is the normal outcome of the workaround given enough weeks.

Your reporting also stops meaning anything. Two completion timestamps for one visit inflate the job count, halve the apparent average duration, and make first-time-fix rate uninterpretable — which matters when the whole argument here is arithmetic.

The sequencing problem, and staggered starts

Booking a crew job needs two technicians free in the same window, and "free" is not the only requirement. Both need to be free and arriving from somewhere that makes geographic sense.

Two technicians whose mornings are on opposite sides of the service area are not really available for an 11 a.m. crew job together, even with both calendars empty at 11. Somebody will drive forty minutes across the metro, and that leg is invisible in a schedule that only checks availability. The fix is to place crew jobs into the day first, before the single-tech work, then fill each technician's remaining slots in the same area. Crew jobs are the fixed points; everything else flexes.

Then there is the better answer for many jobs.

Staggered starts. The primary technician arrives at 9 a.m. and works alone — diagnosis, disconnect, prep, whatever the single-handed portion is. The second arrives at 10:30, spends forty minutes on the lift, and leaves. The primary finishes alone.

The saving is immediate. Instead of two technicians consuming three hours each, you have consumed three plus one, and the second technician has kept a job either side. On the schedule this is one job with two assignments and two time ranges, and it is the highest-value crew pattern available to a small team.

It does require the primary technician to be honest about when the second pair of hands is needed, and to send a message when the timing moves. That is a process habit rather than a feature, and it takes a fortnight to establish.

Skill pairing: licensed plus apprentice

Crew composition is a second decision, distinct from crew size, and often the one with more money in it.

Two senior technicians on a lift is two expensive hours buying one lift. A licensed technician plus an apprentice does the same lift, costs materially less, and produces a trained apprentice. Where licensing applies, the pairing may also be what lets the apprentice be on site at all.

The rule worth writing down is that pairing should be deliberate and should have an end date. "The apprentice works install days with a senior for the next two months" is a plan. "The apprentice always goes out with someone" is a permanent cost pretending to be a training policy. Set the graduation criteria at the start — which job types the apprentice runs solo, and from when — then apply them.

Trade shape matters here. Crew-native trades such as moving companies build the schedule in crews rather than individuals, so the question is crew size and composition rather than whether to send two. Access-and-security work of the kind covered in the locksmith software guide sits at the other end, where nearly everything is single-handed and a second technician is almost always habit rather than requirement.

Reading your own data

You can settle the "did we need two?" argument from records you already have, and it takes an afternoon.

Pull the last three to six months of completed jobs. For each job type that has ever run with two technicians, split them into one-tech and two-tech groups and compare the median arrived-to-completed duration. Three outcomes, three actions.

Two technicians roughly halve the elapsed time. Real parallel work. Keep the crew, make sure the price carries both people, and check whether a staggered start captures most of the saving for less.

Two technicians finish in about the same elapsed time as one. The second person added no throughput. Either the job needs them for safety or lifting — reprice it and consider staggering — or it does not, and you have found capacity.

The two-tech jobs are slower. Usually a scheduling artefact rather than a work one: the crew jobs include the awkward addresses, or the second technician arrived late and the clock started at the first arrival. Read a handful of notes before concluding anything.

Then check the callback rate for the same split. If single-tech jobs of a type come back more often, the second technician was buying quality rather than speed — a legitimate reason to keep them that no duration comparison will reveal. Tracking that properly is its own discipline, covered in warranty and callback tracking.

One more check: how often does a crew job fail on readiness? A two-technician visit that arrives without the right part has wasted twice as much, which makes crew work where pre-dispatch checks pay best — see job readiness and parts before dispatch.

What this costs

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff with multi-location, REST API and outbound webhooks, and an activity log with audit trail. Extra staff seats are $25/mo per seat on Starter and Pro, the SMS bundle is $19/mo, device connectivity is $15 per device per month, and annual billing gives you two months free. Every plan includes a 14-day free trial, and there is a live demo with no signup required that sets up in under five minutes. Details are on pricing.

Crew scheduling is a Pro-tier concern in practice, for a specific reason: Pro is where up to five staff, the mobile-first Tech Mode and the live map arrive, and crew work is exactly where you need to see where the second technician currently is rather than only whether their calendar is empty. If you are choosing tooling for this from scratch, the wider survey in best dispatch software for service companies is the place to compare approaches.

Where to start

Take your last two months of two-technician jobs and sort them into the four genuine categories — lift, elevated, hazardous entry, parallel install. Whatever does not fit is your habit list, and it is usually longer than expected.

Then price the genuine crew jobs for two people, properly, and see how many customers still buy them. Then pick the two or three job types where the second technician is only needed for a lift and convert them to staggered starts. Then stop entering crew jobs twice. Those four moves, in that order, recover more capacity than any amount of route tuning, because they give you back whole slots rather than minutes.