Plan approved hai. Drawings freeze ho chuke hain.
Phir bhi site execution har week drift kyun ho raha hai?
Most founders think this is a discipline problem. The site team just isn’t following instructions.
But that’s rarely what’s actually happening.
Plans don’t fail because site teams don’t respect them.
They fail because nobody clearly defined what’s non-negotiable and what can be adjusted.
Think about how it usually plays out.
The plan gets made at head office. It’s reviewed in meetings. Gantt charts look good. Everyone nods. Then it gets handed over to site.
After that? Pressure takes over.
Material delivery gets delayed by a week. Client suddenly wants a design change. Labour doesn’t show up because of weather. A critical approval is stuck.
At that moment, what does your site team ask themselves?
Not “what was the plan?”
They ask: “What will help us move today?”
And that’s where deviation starts.
Your site engineer sees idle labour. He shifts them to another activity that wasn’t scheduled yet because keeping them productive feels better than having them sit around. Makes sense in the moment, right?
Your project manager gets a call that pipes have arrived early but the approved storage area isn’t ready. He tells them to offload near the boundary wall. Small adjustment.
Your QC inspector is supposed to hold up work until test reports come. But the client is visiting tomorrow and there’s pressure to show progress. So he lets it slide with a mental note to “check it later.”
None of these people are being careless. They’re reacting to reality.
But each small deviation compounds. And within two weeks, the site is running on a completely different sequence than what was planned.
The second problem is ownership.
When deviations happen and there are no real consequences, what message does that send?
Or worse, when management themselves override the plan during an emergency, saying “bas yeh waala kaam nikal do, baaki baad mein dekhenge,” what does the team learn?
They learn that following the plan is optional. That progress matters more than process.
And once that pattern sets in, no amount of monitoring fixes it. You can do more site visits, send more WhatsApp reminders, create more check-in calls. Doesn’t matter.
Because the culture has already shifted. Execution continues, but alignment is lost.
So if your site teams aren’t following the plan, don’t start by correcting execution.
Start by checking whether your plan was actually usable on site in the first place.
Does it clearly state what absolutely cannot change versus what has flexibility? Does your site team know which activities can be swapped and which sequence is locked?
Who has the authority to approve deviations? Is it the site engineer, the project manager, or does everything need to come back to you? Because if that’s unclear, people will make their own calls.
What happens when materials get delayed or clients change their mind? Is there a defined escalation process, or does everyone just scramble and hope for the best?
These aren’t execution problems. These are planning problems.
In EPC, plans don’t fail at the site. They fail before the site ever begins execution.
If you’re dealing with this in your projects and want to figure out where your planning is breaking down, let’s talk. Comment below or send me a message.
Thanks for watching.
