Oct 26, 2026
Planning IT Projects When Hardware Won't Show Up on Time
A delayed hardware shipment can cost an MSP more than a few days. It can leave engineers waiting, push installations into other projects and eat into margins through repeated rescheduling. You can’t control when the equipment arrives, but you can plan for the uncertainty. Here’s how to build an IT project schedule that keeps work moving and makes the impact of a delay clear before it becomes a bigger problem.
The Box That Didn't Come
The firewall refresh was planned for the second week of the month. Engineers were booked. The client cleared a maintenance window and told their staff.
Then the distributor sent an email. The switches were backordered. New estimate: five weeks.
Now the installation needs a new date, the engineers need other assignments and the client wants to know whether the deadline still holds. Every adjustment takes time that wasn’t included in the original estimate.
The shipment is the immediate problem. But the bigger question is whether your plan shows everything that depends on it.
Why This Matters Now
In a July 2026 survey of channel partners across Europe and Asia Pacific, Westcon-Comstor found that 87% are taking steps to deal with hardware price volatility and memory shortages, with project delays as their primary concern. About 23% had already seen projects delayed or cancelled, and 52% had moved hardware purchases earlier to limit their exposure.
The survey also found 60% of partners responding by improving infrastructure capacity planning. That is a useful signal. The partners getting ahead of this aren't just ordering sooner. They are planning differently.
Here are six ways to account for hardware delays in your project plans and limit the disruption to your team, clients, and margins.
1. Make Procurement a Phase, Not a Footnote
In many project plans, hardware is a single task: "Order equipment." It gets checked off when the order is placed, and the plan continues as though the gear is already on the shelf.
Break it out. Ordering, shipping, receiving, staging and configuration are separate steps with separate durations. When procurement has its own phase with real dependencies, a late shipment shows up in the plan the moment it happens, not the morning the engineer arrives on site.
2. Separate What Needs the Hardware from What Doesn't
Not every task in an infrastructure project is waiting on a box. Discovery, documentation, configuration planning, user communication, licensing and cloud setup can usually move ahead without it.
When the plan clearly shows which tasks depend on the shipment, your team can keep making progress while it is in transit. This is exactly what critical path analysis is for: knowing which delays actually move your finish date and which ones don't.
3. Plan With Ranges, Not Promises
A distributor's estimate is a guess with a date attached. Build your schedule to reflect that.
Use realistic durations for delivery based on what you have actually seen from that vendor recently, not the best case on the quote. Build a little breathing room between delivery and installation so a few days of slip don't ripple through every task after it. And when the client has a hard date, like an office move or a lease ending, work backward from it to see exactly how much room you really have.
4. Order Earlier, and Know Your Alternates
For your own projects, that means two things. First, place orders as soon as the client approves, even if installation is weeks away. Second, decide on acceptable substitutes during scoping, so a backorder becomes a quick decision instead of a new round of approvals.
It is also worth shortening how long your hardware quotes stay valid. When prices are moving, a 30 day quote can turn into a margin problem by the time the client signs.
5. Protect Your People, Not Just the Schedule
When hardware is late, the hidden cost is the engineer who was booked and now has nothing to install. Or worse, the engineer who gets double booked when two delayed shipments land the same week.
This is where your schedule and your team's capacity have to move together. If one project slides three weeks, someone needs to see what that does to the other twelve projects that engineer is assigned to. In Moovila, schedules update automatically when a dependency moves, so you can see the knock on effect across your team before the week falls apart.
6. Tell the Client Before They Ask
Clients understand supply problems. What they don't like is finding out late.
When a delivery date moves, share it with the new expected range, what your team is doing in the meantime, and what decisions you need from them. That turns a delay into a moment that builds trust, as long as you keep those updates short and useful. It also helps to agree early on what the client is responsible for when timelines shift.
Frequently Asked Questions
How much buffer should I add for hardware delivery?
There is no single number. Start with what you have actually experienced from that vendor and product line in the last few months, then add room based on how critical the date is. Track promised versus actual delivery so your estimates improve over time.
Should I start a project before the hardware arrives?
Usually, yes. Most projects have planning, documentation and configuration work that can move ahead. Just make sure the plan clearly separates that work from tasks that depend on the shipment.
What should I do if the hardware is delayed after work has started?
Update the delivery date in the plan right away, check what it does to your finish date and your team's other assignments, and tell the client with a new expected range and next steps.
The Shipment Is Out of Your Control. The Plan Isn't.
No one can make the distributor ship faster. But you can build plans that expect delays, keep work moving around them, and show everyone the real impact the moment something changes.
That is the difference between a late box and a late project.
If you'd like to see how Moovila keeps schedules and resources in sync when dates move, book a demo here.
IT Services
