Executive argument
Protective infrastructure is not only a question of stronger walls, special doors or filtration equipment. It is a project-integration problem.
The decisive question is:
At what point does the protection requirement become visible to the architect, structural engineer, MEP designers, authority reviewers, procurement team, contractor and future operator?
Finland and Switzerland provide mature reference systems in which civil-defence shelter requirements are embedded in public regulatory and technical frameworks. The selected Arabian Gulf and Arab jurisdictions show a different but highly relevant set of public processes: national building codes, Civil Defence approvals, multidisciplinary plan reviews, building-permit systems, fire/life-safety packages, inspections and operating licences.
The useful comparison is therefore not “which country has the best shelter”. It is how different regulatory systems move safety requirements through a project.
1. Requirement trigger
Finland
A qualifying new building can trigger a statutory shelter obligation based on floor area and building use. The requirement can therefore be identified at an early project stage.
Switzerland
Shelter-place planning and local coverage determine where additional shelters remain necessary. The technical system itself is highly standardised.
Regional jurisdictions
The public material reviewed for Saudi Arabia, UAE, Qatar, Kuwait, Bahrain, Oman and Jordan is much stronger on building code, Civil Defence, fire/life-safety approval and licensing than on a general civilian shelter obligation.
Iraq is different because the Iraqi Building Council publicly lists a dedicated Shelter Code, although the full technical text still requires clause-level verification before detailed requirements are published.
A project cannot manage a requirement it has not defined.
The first design-management task is therefore a requirements classification:
- statutory shelter obligation;
- authority fire/life-safety requirement;
- client/project-specific protective requirement;
- critical-infrastructure requirement;
- specialist security/blast criterion.
These categories should never be merged into one vague label such as “Civil Defence requirement”.
2. Concept and architecture
The architecture determines where protection can physically exist.
Key early questions include:
- where the protected zone sits relative to ground, structure and access;
- whether it is dedicated or dual-use;
- occupant capacity;
- entrance and emergency egress;
- adjacency to stairs, parking, service areas and technical rooms;
- routes for air intake and exhaust;
- normal-time circulation;
- future maintainability.
Finland’s floor-area-linked shelter obligation provides an early planning input. Switzerland’s standardised shelter logic similarly gives designers known components and spatial expectations.
Jordan and Qatar demonstrate, from another direction, why architecture matters early: their public Civil Defence processes review building plans, occupancy, exits and related geometry before or together with detailed specialist-system submissions.
A protection requirement introduced during concept design can be absorbed into the architecture.
The same requirement introduced after the architectural plan, cores, parking, structural grid and shafts are substantially frozen can trigger:
- loss of usable area;
- relocated walls;
- new structural openings;
- plant-room changes;
- duct rerouting;
- revised escape strategy;
- authority resubmission.
The issue is not regional architecture versus Nordic architecture. It is requirement timing.
3. Structure and the protected boundary
Finland provides explicit shelter pressure classes and reinforced-concrete minimums. Switzerland uses a standardised reinforced-concrete protective shell supported by federal technical instructions.
In the regional jurisdictions, the public building/Civil Defence sources often focus on structural fire resistance, ordinary structural design and permit control rather than a universal public blast-shelter load basis.
A protected boundary should be managed as a project object.
A useful protected-boundary register would identify:
- wall / roof / floor segment;
- design basis;
- door or hatch;
- duct penetration;
- pipe penetration;
- cable penetration;
- drainage penetration;
- opening status;
- responsible discipline;
- approved component;
- drawing reference;
- change status.
This is more reliable than assuming each discipline will independently preserve the protective envelope.
4. MEP integration
Protective ventilation is one of the clearest examples of why terminology matters.
Finland requires protective ventilation with defined airflow, filtration capability and minimum overpressure. Switzerland uses a standard protective ventilation chain including blast/explosion valves, pre-filter, ventilation unit, NBC/gas filter and overpressure/explosion-protection valve.
Regional Civil Defence systems also use ventilation and positive-pressure concepts, especially for smoke control and stair/lobby pressurisation.
Fire/smoke pressurisation is not the same system as shelter overpressure.
They may both use fans, ducts and pressure relationships, but they serve different hazard scenarios and performance objectives.
Project documents should therefore identify the operational mode of every safety-related airflow system:
- normal HVAC;
- smoke extract;
- stair/lobby pressurisation;
- protective ventilation;
- filtration mode;
- emergency/manual mode.
The same applies to emergency power and controls.
5. Authority review
The regional studies reveal several public approval patterns.
Saudi Arabia
National building-code framework plus Civil Defense responsibility for fire-prevention/protection compliance.
UAE / Dubai
Municipal building permit and completion process plus Civil Defence e-engineering and fire/life-safety responsibilities.
Qatar
Building-plan approval followed by detailed fire alarm, firefighting and mechanical-ventilation submissions.
Bahrain
Unified building-permit framework integrating Civil Defence and other authorities, with drawing approval and final inspection services.
Oman
Building-permit process requiring multiple discipline drawings and Civil Defence maps, plus preliminary Civil Protection plan review.
Kuwait
Fire Force Prevention Sector project-study, approvals, facility licensing and inspection-related services.
Jordan
Explicit architectural, electrical and mechanical Civil Defence review with correction/resubmission and later receipt testing.
Iraq
Public code ecosystem is visible; a single national step-by-step shelter approval workflow was not established from the reviewed sources.
The practical tool is an authority interface matrix, not a generic line in the programme saying “obtain approvals”.
Each authority interface should identify:
- submission;
- designer responsible;
- prerequisites;
- expected comments;
- dependency on another approval;
- revision loop;
- evidence needed for closure.
6. Design freeze
A technical freeze should occur only when the high-risk interfaces are mature enough.
For protective infrastructure, freeze should consider:
- protected-space capacity and geometry;
- structural boundary;
- door/hatch schedule;
- penetration schedule;
- ventilation concept;
- intake/exhaust locations;
- specialist equipment space;
- power/control concept;
- water/sanitation where applicable;
- authority conditions.
Procurement should follow interface maturity, not merely programme pressure.
Ordering a specialist door, valve, filter or ventilation unit before dimensions, wall build-up, pressure basis, connection requirements and approval status are stable can transfer design risk into manufacturing and site installation.
7. Construction and inspection
Jordan’s public receipt requirements demonstrate a particularly useful principle: installed systems are checked against approved drawings and calculations, and changed conditions can require re-study.
Dubai’s permit process similarly includes construction-stage inspection and final completion checks. Bahrain and Kuwait also show final inspection/licensing layers.
A robust protective project should maintain three aligned states:
- approved design
- installed condition
- as-built / operational record
The project is not complete if these three tell different stories.
8. Lifecycle and readiness
Finland requires the shelter to be usable within 72 hours and its devices to be inspected and maintained at least every ten years.
Switzerland requires shelters to be capable of being made ready within five days, with owner maintenance obligations and authority inspection at least every ten years.
Regional public frameworks more commonly expose maintenance through fire/life-safety systems, facility licensing and recurring compliance rather than national shelter-readiness intervals.
The transferable principle is lifecycle ownership.
At handover, the project should answer:
- who maintains the protective systems;
- what is inspected and how often;
- where the approved documents are stored;
- how changes are controlled;
- who verifies readiness;
- what parts have finite service life;
- how replacement affects certification or approval.
9. The architectural paradox
A protective requirement can look like a restriction on design freedom.
In practice, early clarity can preserve more architectural freedom than late change.
When the requirement is known early, the architect can:
- place the protected zone intentionally;
- exploit dual use;
- align structure;
- rationalise access;
- reserve shafts and plant space;
- coordinate services;
- integrate authority requirements.
When it arrives late, the same requirement competes with decisions already made.
This is the central design-logic conclusion of the research.
10. What the comparison does not say
This research does not say:
- Nordic systems should be copied unchanged into the Arabian Gulf;
- every Arabian Gulf country has the same approval model;
- Civil Defence fire requirements are equivalent to shelter regulations;
- a Finnish or Swiss shelter specification can be transplanted into another jurisdiction without local design authority;
- architectural differences are cultural weaknesses.
The useful outcome is a project method:
define the protection objective early, classify the requirement correctly, map the authority path, control multidisciplinary interfaces, and maintain the approved technical intent through the lifecycle.
Country modules
- Saudi Arabia
- United Arab Emirates
- Qatar
- Kuwait
- Bahrain
- Oman
- Iraq
- Jordan
Each module uses Finland and Switzerland as fixed references and applies the same sequence:
Regulation → Architecture → Structure → MEP → Authority → Delivery → Lifecycle