Sydney Water's Customer Connection Process — Avoiding Common Engineering Pitfalls

Sydney Water's Customer Connection Process — Avoiding Common Engineering Pitfalls

Sydney Water's customer connection process — from initial application through to final commissioning — looks straightforward on paper. In practice, it's where most developments hit avoidable delays.

The pitfalls are rarely technical. They're procedural. Knowing where the process breaks helps engineers design around it.

The Process at a Glance

For a standard development, the connection journey follows this flow:

1. Service location request — confirm what mains are at the site, where, and at what depth
2. Network capacity assessment — confirm whether existing capacity supports the proposed development
3. Section 73 application — formal application for compliance certificate
4. Notice of Requirements — Sydney Water's response, defining what works (if any) are required
5. Engineering and construction of any required works — including extensions, augmentations, asset protection
6. Commissioning and inspection — Sydney Water's witness of works
7. Section 73 Compliance Certificate issued

Each step is a potential failure point.

Pitfall 1: Inaccurate Service Location

Sydney Water's "Dial Before You Dig" plans are based on as-built records that may be 50+ years old in inner Sydney. Actual main location, depth, and condition can differ significantly.

Engineering response: don't assume. For any project where existing mains are critical (build-over, easement, deep excavation near asset), a physical asset survey using GPR, vacuum excavation, or CCTV is the engineering best practice. Discovering an unrecorded depth difference at construction is much more expensive than verifying it at design.

Pitfall 2: Underestimating Capacity Constraints

The capacity assessment looks at network capacity at the connection point under existing conditions. If the network is already at capacity, your project must fund the upgrade — either as a network extension or as a contribution to a future planned upgrade.

Engineering response: ask early, ask specifically. The capacity question should be raised at the SLR stage (service location request) so any upgrade is in the budget at acquisition, not discovered at Section 73.

Pitfall 3: Misinterpreting the Notice of Requirements

The Notice of Requirements arrives with engineering scope items, financial contributions, and conditions. Each item triggers downstream design and procurement.

We've seen developers respond to NORs by negotiating specific clauses without understanding the engineering implications. Common mistakes: agreeing to install assets that the developer doesn't have rights to maintain, accepting capacity reservations that constrain future stages, or missing financial contribution payment timing.

Engineering response: read the NOR with the design team, model the implications, then engage Sydney Water if changes are needed.

Pitfall 4: Inadequate Construction-Phase Documentation

Sydney Water requires specific construction-phase documentation: as-built surveys of any installed mains, CCTV records, pressure test certificates, witness records of inspections.

Engineering response: build the documentation pack at design, not at construction. Specify the inspection points, the test types, and the records required as part of the contract documentation. The contractor can't produce records that weren't asked for.

Pitfall 5: Late Commissioning

Final Sydney Water sign-off requires their inspector to attend the site at specific construction stages. If the program slips, or if Sydney Water can't be scheduled, certificates are held.

Engineering response: track Sydney Water inspection bookings as critical-path items. Their schedule is constrained. Late requests result in delays, not extensions of their crew capacity.

What ACSES Brings

We've worked the Sydney Water customer connection process across hundreds of developments. The pattern that gets projects through cleanly:

• Engage at SLR stage, not at Section 73
• Verify physical asset locations before designing around them
• Read every NOR with the design team and the developer together
• Document the construction-phase requirements at design, not in the field
• Track Sydney Water inspections as critical path

The process is well-defined. The friction is manageable. The trick is engaging it as engineering work, not as paperwork.

If you're starting a development that involves Sydney Water connections — talk to us before you submit. We'll save you weeks at the gate.