WHAT YOU MIGHT BE NOTICING

• You have concerns about the project but haven’t raised them formally. It didn’t feel safe, or you weren’t sure they would be taken seriously

• In formal meetings, people stay quiet... but in smaller conversations, concerns come out

• Your community received short-term support or benefits, and since then it’s felt harder to raise concerns without seeming ungrateful

• A new project is happening in your area, and your community has had bad experiences with a previous one like promises that weren’t kept or concerns that went unaddressed

• You’ve shared concerns with your local officials or a local NGO, but you don’t know if those concerns have reached the developer or any agency

Section 1: Early Signal Detection

If your concerns never seem to reach anyone or if you’ve stopped trying

WHAT YOU CAN DO

Raise a concern before it becomes a formal complaint

A question, an observation, something that feels unclear: these are all valid starting points. You do not need to have everything figured out before you speak.

Choose the channel that feels safest

Your barangay captain, a community organisation, a CSO working in your area, or the project GRM if one exists. Informal is fine. The important thing is that it reaches someone who can pass it on.

Say something even if you think others already know

What circulates in community conversation is not the same as what enters the system. A concern that is widely discussed but never formally raised is still invisible to the people who need to act on it.

Speak up during benefit periods too

If your community is receiving short-term support (employment, fuel subsidies, cash assistance), you still have every reason to raise concerns about long-term impacts. The two are separate. Accepting support does not mean accepting silence.

Name your community’s history

If a previous project left unfulfilled promises or unresolved concerns, say so when a new project enters. You are not being obstructive. You are giving the new team the context they need to engage honestly.

Ask what happens to what you share

If you raise something with a barangay official or a CSO, ask: will this reach the developer? Will it be recorded? What will happen next? Following up is not redundant; it is how you make sure your concern moved.

Bring someone with you

You do not have to engage alone. A community organiser, a CSO, a trusted neighbour or anyone who can help you articulate what you’re holding, or document that you raised it.

A concern that stays unspoken is not a concern that doesn’t exist. It is a concern the system has not yet reached. The most important step is finding a way to name it, however small and informal, to someone who can help it move.

WHAT YOU MIGHT BE NOTICING

• Equipment, clearing, or construction started, and no one told your community beforehand

• You get different answers depending on who you ask

• People in your community who depend on the land or water (but do not own it) have not been included in any discussion

• It feels like decisions are already made, and consultations are just going through the motions

• You don’t know which government office to bring your concern to

Section 2: Alignment across actors: permits, activities, and communication

If something doesn’t feel right about what’s happening in your area

WHAT YOU CAN DO

Document what you see

If clearing starts, equipment arrives, or surveys begin without prior notification, write down the date, location, and what was happening. You do not need to know exactly what it means; you just need to record that it happened.

Ask for the official approved activity list

Through your barangay, request a copy of what activities have been formally authorized for your area and where. What is happening on the ground should match what has been approved.

Bring inconsistent answers together

If different people (the developer, barangay captain, contractor) are telling you different things, write down who said what and when. Bring those accounts to your barangay captain and ask for one clear written answer from the developer.

Name the people who are missing

If tenants, farm workers, or fisherfolk in your community are affected but not part of any project discussion, bring their names and situations to your barangay. These people have a stake even without formal title, and they deserve to be in the record.

Ask what transition arrangements exist

For people whose livelihoods will be directly affected (tenants, farm workers, fisherfolk), ask before clearing or construction begins whether any transition support has been arranged. If none exists, that is worth raising formally before activity proceeds.

Ask which agency handles your specific concern

Concerns about environmental impact, fishing access, land rights, and indigenous territory each have a different responsible agency. Your barangay can help identify the right one, or a CSO can guide you through the process.

Ask to be told before things happen, not after

If activity has already started without notification, you can formally request, through the barangay or the GRM, that future activities be communicated to the community in advance. Put that request in writing if you can.

Use the GRM if one exists, and bring someone with you

Not only for formal complaints, but for questions, observations, and requests for information. A GRM entry creates a record that something was raised and requires a response. You do not have to go alone; a community organizer or CSO can help you document what was said.

You don’t need to be an expert to use this guide. What you see and experience in your community is already valuable information. The most important step is naming it, to someone who can act on it.

