MUNICIPAL OPERATIONS CENTER (MOC) PROTOCOL

[Name of Municipality/City]

Version: [Insert Version Number, e.g., 1.0] Date: [Insert Date of Last Revision, e.g., July 14, 2025]

I. INTRODUCTION AND LEGAL BASIS

This Municipal Operations Center (MOC) Protocol outlines the procedures and guidelines for the
establishment, activation, operation, and deactivation of the MOC for [Name of
Municipality/City]. It aims to serve as the central hub for the coordination and monitoring of
both routine municipal operations and scaled-up emergency response and management,
ensuring efficient service delivery and effective disaster preparedness and response.

A. Legal Framework: This protocol is anchored on and guided by:

1. Republic Act No. 7160 (Local Government Code of 1991): Grants LGUs the power to
manage their own affairs and deliver basic services.

2. Republic Act No. 10121 (The Philippine Disaster Risk Reduction and Management Act
of 2010): Mandates LGUs to establish and operate DRRM Councils and Offices, and
highlights the need for effective command and control during emergencies.

3. National Disaster Risk Reduction and Management Plan (NDRRMP): Provides the
country's roadmap for DRRM across its four thematic areas.

4. National Incident Management System (NIMS) Philippines: Promotes a standardized

approach to incident management, which the MOC operations will largely adhere to,
particularly the Incident Command System (ICS) principles during emergencies.

5. Relevant Department of Interior and Local Government (DILG) Circulars: On local

governance, public service delivery, and disaster preparedness (e.g., OPLAN Listo, Seal of
Good Local Governance criteria).

6. Approved Local Comprehensive Development Plan (CDP) and Local Disaster Risk
Reduction and Management Plan (LDRRMP) of [Name of Municipality/City]: The
overarching development and DRRM plans for the LGU.

7. Approved Local Contingency Plans for specific hazards and functional plans for specific
services.

B. Purpose: To provide a clear, standardized, and adaptable framework for the effective
management and coordination of municipal operations by:
 1. Serving as the primary command, control, and coordination facility for both routine
municipal service delivery and emergency management.

2. Ensuring continuous monitoring and real-time situational awareness across all critical
municipal functions.

3. Facilitating integrated planning, resource allocation, and decision-making for both daily
operations and crisis response.

4. Defining clear roles, responsibilities, and reporting lines for MOC personnel.

5. Promoting seamless coordination among various LGU departments, national agencies,

NGOs, private sector, and community organizations.

6. Enhancing the LGU's capacity for proactive governance, efficient service delivery, and
rapid, effective disaster response.

C. Scope: This protocol applies to all personnel involved in the operations of the Municipal/City
Operations Center, including the Local Chief Executive (LCE), Department Heads, the
Municipal/City Disaster Risk Reduction and Management Officer (M/CDRRMO), MOC
Management, Section Chiefs, Support Staff, and representatives from local line agencies, Civil
Society Organizations (CSOs), and private sector partners during scaled-up operations. It covers
the continuum of operations, from routine monitoring to full emergency response and recovery,
within the territorial jurisdiction of [Name of Municipality/City].

II. MOC ORGANIZATIONAL STRUCTURE AND ROLES

The MOC shall be designed with a scalable organizational structure, capable of adapting from
routine monitoring to a full-blown emergency operations center (EOC) based on the Incident
Command System (ICS) principles.

A. MOC Management/Command Staff:

1. MOC Director/Manager:

o Routine Operations: Typically, the Municipal/City Administrator or a designated

senior LGU official (e.g., the M/CDRRMO) serves as the MOC Manager,
overseeing daily functions and coordination.

o Emergency Operations: The Local Chief Executive (LCE) (Mayor) assumes overall
command and serves as the EOC Director, with the M/CDRRMO acting as the
technical EOC Manager.
 o Responsibilities (General): Provides overall strategic direction, approves plans,
authorizes resource deployment, liaises with higher authorities, and makes
critical policy decisions.

2. Public Information Officer (PIO):

o Designated Personnel: LGU Information Officer.

o Responsibilities: Manages all official communication to the public, media, and

external stakeholders, ensuring consistent and accurate messaging for both
routine advisories and emergency warnings.

3. Safety Officer:

o Designated Personnel: Representative from LGU Safety Office, BFP, or designated

MOC Staff.

o Responsibilities: Monitors MOC operations for safety hazards, ensures the safety
of personnel during operations, and advises on safety protocols for field
activities.

4. Liaison Officer:

