01
Site and context
Zoning and districts, existing buildings, comparable buildings and permit records nearby.
ALPS
Before design begins — parcel, zoning, statute and ordinance read together into limits, preliminary scale and key risks.
Built from actual statute and ordinance text
Local governments with use-restriction ordinances loaded
Local governments with density limit ordinances loaded
Local governments with parking ratio ordinances loaded
Local governments with building committee thresholds loaded
The denominator is the number of basic local governments nationwide. Coverage differs by regulatory axis, so each is shown separately; areas not yet loaded are reported as needing review. · Most recent ordinance amendment reflected: 2026-06-02
How it works
The address becomes a parcel: area, land category, zoning, boundary and existing buildings. Enter several parcels and individual lots are kept distinct from the combined boundary.
The Building Act, related statutes and the governing municipal ordinance are read together — permitted uses, coverage and floor-area ratio, parking, north daylight, and which reviews or assessments apply.
Planned values sit next to legal limits, each marked compliant · non-compliant · not applicable · needs confirmation · needs review, with the statute or ordinance article that decided it.
What you get
01
Zoning and districts, existing buildings, comparable buildings and permit records nearby.
02
Per-item compliance with the deciding article, plus which reviews and assessments apply.
03
Buildable envelope and preliminary scale, floor schedule, 2D layout and terrain-aware 3D massing.
04
Rough cost and revenue by delivery route, and a schedule built from the applicable approvals.
Not just numbers
Planned value, statutory limit, verdict and basis — compared on one screen.
Output sampleFormat example — not an actual site review
| Item | Planned | Limit | Verdict | Basis |
|---|---|---|---|---|
| Building coverage | 59.4 % | 60 % | Compliant | Statute |
| Floor-area ratio | 197.2 % | 200 % | Compliant | Ordinance |
| North daylight | 2.8 m | 3.0 m | Non-compliant | Building Act |
| Public open space | — | Unknown | Needs confirmation | Ordinance |
We do not pretend to know what we have not verified
Built by a practising architect for their own project reviews. Knowing where a review goes wrong is why nothing unverified is ever marked compliant.
Public data, normalised into reviewable standards
Statute and ordinance source text is collected in advance and normalised into rules a review can act on. The live review server queries those prepared standards to produce results.
Parcels and spatial data from VWorld and KLIS; statutes and ordinances from the Ministry of Government Legislation; buildings, permits and transaction records from Ministry of Land, Infrastructure and Transport open data.
Home purchase budget, loan limits and trade-up assessments are a different kind of question from building code review, so they are offered separately.
Give an address and an intended use, and the review runs from site conditions through applicable code to possible scale and the main risks — in one flow.
A ChatGPT account is required. A review starts by giving an address in the chat.
ALPS is a review tool that supports early judgement and decisions before design begins. District unit plan guidelines, special planning districts, individual design-review conditions, administrative interpretations and site conditions can override general code standards. Final design and permitting decisions require confirmation from the competent authority and qualified professionals.