TOOL T-10 | Planning & Tracking | Module 3: Coordination & Alignment

Activity-Communication Alignment Tracker

WHEN TO USE At the start of every project phase involving visible site activities.

How to Use It

1. List all planned site activities for the current phase: surveys, geotechnical work, clearing, construction, equipment delivery, road use.

2. For each activity, identify: (a) affected barangays and stakeholder groups, (b) required notification lead time (minimum 7 days; 14 days for high-impact activities), and (c) notification method.

3. Record the planned activity date and required notification completion date.

4. As notification is completed, record: notification date, channel used, barangay captain confirmation, and any concerns raised.

5. Do not approve activity commencement if notification has not been confirmed as received.

6. If significant concerns are raised during the notification window, pause and trigger the Signal Escalation Protocol before proceeding.

Purpose

To link every planned site activity (clearing, surveys, construction, equipment delivery) to required prior community notification steps, and to track whether notification was completed before activity began. This tool prevents communities from observing unexplained work before they have been informed.

Field Rationale

Clearing activities began before all affected households had been notified. Equipment arrived by barge before community notification had been issued. In both cases, the visual impact of activity without prior communication triggered rapid shifts from cautious engagement to active resistance.

Fillable Template: Activity-Communication Alignment Log

Guidance Notes

! Field NoteNotification is not the same as receipt. A notification sent is not a notification received. This tracker requires confirmed receipt, a barangay captain who can confirm that the community was told. Without confirmed receipt, the notification has not been completed.

Adaptation Guidance

Build the notification schedule around barangay assembly cycles, not project timelines. If the nearest assembly is three weeks away and the activity is planned for two weeks, either move the activity or use an alternative notification method.

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.