Jurisdiction platform

Planning software should not pretend every country works the same way.

Planeer separates policy, precedent, GIS, documents, validation, and professional supply by jurisdiction so each market can be accurate without contaminating the others.

Live and beta modules

Separate systems, shared product spine

Open evidence library

Jersey

Island-wide planning system with parish-level site context.

Live module

Production site search, analysis, precedent evidence, application packs, workspace workflow, and native map shell.

Runtime gates

Analysis: liveSearch: liveMap: partialMarketplace: live

AI analysisLive

Policy, GIS, precedent, probability, and appeal-readiness output.

Spatial constraintsPartial

PostGIS-backed constraint lookup with GeoJSON fallback while ingestion is applied.

Decision recordsPartial

Structured register search and appeal markers; durable normalised tables remain.

Application packsLive

One-off paid packs with Jersey document naming and caveats.

Data boundary

Uses Jersey Island Plan policy, Jersey GIS constraints, Jersey planning-register decisions, Jersey appeals, and Jersey application-pack templates only.

Individual one-off packs and professional workspace subscriptions.

Open module Workspace surface

Ireland

National planning law with city and county planning authority policy, zoning, and procedure.

Live analysis module

Ireland analysis, national procedure, NPAD precedent, all 31 authority source bundles, source health, MyPlan zoning, and gated national constraint overlays.

Runtime gates

Analysis: partialSearch: liveMap: partialMarketplace: partial

AI analysisPartial

National guidance and authority-aware prompts separate loaded policy bundles from unconfirmed zoning.

31-authority coveragePartial

Every planning authority has a configured local source bundle and curated policy set.

Zoning overlayPartial

MyPlan zoning overlay plus a PostGIS point-query contract ready for reviewed authority geometries.

Constraint overlaysPartial

OPW flood, NIAH heritage, National Monuments, and NPWS designated-site families are inventoried and gated until reviewed PostGIS geometry is loaded.

Application packsPartial

Ireland pack checkout and document naming are live; local validation remains authority-specific.

Data boundary

Uses Irish national procedure, local authority policy bundles, NPAD precedent, MyPlan zoning evidence, RZLT, and derelict/vacant sources without reusing Jersey assumptions.

Professional subscriptions plus one-off individual packs where authority validation is configured.

Open module Workspace surface

United Kingdom

England, Scotland, and Wales are modelled as separate planning systems, with England first for NPPF, Planning Portal, and local planning authority onboarding.

Private beta scaffold

England-first scaffold with NPPF policy topics, Planning Data point-query constraints, Planning Portal proxy readiness, and local authority onboarding candidates.

Runtime gates

Analysis: disabledSearch: private betaMap: private betaMarketplace: planned

NPPF policy indexScaffold

5 national policy topics are indexed for England.

Authority onboardingScaffold

1/2 pilot authorities have at least three readiness signals.

Planning Portal proxyScaffold

Credentials required before live proxy traffic.

Planning Data/PostGIS pathPartial

Official Planning Data point-query constraints can be queried, and 2 beta seed coordinates across 2 England authorities can be dry-run reviewed or persisted into shared PostGIS storage.

England beta gateScaffold

2/2 pilot authorities have configured local-plan, validation, and constraint seed coverage; 0/2 are reviewed for analysis.

Submodules

EnglandPrivate beta path

National Planning Policy Framework (NPPF)

Run guarded Planning Data/PostGIS ingestion for 2 beta coordinate seeds and review local-plan/validation sources before enabling live England analysis.

WalesSeparate planned module

Planning Policy Wales

Create Welsh policy/source registry before offering UK-wide user journeys.

ScotlandSeparate planned module

National Planning Framework 4

Create Scottish policy/source registry before offering UK-wide user journeys.

Data boundary

Uses nation-specific policy, procedure, local planning authority sources, Planning Portal readiness, and PostGIS ingestion paths isolated from Jersey and Ireland.

Private beta only until local-plan, validation, register, and constraint coverage reaches release threshold.

Open module Workspace surface

Expansion queue

Future modules are modelled before they are sold.

Coming-soon markets stay out of live analysis until policy sources, authority structures, GIS layers, validation rules, commercial terms, and legal positioning are ready.

Portugal

Coming soon

Municipal planning plans and licensing procedures must be modelled locally.

countryregionmunicipality

Spain

Coming soon

Autonomous community and municipal planning rules need explicit sub-jurisdiction coverage.

countryregionmunicipality

France

Coming soon

Local plan, commune, and intercommunal planning instruments need source-specific coverage.

countryregionmunicipality

Germany

Coming soon

Federal, state, and municipal planning responsibilities must be represented separately.

countrystatemunicipality

Italy

Coming soon

Regional and municipal planning systems require localised policy and procedure modules.

countryregionmunicipality

United States

Coming soon

State, county, city, and zoning-district rules need deeper sub-jurisdiction modelling.

countrystatecountycityzoning district

Australia

Coming soon

State planning frameworks, local environmental plans, overlays, and council assessment pathways need isolated modules.

countrystatelocal authority

Singapore

Coming soon

URA master-plan zoning, conservation controls, and redevelopment permissions need a dedicated source boundary.

countryzoning district

South Africa

Coming soon

National, provincial, and municipal planning instruments need separate authority and procedure modelling.

countryprovincemunicipality

One product spine, separate planning systems

Identity, billing, workspace workflow, APIs, and marketplace operations are shared. Policy, GIS, precedent, documents, and legal caveats stay jurisdiction-specific.

Open workspace