Series: IOAS Case Study 02/2026
Published by: Irish Office for Administrative Simplification (IOAS)
Publication date: 3 October 2026
Evidence review: 3 October 2026
Integrated evidence review: 3 October 2026
Status: Independent research publication
Suggested citation:
Irish Office for Administrative Simplification (2026), The State Already Knows: Mapping the administrative shockwave of a registered death in Ireland, IOAS Case Study 02/2026.
Analytical method
This paper follows the published administrative journey and tests what happens at each administrative join: where responsibility, information, evidence or action passes between stages, people or institutions. It distinguishes burden from dysfunction. A join is not treated as defective merely because it requires effort or involves more than one actor. The analysis asks what has already been established, what genuinely new information is required, who carries it across the boundary, who owns the next move, and what happens if that move does not occur. A diagnosis is applied only where the evidence supports one.
Directly supported by official or independent evidence.
Visible from the published process itself.
Plausible mechanism requiring case or operational evidence.
Tested, but the available evidence does not justify the diagnosis.
The named people are illustrative. No unreported operational behaviour is attributed to an institution. IOAS concepts are analytical proposals, not official terminology.
Research question
Once a death has been formally registered, where does the authoritative event travel inside public administration, where must a bereaved person still carry it, and which later requests concern genuinely new consequences rather than re-establishing the event?
Existing research and comparative evidence
Ireland has a substantial evidence base on dying and bereavement, but much less published research specifically measuring the administrative work that follows a death. The 2023 National End of Life Survey was completed by 4,570 bereaved family members and friends and provides important evidence about the circumstances in which bereavement is experienced, but its purpose was to examine end-of-life care rather than post-death administrative duplication.[6] The Irish Hospice Foundation’s Dying, Death and Bereavement in Ireland 2026 similarly brings together national and international evidence on dying, bereavement and grief, including their social and financial effects, but does not provide a service-by-service map of repeated death notification.[7]
That absence matters methodologically. IOAS should not infer administrative duplication from the emotional difficulty of bereavement. Instead, the present case combines the published Irish administrative architecture with a real comparative model. Ireland’s Death Events service distributes deaths notified to the General Register Office to approved public-sector bodies, but access is not universal and operational use is not publicly mapped service by service.[3][5]
Britain’s Tell Us Once provides a useful counterfactual. After a death has been registered, the service allows a person to report it to most government organisations in one operation.[8] A 2013 Department for Work and Pensions customer survey was specifically designed to establish an evidence base for reception of the service and possible improvement or expansion; published results reported high levels of satisfaction, while the survey itself also recorded limitations including a 21% response rate.[9]
How IOAS builds on the prior evidence
The comparison does not establish that the British architecture is superior or that every Irish notification is redundant. It gives the IOAS Administrative Shockwave and Event Duplication propositions something concrete against which to be tested. The research question becomes: after the authoritative event exists, which consequences can be propagated institutionally, which require a citizen’s new decision or authority, and which still require the citizen merely to carry an event the public administration could already lawfully consume?
Journey map
Stage-by-stage analysis
1. From human event to administrative event
A death must be registered with the GRO, normally within three months. In an ordinary route, medical certification permits registration with the Registrar of Deaths and a death certificate is issued. Coroner cases follow a different route and may delay final registration while investigation is completed.[1][2]
Administrative join D1 — Registration gateway
Status: structurally observed, but necessary. Until registration, the death has not reached the authoritative civil-registration state used by the Death Events infrastructure. Coroner cases can legitimately lengthen this stage. IOAS does not classify necessary investigation as administrative duplication.
2. The State now holds an authoritative event
Irish research at this join. The Death Event Publication Service has itself been examined by the Institute of Public Administration as a case of public-sector innovation and cross-agency collaboration intended to minimise bureaucracy at times of bereavement.[11] This is significant for IOAS because institutional reuse of a registered death was not merely a technical possibility inferred after the fact; reducing repeated bereavement administration formed part of the service’s policy rationale.
Previous and comparative evidence at this join. The administrative significance of an authoritative event is visible in the design of Britain’s Tell Us Once service: after a death is registered, a single notification can be propagated to multiple central and local government services.[9] This does not establish what Ireland should do, but it demonstrates that death registration can serve as the anchor for cross-government consequence handling rather than leaving every institutional relationship to be restarted separately.
The Death Events service distributes information on deaths notified to the GRO to public-sector bodies and states that it is updated every Friday lunchtime. The Public Service Bodies Data Catalogue says approved bodies can gain access to registered-death data and lists fields including name, date of death, date of birth, PPSN, address and civil status.[3][4]
Administrative join D2 — Registration to distribution
Status: structurally observed, significance unmeasured. Registration and distribution are not necessarily simultaneous: the public service states a weekly publication cycle. This creates an interval during which a death is registered but not yet available through that channel. No evidence reviewed establishes that this interval causes material service problems.
3. Availability is not universal receipt
Evidence of operational adoption. Historical parliamentary evidence shows at least one concrete downstream use: the HSE described receiving a weekly DEPS file, uploading it to the medical-card database and using it to update records, while retaining GP and citizen notification as additional safeguards.[12] This is an especially useful example because it shows that institutional reuse and parallel notification can coexist. A second notification is therefore not automatically Event Duplication; it may operate as a safety net, and the public value of that safeguard must be tested.
Evidence boundary. The Irish Death Events service proves that a distribution mechanism exists; it does not prove that every relevant body subscribes to it, ingests it into an operational system, matches the record successfully, or initiates a consequence automatically. British service-design evidence is instructive here: a 2018 assessment of a death-notification service praised work across organisational boundaries and attention to avoiding repeated questions for bereaved users.[10] That is evidence that backend integration and user burden are connected design questions, not evidence that Ireland currently lacks such integration.
Death Events is currently available only to Public Sector Bodies and access requires an application giving organisation and reason for access.[5] It would therefore be wrong to write “the State knows” as though every public organisation automatically receives and acts upon the record.
Administrative join D3 — Access and operational adoption
Status: candidate. Infrastructure exists for State-side reuse, and historical evidence confirms operational use in at least some services, but the public evidence examined does not provide a current comprehensive map of participating bodies or show whether each relevant service consumes and operationalises the data. The resulting research question concerns not data existence but data adoption and process integration. This requires institutional mapping.
4. The administrative shockwave
What bereavement research contributes. Ireland’s 2023 National End of Life Survey drew responses from 4,570 bereaved relatives and friends.[7] Its focus was end-of-life care rather than post-death bureaucracy, so it cannot be cited as evidence of Event Duplication. Its value here is contextual: the administrative journey begins at a time already associated with care, loss and major practical demands. The absence of service-by-service Irish evidence on post-death notification burden is therefore itself an important research gap rather than permission to infer burden from bereavement alone.
One registered death can alter many relationships. Social Protection's bereavement guidance, for example, still tells people that where a person dies while receiving a social welfare payment, the death should be notified to the relevant section as soon as possible.[1] That instruction sits alongside the existence of Death Events. The sources alone do not establish whether the citizen notification is redundant, accelerative, a safeguard, or needed because a particular operational process does not consume the event feed.
Candidate finding D4 — Parallel notification after State registration
Status: candidate requiring operational evidence. The coexistence of an authoritative death-distribution service and citizen-facing instructions to notify a Department is exactly the kind of join IOAS should investigate. It is not yet evidence of Event Duplication, because the reason for the notification and the receiving section's use of Death Events are not established by these sources.
5. Event versus consequence
Comparative test. Tell Us Once is useful precisely because it does not eliminate all work after death. Current guidance says it notifies specified government bodies, while families still have to contact many private organisations and may need to provide additional information where a consequence depends on a survivor’s circumstances, authority or choice.[9] The comparator therefore supports the IOAS distinction between transporting the authoritative event and supplying genuinely new consequence-specific information.
The key analytical separation is between proving that the person died and deciding what follows. An executor may need to establish authority; a surviving spouse may need to apply for a benefit; a service may need account-specific information. Those are new administrative facts, even where the death itself is already known.
Event Duplication test
Status: proposed test, no blanket finding. IOAS would classify a request as Event Duplication only where (1) the death is authoritatively established, (2) the receiving public body can lawfully and operationally access that fact, and (3) citizen notification adds no information materially necessary to the decision. The present public evidence does not support applying that label across public services generally.
Shockwave / hand-off register
| Join | Information already established | Possible new information | Ownership diagnosis |
|---|---|---|---|
| Death → registration | Medical facts / coroner outcome as applicable | Registration particulars | Necessary formalisation |
| GRO → Death Events | Registered death | No citizen re-proof inherent in published feed | Institutional distribution mechanism exists |
| Death Events → public body | Core death-event fields | Service-specific consequence | Adoption/operational use not publicly mapped |
| Public body → bereaved family | Potentially the death event | Authority, choices, changed household circumstances, claims | Must test event vs consequence before calling burden duplication |
Waiting and ownership map
Registration is institutionally owned once the necessary medical/coroner route permits it. Publication through Death Events is institutionally owned. What remains unclear is the downstream join: which body consumes the event, when, and whether its internal process automatically identifies the next administrative action. That is the most important empirical gap.
Counterfactual test
The British evidence supplies a real-world rather than purely imagined counterfactual. A 2013 customer survey of Tell Us Once was commissioned specifically to create an evidence base about reception of the cross-government service; the published analysis reported strong user understanding, confidence and willingness to recommend it, while also noting the survey response rate and other limitations.[8] That does not prove that the same architecture would have identical effects in Ireland, but it shows that cross-government death notification is operationally feasible and evaluable.
Remove the bereaved relative as messenger. Does the public-service consequence still begin? If a body already lawfully consumes the registered event and can identify the relevant record, the answer may be yes; if it needs a survivor's choice, authority or application, the answer may be no. The value of the test is precisely that it prevents “tell us about the death” and “tell us what you want done because of the death” from being treated as the same request.
Priority questions for field research
Which public bodies currently have Death Events access? Which operational systems actually ingest it? What action is triggered by receipt? Which services still instruct relatives to notify them? What additional information does that notification provide? What is the elapsed time from GRO registration to downstream action? Those answers would permit a genuine Event Duplication map rather than an assumption.
Finding
The evidence establishes a significant piece of shared infrastructure, an explicit historical objective of reducing bereavement bureaucracy, and operational reuse in at least some services—but not universal or comprehensively mapped current administrative reuse. The strongest present IOAS finding is therefore a researchable coordination boundary: the State possesses a mechanism for distributing an authoritative death event, while some citizen-facing guidance still requires notification. Whether that boundary produces avoidable duplication must be tested service by service.
Establish the event once. Carry it safely where the State can carry it. Ask the citizen only for what the State does not already know.
References and sources
- Department of Social Protection, Bereavement. Official guidance ↗
- Department of Justice, Register a death with the Coroner. Official guidance ↗
- Death Events, service homepage. Official service ↗
- Public Service Bodies Data Catalogue, Deaths Events System. Official catalogue ↗
- Death Events, Register. Official access page ↗
- Irish Hospice Foundation, National End of Life Survey (2023). Research overview ↗
- Irish Hospice Foundation (2026), Dying, Death and Bereavement in Ireland 2026. Research report ↗
- UK Government, Tell Us Once. Official service guidance ↗
- Department for Work and Pensions (2013), Tell Us Once customer service survey analysis. Government research ↗
- UK Government, Tell Us Once, current guidance on notifying government after a death. Official comparative guidance ↗
- UK Government Digital Service (2018), Tell us about a death alpha assessment. Service-design assessment ↗
- Institute of Public Administration, Innovation in the Irish Public Sector, case study 5.3: Death Event Publication Service — a cross-agency collaboration to minimise bureaucracy at times of bereavement. Research case study ↗
- Seanad Éireann debate, 23 October 2013, description of HSE use of DEPS in medical-card administration. Parliamentary evidence ↗