Skip to main content
EirePlan

EirePlan is still in early development. Not all features are available yet.

EirePlan — How it works

How it works

Everything about a site is already public.
It is just scattered.

Planning history, ground conditions, services and transport are all published — across 47 sources that were never built to talk to each other. We collect them, resolve them to one address, and keep the source attached to every figure.

  1. 01

    Collect

    Thirty-one planning registers, plus the national datasets for ground, water, services, transport and people. Each on its own schedule, each in its own shape.

  2. 02

    Normalise

    Into one record per application, with the same fields whatever the source register happened to call them — and resolved to the statutory authority, not the nearest one.

  3. 03

    Go past the register

    Open the documents the council published against each application: the planner's report, the conditions, the further-information letters, the objections.

  4. 04

    Answer

    Ask a question against a site and get the passage back, with the document and page it came from — or take the whole thing as a report, or over the API.

What we collect

Six layers, every one of them a public source with a licence. Nothing here is scraped from somewhere it should not be, and nothing is modelled where a real figure exists.

Planning and deliveryApplications, decisions, appeals and what was actually built.
Ground and environmentGeology, aquifers, flood risk, terrain and designations.
Services and capacityWastewater headroom, grid connections and contracted capacity.
People and movementPopulation, commuting, transport, schools and energy ratings.

From thirty-one registers to one record

The step most of this industry stops at is the second one. Normalising register metadata is a solved problem; opening the file behind it is not, and it is the only way to answer why something was refused.

The pipeline, end to end

Registers in, one structured record out, and then the document behind it — with the condition pulled out verbatim and cited.

LADCC
LACork County Council
LAGalway City Council
LAWexford County Council

31 registers

3352/25

14 Oakley Road, Dublin 6

LADCCDecisionGrant

Structured record

Condition 7Verbatim
“The first-floor rear extension shall be set back a minimum of 1.2 metres from the party boundary…”

Decision notice, p.4 · DCC 3352/25

Read from the file

Every figure keeps its source

Nothing on screen is an estimate wearing a number's clothes. If we show it, we can tell you which dataset it came from and when we last read it.

SourceLicenceAs at
National Planning Application DatabaseCC-BY 4.010 Aug 2026
An Coimisiún Pleanála — appealsCC-BY 4.009 Aug 2026
Tailte Éireann — LA boundariesCC-BY 4.02024 vintage
BCMS — commencement noticesCC-BY 4.008 Aug 2026

Named, licensed, and listed

The full ledger of what we hold and where it comes from — because a planning argument built on a source you cannot cite is not an argument.

See every source and its licence

Check it yourself.

A full site — boundary, thirteen applications, the documents behind them — is open to the public. No account needed.