Community Risks and Security Personnel

What PS 4 Covers

PS 4 protects Affected Communities from health, safety, and security risks created by the project. This is distinct from PS 2 (which covers workers) and PS 3 (which covers pollution and resource use). PS 4 is about the people living near the project who didn't sign up for it but bear the consequences.

The standard covers everything from dam safety to disease outbreaks to how security guards behave. If a project activity can hurt, sicken, or endanger surrounding communities, PS 4 applies.

Community Health and Safety

The client must evaluate risks to communities throughout the entire project lifecycle - design, construction, operation, and decommissioning. For each identified risk, the client establishes preventive and control measures consistent with Good International Industry Practice (GIIP) and the IFC's Environmental, Health and Safety (EHS) Guidelines.

This isn't a one-time exercise. As the project evolves, new risks emerge - a construction phase might bring heavy vehicle traffic through a village, while the operations phase might bring noise and air quality concerns.

Health Impact Assessment (HIA)

For projects with significant health risks to communities, PS 4 requires a Health Impact Assessment as part of or alongside the broader Environmental and Social Impact Assessment (ESIA). An HIA systematically evaluates how a project could affect the health of surrounding populations and identifies measures to prevent or mitigate negative health outcomes.

An HIA is particularly important when:

• The project is in an area where baseline health conditions are already poor (high malaria prevalence, limited health infrastructure)
• The project will cause significant labor influx into a small or remote community
• The project involves hazardous materials, emissions, or water resource changes that could affect community health
• The project's area of influence includes vulnerable populations (children, elderly, immunocompromised groups)

The HIA should cover both direct health impacts (exposure to pollutants, traffic accidents, contaminated water) and indirect health impacts (changes in disease vector habitats, stress from displacement, loss of traditional food sources). It links directly to the ESIA by feeding its findings into the project's Environmental and Social Management Plan, ensuring health mitigation measures are budgeted, scheduled, and monitored alongside other commitments.

Infrastructure Safety

Structural elements of a project - buildings, dams, bridges, containment structures - must be designed, constructed, operated, and decommissioned to avoid risks to the community. This means applying recognized engineering standards and safety codes.

For high-consequence structures like dams, tailings dams, and ash ponds in locations where failure could endanger communities, the client must engage independent experts to review the design, construction, and ongoing safety. "Independent" means not involved in the project's design - a separate set of eyes with no stake in cutting corners.

Dam Safety Risk Classification

The Guidance Notes (Annex A) identify 12 criteria for assessing whether a dam poses high risk to downstream communities:

1. Dam height - taller dams store more energy and water behind them
2. Storage capacity - volume of water or tailings impounded
3. Flood evaluation - capacity to pass extreme flood events safely
4. Seismic design - adequacy of design for the local seismic hazard
5. Foundation conditions - geological stability of the dam site
6. Downstream population at risk - number of people in the inundation zone
7. Potential for loss of life - estimated fatalities if the dam fails
8. Potential economic losses - downstream property and infrastructure at risk
9. Potential environmental losses - ecological damage from a dam breach
10. Dam condition and performance history - age, maintenance record, any prior incidents
11. Operational complexity - how difficult the dam is to operate safely (multiple outlets, spillway gates)
12. Hazardous materials stored - whether the impoundment contains toxic tailings or contaminated water versus clean water

A dam that scores high on multiple criteria requires the most rigorous independent oversight - not just a design review, but ongoing independent monitoring throughout the dam's operational life.

Universal Design Principles

Infrastructure safety extends beyond preventing catastrophic failures. The Guidance Notes reference Universal Design principles - designing infrastructure so it is accessible and safe for all community members, including people with disabilities, elderly persons, children, and pregnant women. For example, pedestrian crossings near a project site should accommodate wheelchair users, warning systems should include both audible and visual alerts, and emergency evacuation routes should be accessible to persons with limited mobility.

Hazardous Materials

Projects must avoid or minimize community exposure to hazardous materials. This applies throughout the project lifecycle, with special attention during decommissioning when old equipment and contaminated materials are being handled.

The client also controls the safety of hazardous material deliveries and transport. A chemical plant isn't just responsible for what happens inside its fence - it's responsible for the tanker trucks rolling through town on the way in.

Ecosystem Services and Community Safety

Here's a connection many people miss: project impacts on priority ecosystem services can directly threaten community safety. Wetlands and mangroves that buffer storm surges, upland forests that prevent landslides, floodplains that absorb excess water - these natural systems protect communities.

