Residents rarely complain about how a data centre looks; they complain about the hum, that low and steady drone of cooling plant at three in the morning.
It never stops, because the facility never stops, and that sound has become one of the biggest approval risks facing data centre developers in Australia. Most project teams discover it far too late, long after the design has been locked in.
We’ve watched this pattern repeat across industrial and infrastructure projects for years: the technical case is sound, the community response is not. Underneath the noise issue sits a second problem that almost nobody raises at feasibility stage, and that’s what’s already in the ground.
What a data centre noise assessment actually measures
A data centre noise assessment establishes existing background sound levels at a site, predicts how much noise the completed facility will add, then tests that prediction against the limits your state regulator applies. It covers chillers, cooling towers, generators and switchgear, and a thorough assessment also models the character of the sound rather than volume alone.
That last point matters more than most people expect, because two facilities can produce identical decibel readings while generating completely different levels of complaint.
Background noise surveys come first
You cannot assess impact without knowing the starting point, so we measure ambient sound across a full week to capture weekday and weekend patterns, day and night. Rural and semi-rural sites often record very low night-time background levels, which means a facility that would disappear into the hum of an inner-city precinct becomes genuinely intrusive in a quiet growth corridor.
Honestly, this is where plenty of projects get caught out: developers assume an industrial zoning gives them room to move, and the measured background says otherwise.
Tonal and low frequency noise change everything
Cooling plant produces a narrow band of sound the human ear picks out easily, and regulators apply penalties for it. Victoria assesses this through the EPA’s Noise limit and assessment protocol, known as the Noise Protocol, which adds decibel adjustments where noise is tonal, intermittent or impulsive and can push a compliant-looking design over the limit on paper.
Low frequency noise creates a separate problem, since it travels further than higher frequencies and passes through walls and windows that block ordinary traffic sound. EPA Victoria publishes separate guidance on assessing low frequency noise precisely because standard measurement methods handle it poorly, and frequency spectrum is a prescribed factor when determining whether noise is unreasonable.
Submissions to the NSW parliamentary inquiry into data centres have argued for buffers of 300 to 500 metres between large facilities and homes, schools and parks, drawing on international modelling of exactly this kind of propagation.
Why communities notice the sound before anything else
Noise is the impact residents experience directly and continuously, without needing any technical knowledge to interpret it. That immediacy is what makes noise the trigger for organised community opposition, and organised opposition is what turns a six-month approval into a two-year one.
Consider what’s already happening around the country. The NSW inquiry has heard from councils, academics and engineers about poor planning outcomes, and one Sydney council has called for a moratorium on approvals until consultation guidelines change. Reporting on the Lane Cove cluster in Sydney found operational noise from an existing facility exceeding the levels predicted before it was built.
That gap between prediction and reality is the real reputational risk: once a community sees one facility breach its own modelling, every subsequent application in that corridor faces a far harder audience.
Come to think of it, the commercial argument for getting this right is stronger than the compliance one. Acoustic specialists making submissions to the same inquiry have pointed out that noise-related planning friction costs proponents real money through delayed approvals, forced redesign, retrofitting and operational curtailment, so fixing a problem at design stage is always cheaper than fixing it after commissioning.
Regulators are asking harder questions
State environment protection authorities have sharpened their scrutiny of data centre applications considerably over the past two years, and generic acoustic modelling no longer clears the bar. Assessments now need to address cumulative effects, sensitive receivers and generator testing regimes in detail.
The framework differs by state, which matters for operators building across borders. NSW assesses industrial noise under the EPA’s Noise Policy for Industry, applied in full rather than selectively, while Victoria works through the Noise Protocol alongside the general environmental duty that requires you to understand and reduce risks proactively rather than react to complaints.
The NSW EPA reviewed the environmental impact statement for a major Western Sydney facility in April 2026 and told the state government it lacked the information needed to complete an assessment, seeking further detail on air quality, noise and greenhouse gas emissions. That’s a significant delay for a project of that scale, and it came from documentation gaps rather than any fundamental design flaw.
Generator testing deserves specific mention here. Backup generators at large facilities are typically tested monthly and sometimes weekly, with each test producing a short burst of high-intensity noise alongside diesel emissions. A data centre noise assessment that models only steady-state cooling operation misses this entirely, and the testing regime is usually what generates the loudest community reaction.
Our environmental compliance and approvals team sees the same documentation gaps again and again: the modelling itself is competent, but the scope around it is far too narrow.
Cumulative impact is the emerging test
Single-facility modelling is becoming inadequate as clusters form, with more than 270 data centres now operating across Australia and around 90 of those in New South Wales. Where several facilities share a business park, each one can comply individually while the combined sound level makes nearby homes genuinely unliveable.
Regulators have started responding to this, and submissions to the NSW inquiry have called for cumulative acoustic assessment at precinct and corridor level, particularly in mixed-use growth areas where industrial and residential land sit close together.
Practically, your assessment should account for approved but unbuilt neighbouring facilities rather than just what exists today, so ask the local council what else sits in the pipeline and model the worst realistic scenario. Second movers into an established precinct carry the heaviest burden: the acoustic headroom has already been used, and you inherit whatever community sentiment the first arrival created.
The contamination nobody mentioned
Noise gets attention because people can hear it, while soil and groundwater contamination gets ignored because it’s invisible, and data centre sites are frequently developed on land with an industrial past. PFAS is the risk that keeps surfacing, and it can halt a project far more abruptly than any acoustic complaint.
PFAS chemicals came into Australia through firefighting foams used from the 1970s to the mid-2000s, and contamination now clusters around airports, defence bases, fuel terminals and fire training grounds. Those are exactly the industrial fringe locations where large data centre sites tend to be assembled, because the land is cheap, serviced and well connected to power.
Assessment sits under the PFAS National Environmental Management Plan, now at version 3.1, which sets the nationally agreed guideline values for investigation, soil reuse and waste. Those values have tightened, so a site cleared under earlier criteria may not clear under current ones. The NSW EPA also maintains a public register of PFAS investigation sites worth checking against any land you’re considering.
The stakes rose sharply in May 2026, when the Commonwealth launched a $2 billion claim against 3M over foam-related contamination at defence bases, pushing PFAS liability into every serious land transaction conversation in the country.
Test before you buy, not after
A preliminary risk screening assessment is a modest cost against a nine-figure land acquisition, and it tells you whether the site carries a contamination history worth investigating further. Where screening flags a risk, a full environmental site assessment establishes the extent of the problem and the likely remediation pathway.
Discovering PFAS during bulk earthworks is a different situation altogether: excavated soil becomes regulated waste, disposal costs multiply, the programme slips by months, and notification obligations under general environmental duty provisions kick in immediately.
We’ve written previously about when contaminated land assessment is legally required before you build, and the short answer is earlier than most developers assume.
Sequencing the work through your project
Environmental assessment works best as a series of gates rather than a single pre-lodgement scramble, because each stage informs a decision that’s still reversible. Leave everything until the development application is due, and you’re simply documenting choices you can no longer change.
Here’s the sequence we recommend to clients.
- Site selection. Run preliminary contamination screening and a desktop noise constraints review before committing to the land, identifying sensitive receivers and measuring separation distances at this point.
- Concept design. Commission background noise monitoring across a full week, then model the proposed plant layout against measured levels so you can adjust chiller placement, screening and orientation while the drawings remain fluid.
- Pre-lodgement. Complete the full data centre noise assessment, covering generator testing scenarios, tonal penalties and cumulative effects from neighbouring industrial use.
- Construction. Monitor to confirm compliance with approval conditions, managing contaminated material under a documented plan if screening flagged anything.
- Operation. Verify that real-world performance matches the modelling, since this is the step that protects your next application in the same corridor.
Getting the acoustic case right the first time
A rigorous data centre noise assessment does more than satisfy a planning condition: it gives your project a defensible technical position when residents, councillors and regulators start asking pointed questions, and it surfaces design changes while they’re still cheap to make.
Our consultants work across environmental noise, occupational noise and contaminated land management from offices in Melbourne and Adelaide, assessing sites for developers, councils and national infrastructure operators.
The projects that move smoothly through approval share one habit, and it’s a simple one: they treat environmental assessment as design input rather than paperwork.
Planning a data centre development? Talk to our team about a site-specific noise and contamination scope before your next design milestone, or download our capability statement to see how we support infrastructure projects from feasibility through to operation.