Published diagnosis

Delivery diagnosis

Published timing benchmarks for Ireland transmission delivery, derived from the active eligible case set and linked back to project-level evidence.

Scope

Ireland / TransmissionAll projects and All technologies

Coverage

0 included / 0 excludedExcluded projects stay visible in the registry with reasons

Snapshot

1 Apr 2026v2-manual-case-rebuild

Evidence rule

Manual rebuild in progress

Current answer

Current published answer

Browse registry Export snapshot manifest

Median delivery timeNot published
No published metrics are currently live while the active registry is being rebuilt from manually reviewed cases.
p90 delivery timeNot published
Upper-tail delivery timing using the nearest-rank p90 rule on the eligible case set.
Median build timeNot published
Median duration from build start to public energisation or operational readiness.
Post-consent challenge / reviewNot published
Median duration allocated to post-consent challenge, review, amendment, or legal-hold segments.

Scope

Published scope and evidence boundary

Browse registry Read methodology

IrelandTransmissionAll projectsAll technologies

Only one published scope is currently live, but the active registry has been reset and is being rebuilt from manually reviewed cases.

Metric table

Stage-duration metrics with auditable calculation logic

Review methodology note

The table below shows the currently published metrics. Expand any row to inspect the calculation logic, included cases, and case coverage behind the figure.

Metric	Published value	Coverage	Statistic / Status	Traceability
Median project delivery timeOutcome	N/A	0 included0 excluded	medianinsufficient-data	Trace Middle-of-distribution delivery timing for eligible transmission cases in the current registry snapshot. Definition basis: Start = first formal planning anchor; end = first public energisation or operational-readiness marker. Calculation rule: Median of total traced months across eligible cases in the active snapshot. Method note: Only cases with complete stage boundaries are included. Included cases: Excluded cases: None Open case coverage
p90 project delivery timeOutcome	N/A	0 included0 excluded	p90insufficient-data	Trace Upper-tail delivery timing using the nearest-rank p90 rule on the eligible case set. Definition basis: Same end-to-end delivery window definition as the median indicator. Calculation rule: Nearest-rank p90 of traced delivery months across eligible cases. Method note: With a small sample, the p90 surfaces the slowest currently eligible case. Included cases: Excluded cases: None Open case coverage
Planning timeDiagnostic	N/A	0 included0 excluded	stage_durationinsufficient-data	Trace Median duration allocated to planning segments before formal permitting begins. Definition basis: Planning time is the sum of included planning segments bounded by traced registry milestones. Calculation rule: Median of per-case summed planning-segment months across eligible cases. Method note: Planning totals remain comparable high-level allocations, but they are now derived from explicit segment intervals rather than a single stage boundary. Included cases: Excluded cases: None Open case coverage
Permitting timeDiagnostic	N/A	0 included0 excluded	stage_durationinsufficient-data	Trace Median duration of the formal consent and approvals phase. Definition basis: Permitting time is the sum of included statutory application, examination, and decision-path segments in the registry. Calculation rule: Median of per-case summed permitting-segment months across eligible cases. Method note: Where design work overlaps with permitting, time is allocated once to the dominant permitting segment and not double-counted elsewhere. Included cases: Excluded cases: None Open case coverage
Post-consent challenge / review timeDiagnostic	N/A	0 included0 excluded	stage_durationinsufficient-data	Trace Median duration allocated to post-consent challenge, review, amendment, or legal-hold segments. Definition basis: This row sums segment time allocated to post-consent challenge / review, including build-phase legal or amendment holds where they are separately evidenced. Calculation rule: Median of per-case summed segment months across all included post-consent challenge / review segments. Method note: This replaces the earlier 'appealing' label. It is broader than formal appeals and is designed to prevent challenge-driven pauses from being silently absorbed into build. Included cases: Excluded cases: None Open case coverage
Build timeDiagnostic	N/A	0 included0 excluded	stage_durationinsufficient-data	Trace Median duration from build start to public energisation or operational readiness. Definition basis: Build time is the sum of execution segments only, from traced construction or delivery execution anchors to public operational markers. Calculation rule: Median of per-case summed build-segment months across eligible cases. Method note: Where a case records a separately evidenced post-consent challenge or legal hold during execution, that time is allocated outside build. Included cases: Excluded cases: None Open case coverage

Boundary

Coverage and limits

The active registry is currently empty while legacy cases are being rebuilt under manual review. Public metrics stay offline until trusted cases are reintroduced one by one.

Exclusion is an explicit evidence rule, not a hidden data gap.
Excluded projects stay inspectable in the registry with their missing or disputed fields visible.
The current output is a bounded Ireland transmission diagnosis, not a population-wide benchmark.

Appendix

Definitions and data basis

Method notes, provenance, and concept boundaries

Delivery start

First formal public project-control or consent anchor used as the comparable start point.

Where a statutory pre-application or application filing date is publicly available, that is preferred. Where it is not, the registry may use the earliest published operator gateway or equivalent control milestone and mark any reduced precision and anchor class explicitly.

Delivery end

Earliest dated public signal of energisation, commissioning, operational readiness, or entry into commercial operations.

If an exact operational date is not public, the registry uses the earliest dated public signal that the project has reached that state and keeps the derivation visible on the case record.

Stage model

Planning, permitting, post-consent challenge / review, and build are treated as analytically distinct published stages.

The published diagnosis still exposes four rolled-up stages, but the case registry now stores second-level segments beneath them where official milestone boundaries are available. Older or thinner public records remain coarser and are labelled as such on the case page.

Overlap rule

Where phases overlap, the registry allocates time through explicit segments and does not double-count the same calendar interval in two published stages.

Overlap, challenge holds, source-versioning, and proxy choices remain visible on the case page against the underlying milestone evidence.

Eligibility rule

Only cases with complete start, end, and required phase-boundary anchors are included in the published diagnosis metrics.

Incomplete or still-live cases remain in the registry with exclusion reasons and missing or disputed fields listed explicitly.

The active Ireland transmission registry has been reset for manual case-by-case rebuild. Legacy machine-assembled cases were removed from the active publication path and archived pending fresh human-reviewed reconstruction.

Only manually rebuilt, duration-bearing cases should re-enter this active snapshot. Archived legacy material remains outside the publication path until re-vetted.

Grid Delivery Review. Ireland transmission delivery case registry and derived diagnosis snapshot (v2-manual-case-rebuild, snapshot 2026-04-01).