> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2025/mbie-kicking-schedule-method-to-the-curb.md).

# MBIE Kicking Schedule Method to the Curb

05.07.25

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2FntmmaaLoIVyN9FWzeQNK%2F1751581847177.jpeg?alt=media&amp;token=71fe792c-c21d-459a-963e-8af695d8b873" alt=""><figcaption></figcaption></figure>

The rumors were true! MBIE is ditching the stale Schedule Method for H1 insulation by late 2025. Good riddance; it often led to poor design and overheating.\
\
What's left? The Calculation and Modelling methods. These are effective, cheaper, and might save you $15,000 on a new home! Modelling promises better design flexibility, though the Calculation method still carries design risks with no consideration of solar loads. There's also concern that chasing savings might compromise construction quality.\
\
The kicker? Full implementation won't happen until 2027, as the 12-month transition is delayed a year. If it's about savings, why the wait? Let the market choose now!\
\
On a positive note, MBIE's exploring a separate Far North climate zone for insulation, which seems reasonable. Overall, it's about building smarter and more efficiently in NZ!\
\
👉 Read More - <https://lnkd.in/gykw8eqi>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2025/mbie-kicking-schedule-method-to-the-curb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
