> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.01-ews-notify-sp-system-for-anticipatory-action/example-1-ews-notify-sp-system-about-hazard-to-scale-cash-transfers.md).

# Example 1: EWS notify SP system about hazard to scale cash transfers

### Process Flow

This example illustrates how the [PRS.EWS.01: EWS notify SP System for anticipatory action](/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.01-ews-notify-sp-system-for-anticipatory-action.md) process is to support the timely activation of anticipatory actions through the integration of Early Warning Systems (EWS) and social protection systems. It can be implemented during preparedness, monitoring, or emergency response stages to enable social protection institutions to take early measures before the anticipated hazard impacts affected populations.

This process enables the exchange of hazard-related information and geographic risk data necessary for social protection systems to assess potential impacts on registered beneficiaries and vulnerable populations. Depending on the country context and anticipatory action framework, the process can be implemented independently or in combination with additional processes related to beneficiary verification, targeting, case management, notification delivery, financial support activation, or assistance disbursement mechanisms.

The actual anticipatory actions triggered through this process are dependent on national policies, financing arrangements, operational procedures, and hazard-specific anticipatory action protocols. These actions may include the activation of contingency financing or emergency funding mechanisms, temporary expansion of cash assistance programs, accessible warning dissemination, evacuation support, livelihood protection measures, relief pre-positioning, or referrals to complementary support services.

The Data Standards section outlines the different data elements that may be shared as part of the notification process depending on operational requirements and available information. These options may include sharing hazard event details alone, such as hazard type, severity, forecast period, probability, and affected geographic locations. 

### **Process Flow: Send notification from EWS to SP System**

<table><thead><tr><th width="213">Section </th><th>Description </th></tr></thead><tbody><tr><td>Actors and Entities</td><td>Early Warning System (EWS) , Social Protection (SP),Climate Risk Financing or Contingency Fund Authority</td></tr><tr><td>Assumptions</td><td><ol><li>There is an established agreement between the Early Warning System and the Social Protection program to transmit notification for anticipatory action.</li><li>The Social Protection system has the technical capacity and operational readiness to receive notification and trigger appropriate program responses.</li><li>The notification from the EWS contain sufficient information (e.g., location, severity, type of shock) for the SP system to take informed action.</li></ol></td></tr><tr><td>Prerequisites</td><td><p></p><ul><li>The Early Warning System (EWS) is operational and able to generate risk notification.</li><li>The Social Protection (SP) system is able to receive and process incoming notification.</li><li>Communication protocols and formats for notification are defined and agreed between EWS and SP.</li><li>Targeting criteria for households, regions, or beneficiary groups are established.</li><li>Legal and operational data-sharing agreements between EWS and SP are in place.</li><li>Financing activation protocols between the climate risk financing mechanism and the Social Protection system are established to support timely anticipatory action delivery following EWS trigger notifications.</li></ul></td></tr><tr><td>Process Inputs</td><td></td></tr><tr><td>Process Flow Steps</td><td><p></p><p><strong>Step 1:</strong> The Early Warning System (EWS) identifies a risk event or shock (e.g., flood, drought, food insecurity) and determines affected areas based on monitoring, forecasting, and simulation.</p><p><strong>Step 2:</strong> The EWS generates a notification containing the relevant risk information, severity level, forecast period, and impacted area.</p><p><strong>Step 3:</strong> The Social Protection (SP) system receives the notification through the agreed communication channel and validates the request and notification content.</p><p><strong>Step 4:</strong> The SP system maps the alert to potentially affected beneficiaries, households, or geographic regions within its coverage.</p><p><strong>Step 5:</strong> Based on predefined trigger thresholds and anticipatory action protocols, the relevant financing mechanism, contingency fund, or climate risk financing facility authorizes and releases funds to support the response.</p><p><strong>Step 6:</strong> The SP system triggers anticipatory program actions, such as scaling up cash transfers, emergency payments, targeted outreach, evacuation support, or referral services.</p><p><strong>Step 7:</strong> The SP system logs the notification reception, financing activation, actions taken, and any operational issues for audit, accountability, and monitoring purposes.</p></td></tr><tr><td>Outputs</td><td><p></p><p><strong>Received notification Record:</strong> Confirmation that the SP system received the notification with timestamp and reference.</p><p><strong>Mapping of Affected Beneficiaries/Areas:</strong> List or summary of households or regions identified for programmatic response.</p><p><strong>Audit Logs:</strong> Detailed logs of notification receipt, validation, mapping, and actions taken.</p></td></tr><tr><td>Control Points</td><td><p></p><ul><li><strong>EWS controls the generation and content of alerts.</strong> The SP system does not modify the risk information but ensures proper interpretation and operational response.</li><li><strong>SP system controls programmatic actions.</strong> Decisions on which households or regions receive support remain with the SP program.</li><li><strong>Audit logs are mandatory.</strong> All alert transactions, validation checks, and actions are logged.</li><li><strong>Data sharing must follow established authorization protocols and legal agreements.</strong></li></ul></td></tr><tr><td>Exception Handling</td><td></td></tr></tbody></table>

### Diagram 1 - EWS notify SP System to release cash transfer

<figure><img src="/files/D76CYO0QSgCuUvF0yDOZ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process/prs.ews.01-ews-notify-sp-system-for-anticipatory-action/example-1-ews-notify-sp-system-about-hazard-to-scale-cash-transfers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.