SECTION 3: Inclusion, understanding, and safe expression
A consultation can be formally conducted without producing genuine participation. Attendance can be high while expression is shallow. Consent can be recorded while communities hold reservations they did not feel safe to raise. Information can be disclosed, in the form of technical presentations, regulatory materials, and compliance documentation, while communities leave the room with no clearer understanding of what the project means for their fishing grounds, their farmland, their access to water, or the livelihood their children will inherit.
The gap between the appearance of engagement and its substance is produced by a set of structural conditions that are predictable, recognisable, and addressable, but only if they are actively looked for. Power differentials between community members and authority figures in the room. Technical language that creates knowledge gaps rather than closing them. The perception, widespread across communities in low-trust contexts, that raising a concern will produce no response and may produce negative consequences. The absence of safe channels for groups (women, farm workers, fisherfolk, elderly residents) who are routinely present in communities but routinely absent from formal consultation records.
Inclusion, understanding, and safe expression are not soft dimensions of SE-GRM. They are the conditions under which genuine information flows between projects and communities. Without them, engagement produces compliance documentation but not the two-way exchange of information that enables early detection, shared understanding, and genuine consent.
What the Evidence Shows
Three patterns from the field research illustrate how this system condition needs enhancement in practice. All references are anonymised.
Self-silencing and the Limits of Formal Consultation
Scale Uncertainty and
Moderated Expression
Pre-development context — self-silencing and the limits of formal consultation
Community members attended consultations with a developer and regulatory representatives in a coastal barangay with fishing livelihoods. Attendance was recorded as good. No formal objections were raised. But in separate small-group interviews conducted outside the formal setting, without developer or official representatives present, a different account emerged. Community members described having concerns about vibration impacts on fish presence, about the extent of the project’s footprint relative to existing fishing grounds, and about what the project would actually deliver for the community. They had not raised these in the formal consultations. When asked why: they were uncertain whether their concerns were specific enough to raise formally; they had low confidence that raising them would change anything; and the presence of officials and developer staff made the setting feel more appropriate for listening than for questioning. The concerns were present. The format did not reach 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 context — scale uncertainty and moderated expression
Fishing communities had seen the pilot with their own eyes: modest, contained, more or less what they had been promised. The full-scale project was something else, “mas malawak na sakop” (wider coverage). Their concerns were specific: fishing routes, water movement, the slow logic of seasonal lake conditions. In formal engagement settings, they said less, or said it smaller. The question that moved quietly through the community, “May magagawa pa ba kami?” (Do you think there’s really anything we can do?), was not a statement of defiance. It was not knowing whether showing up and actually having influence were the same thing. The engagement record described concerns as present but manageable. What it did not capture was how much people had already stopped saying.
“We don’t want it, but if it happens, we hope we’re given an alternative.”
Fisher, pre-development RE project
This statement, conditional acceptance rather than genuine agreement, appeared in several contexts. It is not consent. It is the expression of a community that has concluded it cannot prevent a project and is negotiating the terms of accommodation. Recording this as community acceptance is a significant and consequential misreading
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
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.


