Building consent and code complianceBuildPath management templateSometimes requiredBuilding consent and CCCProject-controlledReviewed 11 August 2026

Flashing detail checklist

Use the Flashing detail checklist to assemble, submit and control building-consent, inspection and CCC evidence against the current approved documents and authority process. It is a control aid, not a substitute for the current official, contractual or professionally prepared document where one governs.

Who initiates it

Owner/applicant or authorised agent

Who fills it out

Owner/applicant, authorised agent or relevant designer/consultant

Who reviews it

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

Who approves it

Auckland Council for consent/inspection/CCC decisions and authorised designers/trades for their certificates or producer statements

Applicability

Use where building work requires the corresponding consent/inspection/close-out process; download current prescribed or council forms from the official source.

Who needs it

The project owner and the person controlling building consent and ccc, 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 building consent and ccc decision or activity. Update it when scope, revision, cost, programme, responsibility, evidence or approval status changes.

Information needed

Owner, agent, property and consent identifiers
Means of compliance, drawings, specifications and supporting evidence
Inspection, change, certificate and CCC close-out status

Where to find the information

Current approved consent documents and council portal
Responsible designer/trade certificates and producer statements
Inspection records, as-builts and MBIE/Auckland Council guidance

Step-by-step

How to prepare, review and file it

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

Save the authority receipt, answer RFIs against the controlled revision, update the approved set after decisions and maintain the CCC evidence index throughout construction.

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: Design team and building consent
Related checklist items: Building consent and CCC; Prepare and review Flashing detail checklist; File evidence and close outstanding actions
Related software tool: Consent Tracker / Document Register
Example completed version: Example: Flashing detail 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.

Connected Workspace record

Consent Tracker / Document Register

Open Workspace area

Blank editable template

Complete a project-specific record

Free · saved in this browser

1. Flashing detail checklist: identity and statusEnter the controlled reference, revision, status, prepared/reviewed dates and exact project/work area.Where this information comes from: Project document register, project details and the current source process2. Consent identityUse the exact property, owner, agent, project description and consent number.Where this information comes from: Council portal and approved consent3. Approved document setList each drawing/specification/report number, revision, author and issue purpose.Where this information comes from: Approved document register4. Compliance evidenceRecord the applicable clause/pathway and the project evidence supplied by the competent designer.Where this information comes from: Design certificate/calculation and consent requirements5. Inspection and close-outTrack required result, failed items, change path, PS/ROW/certificate/as-built and final acceptance.Where this information comes from: Official inspection and CCC evidence records6. Actions, owner and deadlineAssign every missing, failed, conditional or conflicting item to one named owner and decision deadline.Where this information comes from: Issue, decision, responsibility and programme records7. Review, approval and close-outRecord reviewer/approver authority, outcome, conditions, linked evidence and final controlled location.Where this information comes from: Authority register, signed/portal response and close-out evidence

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.

Open connected workspace module

Verification

Source / where to check

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

Auckland Council building consents

Auckland Council explains local building consent processes, CCC, related certificates, producer statements, LBP notification, and whether resource consent may also be needed.

MBIE Building Code compliance

Use MBIE Building Performance to find the current Building Code clauses, Acceptable Solutions, Verification Methods, updates, and technical guidance.

MBIE Build to the consent

MBIE guidance explains that work should be built to the issued building consent, inspections must be managed, and records/certificates should be kept for CCC.

Consented drawings and specifications

The issued consent drawings, stamped specifications, engineering drawings, RFIs, minor variations, and amendments control the specific project.

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

Educational resource and verification warning

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.