Quick Reference: Core Principles
Before diving into protocols, anchor in these non-negotiable principles that guide all implementation decisions:
🎯 Speed + Safety
Fast deployment does not mean reckless deployment. Build safety checks into rapid processes rather than treating them as separate phases.
🤝 Community First
Local knowledge always beats external expertise. Design with communities, not for them. Transfer agency, not just resources.
🔄 Adapt or Fail
No plan survives first contact with reality. Build feedback loops into every phase. Measure, adjust, repeat.
📊 Data = Accountability
Collect data to serve communities and funders, not to perform. Privacy-first, transparent, actionable metrics only.
🛡️ Do No Harm
Zero tolerance for exploitation, coercion, or dependency creation. If an intervention can't be sustained locally, redesign it.
🌍 Context is King
What works in urban Kenya won't work in rural Yemen. Conflict zones require different protocols than stable regions. Always localize.
Rapid Deployment Framework (72-Hour Activation)
When speed matters—emergency contexts, acute crises, or time-sensitive opportunities—this framework enables deployment within 72 hours while maintaining safety and community consent.
Hour 0-24: Assessment & Authorization
- Confirm immediate safety for team deployment (security, access, legal clearance)
- Identify local partners or community leaders for initial contact
- Assess baseline need: number of children, age distribution, acute malnutrition rates if available
- Map existing services to avoid duplication or displacement
- Verify supply chain access: roads, ports, warehouses, last-mile options
- Secure initial funding authorization or emergency reserves release
- Active conflict in deployment zone with no safe corridors
- Legal barriers that could endanger team or beneficiaries
- Community leadership explicitly opposes intervention
- No secure communication channels for team coordination
Hour 24-48: Community Engagement & Setup
- Convene community leaders, elders, women's groups, youth representatives
- Present intervention plan in local language with visual aids
- Solicit feedback on timing, location, cultural considerations, and potential barriers
- Co-design distribution or delivery mechanisms with community input
- Identify local volunteers for program support (paid or acknowledged)
- Establish grievance mechanism and feedback channels
- Secure physical infrastructure: distribution points, storage, clean water access
Before finalizing any plan, ask: "Could this intervention inadvertently exclude, shame, or endanger any subgroup?" Consider gender dynamics, ethnic tensions, religious practices, and local power structures.
Hour 48-72: Launch & Monitor
- Pre-position supplies and verify inventory against expected beneficiary count
- Conduct team briefing on safety, cultural protocols, and emergency procedures
- Activate data collection systems (offline-capable forms, photo documentation)
- Begin distribution or service delivery with community volunteers integrated
- Monitor in real-time for bottlenecks, safety incidents, or community concerns
- Document first-day lessons and adjust processes immediately
- Establish daily check-in protocol with coordination hub
- Children receiving nutrition support without reported incidents
- Community feedback channels active and responsive
- Team safety protocols functioning
- Supply chain stable for at least next 7 days
- Data flowing back to coordination hub
Intervention Selection: Context-Based Decision Tree
Different contexts require different approaches. Use this decision framework to match interventions to ground realities.
Stakeholder Coordination Matrix
Field operations require simultaneous engagement with multiple actors. This matrix clarifies roles and engagement strategies for each stakeholder type.
Frequency: Weekly coordination meetings, formal MOUs
Frequency: Daily informal check-ins, formal meetings weekly
Frequency: Bi-weekly clinical reviews, as-needed consultations
Frequency: Monthly planning, daily meal coordination if applicable
Frequency: Cluster meetings monthly, bilateral as needed
Frequency: Weekly pipeline reviews, real-time alerts for shortages
Field Data Collection: Privacy-First Protocol
Data serves accountability and learning, not surveillance. This protocol ensures ethical, useful data collection without compromising beneficiary privacy or safety.
Minimum Required Data Points
| Data Type | Purpose | Privacy Level |
|---|---|---|
| Geographic Area (district/village level only) |
Service coverage mapping | 🟢 Safe to share publicly |
| Age Brackets (0-6mo, 6-24mo, 2-5yr, 5-12yr) |
Targeting accuracy | 🟢 Safe to share publicly |
| Number of Beneficiaries | Reach and efficiency metrics | 🟢 Safe to share publicly |
| Intervention Type (e.g., feeding, cash, education) |
Program effectiveness comparison | 🟢 Safe to share publicly |
| Anthropometric Measurements (MUAC, weight-for-height) |
Nutrition status tracking | 🟡 Aggregate only, never individual |
| Household Registration (unique ID, no names) |
Prevent duplication, track continuity | 🔴 Internal only, encrypted storage |
- Full names (use household IDs only)
- Precise GPS coordinates of individual homes
- Photos showing faces without explicit consent
- Political affiliation, ethnic identity, or religious belief
- HIV status, disability status, or other stigmatizing health information
- Citizenship documentation or asylum status
Data Security Checklist
- All field devices use encrypted storage (minimum AES-256)
- Forms function offline; sync only over secure connections
- No cloud storage without organization-level data protection agreement
- Team trained on consent protocols and data minimization
- Audit trail for all data access and modifications
- Data retention policy: delete individual records after aggregation (typically 90 days)
Team Safety & Security Protocols
No program objective justifies team endangerment. These protocols are non-negotiable for all deployment contexts.
Stop operations and evacuate immediately if:
- Direct threats to team safety (violence, kidnapping risk, targeted threats)
- Government revocation of operating permission
- Sudden escalation of conflict in operational area
- Outbreak of communicable disease endangering team
- Loss of secure communication with coordination hub for >48 hours
Daily Safety Protocol
- Morning team briefing: route plan, security updates, emergency contacts reviewed
- Check-in with coordination hub at deployment and return (minimum twice daily)
- Buddy system enforced: no solo field visits
- Local staff lead in areas where international presence increases risk
- Vehicles clearly marked, alternate routes pre-identified
- Emergency cash and first-aid kits in all field vehicles
- Evening debrief: incidents logged, next-day plan adjusted
Communication Continuity
In low-infrastructure or insecure environments, maintain redundant communication channels:
- Primary: Mobile phones (local SIM cards, secure messaging apps)
- Secondary: Satellite phones (for areas without cell coverage)
- Tertiary: Radio network (if operating in humanitarian coordination system)
- Emergency: Pre-arranged check-in schedule; if missed, trigger search protocol
Sustainability & Handover Planning
External support should phase out as local capacity grows. Plan for handover from day one to avoid creating dependency or sudden disruption when funding ends.
Capacity Transfer Milestones
| Phase | Timeline | Key Transitions |
|---|---|---|
| Phase 1: Co-Implementation | Months 1-6 | External team leads, local partners observe and assist. Training begins on technical skills, data systems, supply management. |
| Phase 2: Shared Leadership | Months 6-12 | Local partners lead daily operations, external team provides oversight and troubleshooting. Financial management gradually transferred. |
| Phase 3: Light-Touch Support | Months 12-18 | Local team fully autonomous, external team provides quarterly reviews, emergency backup, fundraising support. |
| Phase 4: Full Handover | Month 18+ | Program integrated into government systems or sustained by local organization. External team exits, peer learning continues remotely. |
- Program depends on imported supplies with no local procurement plan
- Only international staff hold technical knowledge
- Community perceives program as foreign aid, not their own system
- No government co-financing or policy integration after 12 months
- Beneficiaries have no role in governance or decision-making
If you see these patterns, pause and redesign before scaling.
Ready to Deploy?
This playbook provides frameworks, but every context is unique. Use these protocols as starting points, adapt aggressively based on ground realities, and always prioritize community voice over external templates.
- Rapid Start Kits – Pre-packaged checklists and templates
- Country Templates – Context-specific playbooks
- Constraints Mapper – Identify barriers before deployment
- Data Collector – Offline-first field forms
- Research Hub – Evidence base for intervention selection