Give people an alternative contact, an honest explanation of privacy, and a fair response they can follow.
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
A fictional community conversation about a service concern. The people shown are not FWF participants or personnel.
A person can know exactly where the complaints box is and still feel unable to use it. Perhaps the person who opens it also controls their place in the activity. Perhaps a shared email address is read by the volunteer whose conduct they want to discuss. The instruction to speak up sounds welcoming, but the route asks them to take a risk the organization has not acknowledged.
For a small nonprofit or community group, the practical question is not simply whether a complaints process exists. It is whether someone can raise a concern without first persuading the person involved to accept it. This article offers a service-design exercise for ordinary complaints. It does not establish FWF policy, replace safeguarding procedures, or prescribe legal duties across countries.
Follow the concern, not just the inbox
Consider a fictional adult craft club. Rosa has twice arrived for a reserved sewing-machine session and found that her place was given to someone else. She wants the booking checked and a reliable place next time. The posted instruction says to speak to the session coordinator, who made both decisions. Rosa does not want a public argument or to leave the club. She wants someone else to look at what happened.
There are several separate jobs here: receiving Rosa's concern, checking whether anything needs urgent attention, deciding who can review it fairly, explaining the result, and completing any agreed correction. One person may perform several jobs in a small organization, but the arrangement should not leave the subject of a complaint as its only gatekeeper. A general invitation to send feedback does not settle that problem.
CHS Alliance's guidance for humanitarian and development organizations emphasizes visible, accessible complaint routes, privacy, safety, timely responses and learning. Those are useful reference points for a community group, not evidence that its own arrangements work. The fictional club must still test the route with the people expected to use it.
Offer a second door with a real person behind it
Rosa needs to know who she can contact instead of the coordinator. The club might appoint an uninvolved committee member to receive concerns, with a separate backup when that member is absent or implicated. Before publishing those names or roles, the club should confirm that both people accept the responsibility, can access the appropriate records, and know the limits of their authority. An alternative address that forwards to the original coordinator is not an alternative route.
Choose channels people can actually use and the organization can reliably manage. A private conversation or supported written account may work better than a compulsory online form. Explain where someone can speak without being overheard and whether a trusted person can help them. Ask about a safe way and time to reply. An unexpected voicemail or a message on a shared phone may reveal more than the person intended.
The UK Ombudsman's customer-focused complaint principles, written for public bodies, support simple procedures, communication suited to the person's circumstances, and clarification of the outcome they want. A small group can use those principles as design prompts without claiming that UK public-sector rules govern every community activity. In Rosa's case, the initial conversation should establish the booking problem and requested correction, not require a polished legal argument.
Explain privacy before asking for the full story
Do not promise that nobody else will ever hear about a concern. A reviewer may need to ask another person what happened, and some concerns require a specialist response. Explain who normally receives the information, why further sharing might be necessary, and how the person will be kept informed where appropriate. If the organization cannot explain these boundaries, it should resolve them before advertising absolute confidentiality.
Anonymous and confidential reporting are different choices. An anonymous report omits the person's identity; a confidential process restricts who can access identifiable information. Neither label guarantees that the circumstances will not reveal who was involved. An anonymous concern can still identify a problem, but a missing contact route may prevent follow-up questions or a personal response. Be candid about those limitations rather than rejecting the concern automatically.
The Ombudsman's openness and accountability principles distinguish transparent procedures from protected personal information and call for usable records of evidence and decisions. For this exercise, the club could keep a restricted case record containing the concern, contact preference, assigned reviewer, next update date, decision and action. It does not need to copy the account into a general volunteer chat or a public board report.
A concern involving abuse, immediate danger or another serious safeguarding issue is not an ordinary booking dispute. The receiving person should use the organization's established specialist escalation arrangements rather than improvise an investigation. Applicable reporting obligations and qualified advice need to be checked for the locality and circumstances. The ordinary complaints route should explain where its scope ends; it must not suggest that an unmonitored inbox provides emergency help.
Be fair without making the person prove everything alone
In the fictional club, an uninvolved reviewer can compare Rosa's booking confirmations with the allocation record and hear the coordinator's account. The reviewer should distinguish what the records establish, what each person recalls, and what remains uncertain. If the available information does not support a finding, say that clearly. Listening respectfully does not require accepting every allegation as fact, and fairness to staff does not require dismissing a participant's experience.
The Ombudsman's fairness principles recommend review by someone not involved in the events, decisions grounded in evidence, and fair treatment of staff as well as complainants. They also warn against treating a person differently because they complained. For the club, that means checking practical consequences: is Rosa still receiving booking notices and being considered under the same allocation rules?
A small group may not have enough independence or expertise inside its committee. It should acknowledge that constraint and arrange an appropriate review route under its governing procedures before promising an independent investigation. A friend of everyone involved is not necessarily a suitable reviewer. The important question is whether the person can assess the issue without a conflict that undermines the review.
A response needs a result and a next move
Receipt is not resolution. After acknowledging the concern, give a realistic next update date and identify the contact responsible. If the review takes longer, explain what remains outstanding and provide a revised update. Avoid promising that every complaint will be settled in the same number of days. The person's needs, the issue's seriousness and the work required may differ.
Suppose the club's review finds that Rosa's confirmed bookings were overlooked when a separate paper list was used. Its response can explain that finding, apologize, describe an available replacement session, and say who will check the booking process before the next allocation. It should also explain how Rosa can request a further review if she believes something important was missed. That route should not invent an external appeal body or imply an entitlement the organization has not verified.
The Ombudsman's remedy guidance describes responses including explanation, apology and corrective changes appropriate to the problem. In our example, offering another slot addresses Rosa's immediate experience; reconciling the two booking lists addresses the recurring fault. Record each action separately and check it was completed. Sending a reply is not proof that the underlying service changed.
Rehearse the difficult route before someone needs it
Try a short rehearsal using only invented details. Ask a colleague unfamiliar with the process to play a participant who has a complaint about the usual contact. Give them the information a participant would actually see. Can they find another person, understand the privacy explanation, choose a workable channel, and tell what happens next? Then have the receiving colleague explain who reviews the concern and where the next update will be recorded.
Write one rehearsal note: the point where the route failed, the person responsible for fixing it, the agreed change, and the date of a second test. For Rosa's club, the first failure might be that the alternative committee contact is listed only inside a members-only account she cannot access. The useful improvement is specific: make that route available where participants receive their booking information, then test it again.
This attention to accountable everyday systems connects with Feel Worldwide Foundation Inc.'s Leadership, Institutions & Implementation Capacity pathway. Start with one question this week: if the concern is about our usual contact, where can the person go? Organizations interested in exchanging practical lessons about responsible service design can connect with FWF. Use that invitation for general discussion, not to send confidential case details. A credible route begins with an answer the organization is ready to honor.
Explore Resources for Your Next Step
Start with clear responsibilities and a tested response route; software cannot supply impartiality for you. If you are exploring tools for other parts of your organization's work, the resources below offer places to compare options. Check current terms, costs, accessibility and suitability before choosing, and do not enter confidential complaint records into a tool without an appropriate review.
This section contains affiliate and referral links. Qualifying purchases or sign-ups may generate a commission. Arbab Naseebullah Kasi will donate all commissions he receives through these links to Feel Worldwide Foundation Inc. to support its programs and operations.
For communication and learning, explore ElevenLabs, Synthesia, Pictory, Bookshop and beehiiv. For business tools, website services and independent professional support, compare Zoho, SiteGround and Fiverr.
If travel is part of a separately planned activity, Expedia and Viator are additional options to explore. These links are optional resources, not a requirement to participate in FWF's work or a claim that any provider is suitable for handling complaints.