o Designated Personnel: Representative from LDRRMO or other LGU department.

o Responsibilities: Serves as the primary contact for external agencies, NGOs,

private sector, and other LGUs for both routine inter-agency coordination and
emergency assistance.

B. MOC General Staff (Sections): These sections represent the core functional areas within the
MOC, designed to be scalable. During routine operations, they might be represented by a single
point person from a department; during emergencies, they expand into full units.

1. Operations Section:

o Section Chief: (e.g., General Services Office Head, Public Safety Office Head, or
highly qualified LDRRMO staff)

o Responsibilities: Manages the execution of municipal programs, projects, and

services. During emergencies, it directs tactical response activities, implements
the Incident Action Plan (IAP), and coordinates direct service delivery and
resource deployment.

o Units/Functions (Scalable):
  Service Delivery Unit (Routine): Monitors and coordinates daily
municipal services (e.g., garbage collection, road maintenance, public
market operations, licensing).

 Emergency Response Unit (Emergency - aligned with Response

Clusters):

 Search, Rescue & Retrieval (SRR) Coordination Unit: Coordinates

with BFP, PNP, AFP, and local SRR teams.

 Evacuation & Camp Management Unit: Oversees evacuation,

establishment, and management of evacuation centers (aligned
with CCCM).

 Relief Distribution Unit: Manages relief goods (F/NFIs) inventory,

packing, and distribution.

 Health & Medical Coordination Unit: Coordinates medical teams,

public health surveillance, and psychosocial support.

 Infrastructure & Utilities Unit: Monitors and coordinates repair of

damaged infrastructure, power, and water supply.

 Peace and Order Unit: Coordinates with PNP for security and
order maintenance.

2. Planning Section:

o Section Chief: (e.g., Municipal/City Planning and Development Coordinator)

o Responsibilities: Gathers, processes, and disseminates information for both

routine performance monitoring and emergency situational awareness. Develops
strategic plans, monitors progress, and prepares operational plans.

o Units/Functions:

 Situational Awareness & Monitoring Unit: Collects and analyzes data on

service delivery performance, community issues, crime incidents, hazard
monitoring, and impact assessments. Maintains a real-time common
operating picture (COP).

 Performance Analysis & Reporting Unit (Routine): Generates reports on

municipal service performance, project status, and policy
implementation.
  Incident Action Planning Unit (Emergency): Develops the Incident Action
Plan (IAP) for each operational period during emergencies.

 Documentation & Archiving Unit: Maintains comprehensive logs of all

MOC activities, decisions, and communications; manages municipal
records and emergency documentation.

 Research & Development Unit: Conducts research for policy

development, service improvement, and long-term planning.

3. Logistics Section:

o Section Chief: (e.g., Municipal/City General Services Officer)

o Responsibilities: Provides all necessary support needs for MOC operations,

municipal service delivery, and on-scene emergency activities, including
personnel, facilities, transportation, supplies, and communications.

o Units/Functions:

 Supply & Resource Unit: Manages inventory of municipal assets,

equipment, office supplies, and emergency relief goods. Manages
procurement processes.

 Facilities Management Unit: Ensures functionality and maintenance of

MOC facility, municipal buildings, public spaces, and emergency shelters.

 Transportation & Fleet Management Unit: Manages the municipal

vehicle fleet, fuel, and transportation logistics.

 Communications & IT Support Unit: Establishes and maintains

communication links (internet, telephone, radio, inter-departmental
systems) within the MOC and with field units. Provides IT support for all
MOC systems.

4. Finance/Administration Section:

o Section Chief: (e.g., Municipal/City Treasurer or Accountant)

o Responsibilities: Manages all financial aspects of municipal operations and

incident costs. Ensures compliance with budgeting, accounting, and procurement
procedures. Handles human resource administration for MOC staff.

o Units/Functions:
  Budget & Accounting Unit: Manages municipal budget, tracks
expenditures, and prepares financial reports (including LDRRMF
utilization).

 Procurement Unit: Manages all procurement processes, ensuring

compliance with RA 9184 and emergency procurement guidelines.

 Payroll & Benefits Unit: Handles salary and benefits for MOC personnel;
manages claims.

 Administrative Support Unit: Provides general administrative support to

the MOC.

C. Support Staff:

 MOC Clerks/Encoders: Assist in data entry, documentation, and administrative tasks.

 Messengers/Runners: Facilitate internal document and information flow.

 IT Technical Staff: Ensures functionality of MOC IT systems and network.

 Security Personnel: For MOC facility security.

