Right-of-Way Drainage vs Private: Who Maintains It, How to Design It, and What Councils Require

Rights of way are one of the most common access arrangements in New Zealand subdivision, and the drainage within them is one of the most common sources of post-settlement disputes. The problem is not the engineering. The problem is that the ownership, maintenance responsibility, and design standard for ROW drainage sit at the intersection of property law, council policy, and practical engineering, and most developers do not address all three before titles issue.

This post covers who owns ROW drainage, how to design it, what councils require, and how to avoid the disputes that arise when these matters are left unclear.

What Is a Right of Way and Why Does Its Drainage Matter?

A right of way (ROW) is a legal access arrangement that allows one or more properties to cross another property to reach a public road. In a subdivision context, a ROW is typically a shared driveway serving rear lots, created as an easement on the title of the underlying lot.

The ROW surface collects stormwater. In a typical NZ residential subdivision, a ROW might be 3.5 to 6 metres wide and 30 to 80 metres long. That is 100 to 480 square metres of sealed impervious surface draining to somewhere. If the drainage is not designed, consented, and documented, the water goes where gravity takes it, which is usually onto the lowest neighbouring property.

ROW drainage matters because it affects three separate parties: the lot owner whose land the ROW crosses, the lot owners who use the ROW for access, and the council that may or may not accept vesting of the drainage infrastructure. Each has different interests, and a well-designed subdivision addresses all three at the consent stage.

Public vs Private Drainage: The Key Distinction

The fundamental question is whether the ROW drainage is public (vested in council) or private (owned and maintained by the lot owners).

Public drainage is infrastructure that council accepts responsibility for. Once vested, council maintains, repairs, and replaces the pipes, sumps, and outlets. Public drainage must be built to the council's engineering standard (typically NZS 4404:2010 or the council's local code of practice), inspected during construction, and formally accepted through the as-built and vesting process.

Private drainage remains the responsibility of the property owners. It is not maintained by council and is not subject to the same design standard. However, it must still function, and its existence and maintenance obligations must be documented on the title through easements.

The decision between public and private drainage is not always a free choice. Most councils will not vest drainage infrastructure within a private ROW. The logic is straightforward: council does not control access to private land, and maintaining infrastructure on private land creates legal and practical complications. This means that in most ROW subdivisions, the drainage within the ROW is private infrastructure, and the maintenance responsibility falls on the lot owners.

Maintenance Responsibilities: Who Pays for What?

This is where most disputes originate. If the ROW drainage is private, who pays when a pipe blocks, a sump fills with sediment, or a connection fails?

The answer depends on the easement instrument registered on the titles. A well-drafted easement will specify:

• Which parties share maintenance obligations. Typically all lots that benefit from the ROW (the dominant tenements) share the cost of maintaining the ROW surface and drainage, in proportion to their use or in equal shares.
• What maintenance includes. Clearing sumps, unblocking pipes, repairing damaged outlets, maintaining surface drainage gradients, and replacing failed infrastructure.
• How costs are apportioned. Equal shares are the most common arrangement. Some easements use a proportional split based on the number of vehicle movements or the number of lots served.
• Dispute resolution. A mechanism for resolving disagreements about maintenance scope or cost, without requiring court proceedings.

If the easement is silent on drainage maintenance, the default position under the Property Law Act 2007 is that the grantor (the lot whose land the ROW crosses) and the grantees (the lots that use the ROW) share the cost of keeping the ROW in reasonable repair. In practice, "reasonable repair" is vague enough to generate disagreement, which is why specifying drainage maintenance explicitly in the easement instrument is essential.

How to Design ROW Drainage

The design approach for ROW drainage is the same as for any sealed surface: collect the runoff, convey it to a discharge point, and ensure the discharge does not cause erosion or flooding on downstream properties.

The standard design elements are:

1. Surface grading: The ROW surface is graded to direct stormwater to collection points. A crossfall of 2.5% to 4% is typical. On longer ROWs, a longitudinal grade directs water to sumps or channel drains at intervals.
2. Collection: Sumps, slot drains, or channel drains collect surface runoff. Sump spacing depends on the catchment area and the intensity of the design storm. For a typical 4-metre-wide ROW, a sump every 25 to 40 metres is usually adequate for the 10-year ARI storm.
3. Conveyance: A piped system (typically 100 mm to 150 mm diameter uPVC) conveys collected water from the sumps to the discharge point. Pipe grades must be sufficient to maintain self-cleansing velocity (minimum 0.6 m/s at design flow).
4. Discharge: The discharge point is either a connection to the council stormwater network (if available and approved) or a controlled discharge to a natural watercourse or overland flow path. If the ROW drains to the council network, the connection requires council approval and may trigger stormwater neutrality requirements.
5. Detention (if required): If the council requires stormwater neutrality, the ROW impervious area must be included in the site's detention calculation. The ROW area is part of the post-development impervious coverage, and its runoff contribution must be attenuated accordingly.

For ROWs serving three or more lots, NZS 4404:2010 Table 3.1 provides minimum formation widths. The drainage design should be integrated with the formation design to ensure the sealed surface, kerb or edge treatment, and drainage all work together.

What Councils Require

Council requirements for ROW drainage vary, but the common themes are:

Napier City Council: ROW drainage is typically private. NCC requires engineering drawings showing the drainage layout, pipe sizes, grades, and discharge point as part of the engineering plan approval. If the ROW contributes to the site's impervious area, its runoff must be included in any SW-S1 stormwater neutrality calculation. NCC will not vest private ROW drainage but will inspect it before S224c sign-off.

Auckland Council: Auckland's infrastructure design standards require ROW drainage to be designed and documented regardless of whether it is public or private. For ROWs serving four or more lots, Auckland generally requires a higher standard of formation and drainage. The Stormwater Code of Practice applies to ROW runoff in the same way it applies to any other impervious surface on the site.

Rangitikei District Council: ROW drainage requirements are assessed case by case. The engineering plan must show how ROW runoff is managed, and any discharge to a Horizons-managed watercourse requires regional consent. In Marton, where pallic soils rule out soakage, all ROW runoff must be conveyed to a surface discharge point.

Hamilton City Council: PC12 requirements apply to ROW impervious surfaces in the same way they apply to building platforms and driveways. Both retention and detention obligations extend to the ROW area.

Common Disputes and How to Avoid Them

The disputes SAE sees most frequently in ROW drainage are:

• Blocked pipes with no maintenance agreement. The easement does not mention drainage, the pipe blocks, water ponds on the servient lot, and nobody agrees on who should pay to fix it. Prevention: specify drainage maintenance in the easement instrument at subdivision stage.
• ROW runoff flooding a downstream lot. The ROW was graded without a designed drainage system, and all runoff sheets off the end of the sealed surface onto the lowest lot. Prevention: design the drainage as part of the engineering plan, with a controlled discharge point.
• Sump and pipe sizes that are inadequate. The original design was undersized (or there was no design), and the system surcharges in moderate rainfall events. Prevention: design to a stated standard (10-year ARI minimum) and document the design in the engineering report.
• Unequal use, equal costs. One lot generates most of the ROW traffic and therefore most of the wear on the drainage infrastructure, but the easement requires equal cost sharing. Prevention: consider proportional cost sharing in the easement instrument if the lots have materially different use patterns.

The recurring theme in all of these disputes is that the drainage was either not designed, not documented, or not covered by the easement. Addressing all three at subdivision consent stage costs very little relative to the cost of resolving a dispute after titles have issued.