Cutstruct

Before You Blame the Contractor for Delays, Look at Your Procurement Process

A project is three weeks behind schedule. The developer is frustrated. The project manager is under pressure. The contractor is getting calls. The usual question comes quickly:

“Why isn’t the contractor moving faster?”

Sometimes, that is the right question.

But sometimes the contractor is waiting for materials or an approval or a payment.

Or a revised drawing, or even a supplier who promised delivery two weeks ago.

And by the time everyone starts asking why the project is delayed, the original cause has already been buried underneath several other problems.

Construction delays rarely have one cause.

A 2024 World Bank review of 260 papers on construction procurement and execution found that delays are widespread. The literature reviewed reported that about 74% of construction projects globally experienced delays, with project duration averaging 42% longer than the original contract duration. In the African evidence reviewed, 75% of projects were reported as delayed, with delays averaging 53% of the original contract duration.

The same review identified funding constraints and delayed payments, design and scope changes, and shortages of materials and equipment among recurring causes.

So before the contractor takes the blame, there is another question worth asking:

Did the project give the contractor what they needed to keep moving?

A contractor cannot build with an empty site

This sounds obvious.

Yet it is one of the easiest things to overlook when reviewing project delays.

A contractor might have labour available.

The equipment might be ready.

The next construction activity might be clearly defined.

But if the required material isn’t on site, that activity cannot start.

Research published in Scientific Reports found that material shortages are a major source of jobsite productivity loss. The study linked late ordering and delivery, poor communication, fragmented responsibilities and differences between design and construction to productivity problems, budget overruns and delays.

Consider a simple example.

A project is ready for reinforcement work.

The contractor has the workers.

The drawings are available.

The site is ready.

But the reinforcement bars are still with the supplier.

The contractor isn’t necessarily behind because the contractor is slow.

The work is behind because the input required for the work hasn’t arrived.

That distinction matters.

The delay often starts before the site feels it

Procurement delays are deceptive because the first visible problem often appears on site.

The workers are waiting.

The contractor complains.

The developer gets a phone call.

But the root cause might have happened days or weeks earlier.

Perhaps the material request wasn’t raised early enough.

Perhaps the quantity wasn’t confirmed.

Perhaps the quotation took too long to approve.

Perhaps payment was delayed.

Perhaps the supplier didn’t have sufficient stock.

Perhaps the delivery date wasn’t properly coordinated with the construction programme.

By the time the site team notices the problem, several decisions have already contributed to it.

This is why procurement should not be treated as an activity that happens after project planning.

It is part of project planning.

Your construction programme and procurement plan should speak to each other

A construction schedule might say:

Week 8: Reinforcement works

But that information alone isn’t enough.

Procurement needs to answer:

What reinforcement is required? How much is required? When does it need to arrive? Who is supplying it? How long is the lead time? Has the quotation been approved? Has payment been made? Has the supplier confirmed availability? How will delivery reach the site? What happens if the supplier misses the delivery window?

If those questions aren’t connected to the project programme, procurement becomes reactive.

The site reaches the activity.

Then someone starts looking for the material.

That is when the emergency calls begin.

“We ordered it” is not the same as “it’s ready for site”

This is one of the biggest procurement mistakes.

A purchase order has been issued.

Everyone assumes the problem is solved.

It isn’t.

There is a difference between:

Requested | Quoted | Approved | Ordered | In production | Dispatched | In transit | Delivered | Received and verified

Each stage carries its own risk.

A project team that only knows that “the material has been ordered” still doesn’t have enough information to plan the site confidently, and that is why delivery visibility matters.

Cutstruct’s developer platform, for example, is designed to centralise requests, quotations, approvals and deliveries, with real-time tracking across projects and sites.

The objective is straightforward:

Know where the material is before the site starts waiting for it.

The five procurement questions every project team should ask

When a project is behind schedule, procurement should be part of the delay investigation.

Start with five questions.

1. Was the material requirement clearly defined?

If the specification or quantity wasn’t clear, procurement couldn’t start properly.

2. Was the material requested early enough?

A supplier cannot deliver what nobody ordered.

3. Was the supplier capable of fulfilling the order?

A competitive price means little if the supplier cannot meet the required quantity or delivery date.

4. Was payment processed on time?

