Focal points
Name one accountable contact locally and one in the destination community. Publish roles, not private details.
Diaspora solutions · communication
Build a trusted local–diaspora communication loop
The communication problem is rarely a lack of messages. It is the absence of a trusted route from local needs to diaspora capacity—and back to a visible result. This playbook helps a village group, association, business, ministry, school, clinic or diaspora organization replace scattered WhatsApp requests with accountable two-way coordination.
Common failures and practical fixes
| Problem | Why it breaks trust | Working solution |
|---|---|---|
| Requests arrive through personal contacts | Access depends on who knows whom; requests cannot be compared. | Use one public intake form or email with a named local and diaspora focal point. |
| Updates are promotional, not useful | People hear about ceremonies but not decisions, costs, delays or needs. | Publish a monthly decision note: what changed, what is needed, who owns it, and the next date. |
| Diaspora expertise is collected but unused | Repeated surveys create consultation fatigue. | Ask for a defined task, time commitment, decision owner and response deadline before collecting volunteers. |
| Money is requested without documentation | Donors cannot verify the recipient, budget or outcome. | Attach an organization identity, itemized budget, payment route, safeguards and reporting date. |
| Local voices are filtered out | Projects solve an external assumption rather than the local priority. | Require a local problem statement and affected-person review before diaspora fundraising begins. |
The six-part communication loop
Source of truth
Keep one dated page or document containing the verified request, owner, budget, progress and corrections.
Listening
Collect local needs and diaspora offers separately. Consent to contact is not consent to publish personal data.
Routing
Classify each item: information, expertise, procurement, investment, emergency or policy feedback.
Response
Assign an owner and deadline. Say “not proceeding” when appropriate instead of leaving requests unanswered.
Closure
Report what happened, funds or time used, remaining gaps, lessons and the next decision date.
A request brief people can act on
Copy this seven-line structure
- Local problem: Who is affected, where, and what evidence confirms it?
- Requested outcome: What should be different, and by when?
- Local owner: Which accountable organization and person will deliver?
- Diaspora role: Advice, introductions, procurement, funding, mentoring or investment?
- Resources: Itemized cash, time, equipment and local contribution.
- Safeguards: Verification, procurement, conflicts, data protection and complaints.
- Follow-through: Update dates, success measure and public close-out.
During hurricanes and other emergencies
Verify before amplifying
Route life-safety information through official emergency authorities. Mark unverified community reports clearly and time-stamp every update.
Separate needs from offers
Maintain a verified needs list and a separate offer register. Match them through named coordinators to reduce duplication and unsuitable donations.
Publish the handoff
Record who received funds or goods, delivery status, distribution criteria and unresolved gaps without exposing vulnerable people.
Measure communication by trust and action
- Percentage of requests acknowledged within the stated time
- Percentage assigned to a named owner
- Local participants represented in decisions
- Diaspora skills matched to defined tasks
- Updates published on schedule
- Projects closed with an outcome and expenditure note
- Corrections issued visibly
- Complaints resolved or escalated
Primary guidance
- IOM Diaspora Mapping Toolkit — evidence-based mapping, ongoing engagement, ethical data collection and responsible communication.
- IOM Public Communication Campaign Toolkit — participatory message design, delivery and evaluation.