Trust in the Leader of Collaborative Process Design and Facilitation
Your gap is Learning, response, and institutionalization
A low score in Section 5 does not mean your system is failing now. It means it is one departure, one phase transition, or one escalating conflict away from failing, and the conditions that would prevent that are not yet in place. This is the section where projects that appear to be functioning well are most often surprised. Everything looks fine. The ComRel officer is responsive, the community is engaged, the register shows reasonable activity. And then the ComRel officer leaves, or construction ends and operations begins, and within six months the community is describing the project as having abandoned them. These are the conditions that signal this gap is active in your project:
Your SE-GRM system works because of who is running it, not because of how it is designed. If your best ComRel officer left tomorrow, you could not describe a system that would continue to function, because the system is that person.
You have been resolving grievances consistently but have never reviewed the register as a whole. You do not know whether the same issues keep appearing because no one has looked. A pattern analysis has never been run.
You are approaching a phase transition (from construction to operations, or from pre-development to construction) and no one has initiated the SE-GRM review that should precede it. The engagement intensity, the staffing, the risk profile, and the community's expectations will all change. The system has not been updated to account for any of it.
A key staff member has recently left or is about to leave. No structured handover of open cases, active commitments, community relationships, or informal agreements has taken place. The incoming person does not know what they do not know.
Community trust indicators have been declining (attendance is lower, the tone of interactions has shifted, fewer concerns are being filed formally) but no one has formally investigated what is driving the change. The decline is being observed but not acted on.
You have had a significant conflict, a coordination failure, or a GRM breakdown in the past year. No lesson capture was conducted. The conditions that produced it have not been reviewed. The same conditions exist in the current phase.
Your SE-GRM design document from project inception has not been reviewed since it was written. It describes a system for a project that is now two phases older and in a completely different risk environment.
Community members who interacted with the previous ComRel officer are asking why things feel different now. They cannot get a clear answer about who is responsible, what was agreed, or whether the commitments made in previous discussions still stand.
Toolkit response — protocols, tools, and skills
The following protocols, tools, and skills address the conditions identified in Section 5 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
Learning and institutionalization: for ongoing, proactive use
P-18 Staff Transition Continuity
Tools
Conflict response: when escalation requires structured intervention
T-26 Root Cause Analysis Worksheet
T-28 Facilitated Dialogue Guide
T-29 Negotiation Preparation Guide
T-30 Agreement Documentation Template
T-33 Post-Agreement Monitoring Sheet
Learning and institutionalization: for ongoing, proactive use
Skills
Conflict response: when escalation requires structured intervention
SK-20 Interest-Based Negotiation
SK-23 Impartiality & Neutrality
SK-24 Trauma-Informed Engagement
Learning and institutionalization: for ongoing, proactive use
Your immediate actions for Section 5
1 Run T-34 SE-GRM Health Scorecard this week, before you do anything else. Score your system on signal capture, GRM uptake, feedback closure, pattern analysis, system resilience, and community trust. For any indicator rated Partially Functional or Not Functional, assign a named person and a specific improvement action before the end of the review session. A scorecard that is completed and filed without generating action is not a learning tool. It is a compliance exercise.
2 Run T-23 Grievance Trend Analysis on your full register. Review every entry for the past six months for patterns: the same concern category from different people, the same barangay generating repeated entries, the same type of issue appearing across different phases. Three or more entries in the same category in a 30-day period is a trend that case-by-case resolution will not fix. Identify the systemic condition producing it and assign a structural response.
3 If a phase transition is approaching or has recently passed, initiate T-36 Phase Transition Review Checklist immediately. Check: are open cases formally documented and handed over? Are active commitments recorded and assigned to the incoming team? Has the community been introduced to the new contact, in person, not by letter? If the transition has already happened without these steps, it is not too late to conduct a late handover. It is significantly better than leaving the gap in place.
4 If a key staff member has recently left or is about to leave, activate P-18 Staff Transition Continuity Protocol and T-37 SOP Builder now. The practices, relationships, and informal knowledge that make your SE-GRM work must be documented before the person who holds them walks out the door. Do not wait for the departure to begin the documentation. Departure documentation misses everything that lives in tacit knowledge and relationship, which is most of what matters.
If active conflict is present or escalating, begin with P-14 Conflict Assessment Protocol and T-24 Conflict Mapping Tool before any response action. Understanding the conflict before intervening in it is not optional. A response that misreads the situation will make it worse.
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 context, mature project, long-established community relationship
In an operational 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. When concerns were raised about water discoloration following construction runoff, mitigation measures were implemented. When community members raised issues about project activities, the municipal government served as a structured intermediary, relaying concerns and coordinating responses. 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 that captured all concerns. There was no pattern analysis to identify recurring issues. There was 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 left, the community's primary point of access departed with them.
Early-implementation context, active construction phase, responsive project team
In an early-implementation 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.
Issues Resolved, Patterns Unlearned is what happens when a GRM is designed as a case-resolution tool rather than a learning mechanism. The register fills with closed cases. The same categories keep appearing. Resources keep being spent on the same recurring issues. And the conditions producing them (a contractor briefing gap, a notification failure, an unaddressed livelihood concern) remain unchanged because no one has ever looked at the register as a whole and asked why the same thing keeps happening. A GRM that cannot learn from itself is a GRM that will keep generating the same work indefinitely. Resolution after the fact is not the same as prevention.
Multiple project contexts — the construction-to-operations transition
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 appropriate to the operational phase but as the project getting what it needed and then leaving.
The Construction-to-Operations Transition is not a logistics problem. It is a trust problem, and it is entirely predictable. Every project knows this transition is coming. Very few plan for it with the same rigor they apply to construction schedules. The communities that experienced it as abandonment were not wrong in their interpretation. From their position, the relationship had ended. The question for any project approaching this moment is not whether the transition will happen. It is whether the system has been designed to survive it, and whether the community will experience continuity or disappearance on the other side.
The Construction-to-Operations Transition
“It got fixed quickly, but it didn't need to happen.”
Community member, early-implementation 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.
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.
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.
This website shared to the public for free courtesy of the
THE CONFLICT RESOLUTION GROUP FOUNDATION, INC.
www.coregroup.org.ph * info@coregroup.org.ph
through our SustainABILITIES Lab Project
© 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.