NGO Field and Operations Notice

What a good one includes

• A clear, high-contrast header indicating the security level, distribution scope, and effective date of the operational change.
• A concise context section explaining the driving force behind the notice, such as security updates or regulatory shifts, to build immediate buy-in.
• Step-by-step, bulleted directives that outline exactly what behaviors, procedures, or reporting structures must change immediately.
• A dedicated section detailing who is affected, specifying differences in instructions between international staff, local volunteers, and community partners.
• Clear contact details for designated safety officers or operations managers to handle escalation, questions, and emergency support.
• An official acknowledgment mechanism, such as a confirmation link or sign-off line, to track compliance across remote field offices.

Common mistakes to avoid

• Using overly academic or dense policy jargon that confuses local field staff and volunteers who may speak English as a second language.
• Failing to clearly separate optional best practices from mandatory safety and operational directives.
• Neglecting to specify an exact effective date or timeline, leading to delayed implementation in critical field scenarios.
• Omitting a clear point of contact, leaving field workers stranded without support when trying to implement complex new rules.

Frequently asked questions