Menu
About Us Contact
Login Join the Waitlist

How Subcontractor Management Software Supports Procurement

Related Dashboard Feature: Lookaheads

The schedule doesn't fail on the day the wall goes up. It fails six weeks earlier, when nobody put the long-lead package on order and the submittal sat in someone's inbox. By the time the framing crew is standing there with nothing to hang, the damage is done — you're just finding out about it late.

Most people think of procurement and scheduling as two different departments talking to each other through email. On a well-run job they're the same conversation. Material availability is a constraint on the work, exactly like manpower or a preceding trade being finished. Treat it that way and a lot of the fire drills disappear. This is where good subcontractor management and scheduling tools earn their keep — not by ordering material for you, but by making the gap between "we planned this work" and "the material is actually here" impossible to ignore.

The schedule is your bill of materials, whether you use it or not

Every activity in a look-ahead has material behind it. Metal studs and track before framing. Wire, boxes, and MC before rough-in. Ceiling grid and tile before the ceiling closes. When you build a weekly work plan and a two-to-six week look-ahead, you're also — implicitly — building a procurement schedule. The problem is most teams never make that second schedule explicit. The work dates live in the scheduling tool and the PO dates live in someone's head or a spreadsheet that hasn't been opened since the buyout.

The fix is boring but it works: for every activity entering your look-ahead window, ask one question — is the material for this ordered, in transit, or on site? If you can't answer, that activity isn't ready, and it shouldn't be a commitment on the weekly work plan. It's a candidate, at best. Tools that let you tag an activity with a material-readiness status make this a two-second glance instead of a phone call. But you can do it on a whiteboard too. The discipline matters more than the software.

Work backward from the need date, not forward from today

Here's the mistake I see constantly. A super looks at a three-week look-ahead, sees the activity coming, and orders the material that week. For anything with a real lead time, that's already too late. You have to work backward: installation date, minus delivery lead time, minus fabrication or manufacturing time, minus submittal approval time. That's your drop-dead order date, and it's frequently outside your three-week window entirely.

This is exactly why a longer horizon exists. Your one-to-two week plan is for committing crews. Your six-week look-ahead is for catching procurement before it's late. Rough rules of thumb worth keeping in your head:

  • Commodity material (studs, drywall, standard fasteners, common conduit) — days to a couple weeks. You can usually recover from a miss.
  • Engineered or spec'd items (switchgear, custom AHUs, elevators, large chillers, specialty glazing) — 8 to 30+ weeks, and no amount of yelling shortens it. These have to be identified at buyout and tracked continuously, not "found" in a look-ahead.
  • Anything requiring an approved submittal before fabrication — add the full submittal cycle on top of lead time. That's the piece people forget.

The value of scanning the six-week window every single week is that lead-time items keep sliding into view before they become emergencies. When an activity moves — and it always moves — its need date moves with it, which means the honest order date moves too. A rolling look-ahead that you actually update surfaces that drift. A static bar chart printed in the trailer does not.

Submittals are the silent schedule killer

I'll say it plainly: on the jobs that fall apart, it's rarely the field work that sinks them. It's the submittal-and-procurement chain that ran late and quietly ate the float before anyone was watching the field.

You cannot fabricate a spec'd item until the submittal is approved. So the real chain for a long-lead piece is: submit → review → approve (or resubmit, which is where weeks vanish) → release for fabrication → fabricate → ship → deliver. If a chiller needs 12 weeks after release and the submittal takes 4 weeks of back-and-forth, you're 16 weeks out minimum, and that's if the first submission is clean.

Put submittal review activities on the schedule as real work with real durations. A submittal log that lives separate from the schedule is how a two-week resubmittal turns into a mechanical room that isn't ready at turnover. When your subcontractor management platform links submittal status to the affected activities, an unapproved submittal shows up as a red flag on future work instead of a surprise. That's the whole game — connecting the paperwork constraint to the field date it threatens.

Delivered to the yard is not the same as delivered to the work

A delivery date on a PO tells you material hit the site. It does not tell you the crew can install it. On a tight urban job or a high-rise, getting studs delivered and getting studs to the 14th floor east wing are two separate logistics problems, and the second one is usually harder.

Good staging is scheduling, not warehousing. A few things that separate a smooth job from a scavenger hunt:

  • Stage by location and installation sequence, not by whatever fits on the truck. Material for this week's area goes where this week's crew is working.
  • Track where things are stored, not just that they arrived. A crew leader spending 40 minutes hunting for the right box of devices is 40 minutes of paid labor you'll never get back — and it happens on every floor if nobody's tracking location.
  • On congested sites, treat hoist and crane time as the real constraint. Your just-in-time delivery is worthless if you can't get it vertical when you need it.

Just-in-time delivery is the goal — material arrives shortly before install, not sitting in the weather getting damaged and walked off for weeks. But JIT only works when your schedule is genuinely reliable. If your dates slip constantly, JIT becomes "material shows up and there's no crew," which is worse than a slightly early delivery. Earn the schedule reliability first, then tighten the delivery window.

Draw the line between GC-furnished and sub-furnished, in writing

The nastiest material gaps aren't the ones you forgot to order. They're the ones where everybody assumed someone else was handling it. The electrician thought the GC was providing the temp power gear. The GC thought it was in the electrician's scope. Now it's Thursday and nobody ordered it.

For every material package, one question has a documented answer: who's furnishing this? Your subcontractors are procuring most of their own material, and that's fine — but "their material, their problem" doesn't survive contact with a missed delivery that idles the whole floor. When you pull subs into the weekly planning conversation, you make them confirm their material is coming for the work they just committed to. That confirmation is the point. A sub who commits to framing next Tuesday should be able to say the studs are on site or on a truck. If they can't, that commitment is soft and you should know it now, not Tuesday morning.

Vendor performance is data you already have — use it

After a couple of jobs you know which suppliers hit their dates and which ones need a call every three days or the order "gets lost." Most teams carry that knowledge in their heads and lose it when the PM rotates off. Writing it down — even loosely — pays off. If a vendor is late on a third of deliveries, you plan a bigger buffer for their material or you expedite proactively instead of hoping. Tracking which items you're constantly expediting, and which vendors keep slipping, turns a gut feeling into a decision you can defend at the next buyout.

What this looks like on a Tuesday

Concretely, here's the weekly rhythm that keeps procurement from blindsiding you:

  1. Scan the six-week look-ahead first, before the three-week. Flag any long-lead or spec'd item whose honest order date is inside the window. Confirm it's released.
  2. Walk the three-week window and mark each activity's material status: on site, in transit, ordered-not-shipped, or unknown. "Unknown" is a task, not a status — go find out.
  3. Cross-check submittals. Any activity riding on an unapproved submittal is not ready no matter how good the field looks.
  4. Only pull activities with confirmed material into the one-to-two week commitment plan. This is the whole discipline — you don't promise crews work that has no material behind it.
  5. In the sub coordination meeting, make each trade confirm material for what they're committing to. Soft answers get flagged.

A look-ahead scheduling tool like LookAheadWall helps here because it puts the field plan and the material constraint in the same picture — you see the activity, its trade-flow sequence, and whether it's actually ready, in one view instead of three. But the tool isn't the insight. The insight is that procurement is a scheduling constraint, and the last responsible moment to fix a material problem is weeks before the crew shows up, not the morning they do.

Get that habit into your weekly plan and the missing-material fire drills stop being a way of life. They become the rare exception — a bad delivery you catch early and route around, instead of a crew standing on a slab with nothing to build.