One Consultant Team vs Many: The Hidden Cost of Hand-offs in NSW
Ask a NSW developer what their consultants cost and they will quote you the fees. Ask what the gaps between their consultants cost and you will usually get a pause — followed, if they have been doing this a while, by a war story. The stormwater engineer who designed an OSD tank under the deep soil zone. The traffic engineer whose swept paths arrived after the basement was structurally documented. The energy assessor who first saw the west-facing glazing a week before lodgement. None of these consultants did bad work. The project still paid for all of it.
The uncomfortable truth of development consulting is that the biggest costs rarely sit inside any consultant’s scope — they sit in the hand-offs between scopes. This article itemises those hidden costs and explains the alternative model: a coordinated multi-disciplinary team, which is precisely what the Contrive group in Rouse Hill was built to be — civil and stormwater engineering (Contrive Consultants), architecture, landscape and visualisation (ARQI), town planning (URBA), traffic engineering (Sweptpaths), energy assessment (NathersPRO), telecommunications (Pit and Pipe) and surveying through the group’s partner surveying company.
How many consultants does a NSW project actually need?
Count them for an ordinary townhouse DA: architect, town planner, civil/stormwater engineer, traffic engineer, landscape architect, energy assessor, surveyor, and — depending on the site — arborist, geotech, acoustic and bushfire consultants, plus a telecommunications designer before subdivision or occupation. Ten to twelve scopes is normal, not exceptional. Each one is typically procured separately: separate quotes, separate agreements, separate briefings, separate file formats, separate invoices — and separate understandings of what the project is.
The developer, or their architect by default, becomes the integrator: forwarding drawings, chasing inputs, noticing (or not noticing) when one consultant’s assumptions contradict another’s. Integration is the hardest job on the project, and in the traditional model it is done by whoever has the least time, as unpaid overhead.
The five hidden costs of hand-offs
1. Waiting: the serial-dependency tax
Consultants in separate firms work in sequence, because each waits for the previous output to be issued, transmitted and briefed. Survey, then concept, then stormwater, then landscape revisions, then traffic checks — each interface adding days or weeks of transmittal-and-queue time that has nothing to do with the actual work. On a twelve-scope project, even a week of latency per interface quietly adds months. Inside one team the same dependencies exist, but the queue disappears: the stormwater engineer sees the concept the day it changes, and preliminary advice moves across a desk rather than through a proposal-and-engagement cycle.
2. Rework: decisions made blind
Every discipline optimises what it can see. The architect maximises yield, unaware the extra basement bay just consumed the deep soil zone. The civil engineer routes the OSD outlet, unaware landscape needs that corner for a canopy tree. The facade is resolved before anyone runs a NatHERS simulation, so glazing gets redesigned after DA drawings are “final”. Each of these is a redesign loop — consultant fees paid twice for the same element, plus program. The alternative is concurrent design: thermal, traffic, stormwater and landscape constraints in the room while the site plan is still soft. It is not that integrated teams make no mistakes; it is that their mistakes get caught at sketch stage, where fixing them costs a conversation.
3. Inconsistency: the RFI machine
Council assessors cross-read the DA package, and contradictions between documents are the most preventable RFI category there is: the bin bay in different positions on the waste plan and the landscape plan; swept paths run over a superseded basement layout; a BASIX commitment the elevations do not show; a raingarden on the civil plans missing from the landscape plans. Every one costs an RFI cycle — commonly weeks of assessment time — and erodes the assessor’s confidence in the whole package. A team working from one live model and one drawing register simply does not generate mismatched documents at the same rate, because there is nothing to mismatch against.
4. Scope gaps: the items nobody owned
Between neatly separated scopes fall the orphan tasks: the NBN application no one lodged (discovered at subdivision certificate); the WAE survey no one booked before backfill; the positive covenant for the OSD nobody drafted; the sight-line check at the driveway that was neither the traffic engineer’s nor the landscape architect’s line item. In a fragmented team these surface at certification stage — the most expensive possible moment. In a group that delivers the adjoining scopes, the interfaces are internal: the pit and pipe certifier knows the surveyor captured the conduit WAE because they asked for it directly.
5. Accountability diffusion: whose problem is this?
When something does go wrong across an interface, fragmented teams spend real money discovering whose problem it is. Each firm, reasonably, defends its scope; the developer arbitrates; time passes. With one group accountable for the interacting disciplines, the question “whose issue is the driveway grade — civil, traffic or architecture?” has a one-word answer: ours.
What coordination looks like in practice
Abstract benefits are easy to claim, so here is the concrete version — the standard interaction pattern on a Contrive group multi-dwelling project:
- Feasibility: URBA confirms the planning controls and pathway while Contrive Consultants checks stormwater discharge and flooding constraints and the surveyor scopes the detail survey — before the site is even secured, one briefing covers all three.
- Concept: ARQI’s site plan is tested live against deep soil, OSD location, driveway grades and swept paths, and a preliminary NatHERS pass by NathersPRO shapes orientation and glazing while they are still movable.
- DA documentation: one drawing register; the waste plan, landscape plan, stormwater plan and swept paths cross-checked internally before an assessor ever sees them; photomontages generated from the same model the architecture lives in.
- Post-consent: conditions are split across the same team that created the documents — WAE surveys, OSD certification, pit and pipe compliance, BASIX commitments — with nothing orphaned between firms.
None of this is heroic. It is simply what happens when the people holding the interacting constraints share a coordination meeting, a model and an incentive.
The honest caveats
Is a single group always right? No — and pretending otherwise would undercut the argument. Highly specialised one-off inputs (a heritage architect, a contamination auditor) will always come from outside, and a good integrated team manages those external interfaces with the same discipline it applies internally. Very large projects sometimes deliberately split scopes for capacity or probity reasons. And a multi-disciplinary group must earn each discipline’s credibility on its own merits — a captive traffic engineer who rubber-stamps the architecture helps no one, least of all at a planning panel. The claim is narrower and stronger: for the ordinary run of NSW projects — duplexes to mid-scale residential and mixed use — the coordination cost of a fragmented team routinely exceeds any fee difference, and usually dwarfs it.
Frequently asked questions
Isn’t a single group more expensive than shopping each scope separately?
Line by line, individually shopped fees can look cheaper. But the comparison ignores where projects actually lose money: redesign loops, RFI cycles, program slippage and certification-stage surprises — none of which appear on any fee proposal. A coordinated team’s value shows up as the absence of those costs. On holding costs alone, a saved month typically outweighs any plausible fee delta.
Do I lose independent judgement if all my consultants are in one group?
Only if the group lets internal politeness override professional duty — which is a firm-quality question, not a structural one. Each Contrive group consultancy certifies within its own professional accountability: the swept paths either work or they do not, the NatHERS rating is what the software says it is. What you lose is not independence; it is the months consultants in separate firms spend discovering each other’s assumptions.
We already have an architect we love. Can a group model still work?
Yes — this is common. The group supplies the engineering, planning, traffic, energy, telecommunications and survey scopes as a coordinated block around your architect, which still eliminates most of the interfaces (they are consultant-to-consultant, not architect-to-consultant). One coordination point for eight scopes instead of eight separate engagements is most of the benefit.
At what project size does coordination start to matter?
Earlier than most people think. Even a dual occupancy carries survey, architecture, stormwater, energy, waste, driveway geometry and an NBN obligation — seven scopes and six interfaces. Small projects have thinner margins and less contingency, so a single certification-stage surprise hurts proportionally more. Coordination is not a big-project luxury; it is arguably worth most where there is no project manager to absorb the integration work.
One team, one point of accountability
The Contrive group (contriveconsultants.com.au) brings civil and stormwater engineering, architecture and visualisation, town planning, traffic, energy assessment, telecommunications and surveying together in Rouse Hill — one coordinated team for NSW builders and developers from feasibility to final certification. See everything we deliver under services or contact us to test the model on your next project: +61 497 848 111, info@contriveconsultants.com.au.