SECTION 5: Learning, response, and institutionalization

What the Evidence Shows

Three conditions from the field research illustrate what happens when learning and institutionalization are absent, even in systems that appeared to be working.

The System That Worked Until the People Left

Issues Resolved,
Patterns Unlearned

Operational onshore wind context — the system that worked until the people left

The most effective SE-GRM system in the study operated in an onshore wind project that had been running for several years. Concerns were raised and resolved quickly. Direct communication channels were in regular use. Barangay officials knew how to reach the developer's representatives. Mitigation was visible and timely. By any standard engagement measurement (accessibility, responsiveness, community relationships) this was the best-performing system in the study. But it had a structural condition that made it fragile: it worked almost entirely through the personal relationships, informal practices, and contextual knowledge of specific individuals. There was no formal grievance register documenting what had been raised and resolved. There were no written protocols describing how concerns should be received and handled. The knowledge of who to call, what the community's specific sensitivities were, what informal understandings had been reached over years, all of it existed in people's heads and in the relationships those people maintained. When those individuals left or were reassigned, the community lost its primary point of access. The system didn't fail dramatically. It simply became inaccessible.

Early-implementation solar context — issues resolved, patterns unlearned

In an early-implementation solar context, the project's grievance handling was genuinely responsive at the case level. Crop damage was compensated. Safety issues were addressed. Barangay-level negotiations resolved localized disputes. The response time was fast and the outcomes were generally satisfactory to the individuals involved. But the cases were managed individually, without any systematic review of whether the same types of issues were appearing across different areas or different phases. Crop damage concerns recurred in different barangays. The same coordination failures between contractors and affected landowners appeared more than once. Each instance was resolved. The conditions producing them were not changed. The system could fix problems. It could not learn from them. The result was a project that was spending ongoing resources resolving recurring issues that a pattern analysis could have identified and addressed structurally, weeks or months earlier, at lower cost.

Multiple project contexts — the construction-to-operations transition

Across multiple project contexts, the construction-to-operations transition emerged as the most consistently fragile moment in the SE-GRM lifecycle. During construction, projects typically have large, active community relations teams; formal engagement activities are frequent; contractor presence means direct daily contact with community members; and monitoring and response functions are well-resourced. When operations begin, the picture changes dramatically. Construction teams are replaced by lean operations staff with different mandates and different relationships. Formal engagement activities are wound down. The ComRel officers who spent years building community trust are reassigned. Communities that had weekly contact with familiar faces find themselves with a new contact, if any, whose name they don't know and who has no knowledge of what was discussed, what was agreed informally, or what concerns were still open. In multiple contexts, communities described this transition using the same language: they experienced it as abandonment. Not as a reduced engagement intensity appropriate to the operational phase. As the project getting what it needed and then leaving.

The Construction-to-Operations Transition

“It got fixed quickly, but it happened before it was fixed.”

Community member, early-implementation solar context

This observation captures the core limitation of reactive-only grievance management: resolution after the fact is not the same as prevention. A system that can only respond cannot protect. The GRM must learn from patterns, not just resolve cases.

Toolkit

Who uses this Part: Developers’ project management, ComRel officers, and legal teams activating conflict response. Senior management responsible for SE-GRM governance and continuity. LGU officials facilitating or participating in dialogue or mediation processes. CSOs and neutral facilitators involved in structured conflict response. ComRel officers and incoming staff managing transitions. Community representatives and organisations who want to understand what escalation pathways should look like and how to access them.

DIAGNOSTIC: SELF-ASSESSMENT SECTION 1

Work through these questions with your team and, if possible, with LGU focal persons and community representatives.

Score each on a 1–4 scale using the rubric in Annex A: 1 = Not yet in place, 2 = Emerging, 3 = Established, 4 = Adaptive.

If you score mostly 1s and 2s in this section, begin with the protocols and tools listed below before moving to other parts of the toolkit.

WHAT TO WATCH FOR: EARLY WARNING INDICATORS

These are observable conditions that suggest the SE-GRM system is functionally fragile — working under current conditions but at risk of breaking down when personnel, project stage, or context changes. Several describe systems that appear fine from the inside but are failing in ways that will only become visible when it is too late to prevent the loss.

• The SE-GRM system depends on one or two specific individuals: if they left next month, it is not clear who would maintain the community relationships or know where informal understandings are documented.

• Engagement and grievance processes are not written down anywhere, they exist in practitioners’ heads and are shared through informal training rather than documented protocols.

• The same types of concerns are appearing repeatedly (crop damage, contractor behaviour, notification failures) in different areas or phases, without any structural response to the underlying conditions.

• A staff transition has occurred or is pending, and no structured knowledge transfer process has been initiated, the incoming person will be starting from a blank slate.

• The project is approaching or has just completed a phase transition (construction to operations, or operations to decommissioning), and the SE-GRM system has not been reviewed or adapted.

• Community members describe a change in the project’s engagement intensity or accessibility since a personnel change or phase transition, the relationship has degraded without anyone actively managing the transition.

• Conflict between the project and community, or between community groups, is active or escalating, and no structured conflict assessment or response process has been initiated.