If a project degrades these services, it must identify the impact and take measures to mitigate it. Clearing a hillside forest above a village isn't just an environmental issue (PS 6) - it's a community safety issue (PS 4) if that forest was holding the soil in place.

Community Exposure to Disease

Projects can become disease vectors in ways that aren't obvious. The standard requires clients to minimize potential for water-borne, vector-borne, and communicable diseases. Two common pathways:

• Infrastructure changes - Construction that creates standing water (borrow pits, drainage blockages) can breed mosquitoes and increase malaria or dengue risk.
• Labor influx - Bringing hundreds or thousands of workers into a remote community introduces risks of sexually transmitted infections, respiratory diseases, and other communicable illnesses.

Water-Related Disease Types

The Guidance Notes (Annex B) classify water-related diseases into four categories based on transmission pathway. Understanding these categories helps practitioners identify which project activities create which disease risks:

Emergency Preparedness

The client must assist Affected Communities and local government agencies in preparing for emergencies related to the project. This includes documenting emergency arrangements, disclosing them to affected communities, and conducting practice drills where appropriate.

Where local government agencies have limited response capacity - common in remote or developing areas - the client takes a more active role. You can't just hand off your emergency plan to a volunteer fire department that has one truck and no training on chemical spills.

Required Elements of an Emergency Response Plan

The Guidance Notes specify eight elements that every project Emergency Response Plan must address:

1. Identification of emergency scenarios - What could go wrong? Dam breach, chemical spill, fire, explosion, natural disaster interacting with project infrastructure. Each scenario needs a specific response protocol.
2. Notification procedures - Who gets notified, in what order, and how? This includes internal notification chains, local emergency services, government authorities, and - critically - affected communities.
3. Evacuation routes and procedures - Pre-identified routes, assembly points, and transportation for evacuating communities at risk. Routes must be tested and communicated in advance.
4. Emergency equipment and facilities - What equipment is pre-positioned and where? Fire suppression, spill containment, first aid stations, emergency power, communication equipment.
5. Roles and responsibilities - Clear assignment of who does what during an emergency. No ambiguity about chain of command.
6. Communication protocols - How information flows during the emergency, including communication with communities in local languages and through appropriate channels (radio, sirens, community leaders).
7. Training and drills - Regular training for project personnel and practice drills with community participation. Drills should be realistic and cover each identified scenario.
8. Post-emergency review - After every emergency (or significant drill), a formal review to identify what worked, what didn't, and what needs to change in the plan.

Security Personnel

This is one of the most sensitive areas of PS 4. Projects - especially mining, oil and gas, and large infrastructure in remote areas - often need security. But security arrangements can themselves become a source of risk to communities.

The Voluntary Principles on Security and Human Rights

PS 4's security requirements align with the Voluntary Principles on Security and Human Rights (VPs) - a framework developed jointly by governments, extractive industry companies, and NGOs. The VPs provide detailed guidance on:

• Risk assessment - Analyzing the local security context, identifying potential for conflict, and understanding the human rights record of local security providers (both private and public)
• Private security - Policies on ethical conduct, rules of engagement, appropriate use of force, and incident reporting. Private security contractors must operate under written agreements that incorporate human rights standards.
• Public security - Managing the relationship with government-provided security forces, ensuring that the project's engagement with police or military doesn't contribute to human rights abuses

The proportionality requirement is central: security responses must be proportionate to the threat. Guards protecting a facility perimeter against petty theft should not respond with the same force used against an armed attack. The Guidance Notes emphasize that security personnel should use force only when strictly necessary, in a manner that is defensive (not offensive), and at the minimum level required to address the threat.

Rules of engagement must be written, trained on, and enforced. They should specify:

• When force may and may not be used
• The escalation sequence (verbal warning, then physical intervention, then use of equipment - lethal force only as last resort in defense of life)
• Mandatory reporting of all security incidents
• Mandatory reporting to the client of any credible allegations involving government security forces

Government Security Forces

When government security forces (police, military) are assigned to a project, the client must seek to ensure their conduct is consistent with PS 4 requirements. This is trickier than managing private guards - the client doesn't employ government forces directly. But the standard requires the client to:

• Encourage the government to disclose security arrangements to the public
• Investigate and report any credible allegations of unlawful or abusive acts by government security
• Use its leverage to push for conduct consistent with the standard

Conflict-Affected Areas

In conflict or post-conflict areas, all of these security risks are amplified. The project itself can become entangled in local tensions - a mine that employs one ethnic group but displaces another, for instance. The client must assess whether its security arrangements or its very presence could exacerbate existing conflicts.