Most builds don’t run late on site.
They fall behind schedule months before the first sod is turned – in conference rooms, on an estimate set no one took the time to double check, on a programme that seemed aggressive before pricing. Before ground is broken and that first excavator rolls in, the results are pretty well determined. Nobody realizes it though.
Preconstruction planning is where that outcome gets decided.
Do it right and building can feel mundane. Do it wrong and every week is chaos.
Here’s how the stage really works…
What’s inside:
- What Preconstruction Planning Actually Covers
- Why Projects Are Late Before They Start
- 5x Preconstruction Moves That Protect The Programme
- How To Tell If Preconstruction Is Working
What Preconstruction Planning Actually Covers
Preconstruction planning is everything that happens between “we’re doing this” and “we’re building this.”
That’s scope definition, budget, programme, procurement route, site investigation, permitting and risk register. When done properly, it turns fuzzy wishful thinking into something buildable, with actual dates.
Done badly, it turns into a very expensive guess.
Most teams think of this stage as filling out paperwork. Wrong. Think of preconstruction as your LAST CHANCE. It’s the only stage of a project where changing your mind costs little. Slide a wall on a drawing an hour of work. Slide that same wall after the slab is poured…you get the idea. Extra month, change order and an argument no one wins.
This is also the point at which your digital transformation strategy starts to pay for itself. Clash detection, shared data environments, 4D programme modelling, live cost tracking – all these should be up front on a job, not retro-fitted halfway through. Owners who implement digital transformation as a planning discipline – not just a software purchase – catch issues while they are still lines on a screen. Those who bolt tools on at a later date simply capture their hold-ups in higher resolution.
Same technology. Completely different result. The only variable is when it gets used.
Why Projects Are Late Before They Start
The numbers here are brutal.
Autodesk surveyed industry research which revealed that 98% of megaprojects run late or go over budget. Large projects average about 20% late. That’s not bad luck. That is a trend. Trends are caused by process.
Nor is it much better on smaller work. A recent UK study found that 95% of projects were delayed, and the median delay exceeds 200 days. A twelve month job slips silently to eighteen months.
So what is actually going wrong? Three things, mostly.
Design is not complete. Design related issues impact almost 45% of all projects worldwide and cost approximately six months on average. 60% design is accepted practice when breaking ground and ensures rework.
Risk sits with nobody. Ground conditions, long lead items, utility connections, planning approvals. If each one doesn’t have a named owner in preconstruction they all become site problems later.
Fact: The baseline programme is fiction. Analysis of recent large scheduling datasets revealed that only approximately 12% of baseline programmes achieve a high quality standard. If it’s wrong on day one, then every update thereafter will be wrong as well.
Notice that they are all decisions, not accidents. That’s actually the good news, because decisions can be reversed.
5x Preconstruction Moves That Protect The Programme
Here are habits that successfully keep projects on schedule. They aren’t complex. Most projects still neglect at least three of them.
Lock The Scope Before Pricing It
A price against a vague scope isn’t a price. It’s a placeholder.
Document the scope in simple terms, include what’s out of scope and have all stakeholders sign for the same copy. Scope document ambiguities always become variations onsite, and that’s where programmes silently die.
Investigate The Ground Early
Geological surprises are among the oldest reasons builds go over schedule… and among the easiest to prevent.
Boreholes, surveys, services scans and contamination tests cost fraction of what lost excavation money. Carry them out before the programme is baselined, not when the piling rig is sat idle on day rates.
Build The Programme Backwards
Start at the handover date and work back through every dependency.
Reverse scheduling reveals the activities that truly dictate the timeline of the project: long lead procurement, statutory approvals, seasonal restrictions and commissioning windows. Then place your float where the risk lies, not evenly across the bar chart. Equal floats are lazy floats.
Run A Constructability Review With Site People
Designers design. Builders build. The gap between them is where delay lives.
Involve superintendents, foremen and specialist subcontractors in design review before the drawings are finalized. They’ll find the access issue, sequencing conflict and unrealistic tolerance in about ten minutes. Applied to the drawing stage, field experience is the cheapest construction insurance you can buy.
Set Up The Data Before Mobilisation
Decide upfront how information is going to move around the project.
One model. One document register. One version of the programme. One approval route. If teams commit to this in preconstruction they can spend the build managing work. If not they spend the build managing confusion. And confusion costs money.
How To Tell If Preconstruction Is Working
Here’s a quick test.
Ask three people working on the project what the critical path is. If you get three different answers, preconstruction’s not done yet — even if the drawing register says so.
A few other signals worth watching:
- RFIs in the first month are low, not overwhelming
- Long lead items were ordered before mobilisation
- The risk register has named owners and dates, not just descriptions
- Contingency is based on identified risk, not a round percentage
If those boxes are checked, that build will usually play nice. When they’re not, the site team expends energy reacting rather than sequencing.
And reacting is always slower.
Bringing It All Together
Preconstruction planning is not simply build up time. That is when the schedule is written whether you want to believe it or not.
One hour spent agreeing scope, testing ground assumptions, stress testing your programme and clarifying information flows saves you days at the back end of the project. “Delays occur during construction, but they were incubated long before” and the data from across the industry repeats this message.
To quickly recap:
- Define the scope properly before anyone prices it
- Investigate the site before the programme gets fixed
- Build the schedule backwards from handover
- Review constructability with the people who will build it
- Agree the data and approval process before mobilising
None of that requires new technology. That just requires the discipline to throttle back at the only stage where throttling back remains inexpensive.
Do that, and late becomes the exception instead of the standard.