• The project’s ComRel team is resolving cases but not asking why the same case types keep appearing, the GRM is functioning as a case-resolution tool but not as a learning mechanism.

• No periodic SE-GRM review has been conducted, the system has been running without formal performance assessment.

WHAT NEEDS TO SHIFT

Each pattern below describes a condition that keeps the loop running. Read across and find what resonates in your context.

• Informal practices need to be documented, not left to survive through personal memory and relationships.

• Phase transitions need to be treated as knowledge transfer events, not logistics.

• Pattern learning needs to become a standing practice, not a response to recurring crises.

• Conflict response needs to be prepared before it is needed, not improvised when it arrives.

DEVELOPER: You control what gets documented and what stays in people’s heads. The shift most within your reach: capture the informal practices, understandings, and community relationships that make your SE-GRM work while the people who hold that knowledge are still present. Documentation is not bureaucracy. It is institutional memory with a future.

LGU / BARANGAY: You often hold community-level history and context that the project team doesn’t have: what was promised, what actually happened, what the community remembers. The shift most within your reach: make sure that knowledge is shared across project transitions, and ask to be formally introduced to incoming staff rather than discovering the change by accident.

COMMUNITY: You have the clearest view of whether the system is actually still working after transitions. The shift most within your reach: name it when you notice the quality of engagement has changed since a personnel shift or phase transition, and ask directly who is responsible now.

CSO: You often observe system fragility from the outside before the project team sees it: the informal practices that work, the relationships that are carrying the system, the gaps that appear after transitions. The shift most within your reach: document what you observe, and support communities in knowing their rights and access points when project personnel change.

NGA: Monitoring conducted at one point in time may not capture fragility that only becomes visible after a transition. The shift most within your reach: review whether SE-GRM systems have been explicitly adapted at phase transitions, not just whether they were functioning at the moment of assessment.

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

Conflict response: when escalation requires structured intervention

P-14 Conflict Assessment

P-15 Facilitated Dialogue

P-16 Mediation Intake

P-17 Mediation Process

P-24 Do No Harm Review

P-25 Negotiation Protocol

P-26 Legal Referral

Learning and institutionalization: for ongoing, proactive use

P-18 Staff Transition Continuity

P-19 Phase Transition Handover

P-27 Periodic SE-GRM Review

Tools

Conflict response: when escalation requires structured intervention

T-24 Conflict Mapping Tool

T-25 Escalation Tracker

T-26 Root Cause Analysis Worksheet

T-27 Do No Harm Assessment

T-28 Facilitated Dialogue Guide

T-29 Negotiation Preparation Guide

T-30 Agreement Documentation Template

T-31 Mediator Briefing Kit

T-32 Caucus Planning Guide

T-33 Post-Agreement Monitoring Sheet

Learning and institutionalization: for ongoing, proactive use

T-34 SE-GRM Health Scorecard

T-35 Lesson Capture Template

T-36 Phase Transition Review Checklist

T-37 SOP Builder

Skills

Conflict response: when escalation requires structured intervention

SK-17 Root Cause Analysis

SK-18 Conflict Analysis

SK-19 Conflict Sensitivity

SK-20 Interest-Based Negotiation

SK-21 Principled Persuasion

SK-22 Mediation

SK-23 Impartiality & Neutrality

SK-24 Trauma-Informed Engagement

SK-25 Emotional Regulation

Learning and institutionalization: for ongoing, proactive use

SK-26 Reflective Practice

SK-27 Adaptive Management

SK-28 Knowledge Management

Starting point: If a conflict is active or escalating, begin with T-24 (Conflict Mapping Tool) and T-26 (Root Cause Analysis Worksheet) before choosing a response. Understanding what is actually driving the situation, not just its surface expression, determines which response is appropriate. A facilitated dialogue (P-15) requires willing parties and a neutral facilitator. Mediation (P-16, P-17) requires that direct dialogue has been attempted and reached impasse. Before any significant intervention, complete T-27 (Do No Harm Assessment), well-intentioned responses in high-tension contexts can worsen dynamics if they are not designed with care.

If the concern is institutionalization: start with T-37 (SOP Builder), identify the practices that make your SE-GRM work and document them now, while the people who hold that knowledge are still present. Do not wait for a departure to discover what has not been captured. If a staff transition is approaching or has just occurred, activate P-18 (Staff Transition Continuity Protocol) immediately, the joint community introduction between outgoing and incoming staff is the single most critical step and cannot be substituted with a letter or an email.

If a phase transition is approaching,  particularly construction to operations, initiate T-36 (Phase Transition Review Checklist) at least six weeks before the transition date. The operations-phase SE-GRM is not a lighter version of the construction-phase system. It is a different system designed for different risks, and it requires deliberate design rather than assumption of continuity.

For ongoing learning: T-34 (SE-GRM Health Scorecard) should be completed quarterly throughout the project lifecycle. The most valuable input to each quarterly review is not the internal performance data, it is the answer from five or six community members to the question: “Do you know how to raise a concern, and did you hear back the last time you did?” Internal and community assessments frequently diverge. That divergence is itself the most important finding.