Most builders have never seen it done properly. That's not a criticism — it's just the reality of an industry where design management has been historically underfunded, misunderstood, and bolted on as an afterthought rather than built into the delivery model from day one.
What passes for "design management" on most projects is actually just document chasing. Someone — usually an overloaded project engineer or a site manager who already has forty other things to deal with — is nominally responsible for following up consultants, issuing RFIs, and somehow making sure the drawings are "up to date." There's no real coordination happening. There's no programme discipline. And there's certainly no one sitting above the design process with a clear view of risk, sequencing, and commercial consequence.
The result? Projects that bleed time and money at every phase transition. CC delays that nobody saw coming. IFC packages that aren't actually construction-ready. Variations that were entirely avoidable. And an OC process that becomes a salvage operation.
Here's what good design management actually looks like — when it's done properly, by someone who knows what they're doing.
It Starts Before the Contract Is Signed
Good design management doesn't begin at project award. It begins in the tender and pre-contract phase, when the design is still fluid and the commercial structure is still being negotiated.
A competent design manager will interrogate the design at tender stage — not to rewrite it, but to identify what's missing, what's unresolved, and what's going to cause pain downstream. What consultants are novated and when? What are the DA consent conditions that will drive design obligations? Is the hydraulic design coordinated with the structural? Has anyone actually checked whether the NCC Section J energy compliance strategy is achievable within the architectural intent?
These questions sound basic. But on most projects, nobody is asking them at this stage. They surface later — during construction, when the cost of the answer is ten times higher.
The commercial value of catching a coordination gap at tender versus catching it during structure is not marginal. It's the difference between a $15,000 design resolution and a $200,000 variation with a three-week programme impact.
The Design Programme Is a Live Document, Not a Milestone List
One of the clearest signs that design management is being done well is the quality of the design programme. Not a static list of submission dates, but a living document that maps design deliverables to construction need dates — working backwards from site.
On a well-run project, the design manager owns a design delivery programme that is integrated into the master programme. Every consultant deliverable has a need date driven by a downstream construction activity. When the programme shifts — and it always does — the design manager is the first to understand what the impact is on design, not the last.
"A schedule is not a plan. It's a hypothesis about the future. The question is whether anyone is actively managing the gap between the hypothesis and reality." — attributed to construction programme specialist context, widely cited in project controls practice.
On a well-run project, the design manager owns a design delivery programme that is integrated into the master programme. Every consultant deliverable has a need date driven by a downstream construction activity. When the programme shifts — and it always does — the design manager is the first to understand what the impact is on design, not the last.
This is where most projects fail. The master programme lives with the planner. The design programme (if it exists at all) lives in someone's inbox. Nobody is active
Consultant Coordination Is a Technical Discipline, Not a Meeting
Coordination meetings are a tool. They are not the output. What matters is what happens between the meetings — the active resolution of clashes, the tracking of open issues, the escalation of decisions that need to be made before they become programme-critical.
Good design management means someone with genuine technical literacy is sitting inside the model, reviewing the overlays, and identifying conflicts before they reach site. It means the structural engineer and the services coordinators are being actively directed — not just invited to a weekly call and asked to "check the drawings."
This is particularly acute on high-rise residential and mixed-use projects, where the spatial coordination between structure, hydraulics, mechanical, and façade is genuinely complex. A 200mm conflict between a beam and a duct on Level 12 is not a detail. It's a potential delay to an entire floor cycle if it surfaces during construction.
The DBP Act framework in NSW has sharpened the compliance stakes here. Under the Design and Building Practitioners Act 2020, regulated designs must be declared compliant before construction. That means the coordination work that used to happen informally — or not at all — now has a formal gateway. A good design manager understands that compliance declarations are not an administrative exercise. They are a quality signal. And if the design isn't coordinated, those declarations become a liability.
The IFC Package Is a Contract Document — Treat It Like One
There is a persistent myth on builder-side that "IFC" means the drawings are finished and the consultants are done. Neither is true.
What actually gets issued as IFC on most projects is a package that is 80% resolved, with known gaps that everyone has agreed to "deal with later." Later arrives during construction, usually at the worst possible time, and the cost of resolution is significantly higher than it would have been at documentation stage.
Good design management means applying genuine scrutiny to IFC packages before they are accepted and issued for construction. Not rubber-stamping a consultant's submission because the programme says it's due. Asking the hard questions: Is this actually buildable? Are the details consistent across disciplines? Has the hydraulic drainage strategy been confirmed against the structural slab penetrations?
Risk Is Managed Proactively, Not Reported Reactively
The most visible difference between a well-managed design process and a poorly managed one is the timing of risk visibility. On a poorly managed project, risks surface as problems — variations, delays, disputes. On a well-managed project, risks surface as conversations — early, while options still exist.
A good design manager is running a live risk register that is specific to design: unresolved consultant scope gaps, outstanding authority responses, pending product substitutions, DBP declaration dependencies. Not a generic risk matrix that gets tabled at a monthly meeting and filed. A working tool that drives weekly decisions.
This discipline is what separates design management as a commercial function from design management as an administrative one. The commercial value of early risk identification is real and measurable. The cost of late risk discovery is also real — it just shows up on the variation register instead.
What This Means in Practice
Good design management is not a personality type or a communication style. It is a set of technical disciplines applied consistently across the project lifecycle — from tender to OC.
It requires someone who understands construction sequencing well enough to know what needs to be designed first. Who understands the regulatory framework well enough to know what will trigger a compliance obligation. Who understands the commercial model well enough to know when a design decision is actually a cost decision in disguise.
Most projects don't have this. They have someone doing their best with insufficient authority, insufficient programme visibility, and insufficient technical support. The consequences are predictable and consistent: late design, poor coordination, reactive variations, and programme slippage that never fully recovers.
The builders and developers who understand this — who invest in genuine design management capability rather than document administration — are the ones who deliver on programme, protect their margin, and don't spend the back half of the project firefighting problems that were created in the first quarter.
That's what good looks like. The gap between that and what most projects actually run is where the money goes.
