SOPs for NGOs
Every organisation runs on recurring tasks. Without a written procedure, each one depends on whoever happens to remember how it was done last time.
For NGOs, charities, and foundations, SOPs help document ways of working, secure key processes, and transfer knowledge without depending on a single person.
What they are
A standard operating procedure (SOP) is a written, step-by-step description of how a recurring task gets done, who is responsible for each step, in what order actions should happen, and what good looks like.
It is not a lengthy policy document. It is a short, practical reference someone can follow without having to ask.
Why they are essential
- Continuity when staff leave or change roles, nothing depends on one person's memory
- Faster onboarding, new staff can follow a written process from day one
- Consistency across teams, national offices, and field staff
- Easier scrutiny from funders, boards, and auditors, since the process is documented rather than described after the fact
- Fewer mistakes during busy or high-pressure periods, such as an emergency appeal or a year-end campaign
How they are used in other sectors
SOPs are standard practice well beyond the NGO world. Franchise businesses rely on them to guarantee the same experience in every location. ISO quality management systems require them as a condition of certification. Call centres formalise recurring interactions so that quality does not depend only on which person answers.
The same discipline can adapt well to a resource-constrained NGO context. If anything, it matters more, since smaller teams have less slack to absorb the disruption of losing undocumented knowledge.
Where to start
There is no need to document the whole organisation at once. The first SOPs should focus on processes that meet at least one of these criteria:
- They are repeated often
- They involve several people or teams
- They carry risk if done incorrectly
- They are difficult to explain verbally
- They currently depend on one person
For an NGO, this might start with approving a donor email, processing a tax receipt, publishing content, importing a contact list, or preparing a donor report.
A simple example
A short SOP for approving a donor communication before it goes out.
| Step | Action | Owner |
|---|---|---|
| 1 | Draft the communication using the approved template | Communications officer |
| 2 | Check facts, figures, and any donor commitments referenced | Programme lead |
| 3 | Verify data protection and consent requirements are met | Data protection lead |
| 4 | Final sign-off before publishing | Head of communications |
| 5 | Publish and archive a copy with the sign-off date | Communications officer |
Five steps, five roles, and no ambiguity about who does what, or in which order.
A simple structure
A good SOP template asks the same questions every time, so nobody has to invent the format from scratch. Here is the structure I use.
| Section | What goes there |
|---|---|
| Purpose | One or two sentences, what this procedure achieves and why it exists |
| Scope | Which team, department, or process this applies to |
| Definitions | Any term someone outside the team might not recognise |
| Tools | The systems or platforms involved in carrying it out |
| Roles and responsibilities | Who does what, named by role rather than by person where possible |
| Procedure: preparation | What needs to be in place before starting |
| Procedure: steps | The actual sequence, numbered, one action per line |
| Procedure: completion | Sign-off, reporting, and any cleanup |
| References | Related documents, policies, or external guidelines |
| Revision history | Version, date, and what changed, so the procedure stays trustworthy over time |
The risk of SOPs becoming too heavy
The risk is not only having too few procedures. It is creating documents that are too long for anyone to read. A good SOP should stay short, active, and easy to update. If it cannot be used during real work, it is not yet serving its purpose.
Templates
I am preparing downloadable Notion templates for common NGO SOPs: approving a donor communication, managing a form, importing contacts, publishing content, preparing a donor report, or following up on an internal request.
The goal is not to add another administrative layer. It is to give teams a clear, simple, and reusable base for working with less ambiguity, less dependence on individual memory, and more continuity.
Resource last updated 7 July 2026