Skip to content
EMPOBase
en

What accountability to affected populations means in daily work

By the EMPOBase team · · 4 min read

Short answer

Accountability to affected populations (AAP) means that the people you serve can get information, take part in decisions, give feedback and complain, and see that you act on what they say. In daily work, it is a set of small habits: telling people what to expect, asking before you decide, listening, responding, and changing your plans.

Key points

  • AAP is a way of working, not a separate department or a form.
  • Four habits cover most of it: share information, involve people, hear feedback, act on it.
  • Start with the decisions your team makes each week and ask who was consulted.
  • Feedback only counts as accountability when people can see what changed.

What does AAP mean?

Accountability to affected populations (AAP) means that the people your work is meant to help have a real say in it. They know what you plan, they can influence it, they can complain, and they see results.

The word “accountable” means answerable. You are answerable to donors, to your board, and to the people you serve. The last group often has the least power, so AAP asks you to build in ways for them to be heard.

What are the main parts?

Most descriptions share four ideas. Think of them as four habits.

  1. Share information. Tell people who you are, what you offer, who is eligible, how you chose them, and what they can expect. Use their language and formats they can use.
  2. Involve people. Ask for their views when you plan, and again as you go. Include women, older people, young people, and people with disabilities.
  3. Hear feedback and complaints. Offer safe, accessible channels. See how to set up a complaints and feedback mechanism.
  4. Act and report back. Change what you do, and tell people what changed and why.

What does it look like in a normal week?

AAP shows up in small, concrete moments.

MomentAn accountable practice
Planning a distributionAsk community members about timing and location before fixing them
Selecting peopleExplain the criteria publicly and offer a way to ask questions
At the distributionStaff wear ID, and a help desk takes questions on the day
After the activityA short survey or group discussion on what worked
Monthly team meetingReview feedback cases and decide what to change
ReportingShare a short summary of what you heard and did with the community

If a decision is made without any of these, ask who was left out and why.

How do you start with limited time?

You do not need a large program.

  1. List your regular decisions. Targeting, locations, timing, items, staffing.
  2. For each, ask who was consulted. If the answer is “nobody”, pick one decision to open up first.
  3. Set up one reliable feedback channel. Make sure people know about it.
  4. Hold a short review each month. Look at feedback, decide on one change, and tell people.
  5. Write down what you changed. This is your proof of accountability.

What are the common pitfalls?

  • Collecting feedback and doing nothing. People notice, and stop speaking.
  • Only hearing from community leaders. Leaders matter, but they may not speak for everyone.
  • Using channels people cannot access. A hotline is no use where there is no phone signal.
  • Treating AAP as paperwork. A form does not make you accountable.
  • Ignoring sensitive feedback. Reports about abuse need a protected route, not the general queue.

Our article on what MEAL is shows where accountability sits in the full monitoring, evaluation, accountability and learning cycle.

How do you show that you are accountable?

Keep simple evidence: what you told people, who you consulted, what feedback you received, what you changed. Report the numbers, such as cases received and closed, alongside examples of changes made. Be open about what you could not change and why. Check what your donors and the standards you follow require.

A small example shows the habits at work. A team plans a cash distribution. Before fixing the date, a staff member talks with groups of women, men and older people in the village. They learn that the market day clashes with the planned day, and that older people cannot walk to the proposed venue.

The team changes the date and sets up a second pickup point. They tell the village what changed and why. After the distribution, they hold a short discussion to hear how it went. A few weeks later, the team reports back: “You told us about the market day and the distance. We changed both. You also asked for earlier notice, and we will give a week.”

Nothing here needed new software or a large budget. It needed a decision to ask, to listen, and to answer. That cycle, repeated, is accountability.

Where EMPOBase fits

EMPOBase’s MEAL module includes Complaints & Feedback (CFM), Monitoring and Risk & Learning, so feedback cases, results and lessons sit in the same workspace. The software helps you record and follow cases, and see them next to project results. It does not talk to communities for you. Your team still has to consult people, run the channels and report back. See the platform page for the module list.

Questions people ask

Is AAP the same as a complaints mechanism?

No. A complaints and feedback mechanism is one tool. AAP is wider: it covers information, participation, feedback and how you use what you hear to change your work.

Who is responsible for AAP?

Everyone. A MEAL or community engagement officer may coordinate it, but managers and field staff carry it out. Leaders are responsible for making sure it happens.

How does AAP relate to the Core Humanitarian Standard?

The Core Humanitarian Standard sets out commitments on communication, participation and feedback that match AAP. Read the standard itself for its exact wording and apply what fits your context.