BuildPath NZ logo
Engineering, infrastructure and utilitiesBuildPath management templateSometimes requiredEngineering and infrastructure approvalsProject-controlledReviewed 11 August 2026

Corridor access request checklist

Use the Corridor access request checklist to control civil, Watercare, council and utility evidence from due diligence through connection, inspection and as-built acceptance. It is a control aid, not a substitute for the current official, contractual or professionally prepared document where one governs.

Who initiates it

Client/developer through the civil engineer or authorised applicant

Who fills it out

Client/developer, project manager or delegated document owner

Who reviews it

The project manager and the person with technical, contractual or commercial authority for the subject

Who approves it

Relevant asset owner/authority and responsible engineer for their design or compliance statement

Applicability

Use for the asset/connection/approval actually triggered by the property and design; confirm the current asset owner and application terminology.

Who needs it

The project owner and the person controlling engineering and infrastructure approvals, including each reviewer, approver or recipient named by the live project process.

Who signs it

Only the person with the authority or professional competence required by the source document, contract, insurer, lender or authority process.

When it is needed

Prepare before the related engineering and infrastructure approvals decision or activity. Update it when scope, revision, cost, programme, responsibility, evidence or approval status changes.

Information needed

  • Asset ownership, location, levels, capacity and proposed connection
  • Protection/Works Over, inspection and testing requirements
  • As-built, CCTV, certificate and acceptance status

Where to find the information

  • Survey, GeoMaps and BeforeUdig/service-location records
  • Civil design, CCTV/tests and Watercare/council/utility response
  • Inspection records, as-builts and acceptance correspondence

Step-by-step

How to prepare, review and file it

  1. 01Confirm whether this record applies to the project and who has authority to prepare, review, sign, submit and approve it.
  2. 02Download or open the current official form or source requirements when an authority, insurer, lender or contract controls the format.
  3. 03Gather the latest controlled source documents and confirm their revisions before entering information.
  4. 04Complete every field using project-specific facts; mark not applicable with a reason and clearly label unverified assumptions.
  5. 05Cross-check names, addresses, legal description, consent numbers, dates, values, drawing references, policy details and attachments.
  6. 06Have the appropriate project owner and qualified adviser review technical, legal, financial, insurance, safety and compliance content.
  7. 07Submit or issue it through the required channel, save proof of issue and record any response or RFI.
  8. 08Track actions to close-out, then save the final signed/accepted record and attachments in the controlled project file.

Where to submit or store it

Keep as a controlled internal project record and issue by the contract or project communication method when another party must review, approve or act on it.

Submission channels

  • Controlled project document system
  • Contract communication or document transmittal
  • Email only where the project communication plan permits it

Documents to attach

  • Current drawings, specifications, reports or approval documents referenced in the record
  • Marked-up plans, photographs, quotes, correspondence, inspection results or certificates that support the entries
  • Required signatures, declarations, schedules, evidence or authority-generated receipt/acknowledgement

What happens after issue or submission

Track authority queries, protection and inspection hold points; retain as-builts and written acceptance before closing the work package.

Controlled storage

Save the final record and supporting evidence in the controlled project document system, with the revision, issue status and related workspace record.

Source applicability

Confirm the project stage, contract, consent, consultant scope and actual site circumstances before use.

Common mistakes
  • Using an old template, superseded drawing, expired certificate or outdated authority process.
  • Copying generic wording without checking the specific property, consent, contract, policy or work package.
  • Leaving ownership, dates, revision, status, attachments or close-out evidence unclear.
  • Treating an internal checklist as an official authority, insurance, lender, legal or professional form.
Red flags and stop points
  • Required information conflicts between title, consented plans, consultant reports, contracts or site conditions.
  • A person is being asked to sign, certify or approve outside their authority or competence.
  • Work, purchase, payment, submission or occupation is proposed before a required approval or insurance confirmation is recorded.
  • Insufficient data to verify — confirm against the current consented drawings, specifications, Auckland Council requirements, Auckland Unitary Plan, NZ Building Code, relevant NZ Standard, consultant advice, manufacturer instructions, insurance broker, insurer, lender, lawyer, accountant or project contract.

Connected project controls

Related quote package
Civil engineering and utility approvals
Related checklist items
Engineering and infrastructure approvals; Prepare and review Corridor access request checklist; File evidence and close outstanding actions
Related software tool
Consent Tracker / Document Register
Example completed version
Example: Corridor access request checklist for 12 Example Road, Auckland; prepared by the named project owner; current source documents listed by number and revision; assumptions marked; two actions assigned with dates; reviewed by the appropriate adviser; final version and evidence filed in the controlled project record.

Related problems

  • Infrastructure capacity unavailable
  • Works Over required
  • CCTV failure
  • Unknown service clash

Verification

Source / where to check

Use current official information and the controlled documents for the actual project.

Use GeoMaps as an early desktop check for property layers, contours, flooding/overland flow information, services context, and council spatial information. Confirm critical matters with professionals and council.

Use Watercare and civil engineering advice to verify water and wastewater connection requirements, network capacity, approvals, fees, and construction standards.

Use BeforeUdig and utility providers before intrusive investigations, demolition, earthworks, service trenches, or connection works.

Relevant professional advice

Planner, surveyor, architect, engineer, quantity surveyor, lawyer, accountant, lender, valuer, real estate agent, and other project specialists must confirm site-specific decisions.

Project-specific consented documents and professional advice override generic guidance.

Educational resource and verification warning

BuildPath NZ is an educational guide and project-management resource only. It does not replace advice from Auckland Council, a planner, architect, engineer, surveyor, quantity surveyor, lawyer, accountant, lender, insurer, insurance broker, WorkSafe, Watercare, utility provider, building consent authority or other qualified professional.

Insufficient data to verify — confirm against the current consented drawings, specifications, Auckland Council requirements, Auckland Unitary Plan, NZ Building Code, relevant NZ Standard, consultant advice, manufacturer instructions, insurance broker, insurer, lender, lawyer, accountant or project contract.