Common ELV Design Mistakes (and How to Avoid Them) in Ireland
24 June 2026 9 min read Ireland ASDV Design Team
ELV design mistakes on Irish building projects are not random — they cluster around the same ten failures that appear repeatedly across commercial offices in Dublin, healthcare facilities in Cork and data centres in Galway. They appear in designs from experienced practices under programme pressure and in designs from less experienced consultants who don't know what they don't know. The good news is that all ten are preventable with the right process disciplines. This guide covers the most common ELV design mistakes in Ireland and what the correct approach looks like for each one.
Why ELV Design Mistakes Are Expensive in Ireland
ELV design mistakes cost money at the point where they are discovered — and the later they are discovered, the more they cost. A missing fire alarm category at Stage 2 requires a conversation at Stage 2 cost. The same missing category discovered at assigned certifier review — after the system has been tendered and partially installed — requires re-drawing, re-specifying, re-tendering part of the scope, and potentially re-commissioning. The prevention cost is always lower than the remediation cost. But prevention requires process discipline that is under pressure on most Irish construction programmes.
10
The ten most common ELV design mistakes on Irish building projects — the same ten that appear in BC(A)R assigned certifier review rejections, contractor variation claims and commissioning defects reports across Dublin, Cork and Galway every year. All ten are preventable.
The 10 Most Common ELV Design Mistakes on Irish Projects
Mistake 1
Starting Detector Placement Before Confirming the Category
Placing detectors before the I.S. 3218 category has been formally determined by fire risk assessment is the most common and most consequential ELV mistake on Irish projects. A Category L3 layout (escape routes only) and a Category L2 layout (escape routes plus high-risk rooms) are completely different documents — different detector quantities, different zone plans, different panel specification. Designing to L3 and then discovering the correct category is L2 at assigned certifier stage generates full redesign cost.
→ Fix: Category determination statement confirmed and signed by fire risk assessor before any layout drawing begins.
Mistake 2
Omitting the Cause and Effect Matrix
The single most commonly missing document in Irish fire alarm design packages submitted for BC(A)R review. Without a C&E matrix, the installed fire alarm system is programmed to contractor default logic — which typically doesn't match the fire safety strategy. AHUs continue running during fire events. Doors don't release. Lifts don't return to ground. Suppression pre-alarms don't activate. See our dedicated C&E matrix guide for Ireland.
→ Fix: C&E matrix produced at Stage 3 (draft) and Stage 4 (signed), included as a mandatory deliverable in the tender package.
Mistake 3
Designing Containment Without Clash Detection
ELV containment routes that have not been clash-detected against structural beams and MEP ductwork in BIM are routes that will conflict with something on site. Containment conflicts discovered at contractor mobilisation generate variation orders, rerouting work, programme delays and relationship damage with the main contractor. On large Irish NDP projects, unresolved containment clashes are consistently the largest single source of ELV variation claim cost.
→ Fix: ELV containment modelled in BIM at Stage 3, clash-detected against structural and MEP models, with clash report issued and conflicts resolved before Stage 4.
Mistake 4
Specifying Equipment Without IS EN 54 Certification
An equipment schedule that lists generic descriptions ("addressable heat detector, ceiling-mounted") without IS EN 54 certification references for every component is not a specification — it is an invitation for the contractor to install whatever is cheapest. An equipment schedule without IS EN 54 references will fail assigned certifier review under BC(A)R. The correction requires a complete schedule revision and potentially resubmission.
→ Fix: Every detector, call point, sounder, module and panel in the equipment schedule cites its IS EN 54 part number and certification reference.
Mistake 5
Ignoring Fire Barrier Documentation at Penetrations
Every ELV cable penetration through a fire-rated compartment wall or floor must be fire-stopped to restore the fire resistance. This is a BC(A)R requirement. When fire stop specification is missing from the ELV design package and is left to the contractor, the installed fire stop is typically the cheapest product available — which may not be the correct fire resistance period for the penetrated element. Fire stop defects are a common practical completion punch list item on Irish projects.
→ Fix: Fire stop specification included in ELV design package; builder's work drawings identify every compartment penetration with required fire resistance rating.
Mistake 6
Under-Sizing Cable Containment for Future Growth
Cable tray sized exactly for the current cable population with no future growth allowance is a tray that will be full on day one of practical completion. As-built buildings always have more cabling than the design anticipated. Irish building occupiers typically add structured cabling, security cameras and access control readers within the first two years of occupation — which requires containment capacity that was never designed.
→ Fix: Cable tray sized to 40% fill maximum at design stage, leaving 60% capacity for future cables and installation clearance.
Mistake 7
Treating CCTV GDPR Compliance as an Afterthought
CCTV design in Ireland requires GDPR compliance documentation — legitimate interest assessment, DPIA (for most commercial CCTV above basic scope), privacy masking schedules and signage specifications — as part of the design package. When these are left as a post-handover exercise for the building owner, the CCTV system is typically already installed in a configuration that may not satisfy DPC scrutiny. See our CCTV GDPR guide for Ireland.
→ Fix: GDPR compliance documentation produced alongside the CCTV design package — not as a separate project after installation.
Mistake 8
Producing an ELV Package Without a Design Basis Statement
The design basis statement is a short document confirming the I.S. 3218 category, the applicable standards, and any design derogations. It is the first document a BC(A)R assigned certifier reads. Its absence does not mean the design is wrong — but it means the certifier must infer the design intent from drawings and specifications, which takes longer and generates more review queries. Every review query is a potential programme risk.
→ Fix: Design basis statement produced at Stage 4, signed by the design engineer, included as the first document in the tender package.
Mistake 9
Not Coordinating with the MEP Electrical Engineer Early
ELV designers who don't engage with the MEP electrical engineer at Stage 2–3 consistently produce containment routes that conflict with mains electrical containment; equipment that requires mains power connections that haven't been designed; and fire alarm panels that don't have mains incoming cable sizes confirmed. These conflicts appear at Stage 4 when changing them costs more than resolving them at Stage 2.
→ Fix: Formal ELV/MEP interface meeting at Stage 2 to confirm power supply requirements, containment segregation strategy and distribution board positions for ELV equipment.
Mistake 10
Missing the BMS Integration Requirements in the Brief
Fire alarm shutdown interfaces to AHUs, access control occupancy signals to HVAC, CCTV integration with BMS — all of these require early coordination between the ELV designer and the BMS specifier. When the BMS is specified before these interfaces are agreed, the BMS panel may lack the relay inputs, BACnet points or Modbus registers required for ELV integration. Retrofitting BMS interface capability after the BMS has been commissioned is expensive and sometimes technically impractical.
→ Fix: ELV/BMS interface requirements confirmed at Stage 2–3 and documented in a formal interface schedule shared with both the ELV designer and the BMS contractor at tender stage.
How BIM and AI Are Eliminating Common ELV Design Errors
AI-powered ELV design QA tools are beginning to automate the most mechanical compliance checks — verifying that category determination statements are present; that C&E matrix row counts match the zone plan; that IS EN 54 certification references are provided for every equipment schedule item; and that containment is clash-free against structural and MEP models. ASDV monitors and incorporates these tools as they mature. In 2025, internal QA by a senior engineer against a discipline checklist remains the most reliable prevention mechanism — augmented by BIM clash detection for containment coordination.
ASDV's Internal QA Process for Irish ELV Projects
ASDV's QA process for Irish ELV design packages checks against a discipline-specific checklist before every drawing issue. The checklist covers: category determination statement present and signed; C&E matrix present, signed and cross-referenced to zone plans; IS EN 54 certification references present for every equipment schedule item; design basis statement present with I.S. 3218:2019 citation; fire stop specification present in performance specification; containment clash-detection report included. No ELV package is issued to an Irish client without passing this checklist. This is not extraordinary practice — it is the minimum that Irish building control requires.
Beginning detector placement before confirming the fire alarm category under I.S. 3218. A Category L3 and L2 design are completely different documents. Designing to L3 and discovering L2 is required at assigned certifier stage generates full redesign cost — entirely avoidable by confirming the category before any layout drawing begins.
The system is programmed to contractor default logic — typically doors not releasing, AHUs continuing to run, lifts not returning to ground, suppression pre-alarms not activating. These defects generate variation claims, programme delays and certification failures at commissioning — all avoidable by producing the C&E matrix at design stage.
BIM clash detection in Navisworks identifies ELV containment conflicts against structural beams and MEP ductwork before they reach site. On Irish NDP projects, unresolved containment clashes consistently generate the most expensive ELV variation order claims. BIM clash detection cost is always lower than site-stage conflict resolution cost.
A design basis statement confirms the I.S. 3218 category, applicable standards and any design derogations. It is the first document a BC(A)R assigned certifier reads. Its absence means the certifier must infer design intent from drawings and specifications — adding review time and generating queries that create programme risk.
An experienced ELV design partner with a structured internal QA process eliminates these risks regardless of programme pressure. ASDV's QA checklist verifies that every mandatory document (C&E matrix, design basis statement, IS EN 54 equipment schedule) is present before any package is issued to an Irish client — preventing the mistakes that cost the most to fix.
Get a Free ELV Design Review — Zero Risk of These Mistakes
ASDV's internal QA process prevents every one of these 10 mistakes. Fixed fee confirmed within 24 hours of receiving your drawings.
ASDV's internal QA process checks every Irish ELV package against a discipline-specific checklist before issue — preventing all 10 of the most common ELV design mistakes. Remote delivery from New Delhi to Dublin, Cork, Galway and nationwide.