A supplier’s ability to fulfil an order can depend on the agreed commercial terms.

5. Was delivery tracked against the project schedule?

Knowing the expected delivery date is different from knowing whether the delivery is actually on track.

These questions create a better conversation than:

“Why is the contractor slow?”

Procurement problems don’t stay in procurement

This is the part developers often underestimate.

A delayed material can trigger a chain reaction.

Material delay → Labour waiting → Activity pushed back → Other trades affected → Project timeline extends → Site overhead continues → Financing period increases.

One missed delivery can therefore create costs far beyond the original purchase order.

That is why procurement should be measured by more than:

“Did we get a good price?”

A stronger procurement process also asks:

Did the material arrive when the project needed it?

Did it meet the required specification?

Was the supplier reliable?

Was the delivery properly coordinated?

Did the purchase support the project schedule?

The cheapest procurement decision is not useful if it creates an expensive delay.

But let’s be fair to the contractor

There is another side to this.

Sometimes the procurement process is fine.

The materials arrive.

The drawings are available.

Payments are made.

The site is ready.

And the contractor still doesn’t deliver.

That is a contractor performance problem.

Poor labour management, weak supervision, inadequate planning, low productivity and failure to meet contractual obligations are legitimate causes of delay.

Procurement should not become an excuse for poor execution.

The point is not to move all the blame from contractors to developers.

The point is to find the actual cause.

A good project management process should separate:

Contractor-caused delays

from

Procurement-caused delays

from

Client-caused delays

from

Design-related delays

from

External events

That makes accountability more useful.

The problem with fragmented procurement

One of the reasons procurement delays are difficult to identify is that information often sits in different places.

The material request is in one WhatsApp conversation.

The quotation is in an email.

The approval is somewhere else.

The supplier’s phone number is saved on someone’s personal phone.

The payment confirmation is with finance.

The delivery update is with the site manager.

When something goes wrong, everyone has part of the story.

Nobody has the whole picture.

That makes it harder to answer a basic project question:

“Where is the material we need, and when will it arrive?”

A centralised procurement process creates a clearer trail from request to delivery.

That is one of the areas Cutstruct focuses on: connecting material requests, sourcing, quotations, approvals and delivery within a single procurement workflow.

Procurement should be part of the project schedule

A construction programme tells you what needs to happen and when.

A procurement plan should tell you what needs to arrive before each activity can happen.

Those two plans should work together.

If reinforcement work starts on Monday, procurement should already know what needs to be on site before Monday.

If roofing begins in three weeks, the required materials should already be moving through the procurement process.

If a specialised product has a long lead time, the project shouldn’t wait until installation week to start sourcing it.

This sounds simple.

But simple systems are often the ones that prevent expensive problems.

Better procurement creates better project control

Construction will never be completely predictable.

Weather changes.

Designs change.

Prices move.

Suppliers experience problems.

Clients change their minds.

Unexpected site conditions appear.

The goal isn’t to eliminate every possible delay.

The goal is to reduce the delays created by poor planning and fragmented processes.

That starts with knowing:

  • What the project needs
  • When it needs it
  • How much is required
  • Who is supplying it
  • What it costs
  • When it will arrive
  • Whether the delivery is on track
  • What happens if it isn’t

That information gives project teams something valuable:

time to act before the site is affected.

Before you call the contractor

The next time a project falls behind schedule, don’t start with:

“Why isn’t the contractor working?”

Start with:

“What was supposed to be happening, what was required for it to happen, and did the project provide those requirements on time?”

If the materials were available, the site was ready and the contractor still failed to perform, you have a contractor performance issue.

If the contractor was waiting for materials that were never properly planned, approved, sourced or delivered, the conversation needs to start somewhere else.

That is the difference between blaming delays and managing them.

At Cutstruct, we believe procurement should support project execution rather than become another source of uncertainty. Our platform connects construction material sourcing from request through delivery, giving developers greater visibility across suppliers, orders, spending and project workflows.

Because a project doesn’t fall behind only when workers stop working.

Sometimes, it falls behind when the right material never reaches the site.

And by the time the contractor gets blamed, the delay has already happened.

Build Smarter. Build Faster. Build Better.

Before You Blame the Contractor for Delays, Look at Your Procurement Process | Cutstruct Blog