Delivery start
First formal statutory planning or consent step used as a comparable public anchor.Pre-application engagement may begin earlier, but it is not used as the default start date because it is inconsistently disclosed.
Delivery methodology
Case-anchored method note for the delivery prototype
This methodology page is specific to the delivery surfaces. It defines what counts as a traced case, how dates are derived, and how those cases feed the dashboard-level timing statistics.
Scope
Ireland / TransmissionAll projects and All technologiesMethod version
v0.2-case-anchored-editorial-sampleA scoped research prototype rather than a population datasetSnapshot date
27 Mar 2026Exploratory prototype using a case-anchored editorial sample rather than a population-level administrative dataset.Research design
How the delivery interface maps back to the dissertation question
- Core research questionScope
The delivery prototype asks whether Ireland transmission project timelines can be reconstructed from public materials in a way that is legible enough for later comparative research.
- Variable mappingDesign
Planning, permitting, appealing, and build are the stage variables. Median and p90 delivery time are aggregate readouts built on top of those case-level stage reconstructions.
- Sample logicCases
The case set is deliberately narrow. Each project is included because it helps test whether milestone traceability is strong enough to support downstream timing statistics.
- Source typesEvidence
The prototype uses operator planning reports, programme updates, adequacy publications, and other public milestones. Where no single register exists, derivation notes make the stitching logic explicit.
- Comparability limitsRisk
Public dates do not always align to clean stage boundaries, stage overlap is common, and appeals can surface unevenly. The current output is therefore an exploratory benchmark, not a settled administrative series.
- Why this mattersUse
The value of the interface is that every dashboard statistic can be traced back to inspectable case evidence before the project scales to a broader cross-country dataset.
Definition frame
Concept boundaries used across the delivery dashboard
Delivery end
Earliest public signal of commissioning, energisation, or operational readiness.Substantial completion without energisation is not treated as the preferred end point unless that is the last public milestone available.
Stage model
Planning, permitting, appealing, and build are treated as analytically distinct stages.The stages are useful for comparison, but they do not imply that every project discloses progress in the same way.
Overlap rule
Stages may overlap in practice, but the displayed month counts allocate time to the dominant decision phase and avoid double-counting.Late-stage engineering and procurement can continue during permitting; those overlaps are documented in the case notes.
Data basis
Current figures are case-anchored editorial reconstructions from public materials.They should be read as exploratory research inputs, not as project-system administrative extracts.
Reading order
How to audit the prototype
Method, then cases, then aggregates
Reading order
How to audit the prototype
- Start here to understand what the stage labels and time windows mean.
- Use the cases page to inspect milestone-level evidence and derivation choices.
- Read the diagnosis page last; its timing cards are summary outputs of that traceable case layer.
Current limits
What this page does not claim yet
Important scope guardrails
Current limits
What this page does not claim yet
- No population-level claim for all Irish transmission projects.
- No cross-country comparability claim beyond the current methodological feasibility test.
- No assumption that the stage windows add up mechanically without overlap adjustment.