From consent
to sign-off.
Track every build from lodgement to sign-off. Consent status, BCA references, RFIs, and inspections in one workspace, with an AI co-pilot that answers questions across all of it.
First, one source of truth.
Every project's consent status, open RFIs, and inspections in one workspace, so nothing hides in an email thread.
From lodgement to sign-off
Every project carries its consent status, open RFIs, and inspections in one place, so you see at a glance what's active, what's in review, and what's blocked, and why.
- Live consent and RFI status per project
- Timeline view across inspections and milestones
- Blockers surfaced instead of buried in email
Built around real council process
ARRO is mapped to how each council actually works: their lodgement portals, document naming conventions, and how each runs vetting and the processing clock. Launching with Canterbury's three BCAs (Christchurch City, Selwyn, Waimakariri), with Wellington-region councils next.
- Per-council portals and document naming conventions mapped
- Vetting and processing-clock behaviour tracked per BCA
- Address autocompletion and BCA linkage on every project
Everything in one queryable place
Projects, drawings, specs, consents, and RFIs live in one workspace the analyser and co-pilot can see, with access controlled project by project.
- Drawings, specs, consents, and RFIs alongside the project record
- The same workspace powers plan analysis and the co-pilot
- Per-project access control
Then, to Code Compliance.
Once consent is granted, ARRO tracks the inspection schedule through the build and assembles the CCC paperwork, so sign-off never stalls on a missing form.
Through construction to code compliance
Once consent is granted, ARRO tracks the inspection schedule through the build and assembles the CCC paperwork: PS3s, PS4s, Records of Building Work, and producer statements, so sign-off doesn't stall on a missing form.
- Inspection schedule tracked stage by stage through the build
- CCC document checklist: PS3, PS4, RBW, producer statements
- Missing paperwork surfaced before you apply for the certificate
Ask the workspace anything
The same workspace powers a co-pilot. It reads everything on the project - drawings, consents, RFIs, inspections - and grounds every answer with a citation to the exact source.
Questions we get asked
Which councils is project management built around?
ARRO is mapped to how each council actually works - lodgement portals, document naming conventions, and vetting and processing-clock behaviour - launching with Canterbury's three BCAs (Christchurch City, Selwyn, Waimakariri), with Wellington-region councils next.
Does it handle inspections and CCC, not just consent status?
Yes. Once consent is granted, ARRO tracks the inspection schedule through the build and assembles the Code Compliance Certificate paperwork - PS3s, PS4s, Records of Building Work, and producer statements - so sign-off doesn't stall on a missing form.
What can the AI co-pilot actually answer?
It reads everything on the project - drawings, consents, RFIs, inspections - and answers questions across all of it with a citation back to the exact source - for example, which projects have an RFI open longer than 10 working days, or what's still outstanding before requesting CCC on a specific address.
Is this a replacement for our existing project tracker?
It's a single workspace for everything consent-related - projects, drawings, specs, consents, and RFIs together, with access controlled project by project - so the same data also powers plan analysis and the co-pilot rather than living in separate tools.
Bring your projects into one place.
Be first to bring your projects, drawings, and RFIs into ARRO. Drop your email and we'll be in touch as access opens.