III. PHASES OF MOC OPERATION AND PROTOCOLS

The MOC operates on a continuum, seamlessly shifting between routine monitoring and scaled-
up emergency response.

A. Routine Operations / Preparedness Phase (Normal Operating Condition)

1. Policy and Planning:

o MOC Operational Plan: Develop and regularly review the detailed MOC
Operational Plan and Standard Operating Procedures (SOPs) for each
section/unit.

o Integration with LGU Plans: Ensure the MOC protocol is integrated into the LGU's
Comprehensive Development Plan (CDP), Local Disaster Risk Reduction and
Management Plan (LDRRMP), and sectoral plans.

o Data Collection Framework: Establish systematic data collection protocols for all
municipal departments to feed into the MOC for performance monitoring (e.g.,
daily service reports, citizen feedback, project progress).

o Contingency Planning: Develop and regularly update specific Contingency Plans

for various hazards (e.g., flood, earthquake, typhoon, health emergencies) and
 functional plans for services (e.g., power outage response, water supply
disruption).

2. Staffing and Training:

o Core MOC Team: Maintain a dedicated core MOC team (e.g., from LDRRMO or
Administrator's Office) responsible for daily operations and monitoring.

o Role Assignments: Clearly define roles and responsibilities for all MOC personnel,
including designated alternates.

o Capacity Building: Conduct continuous training for all MOC staff on ICS, MOC
operations, data management systems, Rapid Damage Assessment and Needs
Analysis (RDANA), Basic Life Support, Public Information management, and
relevant technical skills.

o Exercises and Drills: Conduct regular drills, simulations, and tabletop exercises
involving all MOC sections and key LGU departments to test protocols and
improve coordination.

3. Facilities and Equipment Maintenance:

o Primary MOC Location: [Specify address], equipped with redundant power

supply (generator, UPS), robust internet connectivity, diverse communication
systems (landline, cellular, dedicated radio frequencies, satellite phones), large
display screens, interactive maps, secure servers, and ergonomic workstations.

o Alternate MOC Location: [Specify address], fully equipped and ready for
immediate activation if the primary MOC is compromised.

o System Checks: Conduct daily/weekly functional tests of all MOC equipment

(communication systems, computers, power backups, GIS software).

o Inventory Management: Maintain an updated inventory of all MOC supplies,

equipment, and assets, including backup systems.

4. Information Systems and Technology:

o Unified Data Platform: Develop or acquire a centralized information

management system (e.g., a dashboard, GIS platform) to integrate data from
various LGU departments (e.g., health, social welfare, engineering, public safety,
business permits).
 o Real-time Monitoring: Implement systems for real-time monitoring of key
performance indicators (KPIs) for municipal services and hazard parameters (e.g.,
weather data, water levels, traffic).

o Cybersecurity: Implement robust cybersecurity measures to protect MOC data

and systems.

5. Partnerships and Coordination:

o Inter-Departmental MOAs: Formalize internal MOAs between LGU departments

outlining their roles and responsibilities in providing data and support to the
MOC.

o External MOAs: Establish and regularly review Memoranda of Agreement

(MOAs) with national government agencies (e.g., PNP, BFP, DOH, DSWD, DEPED,
DPWH, AFP), NGOs (e.g., Red Cross, local charities), private sector entities (e.g.,
utility companies, transport groups), and neighboring LGUs for mutual aid,
resource sharing, and coordinated action.

o Community Engagement: Establish protocols for engaging with Barangay Officials

and community leaders for bottom-up information flow and service feedback.

B. Escalation / Alert Phase (Based on Situational Analysis and Threat Levels)

1. Triggering Mechanisms:

o Routine Incident Escalation: For minor service disruptions or incidents (e.g.,

localized power outage, small traffic accident) that require multi-departmental
coordination but not full emergency activation.

o Pre-emptive Hazard Alert: Upon receipt of advisories of potential threats (e.g.,

PAGASA Tropical Cyclone Wind Signal (TCWS) No. 1 or 2, PHIVOLCS Advisory for
abnormal seismic activity, DOH health alert).

2. Notification and Shift:

o Level 1 (Enhanced Monitoring): Triggered by minor incidents or low-level hazard

advisories.

 Protocol: MOC core team enhances monitoring, verifies reports, and

facilitates inter-departmental coordination. Key section chiefs are notified
and on standby for potential escalation.

o Level 2 (Partial Activation/Standby): Triggered by escalating incidents requiring

significant multi-departmental response or a more serious hazard advisory (e.g.,
 TCWS No. 2 or 3, significant flooding advisory, initial reports of large-scale
incident).

 Protocol: MOC Manager (or M/CDRRMO) recommends partial activation

to the LCE. Designated MOC Command and Section Chiefs report to the
MOC. Initial staffing for key functions (e.g., Situational Awareness,
Communications, Response Coordination) is established. Resources are
placed on standby. Initial operational objectives are set.

o Level 3 (Full Activation/Emergency Operations): Triggered when a significant

disaster or emergency is occurring or highly anticipated with widespread impact
(e.g., TCWS No. 4 or 5, major earthquake, widespread flooding with mandatory
evacuations, large-scale fire, health epidemic). This is when the MOC fully
transforms into an EOC.

 Protocol: LCE formally declares full MOC/EOC activation. All primary and
alternate MOC/EOC personnel report for duty. All sections are fully
operationalized. Continuous 24/7 operations are established (with shift
schedules). All MOC/EOC functions are fully implemented.

3. Initial Actions Upon Activation (for all levels):

o MOC personnel check in and report to designated workstations.

o Initial briefing for all activated staff by the MOC Director/Manager, outlining the
situation, objectives, and expected operational period.

o Activate all communication lines and information systems.

o Initiate activity logs for all sections/units.

C. Operations Phase (Routine to Emergency)

1. Information Management and Situational Awareness:

o Continuous Data Collection: Systematically collect data from field units,

barangays, LGU departments, national agencies (PAGASA, PHIVOLCS, DENR-MGB,
DOH), and public reports.

o Data Validation: Implement strict protocols for verifying the accuracy of all
incoming information.

o Analysis and Visualization: Process raw data into actionable intelligence.

Maintain a dynamic Common Operating Picture (COP) using large format maps,
digital dashboards, and situation boards. During emergencies, this includes:
  Hazard footprint and affected areas.

 Deployed resources and personnel.

 Location of evacuation centers, number of evacuees (disaggregated data).

 Damaged infrastructure and critical lifelines.

 Key decision points and incident objectives.

o Reporting: Generate regular Situational Reports (SitReps) (daily for routine,

every 6/12/24 hours during emergencies) for the LCE, LGU departments, and
higher EOC levels (Provincial/Regional/National), adhering to DSWD's DROMIC
Reporting Guidelines for disaster-related data.

2. Planning and Decision Making:

o Strategic Planning: The Planning Section leads the development or update of

plans (service delivery plans, IAP for emergencies) based on current situation and
objectives.

o Operational Period Briefing: Start each operational period with a briefing for all
MOC staff and key partners, reviewing accomplishments, current situation, and
objectives for the new period.

o Incident Action Plan (IAP) Development (Emergency): The Planning Section

develops a concise IAP for each operational period (e.g., 12-hour or 24-hour
cycle), outlining SMART objectives, strategies, tactics, resource assignments, and
safety considerations.

o Execution: Operations Section implements the plans/IAP.

o Evaluation: Continuously monitor progress against objectives and adjust plans as

needed.

3. Resource Management:

o Resource Requests: Standardized request forms for personnel, equipment, and

supplies are submitted to the Logistics Section.

o Sourcing and Allocation: Logistics Section identifies and allocates resources from
LGU inventory, pre-contracted suppliers, partner agencies, or through inter-LGU
mutual aid agreements. Prioritize allocation based on operational needs and
critical impact.
 o Tracking: Maintain a real-time inventory and tracking system for all municipal
assets and deployed resources (who, what, where, when, status).

o Emergency Procurement: Implement fast-track, but still auditable, emergency

procurement procedures following RA 9184 guidelines during disasters.

4. Communication and Coordination:

o Internal MOC Communication: Use designated secure communication channels

(internal radio network, secured messaging apps, VoIP) for MOC staff and inter-
departmental coordination.

o External Communication:

 With Barangays: Establish reliable communication with Barangay Officials

for ground truth reporting, service requests, and information
dissemination.

 With On-Scene Incident Command Posts (ICPs): Regular scheduled

communications and on-demand updates for emergency operations.

 With National Agencies/Other LGUs: Maintain continuous

communication with relevant national agencies and neighboring LGUs for
coordinated efforts.

 With External Partners (NGOs, Private Sector): Coordinate through the

Liaison Officer for resource augmentation and specialized assistance for
both routine projects and emergency response.

o Public Information: PIO continuously provides transparent, accurate, and timely

information to the public through official social media accounts, LGU website,
local radio, and community warning systems. Actively counter misinformation
and rumors.

5. Documentation and Record Keeping:

o Comprehensive Logs: Maintain detailed chronological activity logs for each MOC
section/unit.

o Document Management: File all incoming and outgoing messages, reports,

forms, decisions, and official correspondences.

o Financial Records: Document all resource requests, deployments, expenditures,

and procurement activities.
 o This rigorous documentation is vital for accountability, performance review,
financial reconciliation (especially for LDRRMF utilization), and post-incident
analysis.

D. De-escalation / Demobilization Phase

1. Criteria for De-escalation/Demobilization:

o For routine operations: When a project or service delivery objective is met.

o For emergencies: When the immediate emergency phase has concluded, incident
objectives are met or significantly progressed, the threat to life and property has
subsided, and remaining tasks can be managed by regular LGU departments or a
reduced MOC staff.

o A clear transition plan to post-incident recovery or new routine operational cycle

is in place.

2. Demobilization Planning:

o The Planning Section, in coordination with Operations and Logistics, develops a

detailed demobilization plan.

o Identifies personnel and resources no longer required.

o Establishes procedures for the orderly return of resources to their respective

owners/agencies or for reassignment.

3. Resource Return and Accountability:

o Ensure all deployed resources are properly accounted for, returned, serviced,
repaired, or replaced as necessary.

o Finalize all financial documentation related to the specific operation or incident.

4. Personnel De-briefing:

o Conduct post-operational debriefings for MOC staff and field personnel.

o Provide opportunities for stress debriefing or psychosocial support if needed,

especially after prolonged or traumatic emergency operations.

5. MOC Stand-down/Return to Routine:

o Formal announcement by the LCE or MOC Director of the de-escalation/stand-

down from emergency mode to routine operations.
 o Transition remaining coordination functions to relevant LGU departments for
rehabilitation, recovery, or new operational cycles.

E. Post-Operation / Evaluation Phase

1. After-Action Review (AAR):

o Conduct a comprehensive AAR for significant routine projects or all emergency

operations involving all MOC personnel and key partners.

o Identify strengths, weaknesses, lessons learned, and areas for improvement in

MOC operations and municipal service delivery.

o Develop an After-Action Report (AAR) and Improvement Plan (IP) with concrete
recommendations, timelines, and assigned responsibilities.

2. System and Plan Updates:

o Integrate lessons learned from the AAR into the MOC Protocol, LGU's CDP,
LDRRMP, Contingency Plans, and departmental SOPs.

o Update information systems and training modules based on findings.

3. Public Communication:

o Communicate outcomes, achievements, and lessons learned (where appropriate)

to the public.

IV. COMMUNICATION AND DATA MANAGEMENT STANDARDS

A. Communication Systems:

 Primary: Dedicated landlines, cellular phones (official and personal), email, secure
internet-based messaging platforms (e.g., local government internal network, specific
DRRM platforms).

 Secondary/Backup: Two-way radios (VHF/UHF) for inter-departmental and field

coordination, satellite phones for critical remote areas, HF radios (if available for long-
range), runners for localized communication failures.

 Public Warning Systems: Integration with LGU-wide warning systems (sirens, public
address systems, local radio stations, LGU social media channels, SMS blast services).

B. Information Flow and Reporting:

 Vertical Flow:

o Barangay officials/units to MOC

 o MOC to Provincial Operations Center/DRRM Council

o Provincial to Regional to National (NDRRMC)

 Horizontal Flow:

o MOC Sections/Units to each other.

o MOC to field units and on-scene incident command posts.

o MOC to supporting agencies, NGOs, private sector partners.

 Standardized Forms: Strict use of DILG, DSWD (e.g., DROMIC), and NDRRMC-prescribed
forms for all reporting, including:

o Situation Reports (SitReps)

o Rapid Damage Assessment and Needs Analysis (RDANA) forms

o Resource Request Forms (RRF)

o Evacuation Center Reports

o Incident Action Plans (IAP)

o Activity Logs

 Data Management System: Implement a robust and accessible information

management system for data entry, storage, retrieval, and analysis. This can range from
well-organized cloud-based spreadsheets to more advanced GIS-based platforms (like
the NDRRMC's HANDA or locally developed systems). Emphasis on real-time data input
and visualization.

V. RESOURCE MANAGEMENT GUIDELINES

 Comprehensive Inventory: Maintain an updated, categorized, and digitized inventory of

all municipal DRRM assets and resources (personnel skills, equipment, vehicles, relief
goods, pre-identified evacuation centers, available funds).

 Resource Mapping: Utilize GIS to map the location and status of critical resources and
infrastructure.

 Pre-positioned Resources: Identify and pre-position critical emergency resources in

strategic locations, especially in vulnerable or geographically isolated barangays.

 Resource Agreements: Secure formal MOAs/MOUs with private entities, NGOs, and
neighboring LGUs for mutual aid and resource augmentation during large-scale incidents
or for specialized services.
  Local DRRM Fund (LDRRMF) Utilization: Adhere strictly to the guidelines set by the
Department of Budget and Management (DBM) and DILG for the utilization of the
LDRRMF (including the 30% Quick Response Fund - QRF), ensuring proper procurement
procedures (RA 9184) and full accountability. All expenditures must be documented and
auditable.

VI. SAFETY, SECURITY, AND WELFARE PROTOCOLS

 MOC Facility Safety: Ensure the physical safety and security of the MOC facility (fire
safety, structural integrity, access control, alternative power).

 Personnel Safety and Welfare:

o Provide clear safety briefings and guidelines for all MOC staff and field
responders.

o Ensure availability and proper use of Personal Protective Equipment (PPE) for
field personnel.

o Implement protocols for adequate rest, nutrition, and hydration for MOC staff
during extended operations.

o Establish a system for providing stress debriefing and psychosocial support

services for personnel involved in traumatic or prolonged operations.

 Data Security: Implement robust cybersecurity protocols to protect sensitive municipal

and incident-related data from unauthorized access or cyber threats.

VII. APPENDICES

 Appendix A: MOC Organizational Chart with Contact Information

 Appendix B: MOC Personnel Roster with Primary and Alternate Roles and
Responsibilities

 Appendix C: Communication Directory (Internal, Inter-departmental, External

Stakeholders)

 Appendix D: List of Standardized Forms and Templates (Routine and Emergency)

 Appendix E: Comprehensive Resource Inventory (Personnel, Equipment, Supplies,

Facilities, Services)

 Appendix F: Map of Municipal/City MOC, Alternate MOC, Critical Facilities, and Hazard
Overlay Maps.
  Appendix G: Relevant National and Local Issuances (e.g., specific DILG, DSWD, NDRRMC
Circulars).

General References and Sources (Philippine-specific where applicable):

1. Republic Act No. 10121 (The Philippine Disaster Risk Reduction and Management Act
of 2010): The foundational law for DRRM in the Philippines.

o LawPhil: https://lawphil.net/statutes/repacts/ra2010/ra_10121_2010.html

o Official Gazette: https://www.officialgazette.gov.ph/2010/05/27/republic-act-no-

10121/

2. National Disaster Risk Reduction and Management Council (NDRRMC) Website: The
official source for national DRRM policies, plans, and issuances, including those on ICS
and EOCs. Look for "Issuances" and "Publications."

o https://ndrrmc.gov.ph/

o Specifically relevant for EOC Typing/Capability: NDRRMC Memorandum No. 137,

s. 2022 (Typing of Emergency Operations Centers (EOCs) Recommended
Minimum Capability and Resource Requirements):
https://ndrrmc.gov.ph/attachments/article/4180/NDRRMC_Memorandum_No_1
37_s_2022.pdf

3. Department of Interior and Local Government (DILG) Website: Provides various local
governance guides and manuals, including those related to disaster preparedness for
LGUs (e.g., OPLAN Listo, Seal of Good Local Governance criteria).

o https://www.dilg.gov.ph/

o Search for "OPLAN Listo" for LGU preparedness guides.

4. Department of Social Welfare and Development (DSWD) Disaster Response Operations

Monitoring and Information Center (DROMIC) Guidelines: Crucial for standardized
reporting on affected populations and relief efforts. While specific links may change,
searching "DSWD DROMIC Reporting Guidelines" should lead to the latest version.

5. Department of Budget and Management (DBM) and DILG Joint Memorandum Circulars
on LDRRMF Utilization: These detail how LGUs should manage and utilize their disaster
funds.

o Search for "DBM-DILG-NDRRMC Joint Memorandum Circular LDRRMF" on DBM

or DILG websites.
6. Philippine Institute of Volcanology and Seismology (PHIVOLCS) and Philippine
Atmospheric, Geophysical and Astronomical Services Administration (PAGASA): These
agencies provide the scientific hazard information that triggers MOC/EOC activation.

o https://www.phivolcs.dost.gov.ph/

o https://www.pagasa.dost.gov.ph/