ConsentIQ started as a pattern recognition problem. After working through enough RFI letters, you notice: most of them are asking for the same things. Not design failures — documentation failures. And nearly all of them were preventable.
ConsentIQ was founded by a practicing NZ architectural designer with more than a decade of building consent experience — and a co-founder who brings the engineering discipline to turn that domain knowledge into a product that scales.
The idea started simply: take a stack of real RFI letters, go through them item by item, and ask what would have prevented each one. The answer kept coming back the same: structure. Completeness. Knowing what your specific BCO at your specific council expects to see before you hit lodge.
The ConsentIQ dataset now covers 100,000+ real RFI items across NZ councils — built from OIA requests, case study analysis, and a compounding learning engine that improves with every project run through the platform.
ConsentIQ is the first product built on the Kozure compliance intelligence platform — designed from day one to work for any regulated domain, configured specifically for NZ building consent.
A single RFI round typically costs 3–6 weeks. For designers managing a pipeline of jobs, that delay compounds quickly — and clients don't see the difference between a BCO problem and a designer problem.
Repeat RFIs from the same designer build a reputation with BCOs. Designers who lodge clean applications consistently build trust that benefits every future submission. ConsentIQ is a tool for protecting that reputation.
RFIs create stress for everyone in the chain: the designer managing client expectations, the owner watching their build timeline stretch, even the BCO managing a workload of repeat requests. Reducing RFIs is a welfare issue, not just an efficiency one.
ConsentIQ's rules aren't drawn from the Building Code alone. They're drawn from real RFI letters — the actual questions BCOs ask, at actual councils, on actual projects.
That distinction matters. The NZBC tells you what the standard is. Our dataset tells you how each BCO interprets and applies that standard in practice — which items they check, which they let through, and which they've flagged consistently for years.
Every item in the gap tracker shows its frequency in the dataset: "3/3 DCC projects received this RFI". That's not a theoretical risk — it's a real pattern. The dataset grows with every project run through ConsentIQ.
Start with the live demo — or jump straight into a free trial and run your next consent submission through ConsentIQ before you lodge.