Use Objective Build and current Hastings building-consent guidance.
HASTINGS DISTRICT COUNCIL WORKFLOW
Hastings building consent checklist and council guide.
Prepare the Hastings Objective Build application with coordinated site, hazard, infrastructure and regional information, then manage inspections and CCC evidence against the issued consent.
This guide is for preparing a building-consent document pack. Resource-consent applications follow a separate process.
WHAT THE PRE-CHECK COVERS
A coordinated record, not another loose checklist.
ConsentMuster starts with the national application structure, then records the local authority, official source and project-specific hand-off checks. The report highlights what the applicant team should resolve or confirm before submission.
Address liquefaction, flooding, coastal, contaminated-land and other Hawke's Bay site constraints.
Coordinate regional approvals, earthworks, water, wastewater and stormwater infrastructure information.
01
Before lodgement
Check application details, plans, specifications, engineering, H1, drainage and supporting forms for missing information and revision conflicts.
02
During processing
Turn an RFI into plain-English actions, owners and a point-by-point response register linked to the affected documents.
03
During the build
Collect inspections, photographs, Records of Work, producer statements, test results, variations and as-builts before work is covered.
04
At CCC
Review the issued consent conditions and assemble an indexed close-out record for the project team to submit to the BCA.
What to prepare for a building-consent application in Hastings.
This is a practical starting list, not a substitute for the current Hastings District Council project checklist. Include only the documents that apply to the site and work, and confirm the live council requirements before lodgement.
- Application and ownershipCurrent Form 2 details, owner and agent information, project description, estimated value and proof of ownership where requested.
- Architectural drawingsSite and floor plans, elevations, sections, construction details, demolition information and clearly identified existing and proposed work.
- Specifications and productsA project-specific specification with the selected systems, materials, installation requirements and supporting product information.
- Structure and groundApplicable engineering, calculations, geotechnical evidence, design features reports and producer statements aligned with the architectural set.
- H1 and Building Code evidenceEnergy-efficiency calculations and the project-specific evidence relied on for relevant Building Code clauses and alternative solutions.
- Drainage and servicesStormwater, wastewater, water-supply and site-servicing information coordinated across the civil, drainage, architectural and structural documents.
- Site and separate approvalsRelevant hazard, planning, resource-consent, infrastructure, road-corridor and network-utility information kept distinct but coordinated.
- One controlled submission setA searchable document register showing filenames, authors, dates and revisions, with superseded files removed before upload.
Common Hastings consent questions.
These answers are an applicant-side starting point. Confirm the current project-specific requirements with the live council source and the appropriately qualified members of the design and construction team.
What should a Hastings building-consent application contain?
Use Objective Build and the current Hastings guidance to lodge a controlled set of application information, plans, specifications and site-specific supporting evidence.
- Use the authority's current form, project-specific checklist and live lodgement instructions.
- Coordinate the application, plans, specification, engineering, H1, drainage and supporting statements.
- Submit one current document register and remove superseded files before upload.
Which Hastings site issues should be checked before lodgement?
Coordinate liquefaction, flooding, coastal and contaminated-land information with regional approvals, earthworks and water, wastewater and stormwater infrastructure decisions.
- Confirm the current property, planning and natural-hazard information before design decisions are fixed.
- Identify separate infrastructure, regional, road-corridor or resource-consent approvals that may apply.
- Make every relied-on report traceable to the site, proposal, author, date and drawing revision.
How should Hastings inspections and design changes be recorded?
Plan inspections and professional observations around the issued consent, and record each site change before the affected work proceeds.
- Use the issued consent and inspection schedule as the controlling construction record.
- Book required inspections before affected work is covered and close every failed item in writing.
- Link each site change to an accepted minor variation or approved amendment and update affected documents together.
What should be collected for a Hastings Code Compliance Certificate?
Prepare the Hastings CCC record from the consent conditions and completed inspection history, with final as-builts and all applicable trade and professional documents.
- Apply using Form 6 and include the completed inspection and approved-change record.
- Collect applicable Records of Work, trade certificates, producer statements, tests, commissioning and as-builts.
- Confirm the final evidence list against the issued consent and Hastings District Council's current CCC instructions.
SOURCE-BOUNDARY NOTE
Use the live council source for the final submission.
This page is an independent applicant-side preparation guide, not Hastings District Council guidance, endorsement or approval. Requirements depend on the property and work. ConsentMuster records the source used, but the project team must confirm the current official requirements before lodgement.
See whether the check helps your team.
For NZ residential design practices, we offer one scoped initial check on a completed pack, free. We agree fit and file handling by email before you share documents.
Ready to use the software on another project?