Belfast approves new two-chapel crematorium at Roselawn Cemetery
Summarised from 2 outlets · Updated 4 Nov, 17:00 · Archive
Belfast City Council has voted to progress a new two-chapel crematorium at Roselawn Cemetery in East Belfast. The decision came after councillors rejected a Sinn Féin proposal to build a crematorium at Milltown in west Belfast. Votes from Alliance, the unionist parties and the Green Party carried the decision, with twelve councillors voting in favour and eight against.
Plans for the new crematorium were unveiled by the council in 2021 but had faced delays. The decision followed more than a decade of debate among Belfast councillors about whether to expand cremation capacity. Projected costs for the new facility have spiralled to £23 million.
The existing Roselawn crematorium, which opened in the 1960s, now performs more than 3,000 cremations annually, far exceeding its original design capacity of 700 per year. Stephen Larkin, past president of the Association of Funeral Directors, said the new facility could 'make everything less rushed' for grieving families. When Antrim and Newtownabbey crematorium opened in 2023, it eased some pressure on Roselawn, but both facilities remain under strain. The new crematorium will bring the total number of such facilities in Northern Ireland to three.

How it is being reported
- Go ahead for new crematorium could reduce 'rush' for bereaved familiesPlans for a new crematorium at Roselawn Cemetery were unveiled by Belfast City Council (BCC) in 2021 but had faced delays.BBC Northern Ireland · 4 Nov, 16:33
- New Roselawn crematorium finally voted through and Milltown plan rejectedProjected costs for a new two-chapel crematorium at Roselawn have spiralled to £23millionBelfast Live · 3 Nov, 20:22
In this story: Belfast City Council · Roselawn Cemetery · Sinn Féin · Milltown · Stephen Larkin · Antrim and Newtownabbey
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)