Why 4D Planning still isn’t taken seriously - until its too late
We've seen it tens if not hundreds of times.
A project team is brought together - often having had no involvement in delivering the tender that won the work, and in some cases completely new to the business. Either way, their last project had its fair share of problems. Unmanaged interfaces, access issues, general drag and delay. But hey, this is a new project. Surely lightning can't strike twice?
Wrong.
It feels like the majority of people assume that everything will be delivered safely and on time, utilising the same tools and processes from the last project that had problems. Optimism bias. They head into the scheme having done their best before starting on site - they've reviewed all the design information, developed a detailed construction-ready programme, engaged with the whole team. The same meetings with subcontractors and stakeholders. Spreadsheets, Gantt charts, everyone around the table. They genuinely believe everything has been explored, that everyone is on the same page, and that the team collectively understands what the next six months looks like.
Then something goes wrong.
Everyone is scrambling to figure out what happened and why. How could this happen with all the upfront effort that went into planning?
Turns out, reviewing information and understanding how a project actually builds are two very different things.
A 2D drawing tells you what needs to be built. A programme tells you when. But neither tells you how - in what order, in what space, with what access, alongside what other trades. That gap between the plan and the physical reality of construction is exactly where projects get into trouble. And it's exactly the gap that 4D planning is designed to close.
The problem is that 4D still gets brought in too late, if it gets brought in at all.
On most projects where we're engaged, the sequencing decisions have already been made. The logistics strategy is agreed. The programme has been issued. By that point, a 4D model can reflect those decisions - it can visualise what's already been planned - but it can't meaningfully influence them. The window where 4D adds real value is earlier than most people think: during pre-construction, when the sequence is still fluid and the cost of changing it is low. That's when the hard questions need to be asked. Not after the subcontract packages have been let.
This isn't a technology problem. The tools exist. The capability exists. The issue is perception.
4D planning is still widely seen as a visualisation exercise - something you produce for a client presentation, a bid, or an opening ceremony video. The animated flythrough is what people think they're buying, so it gets treated as a communications deliverable rather than a planning one. When budgets tighten, it's one of the first things cut, because the people cutting it don't yet understand what it was protecting them against.
We see the consequences of that in patterns that repeat across projects and sectors. A logistics route that conflicts with a neighbour access agreement nobody had modelled spatially. Trades programmed to work in areas the schedule shows as complete but the model would have flagged as inaccessible. A handover sequence that works perfectly on the Gantt but creates a fire compartmentation problem in practice. These aren't unusual edge cases. They're the predictable result of planning in two dimensions when the problem is three-dimensional and time-dependent.
The fix isn't complicated, but it does require a shift in when and how 4D is commissioned. It needs to sit inside the pre-construction appointment, not get bolted on after contract award. Clients need to ask for it in their briefs rather than waiting for a contractor to offer it. And the industry needs to stop measuring the value of 4D by the quality of the animation and start measuring it by the quality of the decisions that animation helped to make.
The projects where 4D planning made the biggest difference weren't always the ones with the most sophisticated models. They were the ones where someone asked the hard sequencing questions early enough to actually do something about the answers.
Lightning does strike twice. It strikes on almost every project that doesn't take planning seriously enough, early enough. The teams that avoid it aren't the ones who got lucky - they're the ones who looked at what the last project got wrong and decided not to carry the same assumptions into the next one.