> 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.md).

# Process

The process pages describe the core generic interoperability processes between Social Protection (SP) systems and Early Warning Systems (EWS). These processes define how the two systems exchange information in a standardized and secure way to enable timely, anticipatory, and well-coordinated responses to emerging risks. The design is intentionally flexible so countries can adapt implementation details while maintaining consistent, secure data exchange.

This interface focuses on 2 simplified use cases:

**1. Early Warning Notifications to Inform Social Protection Action**\
This process describes how Early Warning Systems transmit risk alerts (such as climate or food security warnings) to Social Protection systems. These alerts can trigger predefined actions such as preparedness measures, temporary program adjustments, or shock-responsive scale-up.

**2. Sharing Aggregated Social Protection Data with Early Warning Systems**\
This use case describes how SP systems provide aggregated and anonymized data (e.g., counts of vulnerable households by location, demographic breakdowns) to Early Warning Systems. This strengthens risk analysis, exposure mapping, and preparedness planning without exposing personally identifiable information.

Together, these use cases enable SP and Early Warning Systems to operate as a coordinated, risk-informed ecosystem. They support faster communication with affected populations, stronger evidence for risk analysis, reduced data silos, and more timely social protection responses.

Please refer to the sub-pages in this section for detailed process flows and illustrative examples.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/1.2-process.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.