Scheduling multiple crews across jobs is not a calendar problem. It is a commitment problem. The calendar is where the failure becomes visible, which is why every article on this topic tells you to buy a better calendar, but the failure happens earlier: you committed a crew to work that was never going to be ready for them.
The short answer
To schedule multiple crews across jobs: put every crew and every day on one grid so overlaps are visible, then, before a crew is committed to any job, screen that job against a constraint checklist and only commit to work where every constraint is closed. Give each crew a home base job for the week, keep a bank of small ready jobs to absorb the days a main job falls through, and build tomorrow's plan the evening before rather than at 6:45am.
The grid part is table stakes and takes an afternoon. The screening part is the one nobody does, and it is the one that decides whether your week survives contact with Tuesday.
Your plan is the problem, not your calendar
Start with the number that reframes this entire topic. In the research that produced the Last Planner System, Glenn Ballard and Greg Howell measured how much of the work a project team planned for a given week was actually completed in that week. The Lean Construction Institute states the finding plainly: on average, only 54 percent of work planned for a given week is completed within the allotted schedule.
By the numbers
About half of what you write on Monday does not happen by Friday. That figure is not a measure of lazy crews. It is a measure of unreliable commitments, and it has held up across decades of projects, sectors and countries.
If half your weekly plan is fiction, a tool that distributes that plan faster and to more phones is distributing fiction faster. It removes the clerical failures, which is worth something, and leaves the structural failure untouched.
The surrounding numbers are not in dispute. McKinsey's construction productivity work found that 98 percent of projects experience cost overruns, delays, or both, and that large projects typically finish about 20 percent later than scheduled. A 2024 analysis of activity delay patterns published on ScienceDirect puts the delayed share of construction projects at roughly 75 percent, with a median delay between 20 and 40 percent of project duration.
The more useful data is the breakdown of causes. A systematic review of delay factors indexed on SciELO attributes:
| Cause of delay | Share of delay causes |
|---|---|
| Supply chain and material management | 21.41 percent |
| Workforce management issues | 20.79 percent |
| Project management failures | 17.64 percent |
| Climate and environmental conditions | 9.34 percent |
Look at the last row against the two above it. Workforce management and project management together account for 38.43 percent of delay causes, better than four times the share attributable to weather. Every contractor has a weather story. Almost nobody has a coordination story, because coordination failures do not feel like events. They feel like a normal Tuesday. That is the case for spending your effort upstream of the schedule rather than inside it.
What actually breaks, and in what order
The constraint changes shape as you add crews, and knowing which stage you are in tells you what to fix.
One to two crews: the constraint is drive time. You are optimising a route. Cluster jobs by area, batch supply runs, protect a daily buffer. We covered that version in how to schedule jobs efficiently as a contractor, where roughly 30 of 40 clocked hours end up billable and drive time eats most of the difference.
Three to six crews: the constraint is dependency collisions. A delay on job A does not just push job A. It orphans the crew that was going there, and wherever you send them instead was already sequenced for someone else. The OP of a 2026 r/Contractor thread described it exactly: "The time it takes to plan everything for the upcoming months to have a job delayed 2 weeks than another one with the material arriving a week later. Reposition all the guys."
Seven or more crews: the constraint is you. Every change routes through one head. An owner running eight crews in the busy season replied in the same thread with the most honest line in it: "I've got 8 crews that I run in the busy season, I've never found anything that makes it easier other than foreshadowing the pivot."
He does not say he found the right app. He says he learned to see the pivot coming. That is constraint screening described in field language, and it is learnable faster than by running eight crews for a decade.
Watch out
The signal you have outgrown your current setup is not crew count. It is change count. Count the reschedules you personally handled last week. Under about five, a spreadsheet and a morning call still work. Over that, you are the bottleneck, and adding a ninth crew makes you a worse bottleneck rather than a bigger company.
Screen every job before you commit a crew to it
Here is the mechanism the page-one advice leaves out entirely. In the Last Planner System, work does not go onto a weekly plan because it is due. It goes on because it has been screened and every constraint closed. The question asked out loud for each task: what has to be true before a crew can walk up and work?
Run every job entering your next two to six weeks against these categories:
- Materials. Ordered, confirmed and staged, not "the order went in." A submittal or approval still pending is not material you have.
- Information. Drawings, an approved selection, an answered question, a colour or finish choice. This is the sneaky one, because the gap stays invisible until a lead opens the plans on site.
- Predecessors. The prior trade complete and inspected, not "basically done." Rough-in at 90 percent is zero percent ready for whoever follows it.
- Labour. The right headcount and the right skill, actually named. A sub who is "sending guys" without a name and a number is a constraint, not a plan.
- Equipment. The lift, the pump, the machine, and the person qualified to run it. On a shared fleet the equipment is its own schedule.
- Access and space. Is the work face clear, is the customer out, is the area safe to occupy, is another trade stacked on top of you.
- Permits and inspections. Lead times you do not control, which is exactly why they have to be screened early rather than assumed.
- Conditions. Temp power, a dry slab, a heated space in February. Work that cannot be done safely or correctly is not ready regardless of what else is cleared.
Most small shops screen categories 1 and 3 and stop. Information and inspections are where the surprises live, because both have lead times measured in weeks and neither announces itself.
The rule that makes the screen worth running: an item with an open constraint does not get a crew committed to it. Not "should be fine by then." Closed and verified. The moment "almost ready" is allowed onto the plan, ready stops meaning anything and you are back at 54 percent.
If your screen currently lives in your head, that is the real bottleneck, and it is why you cannot take a week off. A custom CRM built around your actual job stages can hold the constraint list per job, flag what is unresolved inside the window, and refuse to let a crew be assigned to a job that is not clear. That is a workflow decision, not a feature you can shop for off a comparison table.
Confirmed starts and tentative starts
The practical small-shop version of constraint screening is a two-column ledger, and a flooring owner in the r/Contractor thread described arriving at it independently:
"What finally worked for me was separating 'confirmed starts' from 'tentative starts.' Any job where the site wasn't 100% ready to go stayed in tentative status."
That one distinction does more for a multi-crew schedule than any feature on any vendor page. A tentative job can sit on the plan and can be discussed with the customer, but it cannot have a crew committed to it and it cannot be the reason another job gets pushed. Only confirmed work earns a crew.
Flooring is a useful trade to reason about because the dependency chain is unforgiving and internal to the job. As the same operator put it, "you can't sand before the install is done, and you can't move furniture back before the finish cures. So one delay on Monday means you're rebooking three crews for the rest of the week." The tighter your internal dependencies, the more expensive an unscreened commitment is, because it never slips alone.
Build a bank of filler work, not empty slack
Every competing article on this topic tells you to plan crews to 80 or 90 percent of available days and leave the rest as slack. It is directionally right and almost nobody follows it, for an obvious reason: an empty day is a day you pay for and do not bill. Under pressure, owners fill the slack, and the first delay then cascades exactly as predicted.
Lean construction solved this thirty years ago with a better shape of buffer, the workable backlog: a pool of work that has been fully screened and is constraint free, but that you have not committed a crew to. When the primary task falls through, the lead pulls ready work off the shelf instead of sending people home. Your buffer is made of work, not of emptiness.
Two operators in the threads above reinvented this without the vocabulary. The flooring owner: "I kept a rolling list of small fill jobs (repairs, callbacks, warranty work) that my guys could pivot to if the main job fell through. That way nobody's sitting in a parking lot at 7am texting me 'what now?'" The eight-crew owner went further and used his least reliable jobs as the buffer itself: "I started using those problem jobs as fillers instead of being fully devoted. That way I'm using them more as an advantage rather than a problem."
Tip
Build the backlog on purpose. Aim for two to three days of ready filler work per crew at all times: callbacks, warranty work, punch items, small repairs, shop and yard work, deferred maintenance on your own equipment. Screen these the same way you screen real jobs, or they are not backlog, they are just a list.
A thin backlog is itself a warning. If you cannot name two days of ready work per crew, your screening is not running far enough ahead of your calendar, and the next delay will find you with nothing to send people to.
Home base, and a written rule for who moves
Reassignment decisions made at 6:45am are made badly, by one tired person under time pressure with incomplete information. Take the decision out of the morning.
Give each crew a home base job for the week. Another operator in the r/Contractor thread runs it this way: "crews know their home base job for the week and only get moved if there's a real reason." A home base reduces the number of moves, and makes each remaining move a deliberate act someone has to justify.
Then write the move order down, once, and follow it every time:
- Point the affected crew at backlog work on the same site.
- Point them at backlog work nearby.
- Move the crew whose current job has the most float, not the crew that is easiest to reach.
- Only last, split a crew across two sites.
Splitting is last because it is the most expensive option and it feels like the cheapest. Half a crew on each of two sites means two mobilizations, two setups, two cleanups, and two jobs running slower than either was estimated at. Borrowing one person off crew A to fill out crew B degrades both, and the cost never appears on either job's numbers.
Count your mobilizations
Here is a number almost no contractor tracks and every contractor pays for: how many times per week does each crew change sites?
Every change costs drive time, setup and cleanup, none of which you bill. A contractor in a 2026 r/Contractor thread on moving to four ten-hour days described the effect after his company switched: "Less hours driving and set up/cleanup for the same amount of work being done." Fewer, longer days on a site produced the same output because the fixed cost per visit was amortised over more hours.
You do not have to move to four tens to use that. Just count. If a crew changes sites five times a week, you are paying for five mobilizations to produce four days of work. Getting it to two or three is usually worth more than any scheduling feature you could buy, and it is entirely within your control when you build the plan.
What to measure
Three numbers, and only three.
Percent plan complete. Of the work you committed each crew to on Monday, what share was done by Friday. The Last Planner baseline is about 54 percent. Track it for a month and you will know whether your commitments mean anything.
Reason for the miss. More valuable than the percentage. For every missed item write one word: materials, predecessor, information, inspection, labour, weather, access. After four weeks the list will be lopsided, and the lopsided category is what to fix. Log why, not who.
Mobilizations per crew per week. Cheap to count, immediately actionable.
Be careful with utilization, the metric everyone reaches for. Bridgit's workforce planning guidance notes that two denominators are in common use and they do not produce the same number: billable hours over available hours is the finance definition behind published benchmarks, while project allocation over full allocation is what most planning software reports. The American Institute of Architects puts the benchmark at 60 to 65 percent of total labour dollars, and the 47th annual Deltek Clarity study reports a median of 58.9 percent. If your software says your crews are 95 percent utilized, you are reading allocation, not billable hours, and those benchmarks do not apply.
Whiteboard, spreadsheet, or something built for you
| Setup | Works when | Where it fails |
|---|---|---|
| Whiteboard in the shop | One to three crews, everyone passes through the same building daily | Invisible to the field, no history, no record of why a job slipped |
| Shared spreadsheet | Up to about three or four crews with one owner of the file | No conflict warning, no field reach, version drift the moment two people edit |
| Off-the-shelf field app | Several crews, frequent changes, scheduling is your main pain | Priced per seat, opinionated about your job stages, usually stops at the calendar |
| Custom system | Your stages, screening rules or job types do not fit any product, and the workflow is a competitive advantage | Real build and maintenance cost, and wrong for a shop that has not stabilised its process yet |
A software co-founder working with concrete contractors made the sharpest observation in the r/Contractor thread about why these transitions happen: "most teams don't outgrow Google Calendar because they need more scheduling features. They outgrow it because the amount of coordination around the schedule becomes impossible to manage manually." She also flagged the trap: "A lot of contractors end up replacing their scheduling software a second time because they outgrow the first solution."
And the honest counterargument, from a general contractor in the same thread when the OP mentioned hiring developers: "Would caution against hiring devs. Anything in software that is custom has a maintenance cost or can break."
That is fair, and worth saying plainly by a company that builds custom systems. A custom build is wrong when your process is still changing weekly, when an off-the-shelf product genuinely matches your stages, or when nobody internally owns the system. It is right when you have a screening and commitment process that works and every product you try forces you to abandon half of it. Building software around a process you have not proven just encodes the confusion. If you are earlier than that, the best software for a two man crew covers the smaller end, including when another subscription is the wrong answer.
The Monday routine
The whole system fits in about 40 minutes a week plus 10 minutes a day.
- Thursday, 20 minutes. Screen every job entering the next four weeks against the eight constraint categories. Each open constraint gets one named owner and a date it must clear by.
- Thursday, 10 minutes. Move anything fully cleared from tentative to confirmed. Anything still open stays tentative and does not get a crew.
- Friday, 10 minutes. Build next week's grid from confirmed work only. Assign each crew a home base. Check the backlog has two to three ready days per crew.
- Daily, evening. One named lead per crew sends a two-line end of day report: what got done, what is blocking tomorrow. Build tomorrow's plan from that, not from the 6:45am phone call.
- Friday, 10 minutes. Score percent plan complete and write one word next to every miss.
An operator in the thread put the timing point better than any vendor page does: "building the schedule the night before instead of the morning of. even a rough one. forces you to think through who's where and what's likely to go sideways instead of finding out at 7am."
The bottom line
Multi-crew scheduling advice fails because it treats the schedule as the thing to improve. The schedule is downstream. Half of what gets planned does not happen, coordination failures cause four times more delay than weather, and both are decided before anything reaches a calendar.
Screen the work. Commit only to what is ready. Bank ready work for when it is not. Give each crew a home base and write the move rules down. Then pick the tool that carries those decisions to the field, because a tool carrying an unreliable plan only makes you unreliable faster.
Sources
- Lean Construction Institute, Last Planner System: 54 percent average weekly plan completion.
- Ebbs, P., 5 Levels of the Last Planner System, Lean Construction Blog: constraint screening, workable backlog, percent plan complete and reasons for missed commitments.
- LookAheadWall, Building a Make-Ready Process with Last Planner System Software: the constraint categories and the definition of ready.
- SciELO systematic review of construction delay causes, via OpenSpace, Construction project delay statistics: cause breakdown, plus the McKinsey and ScienceDirect figures cited there.
- Bridgit, What is your workforce utilization rate telling you: the two utilization denominators, AIA 60 to 65 percent benchmark, Deltek Clarity median of 58.9 percent.
- r/Contractor, How do you schedule for multiple projects and a growing crew: operator quotes on filler jobs, tentative starts, home base and evening planning.
- r/Construction, Does anyone have any recommendations for a scheduling software for crews: a 20-crew shop running Excel.
- r/Contractor, Switch to 4/10s: fewer site changes producing the same output.