Dear CCCM Practitioners, 

 

I am happy to share with you some updates on the recent work done by Area-Based Approach Working Group:

- a newly released Case Study by IOM South Sudan on working with mobile teams  to support hard to reach communities displaced by floods;

- If you were not able to join our breakout session at the 2024 CCCM Annual Meeting in Nairobi, here you can find our presentation on how to diversify channels for communicating with communities in Area-Based Site Management Responses, adapted from the Area-Based Site Management Training Package;

-the ABA Resource Matrix has been updated again with links to new relevant resources, including the online self-paced training recently published by InterAction and available on DisasterReady. The Matrix can be downloaded here, from the WG webpage (for easy reference, the resources that have been added are highlighted in yellow).

 

Should you want to contact the coordinator to ask questions, share resources, tools or suggestions for the working group, you can get in touch with me at elvalentini@iom.int .  Finally, as you know we are always looking for best practices, challenges and success stories related to ABA to document through brief operational case studies: if you would be willing to share yours and your organization’s experience, do not hesitate to let me know.

 

Kind regards, 

 

Elena Valentini (IOM)

 

================= The information contained in this electronic message and any attachments are intended for specific individuals or entities, and may be confidential, proprietary or privileged. If you are not the intended recipient, please notify the sender immediately, delete this message and do not disclose, distribute or copy it to any third party or otherwise use this message. The content of this message does not necessarily reflect the official position of the International Organization for Migration (IOM) unless specifically stated. Electronic messages are not secure or error free and may contain viruses or may be delayed, and the sender is not liable for any of these occurrences.