A sample Social Welfare Department Funding and Service Agreement for a Neighbourhood Elderly Centre sets one performance standard: at least 75% of service users, carers and elderly volunteers should be satisfied with the service. A note explains that satisfaction is measured through a service-evaluation questionnaire. This is a clear, reportable indicator. It also leads naturally to another question: what happened to the remaining feedback?
The same Service Quality Standards set out a fuller expectation. Service units should collect and respond to views, take account of service-user and staff opinions when reviewing policies and procedures, and follow up on identified service-quality problems. Several handoffs can still break between a percentage and an actual service revision.
Lingxi Insight believes that feedback can become service learning only when it moves through collection, interpretation, decision and response. An NGO is positioned where frontline experience, community relationships and institutional requirements can meet along that path.
What Can One Indicator Show?
Satisfaction has practical uses. It provides a consistent way to observe service users' overall responses, supports periodic reporting, and can reveal marked changes over time. Service volume, participation and satisfaction percentages together provide a basic set of coordinates.
Coordinates are not a route. Two services that both reach 75% satisfaction may face very different situations. In one, a small group of service users may repeatedly raise transport problems. In another, carers may be broadly satisfied with activities but use open-ended questions to explain that the timetable is difficult. If a report retains only the total, the service team cannot see who needs to act, what can change, or which problems fall outside a single unit's authority.
Daniel and Fyall note that public-service contracts and evaluations often rely on output indicators, but such indicators can overlook recruitment methods, service intensity and different understandings of service goals. Numbers can show whether a service is broadly on track; they may not explain how the service reaches users or preserve the institutional friction seen by frontline staff.
NGOs Occupy Several Positions at Once
Daniel and Fyall place nonprofit organisations back within their multiple roles. Beyond providing services, an organisation may build social connections, support civic participation, express stakeholder values, advocate for policy change or test new approaches. The same activity can fulfil several roles, while government, organisations, frontline staff and service users may understand 'a good service' differently.
The authors organise this complexity around four themes: roles coexist; service providers and policy actors may understand services differently; organisational roles change over time; and roles shape whether and how an organisation joins a service network. This theoretical synthesis identifies what policy implementation may overlook. It does not prove that multiple roles necessarily improve outcomes.
A separate study based on survey data from nonprofit organisations in Massachusetts classifies the organisational relationship between service and advocacy as differentiated, compartmentalised, outsourced or integrated. This article uses only the typology verified in the publisher's abstract. It does not cite sample sizes or detailed model results without access to the full text. Its practical reminder is that whether service data enters advocacy or institutional dialogue depends not only on whether an organisation 'does advocacy', but also on whether the two kinds of work have a handoff between them.
Local Rules Already Require Feedback
Hong Kong's self-assessment checklist for the 16 Service Quality Standards is more specific than a requirement to 'run a questionnaire'. Criterion 2.2 asks a service unit to explain how it collects and appropriately considers service-user and staff opinions when reviewing and revising policies and procedures. Criterion 6.2 requires it to collect and respond to views about performance from service users, staff and other concerned parties. Criterion 6.3 further requires follow-up action on identified performance or quality problems and a record of that action.
The local practice problem is therefore not a complete absence of feedback requirements. A more useful check is whether three types of record connect: what questionnaires, complaints or frontline notes preserve; how a review meeting interprets them; and what policy, procedure or service arrangement eventually changes. If all three are compliant in isolation but have no traceable relationship, feedback still struggles to accumulate into organisational learning.
Seventy-five per cent is a result. 'What was received, how was it judged, who decided and how did the organisation respond?' is a governance path.
Four Handoffs: Finding Where Feedback Stops
Four Handoffs: Finding Where Feedback Stops
From collection to response, each step needs clear data boundaries, an owner and a decision record.
Collect
Preserve the sources and limits of questionnaires, open comments, complaints and frontline observations.
Interpret
Distinguish individual preferences, recurring barriers, safety risks and systemic problems.
Decide
Record the owner, response level, reasons for the decision and review date.
Respond
Explain what changed, what did not and when it will be reviewed, so the next cycle does not start from zero.
The first handoff is collection. Questionnaires support comparison through consistent questions. Open comments, focus groups, complaints, case records and staff observations add context. Collection methods should explain purpose, consent and confidentiality, rather than expanding every service conversation into an unlimited personal database.
The second handoff is interpretation. Teams should distinguish individual preferences, recurring barriers, safety risks and systemic problems. They should also ask who is less likely to complete a questionnaire and which views may remain unexpressed because of language, digital access or dependence on the service. The volume of comments alone cannot establish representativeness. Recording sources, limits and counterexamples provides a stronger basis for judgement.
The third handoff is decision. Each material issue needs an owner and a level of response: immediate frontline adjustment, service-manager review, cross-service coordination, or dialogue with a funder. Adoption, piloting, deferral and non-adoption can all be reasonable decisions, but the reasons and review date should be recorded.
The fourth handoff is response. Service users may not need to read full meeting minutes, but they should know whether their feedback was received, what changed, what could not change, and when the issue will be reviewed. A response shows participants whether their views entered a decision and prevents the next feedback cycle from starting from zero.
From Service Data to Institutional Learning
When the same problem recurs across periods, cases or service units, it may have moved beyond the scope of a single activity adjustment. For example, if many carers remain unable to participate because of service hours, frontline staff can first test another time slot. If the constraint comes from staffing, premises or funding specifications, the issue needs to move to management, a collaborative network or dialogue with the funder.
This kind of feedback does not turn every comment into a policy demand. An organisation should state the scope of the evidence, the groups affected, the changes already tested and the remaining constraints. An NGO's public value lies partly in placing abstract rules and service experience within one intelligible record, so institutions can understand how a requirement is lived in practice.
Digital systems can help record the source of feedback, consent status, responsible person, decision and review date. They can also identify recurring issues over time. They cannot decide whether a view is representative or resolve value conflicts by themselves. A tool is most useful when it keeps a handoff from existing only in one colleague's memory.
At the next service review, an organisation can choose one reported satisfaction indicator and trace it backwards through one cycle. Where is the source feedback behind the percentage? How did the team interpret it? What decision changed as a result? What response did service users receive?
When a questionnaire leaves a trace leading to decisions and responses, satisfaction does more than complete a report. It begins to shape the next revision of services and policy.