How long a building consent really takes

Ask how long a building consent takes and you will get the official answer: twenty working days. It is true, and it is also not the answer to the question you asked. The twenty days is a statutory processing clock, and the clock has a pause button that councils use on most applications of any complexity.

Understanding how the clock actually runs is the difference between a realistic project programme and a spring start date that quietly becomes winter. Here is how it works, and what it means depending on which side of the Auckland and Waikato boundary you are building.

The clock, and the pause button

When your application is lodged and accepted, council has 20 working days to process it. Working days, so weekends and public holidays do not count, and the summer shutdown period swallows more calendar time than people expect.

The pause button is the request for further information, or RFI. Any time the processing officer needs something clarified, an RFI goes out and the statutory clock stops until the answer comes back and is accepted. The clock does not restart from zero, but every day spent waiting on an answer is a day added to the calendar. Two or three RFI rounds on a consent is not unusual, and each round can add weeks of elapsed time while consuming none of the twenty statutory days.

This is why the honest answer to 'how long' is: it depends on how many times the clock stops, and how fast each stop is turned around. Both of those are partly in your control, which is the useful part of this article.

The twenty days also do not begin the moment you press send. An application first has to be accepted for processing, and councils vet applications at the door: obviously incomplete documentation can be turned around before the statutory clock ever starts, and in busy periods there can be a queue between lodgement and acceptance. None of that time shows up in any official processing statistic. All of it shows up in your calendar.

Auckland Council and Waikato District, in practice

Around here the boundary matters. Franklin and South Auckland, including Pukekohe, consent through Auckland Council. Cross the Waikato River and Pokeno, Tuakau, Te Kauwhata and their neighbours consent through Waikato District Council. Same Building Act, same statutory clock, noticeably different experience.

Auckland Council processes an enormous volume of consents, and its elapsed times have recently been averaging closer to 30 working days than the statutory 20. That is not a scandal so much as arithmetic: high volume, plus RFI rounds, plus the queue to get an application accepted for processing in the first place. Waikato District runs a much smaller volume. Timeframes there move around too, and neither council should be programmed at the statutory minimum. When we build a project programme we treat the consent stage as a range, not a date, and we tell you which end of the range your job is likely to sit at and why.

What actually makes consents slow

Most consent delay is manufactured before lodgement. The pattern is consistent enough to list.

• Incomplete applications. Missing details, unresolved junctions on the drawings, a specification that contradicts the plans. Every gap becomes an RFI, and every RFI stops the clock.
• Ground and engineering questions left open. On peat, on coastal sites and on sloping sections, council will want the geotechnical and engineering story resolved. Lodging before it is resolved just moves the wait inside the consent process, where it costs more.
• Slow RFI responses. The clock stays stopped until the answer is in and accepted. An RFI that sits in someone's inbox for a fortnight adds a fortnight to your build, invisibly. On our jobs we answer the requests, not you, and speed here is one of the quiet things that separates builders.
• Fishing for approval with a thin application, hoping council will fill in the gaps. Council will fill them in, one RFI at a time, at their pace rather than yours.

Your own decisions feed the clock more than people realise. Every product left as 'to be confirmed' on the drawings is a future RFI or amendment, and every late design change is elapsed time somewhere. The cheapest fast-tracking available on any consent is boring: decide early, document fully, and leave the processing officer nothing to ask about. Councils get blamed for a lot of delay that was posted to them by the applicant.

The consent is not the last time you deal with the process, either. Change something meaningful mid-build, move a window, alter the bracing, substitute a cladding, and the consent may need a formal amendment, with its own processing and sometimes its own RFIs. Genuinely minor variations can often be handled on site with the inspector, but the line between minor and formal is council's to draw, not yours. One more reason to settle decisions before the build rather than during it.

How to plan around all this

Treat the consent as a project stage with its own programme, not as a form to file. Get the documentation genuinely complete before lodgement, resolve the engineering early, and make sure someone owns the RFI responses and turns them around in days rather than weeks. Done that way, a straightforward consent still lands in a predictable window and the twenty-day clock does most of its statutory job.

Remember too that the consent is only the first council timeline on your job. Once building starts, every inspection, from the pre-pour check on the foundations through pre-line to the final, has to be booked, and booking lead times stretch when the region is busy. A well-run job books inspections ahead of the work reaching them, so the site never stands still waiting for a council vehicle. It is one of those quiet scheduling habits you never see and only ever feel the absence of.

And build your wider plans around the range, not the best case. Fixing tenancy end dates, finance drawdowns or a demolition crew to the statutory twenty days is how people end up paying rent on two houses while a second RFI round works itself out. The consent stage rewards preparation and punishes optimism, which makes it a fair preview of the build itself.