Introduction
The success of a non-profit organisation is no longer measured solely by the number of people reached through its services. It is also measured by its ability to understand how beneficiaries experienced those services, what worked, what did not, and what needs to change.
A programme may appear successful according to organisational indicators while beneficiaries still face complicated procedures, unclear information, barriers to accessing services, or inappropriate treatment that may never appear in conventional reports.
This is where Complaints and Feedback become essential.
A complaint is not necessarily evidence of organisational failure, just as the absence of complaints does not necessarily indicate success. Beneficiaries may remain silent because they do not know how to complain, do not believe anything will change, or fear that raising concerns could affect their access to services.
Mature organisations therefore treat beneficiary voices as a source of information, accountability, and organisational learning, rather than as problems to be managed away.
This sits within the broader concept of Accountability to Affected People (AAP), which involves engaging affected people in decisions that concern them, providing them with relevant information, enabling them to express opinions and concerns, and responding appropriately to their feedback.
An effective system therefore begins before a complaint is ever submitted:
Inform Beneficiaries of Their Rights → Provide Appropriate Channels → Receive Their Feedback → Classify the Case → Resolve or Refer It → Enable Escalation Where Appropriate → Close the Case → Analyse Patterns → Implement Improvements → Communicate What Changed
This is the difference between having a complaints box and operating an institutional Complaints and Feedback Mechanism.
This article develops the framework established in the original version, including the distinction between different forms of feedback, confidentiality, fairness and non-retaliation, the complaint lifecycle, analysis, performance indicators, and the role of leadership and governance.
First: Complaints Are Not the Problem — Silence May Be
Some organisations view a low number of complaints as an indicator of beneficiary satisfaction.
That conclusion can be misleading.
A beneficiary may not complain because they:
- Do not know a complaints mechanism exists.
- Do not know where or how to submit a complaint.
- Cannot access the available channels.
- Believe complaining will make no difference.
- Fear losing access to services.
- Fear that the employee concerned will discover their identity.
- Find the process too complicated.
- Face language, disability, literacy, or digital-access barriers.
The better question is therefore not:
How many complaints did we receive?
but:
Can beneficiaries speak when something is wrong, and do they trust the organisation to listen without causing them harm?
An increase in complaints after introducing a new mechanism may therefore be a positive indicator of increased awareness and trust rather than evidence that service quality has deteriorated.
Second: Not Every Message Received by the Organisation Is a Complaint
Feedback should be classified from the outset because different types of input require different responses.
Complaint
An expression of dissatisfaction concerning a service, procedure, decision, or behaviour that the complainant believes caused harm or was unfair or inconsistent with stated standards.
A complaint will generally require review, a decision, and a response.
Feedback
Positive or negative views about a beneficiary's experience with a programme or service that can be used to assess quality and improve performance.
Suggestion
An idea proposed by a beneficiary to improve a service or procedure or contribute to the design of a new programme.
Enquiry
A request for information or clarification concerning services, procedures, or eligibility criteria.
Compliment
Positive experiences also matter. They help the organisation understand which practices beneficiaries value and which should be maintained or expanded.
This simple classification prevents a common problem: placing every incoming message into the same administrative workflow despite major differences in its nature and priority.
Third: Do Not Wait for Complaints — Ask Beneficiaries What They Think
A mature system does not passively wait until a beneficiary becomes dissatisfied enough to submit a complaint.
Instead, the organisation proactively seeks feedback through appropriate mechanisms such as:
- Beneficiary satisfaction surveys.
- Interviews.
- Focus group discussions.
- Follow-up calls after service delivery.
- Field assessments.
- Digital surveys.
- Community meetings.
- Suggestion and feedback channels.
The objective is not to collect the largest possible number of surveys.
It is to obtain information that helps answer questions such as:
Is the service appropriate? Is access fair? Is the information clear? Do beneficiaries feel safe and respected? What needs to change?
Feedback therefore becomes part of programme design, monitoring, and improvement, rather than a separate activity conducted only after a project has ended.
Fourth: Accountability to Beneficiaries — From Service Delivery to Participation
Complaints and Feedback Mechanisms are closely connected to Accountability to Affected People (AAP).
Accountability does not simply mean allowing people to submit complaints.
Beneficiaries should understand:
- What services the organisation provides.
- Who is eligible to receive them.
- What criteria and procedures apply.
- What they can reasonably expect from the organisation.
- How they can provide feedback or submit a complaint.
- What will happen after a complaint is submitted.
Accountability also means enabling affected people to influence decisions that concern them where appropriate and feasible.
Beneficiaries are not merely data sources or end recipients of assistance.
They possess knowledge that the organisation may not have:
Their lived experience of the service.
Fifth: Designing a System That People Can Actually Use
Having a complaints email address does not mean an organisation has an effective Complaints and Feedback Mechanism.
An institutional system requires several elements working together:
- A clear Complaints and Feedback Policy.
- Defined scope for cases covered by the mechanism.
- Clear responsibilities and authorities.
- Appropriate reporting channels.
- A system for recording and tracking cases.
- Classification by type and severity.
- Response and resolution timeframes.
- Escalation and referral procedures.
- Confidentiality protections.
- Non-retaliation rules.
- Closure and documentation procedures.
- Periodic trend analysis.
- Corrective-action monitoring.
- Management and leadership reporting.
Most importantly, the mechanism should make sense to beneficiaries themselves, not only to the employees responsible for administering it.
Sixth: Multiple Channels Matter — but Appropriate Channels Matter More
Beneficiaries differ in age, language, ability, access to technology, and social circumstances.
Depending on the organisation and its programmes, available channels may include:
- Telephone.
- Email.
- Website.
- Paper forms.
- Approved messaging applications.
- Complaints boxes.
- In-person interviews.
- Community engagement staff.
- Digital applications and platforms.
- Surveys and community meetings.
However, the number of channels is not an objective in itself.
If an organisation serves people who do not use the internet, an online form alone will not be sufficient.
If complaints may concern field staff, requiring beneficiaries to submit complaints through those same employees may not provide a safe or independent channel.
Channels should therefore be designed around one central question:
Can different beneficiaries use this channel easily, safely, and independently?
This includes considering the needs of older people, persons with disabilities, people with limited literacy, and groups facing social or technological barriers.
Seventh: Confidentiality, Fairness, and Non-Retaliation
Beneficiaries will not use a mechanism if they believe they may be punished for speaking.
An effective system should therefore be based on clear principles.
Confidentiality
The identity of the complainant and details of the complaint should only be accessible to those who need the information to handle the case.
Impartiality
A person directly involved in the subject of the complaint should not be solely responsible for deciding its outcome.
Fairness
Relevant facts should be reviewed, affected parties should be heard where appropriate, and neither side should automatically be presumed right or wrong.
Non-Retaliation
Submitting a complaint or feedback in good faith should not result in loss of service, reduced eligibility, or adverse treatment.
Transparency
The complainant should understand, to an appropriate extent, what will happen to the case and when a response can be expected.
These are not merely ethical statements. They are essential conditions for building a mechanism that people can trust and use.
Eighth: What About Anonymous Complaints?
In some circumstances, individuals may fear disclosing their identity, particularly where a concern involves a person in a position of authority or where retaliation is feared.
Organisations may therefore allow anonymous complaints where appropriate.
Anonymous reports should be taken seriously, while recognising that the absence of contact details or sufficient information may sometimes limit the organisation's ability to request clarification, conduct a complete investigation, or communicate the outcome to the complainant.
The key principle is:
Not knowing the identity of the complainant does not automatically make the information irrelevant.
Ninth: Not All Complaints Are Equal
This is one of the most important principles in designing the mechanism.
A complaint about waiting times is not equivalent to an allegation of fraud.
Feedback about a complicated registration form is not equivalent to a report involving the abuse of a child.
The system therefore needs Triage and Classification to determine severity and the appropriate response pathway.
For example:
Lower-Risk Cases:
Enquiries, service delays, and limited procedural problems.
Moderate-Risk Cases:
Disputes over decisions, staff conduct, or recurring operational issues.
High-Risk Cases:
Suspected fraud or corruption, serious misconduct, threats to safety, or other cases requiring specialised escalation.
The purpose of classification is not merely to label a complaint.
It determines:
Who handles it? What priority does it receive? What is the response timeframe? Does it require referral or investigation?
Tenth: Sensitive Complaints and Safeguarding Require a Different Pathway
Some reports should not enter the ordinary operational complaints process.
Depending on the organisation's activities, a report may involve safeguarding concerns, exploitation, abuse, harassment, or conduct that threatens the safety of a child or another person at risk.
Such cases should activate the organisation's approved safeguarding and referral pathway, rather than being circulated among staff as ordinary service complaints.
Depending on the case and applicable policies, this may involve:
- Restricting access to information.
- Rapid referral to an authorised person or function.
- Prioritising the safety of the affected individual.
- Protecting confidentiality.
- Avoiding inappropriate investigation by unqualified personnel.
- Documenting the case according to specialised procedures.
The fundamental principle is:
Where a complaint may involve someone's safety or a serious violation, protection and specialised handling take priority over rapidly closing the case.
Eleventh: The Complaint Lifecycle
Complaint handling should not depend on the personal judgement of whichever employee happens to receive it.
A clear workflow can be established:
Receipt → Registration → Triage and Classification → Acknowledgement → Resolution or Referral → Decision → Communication → Appeal or Escalation Where Appropriate → Implementation → Closure → Analysis
Receipt and Registration
The case is recorded and, where appropriate, assigned a reference number while collecting only the information necessary for handling it.
Triage and Classification
The nature, severity, and appropriate responsible function are determined.
Acknowledgement
The complainant is informed that the case has been received and, where possible, what will happen next and the expected timeframe.
Resolution
Necessary information is gathered and relevant facts and policies are reviewed.
Decision
A decision is made based on the available evidence and authorised responsibilities.
Response
The complainant is informed of the outcome or action taken to the extent permitted by confidentiality requirements.
Implementation
A complaint is not resolved merely because a decision has been made. Required actions must actually be implemented.
Closure
The case is closed once required actions have been completed and the outcome appropriately documented.
This distinction matters:
“Closed” should not simply mean that an employee closed the ticket. It should mean that the required actions have been completed according to established closure criteria.
Twelfth: What If the Beneficiary Disagrees with the Decision?
A fair mechanism should provide an Escalation or Appeal pathway for cases where such a review is appropriate.
Beneficiaries should know:
- Whether they can appeal.
- Within what timeframe.
- How to submit an appeal.
- Who will review it.
- When they can expect a response.
Where the nature of the case requires greater independence, the person who made the original decision should not be the sole authority reviewing the appeal.
A clear escalation mechanism does not weaken the organisation.
It reduces arbitrary decision-making and strengthens confidence in the fairness of the process.
Thirteenth: From Complaint to Organisational Improvement
The real value of complaints begins after the individual case has been handled.
Suppose an organisation receives an increasing number of complaints over two months concerning rejected registration applications.
If each complaint is handled separately and closed, the organisation may miss the underlying problem.
Trend analysis may reveal that most cases relate to a single document requirement that beneficiaries do not understand.
The organisation can then move from:
Handling the Complaint
to:
Identifying the Pattern
then:
Finding the Root Cause
then:
Changing the Process
and finally:
Measuring the Result
The solution might involve revising registration instructions, simplifying a requirement, or retraining staff.
The complaint has now become a source of system improvement, rather than merely a case to be closed.
Fourteenth: The Complaints Register Is Not an Archive
A Complaints and Feedback Register should help the organisation understand what is happening, rather than simply prove that complaints were received.
Depending on organisational needs, it may record:
- Case reference number.
- Type of input.
- Programme or service concerned.
- Reporting channel.
- Severity.
- Date received.
- Responsible person or function.
- Case status.
- Response and closure dates.
- Outcome.
- Root cause where appropriate.
- Corrective action.
- Person responsible for implementing the improvement.
Periodic analysis then allows management to ask:
Which problems occur most frequently?
Where are they happening?
Are they associated with a particular programme, location, or procedure?
Do they recur after being closed?
Which corrective actions remain outstanding?
The register therefore becomes Management Information that supports decision-making.
Fifteenth: Close the Feedback Loop
One of the most common mistakes is repeatedly asking beneficiaries for feedback without ever showing them what happened afterwards.
This is where Closing the Feedback Loop becomes important.
Where feedback results in a meaningful change, the organisation can appropriately communicate:
What did we hear?
What did we learn?
What did we change?
For example:
Beneficiary feedback showed that registration procedures were unclear, so the instructions and registration steps were simplified.
This can be communicated without revealing the identity of complainants or confidential case details.
The message is powerful:
Your feedback does not disappear into a closed box. It can lead to change.
This, in turn, strengthens trust and encourages future participation.
Sixteenth: How Should Effectiveness Be Measured?
The number of complaints alone is not an adequate performance indicator.
More useful indicators may include:
- Percentage of beneficiaries who know how to submit a complaint.
- Average initial response time.
- Average resolution time.
- Percentage of cases closed within approved timeframes.
- Percentage of overdue cases.
- Percentage of recurring complaints concerning the same cause.
- Complainant satisfaction with the handling process.
- Use of complaints channels by different beneficiary groups.
- Number of corrective actions resulting from feedback.
- Percentage of corrective actions implemented.
- Recurrence of issues after corrective action.
These indicators must be interpreted carefully.
Fewer complaints should not automatically be treated as the objective.
The objective is to maintain an accessible and trusted system that handles cases fairly and uses the resulting information to improve services.
Seventeenth: The Role of Leadership and Governance
A Complaints and Feedback Mechanism will not succeed if leadership treats complaints as threats to the organisation's reputation.
Leadership should instead turn them into sources of learning and accountability.
Its role includes:
- Approving policies and responsibilities.
- Providing necessary resources.
- Overseeing high-risk cases within appropriate authority structures.
- Reviewing complaint trends.
- Monitoring corrective actions.
- Protecting the independence of escalation and investigation mechanisms.
- Preventing retaliation.
- Promoting learning rather than concealment of mistakes.
Leadership should not receive only a report saying:
“We received 85 complaints and closed 80.”
It needs to understand:
Why did people complain? What patterns emerged? What risks were identified? What changed? Did the problem happen again?
At this point, the Complaints and Feedback Mechanism becomes an actual component of governance, risk management, and quality management, consistent with the framework established in the original article.
Eighteenth: How Can a Donor Know That the Complaints Mechanism Actually Works?
A statement in an organisational policy saying “beneficiaries may submit complaints” is not sufficient evidence of an effective system.
During institutional due diligence, a donor or partner may look for evidence such as:
- Complaints and Feedback Policy.
- Complaint-handling procedures.
- Published and accessible reporting channels.
- Complaints and Feedback Register.
- Case severity classification.
- Response and resolution timeframes.
- Escalation and Appeal Procedure.
- Safeguarding and sensitive-case referral pathways.
- Confidentiality and non-retaliation controls.
- Staff training records.
- Complaint trend-analysis reports.
- Corrective Action Register.
- Evidence that improvements were implemented.
- Performance indicators for the mechanism.
The organisation should therefore be able to answer not only:
Do we have a complaints mechanism?
but:
Can we demonstrate that beneficiaries can use it safely, that the organisation responds, and that what we learn leads to improvement?
This is the difference between having a formal mechanism on paper and operating an effective institutional accountability system.
Nineteenth: From Service Recipient to Partner in Impact
Beneficiaries are the people closest to the experience that the organisation is trying to improve.
The organisation may see a programme through:
Budgets, activities, performance indicators, and beneficiary numbers.
Beneficiaries experience it through different questions:
Did I understand the service? Could I access it? Was I treated with dignity? Did it meet my needs? Did anyone listen when I experienced a problem?
Neither perspective replaces the other.
Bringing them together gives the organisation a more realistic understanding of programme quality.
Beneficiary participation does not mean that beneficiaries make every organisational decision. It means establishing a genuine mechanism for hearing their experiences, analysing them, and incorporating relevant learning into decisions that improve services and impact.
Before Moving to the Next Article...
A charity can begin with practical steps:
✓ Adopt a clear Complaints and Feedback Policy.
✓ Inform beneficiaries of their right to provide feedback and submit complaints.
✓ Provide multiple appropriate and accessible channels.
✓ Establish confidentiality and non-retaliation protections.
✓ Allow anonymous reporting where appropriate.
✓ Classify cases according to nature and severity.
✓ Separate Safeguarding and sensitive cases from the ordinary operational pathway.
✓ Define clear response and resolution timeframes.
✓ Provide escalation and appeal mechanisms where appropriate.
✓ Maintain a central register of cases.
✓ Analyse trends and root causes.
✓ Monitor corrective actions through completion.
✓ Communicate improvements resulting from beneficiary feedback where appropriate.
Quick Self-Assessment
Ask yourself:
□ Do beneficiaries know that they have the right to provide feedback or submit complaints?
□ Do they know how and where to do so?
□ Are the available channels accessible to the different groups we serve?
□ Can a beneficiary complain without fearing loss of service?
□ Do we protect complainant identities and sensitive information?
□ Can we receive anonymous reports where appropriate?
□ Do we distinguish ordinary complaints from Safeguarding concerns and other high-risk cases?
□ Are there clear response and resolution timeframes?
□ Can beneficiaries escalate a case or appeal a decision where appropriate?
□ Do we analyse the causes of recurring complaints?
□ Do we monitor corrective actions through implementation?
□ Can we identify actual improvements that resulted from beneficiary feedback?
□ Could we provide evidence of all of this if requested by a donor?
If the answer is “No” to several of these questions, the problem may not be that beneficiaries are unwilling to speak.
The organisation may simply not yet have built a system that makes speaking easy, safe, and worthwhile.
Conclusion
The value of a Complaints and Feedback Mechanism is not determined by the number of channels an organisation provides or the number of cases it manages to close.
Its real value becomes visible when a beneficiary can say:
There is a problem.
And the organisation can listen safely, understand what happened, protect the person from retaliation, handle the case fairly, and then look beyond the individual complaint and ask:
Why did this happen? Is it happening to others? What should we change?
When the answer results in an improved service, a simplified procedure, a mitigated risk, staff training, or a revised policy, the feedback loop is completed.
The beneficiary then moves from being someone who simply receives a service to becoming a source of knowledge and a partner in improving it.
That is the essence of a mature institutional Complaints and Feedback Mechanism: not protecting the organisation from criticism, but building an organisation capable of listening, accountability, learning, and continuous improvement.
