SECTION 4:
Grievance and feedback system
The grievance redress mechanism is where the accountability of the entire SE-GRM system becomes visible. It is the structure through which communities can raise concerns formally, track what is happening with them, and know that a response (either a resolution or an honest explanation of why resolution is not possible) will reach them. When a GRM functions well, it does more than handle complaints. It demonstrates, repeatedly and concretely, that the project team is listening and that raising concerns is worth the effort. That demonstration is what builds and sustains trust.
When a GRM does not function well, the damage goes beyond the unresolved individual concern. Across all four project contexts studied in the field research, the most consistent finding about grievance systems was not the absence of intake channels. It was the absence of the response. Concerns were submitted (formally or informally) and were never acknowledged, never tracked, and never responded to in any way the person who raised them could see. From the community’s perspective, nothing happened. That experience, raising a concern and hearing nothing back, is not experienced as bureaucratic delay. It is experienced as confirmation that the process is designed to create the appearance of accountability rather than deliver it.
A GRM without feedback closure is not a functioning system. It is a document, a record that concerns were received, with nothing downstream to show they were acted on. This is why the feedback closure step is the most important single element in GRM design, and the most consistently skipped.
What the Evidence Shows
Three GRM conditions appear across project contexts in the field research. One showing what a functioning but fragile system looks like, one showing what happens when no formal system exists, and one showing what reactive-only response produces over time.
Accessible but Undocumented
Concerns with No Institutional Home
Operational context — accessible but undocumented
In an operational onshore wind context, a relatively stable pattern of grievance handling had developed over years. Community members and barangay officials knew they could contact the developer’s representatives directly (by phone, by text message, by in-person visit) and that doing so would typically produce a response. The system worked, in the sense that issues were raised and addressed. But it worked almost entirely through informal channels, personal relationships, and the accessibility and goodwill of specific individuals. There was no formal grievance register capturing all concerns, no pattern analysis to identify recurring issues, and no documentation of what was raised, how it was responded to, and when it was closed. When the individuals who made the system work were reassigned or departed, the community’s primary point of access departed with them.
“Come to the people. Assure the people that fishing and the environment will not be harmed."
Community member, pre-development offshore wind context
Pre-development floating solar context — concerns with no institutional home
In a pre-development floating solar context, stakeholders who had concerns about the project’s implications for fishing access, water conditions, and livelihood security faced a structural problem: they were uncertain which institution was responsible for receiving and acting on those concerns. Each institution confirmed partial jurisdiction and referred to the next. At the time of fieldwork, no floating solar-specific grievance mechanism was operational. From the community’s perspective, concerns that entered this referral chain simply disappeared. The absence of a GRM was not experienced as a regulatory gap to be resolved at a future policy level. It was experienced as an absence of recourse.
Pre-development context — information asymmetry and broken expectations
Multiple community members had expectations about the project that had never been formally corrected because the underlying question had never been formally surfaced. Several interviewees understood, based on information received through informal channels, that the wind project would deliver cheaper or more stable electricity directly to the host community. When this assumption was probed, they learned that electricity generated would be fed into the national grid rather than distributed locally. The gap was not the result of deliberate misrepresentation. It was the result of information shared at a level of technical detail that communities could not independently verify, combined with an engagement format that created few genuine opportunities for direct questioning. When asked what they needed: “Come to the people. Assure the people that fishing and the environment will not be harmed.” The request was not for more information. It was for information in accessible form, verified through genuine dialogue.
Information Asymmetry and Broken Expectations
“They can be texted, they can be messaged.”
Municipal official describing the GRM, operational onshore wind context
This quote captures the strength and the fragility of the system simultaneously. Accessibility through direct messaging is genuinely valuable, it lowers the threshold for raising concerns and produces faster responses than formal intake processes. But accessibility through personal contact is not a GRM. It is a relationship. And relationships do not survive personnel changes, phase transitions, or the organizational dynamics that move key people out of their roles.
Toolkit
Who uses this Part: Developers’ ComRel and community engagement staff. CSOs and NGOs facilitating or monitoring community engagement. Community organisations, women’s groups, fisherfolk associations, and other groups who want to understand what inclusive engagement should look like and how to request it. LGU officials who facilitate or host community consultations. NCIP officers involved in FPIC processes.
WHAT TO WATCH FOR: EARLY WARNING INDICATORS
Several of these indicators can only be detected through deliberate follow-up. They will not be visible in attendance records or formal consultation documentation
Attendance at consultations is high but discussion depth is low. The same few representatives speak across all sessions while most participants are passive.
Concerns are expressed informally after meetings end, or to barangay officials and NGOs rather than to project staff or through the GRM.
Community members are unable to explain in their own words what the project will mean for their livelihood, access, or environment after formal information sessions have been conducted.
Community members receive different answers depending on who they ask.
Consent or agreement has been recorded but no one has checked whether it reflects genuine understanding and free choice, or conditional acceptance in the absence of perceived alternatives.
Women, fisherfolk, elderly residents, farm workers, or other groups with obvious stakes in the project are consistently absent from consultation records or present but non-speaking.
Technical consultation materials have not been translated into the primary local language or adapted for audiences with limited technical background.
Communities are relying on informal narratives or rumors to fill information gaps, suggesting that official information is not accessible or credible enough to meet their actual questions.
The same information has been delivered multiple times but understanding has not improved, the format is the problem, not the frequency.
No independent or community-accessible verification mechanism exists for project-related data. Communities must accept developer-provided information with no means to question or validate it.
WHAT NEEDS TO SHIFT
Each pattern below describes a condition that keeps the loop running. Read across and find what resonates in your context.
Information needs to be translated into livelihood terms, not just technically disclosed and formally recorded.
Engagement design needs to actively create conditions for safe expression, not just formally invite participation and treat the silence that follows as acceptance.
Power dynamics need to be addressed through deliberate design, not overlooked because the meeting was technically open to all.
Conditional acceptance needs to be read as what it is, a community negotiating the terms of something it cannot stop, not consent.
DEVELOPER: You design the format. A format that consistently produces passive attendance, shallow discussion, and absent voices is not neutral, it is a design choice with consequences. The shift most within your reach: redesign at least one component of your next engagement specifically to reach the group that is least visible in your current records.
LGU / BARANGAY: You host and facilitate many of these engagements. Who is speaking in the room you are in, and who consistently is not? The shift most within your reach: notice that absence, and ask the developer what format change would reach those people. Your observation carries weight.
COMMUNITY: Saying yes because you feel you have no real choice is not the same as genuine agreement, and the distinction matters, both for you and for the record. The shift most within your reach: name what kind of yes it was, to someone you trust, even informally. Conditional acceptance deserves to be on record as conditional.
CSO: You can create the separate spaces that formal settings don’t. What is being said in your presence that isn’t being said in front of developers or officials? The shift most within your reach: treat what you hear in those spaces as data, document it carefully, and find the right moment to bring it into the process.
NGA: Attendance records and signed documentation tell you that a process happened. They do not tell you whether genuine participation occurred. The shift most within your reach: ask what your monitoring would look like if it measured expression, understanding, and safe voice, not just presence.
Toolkit response — protocols, tools, and skills
The following protocols, tools, and skills address the conditions identified in Section 3 of the self-assessment. They are designed to be used together: the skills build the practitioner capabilities needed to recognize signals; the tools provide the structures for capturing and monitoring them; the protocols define when and how to act on what is found.
Protocols
P-05 Safe Space Facilitation
P-20 Information Disclosure
P-21 Rumour Response
P-22 Vulnerable Group Engagement
P-23 FPIC Protocol
Tools
T-14 Communication Kit
T-15 Information Asymmetry Audit
T-16 Rumour & Misinformation Tracker
T-17 Inclusive Engagement Design Guide
T-18 Vulnerability & Exclusion Screening
T-19 Consent Quality Assessment
Skills
SK-06 Trust Building
SK-07 Community Sensitivity
SK-08 Technical-Community Translation
SK-09 Culturally Adaptive Communication
SK-10 Visual Communication Design
SK-11 Facilitation
SK-12 Psychologically Safe Space Creation
SK-13 Dialogue Facilitation
Starting point: Before your next significant community consultation, complete T-18 (Vulnerability and Exclusion Screening) to identify which groups face the highest participation barriers. Use T-17 (Inclusive Engagement Design Guide) to redesign the format, facilitator, venue, and timing of at least one component of the engagement to specifically reach those groups. After the consultation, use T-07 (Silence and Passive Consent Checklist, from Part 3) and T-19 (Consent Quality Assessment) to review what the participation actually produced — not just who attended.
If communities are relying on informal narratives to fill gaps in their understanding, activate T-14 (Communication Kit) to produce accessible materials, and use T-15 (Information Asymmetry Audit) to identify specifically which information is not reaching people in usable form. Address the gap before the next engagement event, not after.
For communities where power dynamics are actively inhibiting expression, trigger P-05 (Safe Space Facilitation Protocol) and conduct separate sessions with the most affected groups. These sessions are not a luxury. They are the only reliable way to hear what communities are actually experiencing.
Th shared to the public for free courtesy of the
THE CONFLICT RESOLUTION GROUP FOUNDATION
www.coregroup.org.ph * info@coregroup.org.ph
in partnership with SustainABILITIES Lab
© Pixelhaze 2024. A Hostinger Website Builder Template by Pixelhaze Studio
This toolkit is provided for general guidance and informational purposes only. It is not intended as legal, technical, or professional advice. While efforts have been made to ensure accuracy and relevance, users are encouraged to exercise their own judgment and consult appropriate experts when necessary. The developers of this toolkit assume no liability for any decisions or actions taken based on its use.


