Three Stop-the-Clocks and Counting — Getting Consent Right the First Time

The Real Problem

You're a builder in Kumeu doing a ground-floor extension on a 1990s brick-and-tile. Your designer has done the plans, your engineer has signed off the structural details, and you lodge the building consent application with Auckland Council. The Building Act gives them 20 working days to process it.

On day 18, you get an email: Request for Additional Information (RFI). The clock stops. Council wants:

1. A producer statement for the specific cladding system
2. Confirmation of the bracing schedule for the new opening
3. Updated drainage plan showing the relocated stormwater connection

You chase your designer. The designer chases the engineer. The engineer says the bracing was implied in the structural drawings but not explicitly stated. Two weeks pass. You resubmit. On day 15 of the resumed clock, another RFI: the cladding producer statement references the wrong NZBC clause.

This bathroom extension — a straightforward job — has been sitting in consent for over three months. Your client is frustrated. Your subbies have moved to other jobs. Your cash flow is stalled because you can't invoice for work you haven't started.

This is not unusual. A BRANZ study found that consent processing inefficiencies cost the New Zealand construction industry approximately $500 million per year. Their research shows that 72% of builders experience "stop-the-clock" delays that push processing well beyond the statutory 20-day timeline, and 1 in 4 builders face 10 or more requests for additional information before reaching Code Compliance.

The complexity is compounded by the fact that New Zealand has 67 territorial authorities, each with their own interpretation of the Building Code and their own documentation requirements. What flies in Tauranga gets bounced in Wellington. What Auckland Council accepted last year might not be accepted this year.

Why Existing Tools Don't Solve This

Buildxact helps with estimation and takeoffs. Buildertrend manages project timelines. NextMinute tracks job costs. Fergus and Tradify handle workflow and invoicing. YourQS manages quantity surveying.

None of them check whether your consent application is complete before you lodge it.

There is no widely-used tool in the NZ market that reviews a building consent application package and flags:

• Missing producer statements
• Incomplete specifications
• Drawings that don't match the written description
• Required calculations that haven't been included
• NZBC clause references that are incorrect or outdated

This is exactly the kind of pre-submission review that would catch 80% of RFIs before they happen. BRANZ itself is actively researching AI-assisted consent pre-checking, recognising that the technology is now capable of this kind of document analysis.

How AI Solves This

Before you lodge your next consent application, you upload the document package to your OpenClaw workspace and send a message via WhatsApp:

"Just uploaded the consent docs for the Kumeu extension. Plans, specs, engineering, drainage. Can you check if anything's missing before I lodge with Auckland Council?"

The AI reviews the package against a consent-checklist skill that includes:

• Standard documentation requirements under the Building Act 2004
• Common Auckland Council RFI triggers (based on patterns from publicly available guidance)
• NZBC clause cross-referencing
• Producer statement requirements for specified systems

Within 5 minutes, you get a structured review:

Consent Pre-Check — 15 Oraha Road, Kumeu

Documents Received: Site plan, floor plans, elevations, cross-sections, structural engineer's PS1, drainage plan, specifications

Potential Issues Found:

1. Cladding producer statement missing — Plans specify "cavity-backed plaster system" but no PS1 from the cladding manufacturer or installer is included. Auckland Council almost always requires this for plaster systems. Action: obtain from your plasterer or cladding supplier.

2. Bracing schedule not explicit — Structural drawings show the new wall opening but the bracing demand/capacity summary isn't presented as a standalone schedule. Some council processors expect this as a separate document. Action: ask your engineer to provide a bracing summary table.

3. Stormwater connection — Drainage plan shows existing stormwater layout but doesn't clearly show the proposed connection point for the extension downpipes. Action: ask designer to add proposed stormwater connection detail.

4. Energy work specification — No insulation schedule included. NZBC Clause H1 requires insulation details for new building work. Action: add insulation R-values to specifications.

Looks Good:

• Structural engineering PS1 present and correctly referenced
• Foundation details match the geotech recommendations
• Site plan shows correct setbacks from boundaries
• Fire rating details included for the inter-tenancy wall

You fix the four issues before lodging. The consent sails through in 17 working days with zero RFIs.

How It Works Under the Hood

1. Documents uploaded to your OpenClaw workspace (PDFs, drawings, specifications)
2. AI reads and extracts content from each document using document analysis
3. A custom consent-checker skill cross-references the package against a checklist of common requirements, weighted by territorial authority
4. AI generates a structured review with specific action items
5. Review is sent via WhatsApp with a summary of issues found and items that passed

The Result

• Catch missing documents before council does — no more surprise RFIs at day 18
• Faster consent processing — complete applications get processed faster, even within the 20-day window
• Less back-and-forth with designers and engineers — you know exactly what's needed upfront
• Cash flow improves — projects start sooner when consent isn't delayed by months
• Works across councils — the checklist can be adjusted for different territorial authority requirements

What AI Can't Do Here

• AI won't guarantee consent approval — council still makes the final decision, and complex design issues require human assessment
• AI won't replace your designer or engineer — it checks for completeness, not technical correctness of the designs
• AI won't interpret council-specific policies that aren't in publicly available guidance
• AI won't generate the missing documents — it tells you what's missing, but you still need your professionals to produce them
• Building Code interpretation is ultimately council's call — AI flags common issues, not every possible objection

Who This Is For

• Residential builders who lodge their own consent applications or coordinate the process
• Small building companies tired of consent delays eating into project timelines and cash flow
• Designers and drafters who want a second check before submitting to council
• Any builder who's had a consent application stopped three times and thought "there has to be a better way"