What is a CFM and why build one?
A complaints and feedback mechanism (CFM) is how affected people tell you what is working, what is not, and what has gone wrong. It is a core part of accountability. Without it, you find out about problems late, or never.
A good CFM protects people. It gives them a safe way to raise issues such as unfair selection, wrong items, or staff misconduct. It also gives your team early warning, so you can fix things before they grow.
How do you design it?
Follow these steps.
- Ask the community. Hold discussions with women, men, older people, young people and people with disabilities. Ask: how would you prefer to raise a concern? Who do you trust? Which channels can you reach?
- Choose several channels. Examples are a suggestion box, a hotline, a help desk at distributions, community committee members, and face-to-face contact with staff. Different groups prefer different ones.
- Include a confidential route. Some people will not speak in public. Offer a way to give feedback privately.
- Define case types. Typical groups are questions, requests, suggestions, complaints about services, and serious concerns such as abuse or fraud.
- Assign owners. For each type, name the role that handles it.
- Set response times. Choose a target for acknowledging and for resolving each type.
- Tell people. Explain what the CFM is, how to use it, and what happens next, in the languages people speak.
How do you handle sensitive cases?
Some cases cannot go through the normal queue. Allegations of sexual exploitation and abuse, fraud, or threats need a separate route with few people involved.
- Refer straight away to the designated focal point or your safeguarding process.
- Limit access to the case details to those who must act.
- Never ask the person to repeat the story to many staff.
- Think about safety. Do not contact someone in a way that could put them at risk.
Your organization’s policy and local law decide the exact steps. Check both. Our article on what accountability to affected populations means in daily work places the CFM within wider practice.
What should a case record contain?
A simple record is enough, if it is used the same way every time:
| Field | Purpose |
|---|---|
| Case number | Unique reference |
| Date received and channel | Shows which channels work |
| Case type | Decides who handles it |
| Description | What was said, in the person’s words |
| Owner | Who is responsible |
| Action taken and date | The response |
| Status | Open, in progress, closed |
| Feedback to the person | Whether they heard back |
Keep personal details to the minimum, and restrict who can see them.
How do you close the loop?
Many mechanisms receive feedback and never reply. People then stop using them.
- Acknowledge each case, if the person can be reached.
- Tell the person what you did, or why you cannot act.
- Share common themes with the community: “You told us the distribution was too far. We moved it.”
- Review the cases monthly in a team meeting. Look for repeat issues, slow responses and channels nobody uses.
- Feed what you learn into project decisions.
How do you know it works?
Check three things regularly: do people know about it, do they use it, and do they trust it. Ask in community meetings or surveys. Watch who is not using it, since a CFM that only men use is missing something. Track how many cases are closed within your target time.
One practical point is staff training. A channel only works if the person who receives a concern knows what to do. Train every staff member and volunteer who meets communities to listen without judging, to write down what was said, to explain what happens next, and to pass sensitive cases on at once without investigating them alone. Run a short practice session with role play, and repeat it when new staff join. Also test the CFM yourself, by sending a trial message through each channel and following it to the end, to see where it gets stuck.
Where EMPOBase fits
EMPOBase’s MEAL module includes Complaints & Feedback (CFM), so your cases are logged in the same workspace as your projects and indicators. It is a place to record and follow cases; it does not set up your channels, such as a hotline or a suggestion box, and your team still runs the process. For cases of abuse or exploitation, EMPOBase also has Safeguarding & PSEA. Look at the platform page for the full module list, or ask us for a walk-through.