Community Of Practice Operations Support – AI in Emergencies (AIDERS CoP)

The World Health Organization serves as the directing and coordinating authority for public health within the United Nations system. WHO seeks to promote health, ensure everyone can attain the highest level of health, keep the world safe and serve the vulnerable through partnerships, people and countries.

WHO EMRO has launched the AIDERS Community of Practice on the WHO Collaboratory to support practical, responsible use of AI for emergencies (surveillance, response, and operational decision-making). The CoP now needs a structured 12-week operational push to keep daily activity consistent and grow membership and participation. The UN Volunteer will support execution and moderation of engagement and working group activities, working closely with WHO CoP coordinators and technical leads. All technical direction, content approval, and final decisions remain with WHO staff; the UNV helps implement and coordinate the process.

Task description The candidate will work under the supervision of the CoP Coordinator (WHO Health Emergencies). The role requires strong community management skills, clear writing, comfort with AI concepts in emergency settings, and the ability to deliver structured outputs on schedule. Key deliverables (12 weeks) The UN Volunteer is expected to deliver the following minimum outputs. 1) CoP daily operations (Weeks 1–12) Moderation coverage: Platform check twice per weekday; respond/tag the right focal point within 24 hours. Member onboarding: Welcome message and orientation for new members within 48 hours of joining. Community hygiene: Maintain pinned posts (“Start here”, rules, how to join WGs), keep key links updated, and escalate sensitive issues promptly. 2) Engagement programme (Weeks 2–12) Weekly engagement package (minimum): 3 tips per week (short operational tips on AI use in emergencies) 1 poll per week (priorities for webinars, tools, learning needs) 1 discussion thread per week (scenario-based, emergency-focused) Two engagement campaigns to drive growth (e.g., Weeks 4 and 8), including outreach text packs for WHO/partners. 3) Working Groups (WGs) – support establishment and outputs (Weeks 2–12) Establish and support 2 Working Groups (or as agreed with the coordinator), each with: WG page created on the platform 1-page WG charter (scope, objectives, deliverables, cadence, leads) Membership list and onboarding post 4) Support development of Knowledge products (by Week 12) Prompt pack v1: minimum 40 prompts grouped by emergency function (surveillance, sitreps, QA, risk assessment). Case cards: minimum 8 mini case cards (200–300 words) with problem → AI approach → risks → safe steps. Resource library: minimum 25 curated resources, each with a 2–3 line summary + tags. 5) Monitoring and reporting (Weeks 1–12) Weekly metrics update (every Friday): New members, total members Weekly active members Posts/comments/reactions Top 3 threads Issues/risks + mitigations Plan for next week Final report + handover pack (Week 12): Summary of KPIs, what worked/what didn’t Links to all outputs (WGs, content, resources) Recommendations for the next 12-week cycle Handover folder: templates, calendars, welcome messages, WG charters, trackers