WHAT YOU MIGHT BE NOTICING

• You attended a consultation, but left still unclear about what the project actually means for your livelihood, access to resources, or daily life.

• The meeting felt more like a presentation than a conversation, information was given, but there was little real space to ask questions or challenge what was said.

• You had concerns, but did not feel comfortable raising them in the room, because of who was present, how the meeting was structured, or uncertainty about how your concern would be received.

• You said yes, or stayed silent, not because you fully agreed, but because it felt like the project would proceed anyway.

• Some people in your community (such as women, fisherfolk, farmers, elderly residents, or tenants) were present but did not speak, or were not included at all.

• Information was shared, but it was too technical, too fast, or not in your language, making it difficult to fully understand or question.

• You are hearing different versions of the project from different sources (neighbors, social media, barangay officials), and are unsure which is accurate.

• The same information has been presented multiple times, but your understanding has not improved.

• You are not sure what happens to the concerns that are raised, whether they are recorded, acted on, or followed up.

• You feel that being present in the meeting is not the same as having influence on the outcome.

Section 3: Inclusion, understanding, and safe expression

If your concerns never seem to reach anyone or if you’ve stopped trying

WHAT YOU CAN DO

Ask for information in plain language, or in your own dialect

Not a technical presentation. Not a brochure. A real explanation of what the project will mean specifically for your fishing grounds, farmland, water access, or livelihood. This is a reasonable request, not a complaint.

Ask to have a genuine opportunity to ask questions

If a session feels more like a presentation than a conversation, you can say so, and ask when the conversation part happens. A good process welcomes questions; it does not just deliver information.

Ask to participate in a format that works for you

If large formal meetings with officials and developer representatives make it hard to speak freely, ask for a smaller group session, a community-only discussion, or a written channel. This is not a special request, it is how good engagement is supposed to work.

Ask that your concerns be heard without consequence

If you feel that speaking up puts something at risk (your access to benefits, your relationship with officials, your standing in the community), say so to your barangay captain, a CSO, or whoever you trust. That feeling is itself important information about how the process is working.

Name what kind of yes you gave

If your agreement was conditional, reluctant, or made because you felt you had no real choice, put that on record, through the GRM, the barangay, or a CSO. A conditional yes is not the same as a free yes, and it should not be recorded as one.

Ask what happens to the concerns you raised, and ask to be told if anything changes

A concern with no follow-up is a concern the system has not processed. And if the project scope, timeline, or footprint changes after you have been consulted, your earlier participation does not cover it. You can ask both: was this recorded, and will I be told when things shift?

Ask to see what was recorded after a consultation

You can ask the developer or barangay for the minutes or summary of what was documented from any consultation you attended. If what was recorded does not match your experience, you can ask for it to be corrected.

Bring someone with you

You do not have to engage alone. A community organiser, a CSO representative, or a trusted community member can help you articulate what you want to say, document what was said in the meeting, and ensure your concern is on record.

Being in the room is not the same as being heard. A signature is not the same as genuine agreement. If the engagement did not reach you in a way that made real participation possible, that is worth saying, to someone who can act on it.

WHAT YOU MIGHT BE NOTICING

• You raised a concern, formally or informally, and never heard back.

• You are not sure whether your concern was received, recorded, or acted on.

• You were told your concern was “resolved,” but no one explained to you what was actually done.

• You have been referred from one office or agency to another, with no clear answer on who is responsible.

• You are hearing that others have raised similar concerns, but the same issues keep happening.

• You raised something through a barangay official, contractor, or CSO, but do not know if it entered any formal system.

• You do not know whether a grievance mechanism exists, or how to access it in practice.

• The only way to get a response is through personal connections or direct contact with specific individuals.

• You feel that raising a concern is uncertain, it may or may not lead to anything.

• From your perspective, raising a concern feels like it goes nowhere.

Section 4: Grievance and feedback system: from intake to visible response

If your concerns never seem to reach anyone or if you’ve stopped trying

WHAT YOU CAN DO

Ask whether a GRM exists and how to use it

Every project with a community engagement obligation should have a grievance mechanism. Ask the developer, barangay, or CSO directly: is there one, what is the channel, and what happens after you submit something?

Submit your concern in writing if you can

