In this article
Begin with a useful review question
Before collecting feedback, decide what the programme needs to learn. The question might concern access, the usefulness of a particular service or a recurring difficulty after enrolment. A focused question helps avoid collecting personal information simply because it could become interesting later. It also makes the review easier to explain to participants.
For Captain welfare work, connect the question to a decision that someone can make. If a programme wants to understand why appointments are missed, it may need information about timing and travel rather than a detailed personal history. Define the smallest useful record and identify who will review it.
Explain participation and permissions separately
Tell people what the review involves, who will see their responses and how the findings will be used. Explain whether participation is optional and any limits on confidentiality. Do not present an optional interview as an unavoidable step in receiving support. Where information is necessary to provide a service, make that purpose clear instead of disguising it as voluntary feedback.
The UN system’s privacy principles offer a reference for specified purpose, proportionate collection and transparency. They apply within the UN system, so the actual programme must separately establish its applicable obligations. As a design practice, keep permission for evaluation distinct from permission to publish a name, photograph or personal story. One conversation should not silently authorise every later use.
Interpret responses in their circumstances
A participant’s account can explain an experience without proving the programme caused a wider change. Working hours, household circumstances and other services may also affect what happened. Listen to the account on its own terms, then distinguish what was directly observed from what the review is inferring. Include different experiences rather than selecting only the easiest success stories.
HM Treasury’s evaluation guidance distinguishes monitoring from evidence of causal impact. For a support review, that means attendance, satisfaction and an outcome each answer different questions. State the period, who contributed and any important gaps. A small voluntary feedback exercise can guide improvement without being presented as a representative measure of every Captain’s experience.
Share the learning without exposing the person
When reporting to community and institutional partners, use summaries that fit the audience and purpose. A small group can sometimes be identifiable even after names are removed, especially when a location or unusual circumstance is included. Review the detail before sharing, and keep sensitive individual matters in the appropriate resolution process.
Give participants an understandable account of what was learned and what will change where practical. Assign an owner for the improvement and a time to review it. Keep retention and access responsibilities clear for the underlying records. A useful review respects the person contributing, makes its limits visible and produces a specific next step for the support programme.
