Bidding for data centres? Five things data centre clients need to see.
Data centre developers are now asked to evidence community benefit commitments to win approval. Most of that evidence comes from trade partners and suppliers. Here is what they will ask you for, and how to have it ready.
Why nowTwo planned Sydney data centres were withdrawn this spring after community opposition. Developers now need evidence, and it comes from their supply chain.
- Free to download
- Sources named in every paper
- No project or client identified
Built on the 2026 NSW and Victorian data centre frameworks, the National Cabinet agreement and Data Centres Australia's member commitments.
- Local jobs, counted their wayWhy "local" needs the client's definition before the first package is let.
- Local and First Nations spend, tracedSpend by named supplier, against how the project defines each kind.
- Training you can countThe apprentices, trainees and placements a developer can point to.
- Records kept as you goWhat post-approval monitoring and yearly reporting expect.
- Figures that survive an auditEvery total resolving to a named worker, supplier or transaction.
Your Copy Is Ready
Select the button below to open the PDF, then save a copy.
Download the PDFWant to talk through what it means for your projects?
Book a Demo →
The obligation sits with the developer. The evidence sits with you.
Social licence, a community's acceptance of a project beyond its legal approval, can now decide whether data centres get built. Planning frameworks in NSW and Victoria ask developers to demonstrate local jobs, local supply chain participation, training and community benefit.
- Data centre projects in Australia's investment pipeline, per Deloitte Access Economics, November 2026
- A$141b
- Construction jobs Data Centres Australia estimates the current pipeline will support
- 18,930
- Planned Sydney data centres withdrawn after community opposition, September to November 2026
- 2
Social licence is built on site. Catchment keeps the record.
Data centre developers now have to show communities what a build delivered. On Catchment, every package reports into the record they will rely on.
Every package reports the same way
Head contractors, trade partners and suppliers report hours, spend and evidence into one system each month, on definitions set at the start. Nothing is retyped at the deadline.
Local jobs and spend, as they happen
See local employment, First Nations participation and local spend by package across the build, not reconstructed for the developer at the end.
Commitments tracked from day one
The local jobs, training and spend commitments a developer made for approval are set up once and tracked through delivery, with forecasts beside them.
A record the developer can stand behind
Accepted figures with the evidence beside them, for the developer's community and planning reporting, and for your next data centre bid.
Read it from your seat on the project.
Each role carries a different part of these commitments. Free papers on what the data shows for each one.
Head contractors34 of 45 Catchment projects missed the same target. What the data means for head contractors.Free download →
Government agenciesPathways are working. They may also be a ceiling. What the data means for agencies.Free download →
Private clients and developersIn Catchment's data, a third of social spend sits with one supplier. How solid is the data behind your claims?Free download →
Trade partners15 of 44 Catchment projects missed a target the trades beat. What it means for trade partners.Free download →
SuppliersHead contractors can only count suppliers they can verify. How to be one of them.Free download →
ConsultantsAt least six rules changed in 2026. What to check before you sign off a client's numbers.Free download →