A written concern — however short — creates a record. A text message, a note to your barangay captain, a form, an email — any of these counts. The important thing is that it is dated and attributable to you.

Ask for an acknowledgement

Once you submit a concern, ask: has this been received? Who is handling it? When will I hear back? These are reasonable questions — not demands — and a functioning system should be able to answer them.

Follow up if you haven’t heard back

If a reasonable time has passed and you have received no response, follow up through the same channel you used, or through your barangay. A concern sitting in a register without response is not being managed — following up is how you make sure it moves.

Ask what was done with your concern

You are entitled to know how your concern was addressed — what decision was made, what action was taken, or why it could not be resolved. “Resolved” in a register means nothing if you were never told what actually happened.

Name it if you’re being passed between agencies

If you’ve raised a concern and been referred from one institution to another without resolution, document the referral chain — who sent you where, and when. Bring that record to a CSO or barangay official and ask them to help identify who actually owns your concern.

Raise it as a pattern if it keeps happening

If your concern is recurring — affecting multiple households or happening repeatedly over time — raise it as a pattern, not just an individual case. A recurring problem requires a structural response, not just a one-off fix. Ask the developer what trend analysis they are doing on the GRM register.

Bring someone with you

You do not have to navigate the GRM alone. A community organiser, CSO representative, or trusted community member can help you document your concern, follow up on your behalf, and ensure the feedback loop closes with you — not just with the register.

A GRM that receives concerns but never responds is not a functioning system — it is a way of making concerns disappear with paperwork. If you raised something and heard nothing, that is not the end. Follow up, bring someone, and put it on record that you followed up.

WHAT YOU MIGHT BE NOTICING

• The people who used to be your main contact on the project have changed — the new contact doesn’t know what was agreed or discussed before, and earlier commitments no longer seem to be remembered.

• The project has moved into operations and the regular meetings, community activities, and face-to-face contact have stopped or reduced dramatically.

• A concern you raised was addressed at the time, but the same kind of problem keeps coming up — for you or for others in your community — and no one seems to be looking at why it keeps happening.

• There is an unresolved conflict between the project and your community, or between groups in your community, that is getting worse rather than better and has no clear path forward.

• Informal understandings or agreements from earlier project stages don’t seem to be known or honoured by the current team.

• You want to escalate a concern beyond the frontline level but don’t know where it should go, or it feels like it has nowhere to go.

• You feel like the project got what it needed and then the relationship changed — you are no longer being engaged the way you were before.

Section 5: Learning, response, and institutionalization

If the project has changed and the people have changed, and something important seems to have been lost

WHAT YOU CAN DO

Ask for a written record

If something was agreed or committed to informally, ask for it in writing. Informal agreements that are not documented can disappear with the people who made them. You are entitled to a record.

Request a formal introduction to new personnel

If your contact has changed, ask to be formally introduced through someone you already know and trust — not just given a new name and number. This is not a formality. It is how relationships and prior context transfer across transitions.

Name the pattern

If the same type of concern keeps coming up — for you or for others — say so explicitly when you raise it. A recurring concern is not the same as an individual complaint. Naming it as a pattern is what creates pressure for structural change rather than case-by-case management.

Use escalation pathways when frontline resolution fails

If a concern has gone unresolved through normal channels, ask what the escalation process is. The GRM should have a documented pathway for concerns that cannot be resolved at the first level. Ask for it.

Document your own engagement history

Keep a simple record of dates, what was raised, who was present, and what was said in response. Your record may be the only one that exists — and it matters when contacts change or disputes arise.

Know your right to a response

A concern that was raised and never properly closed is not resolved. You have every right to follow up, ask for the status, and name it as unresolved if it is. Silence from the project side is not closure.

Know your right to a response

A concern that was raised and never properly closed is not resolved. You have every right to follow up, ask for the status, and name it as unresolved if it is. Silence from the project side is not closure.

Ask for the system review

If the project has been operating for a year or more without any formal SE-GRM review, ask when the last one happened and what it found. Regular review is a standard commitment of a functioning system

A system that worked because of the right people, and only because of those people, was not yet a system. What endures is what has been built into structures, not just into relationships. When the people change — as they always do — the question is whether what mattered was documented, transferred, and held. Your right to ask that question does not expire when the project moves to operations.