Accountability governance and power analysis · Lesson 3

Participation charter and boundaries

6 min read

Lesson objectives

  • Apply participation charter and boundaries to a fictional humanitarian case and justify the decision, limits and observable output.
Reading tools

Participation has different value at different decision gates. During needs assessment, staff may ask people about access barriers. During service design, people can compare feasible options. During delivery, they may reveal harm the plan did not anticipate. During evaluation, they can challenge the interpretation of results. If views are gathered after resources are committed and the location is fixed, do not call a presentation of the decision co-design. At each gate, specify what remains open, what is closed by an agreement, resource ceiling or safety constraint, and who can reopen it. Candour does not diminish participation. It prevents using people's time to legitimise a choice that will not change. Do not promise a final vote where the organisation cannot transfer its responsibility for safety or resource use.

Four practical levels can be distinguished without treating them as a fixed moral ladder. Information gives people what they need to understand a service and how to challenge it. Consultation requests their experience while the organisation retains the decision and must explain why proposals were accepted or rejected. Co-design develops and tests options with diverse participants before selection. Bounded delegation gives a defined group authority to choose within an announced scope, budget and safeguards. The highest level is not always appropriate. Allocating scarce resources between competing groups may require an independent equity review; a sensitive risk may call for a specialist decision. The error is to advertise delegation while management can ignore the result without explanation, or to call a poster consultation because people saw it. Describe participants' authority in plain language rather than relying on the method's label.

A concise participation charter answers six questions before a session: What decision is at stake? Which alternatives are feasible? Who is invited and why? How will representation gaps be addressed? What authority does each party hold? When and how will an answer return? Add a safe way to challenge an invitation or facilitation arrangement that gives someone inappropriate influence. If the decision concerns household eligibility, do not collect applicants' names in a group discussion to rank them. Participants can discuss whether criteria are understandable and what effects they have using aggregated information, while individual cases remain in protected channels. Ask what participation costs people: travel, work time, care duties or the risk of being seen. Reimbursing such costs should not become a reward conditional on a preferred opinion or a reason to favour people able to attend repeatedly.

Where proposals conflict, do not substitute a popularity count for comparison. For each option, record effects on access, staff workload, possible unintended harm, reversibility and whose voice is still missing. An evening window may help daytime workers but prevent others from travelling home safely. A trial on a specified day, with monitoring, may be better than moving the entire service. Do not presume one participant speaks for a whole group. Ask what their knowledge covers, and check whether other channels reveal another picture. Management may decide against the preference of most attendees, but it should record the decision criterion, contradictory evidence and how the effect will be watched. A sound participation charter leaves space for criticism after the decision; participation does not end when meeting minutes are closed.

Read the charter from an invitee's perspective. Do they know how to use the answer if they disagree? Can they leave the discussion without losing service? Can they see the difference between a personal preference and a collective decision affecting others? Then read it from management's perspective: can it deliver the promise by the stated time? If not, narrow the promise before the meeting and explain why. If new information emerges after agreement, do not silently move the participation boundary. Announce the change and reopen the portion it affected. These disciplines protect trust when not every preference can be met.

Keep a proposal record separate from an approval record. If participants propose another evening, record that it will be tested, not that it has been adopted before capacity and effects on others are checked. Give an intelligible reason for rejection and an owner and response date for a pending idea. A safeguarding allegation belongs in a specialist route, not in a timetable design meeting. Aggregated patterns may inform design only after unnecessary identity details are removed.

Lesson summary

Accountability begins with a decision that people can understand and challenge, not with a feedback box detached from management.