Every schedule ever drawn assumes the bodies, the machines, and the material will be there when the wall says "start." On a whiteboard that assumption is invisible. On a jobsite it's the thing that sinks you. You can sequence a floor perfectly, sell the plan in the coordination meeting, and still lose the week because the framers you were counting on got pulled to another job, the boom lift you needed showed up Wednesday instead of Monday, or the door frames sat on a truck at the yard while your carpenters stood around.
Resource planning is the unglamorous half of scheduling that decides whether the pretty part is real. It's the work of matching people, equipment, and material to the tasks in front of you, over a window you can actually see and control. Good field management software doesn't do that thinking for you, but it makes the collisions visible early enough that you can fix them on paper instead of on the deck. Here's how that actually works in practice.
Start With the Look-Ahead, Not the Master Schedule
The master CPM schedule is where resource planning goes to die. It's too coarse and too optimistic to tell you whether next Tuesday is deliverable. Resource planning lives in the look-ahead — the three-to-six-week window where the work is close enough that you know which specific crews, which specific lifts, and which specific submittals it depends on.
The discipline is simple: for every activity in that window, name what it needs before you commit to the date. Not "labor" in the abstract, but "two carpenters and a laborer, Tuesday through Thursday, needs the layout signed off Monday." When you load resources onto a weekly work plan at that grain, the shortages announce themselves. You'll see that you've promised the same three-man crew to two locations on the same day, or that the concrete pour and the underground rough-in both want the same excavator Wednesday morning. That's the whole game — catching the double-booking while it's still a line on a screen.
Labor: Plan the Crew, Not the Headcount
The most common resource-planning mistake is thinking in totals. "I have twelve guys this week" tells you nothing useful. Twelve guys split into the wrong trades at the wrong locations gets less done than eight planned well. What matters is crew composition against the specific work fronts you're opening.
Load your labor by crew and by location, day by day, and watch for three failure modes:
- The stacked front. Two crews assigned to the same physical area on the same day. They'll trip over each other, one will end up watching the other, and you'll swear productivity dropped for no reason. It didn't — you overloaded the space.
- The starved front. Work is available and ready, but you've committed the crew elsewhere. This is pure lost float. If a location is constraint-free and you're not working it, that's a planning miss, not a manpower shortage.
- The phantom crew. You planned around a sub's foreman showing up with six men. He shows with three because his other job ran long. If your plan can't survive that, it was never a plan — it was a wish.
A rule of thumb from years of watching this go sideways: never plan a week that assumes 100% of promised manpower shows up. Build to about 85–90% of committed labor and keep a short backlog of ready, low-dependency work — punch, cleanup, prep for next week — that you can flex a light crew into when someone comes up short. When the software shows you a crew's daily load next to the work that's actually released, that backlog stops being guesswork.
Equipment: The Constraint You Book Too Late
Labor you can often shuffle same-day. Equipment you cannot. A scissor lift, a boom lift, a crane pick, a concrete pump — these have lead times, rental clocks, and delivery windows, and they're frequently shared across trades who all assume it's theirs.
The trap is that equipment need is downstream of activities that live in different crews' heads. The drywall hangers need lifts for the high work. So do the mechanical guys hanging duct and the electricians pulling the overhead. If nobody plotted those lift-days against each other, three trades show up Monday expecting two lifts you rented one of.
Forecast equipment off the look-ahead the same way you do labor: which activities in the next four weeks need which machine, on which days, and does the total demand ever exceed what's on site. When it does, you have three moves and you want to make them a week out, not that morning — add a unit, resequence so the trades share by shift or by zone, or slide one activity. All three are cheap on paper and expensive at 6:45 a.m. with idle crews watching. Watch your rental clock too: a lift that sits three weekends because you booked it early for a Friday task is money leaking with nothing to show. Tie the delivery to the day the work actually releases.
Material: Tie Deliveries to the Work Front, Not the Calendar
Material planning fails in two directions. Order too late and you idle crews. Order too early and you're storing pallets in the way of the work, moving them twice, and eating damage and theft. The fix is to plan procurement backward from the look-ahead, with the lead time and a real buffer built in.
Practical sequence for anything on a lead time:
- Find the activity in the look-ahead and its planned start.
- Subtract the supplier's honest lead time — the real one, not the optimistic quote.
- Add a buffer. For routine stock, a few days. For long-lead or fabricated items — switchgear, custom glazing, structural steel, elevators — you're planning in weeks or months, and that horizon belongs on the schedule as its own constrained line, not buried in someone's inbox.
- Set the order-by date, and treat a missed order-by date as a schedule threat the same as a blown inspection.
Then stage to the front. Material should land close to the calendar week it gets installed, in the zone where it's used. When your weekly work plan shows a delivery date sitting next to the activity that consumes it, a late order stops being a surprise you discover on install day and becomes a red flag you saw two weeks out.
Leveling: Smooth the Peaks Before They Become Overtime
Loaded honestly, most schedules are lumpy. One week wants twenty electricians, the next wants six. That saw-tooth is expensive — you can't hire and lay off week to week without killing quality and morale, so the peaks become overtime and the valleys become guys leaning on brooms.
Resource leveling means nudging non-critical activities within their float to flatten the demand curve. If two heavy-labor tasks both land in week three but one has four days of float, slide it into week four and pull the peak down. You're not compressing the schedule — you're smoothing it, so a steadier crew stays busy without swinging. The value of doing this in software rather than on paper is that when you drag one activity, you immediately see what it did to the resource histogram and whether it created a new collision somewhere else. That feedback loop is the difference between leveling and just moving problems around.
Make Resource Conflicts a Constraint, Not a Surprise
The Last Planner mindset is worth borrowing here: an activity shouldn't be committed to a weekly work plan until its constraints are cleared, and a resource shortage is a constraint like any other. Missing manpower, an unavailable lift, undelivered material — each one is a reason the task isn't ready. Treating them that way, in a shared constraint log everyone can see, does something a spreadsheet buried on one laptop never will: it forces the conversation before the commitment.
This is where field management software earns its keep. Not because it "optimizes resources" — that phrase means nothing on a jobsite — but because it puts the labor, the equipment, and the material demand on one picture, in the same window, updated as the plan changes. Tools built for short-interval scheduling, LookAheadWall among them, are useful here precisely because they're location-based and trade-flow aware: you see the crew load by area, the sequence dependencies between trades, and the shared schedule the subs are working from, all in the look-ahead where the decisions actually get made. The subs seeing the same plan matters more than any feature — half of resource conflicts are just two foremen who each thought the space, the lift, or the week was theirs.
Close the Loop: Plan Versus Actual
None of this improves unless you look back. At the end of each week, compare what you planned to deploy against what you actually got done, and be honest about why the gaps happened. Track your Percent Plan Complete — of the tasks you committed to, how many finished — and when one doesn't, log the real reason. Over a month, those reasons cluster, and the pattern tells you where your resource planning is weak.
If manpower shortfalls keep showing up, you're over-promising labor and need to build to a lower commitment. If material lateness dominates, your order-by discipline is broken and needs a hard date on the schedule. If it's equipment, you're booking too late or not sharing across trades. The reason codes turn a vague sense that "we keep falling behind" into a specific, fixable problem — which is the entire point of planning resources on purpose instead of reacting to whatever shows up at the gate.
Resource planning isn't a feature you buy. It's a habit: name what each task needs, put the demand on one picture, catch the collisions a few weeks out, and check yourself every Friday. The software's job is just to make that habit fast enough to actually keep, week after week, on a job that never stops moving.