The RFI
engine.
A source-linked model of what New Zealand councils ask for, organised by clause, discipline, location, and evidence type. It powers both pre-lodgement flags and cited RFI response drafts.
The RFI is not an edge case. It is the normal operating condition of New Zealand's consent system.
726 triggers, not one generic checklist.
The corpus is weighted toward the disciplines that generate the most documented questions: structure, services, fire, and weathertightness. The long tail is retained rather than hidden, because accessibility, H1, planning, and site conditions still change what evidence a council expects.
Every result has somewhere to point.
ARRO does not present public MBIE and council material as a private dataset. Publisher, document, page or section, and the supporting text stay attached to each structured record.
From public record to reviewable output.
One evidence pipeline supports both sides of the product. Before lodgement it helps rank likely issues on a drawing; after an RFI arrives it helps ground the response against the submitted project record.
Collect
Published council guidance, check sheets, MBIE determinations, Building Code material, and regional policy text.
Structure
Each trigger is classified by council, discipline, clause, project context, and the evidence commonly requested.
Match
The engine compares a drawing finding or incoming RFI with the closest relevant, council-specific evidence.
Cite
The output keeps its source trail so a reviewer can inspect the basis, edit the response, and make the final call.
Put the evidence to work before council does.
Be first to run a consent through ARRO's source-linked RFI Engine. Drop your email and we'll be in touch as access opens.