Disaster Sitrep Chain (Barangay to Province)

One reporting thread from barangay to municipal to provincial DRRM during typhoons: incidents, evacuation counts, and needs flow upward as structured data with offline queueing for when networks fail — because consolidating sitreps by radio and text message costs hours that response operations don't have.

Typically bought by: PDRRMO, MDRRMOs, Punong Barangays / BDRRMC chairs, Governor and Mayors

Standard features — always included

• ✓Structured report submission at each level: incidents, evacuations, casualties, needs, lifeline status
• ✓Automatic upward consolidation with per-level review and annotation
• ✓Offline queueing: reports compose without signal and transmit when connectivity returns
• ✓SMS-fallback intake for barangays with text-only connectivity (structured keywords)
• ✓Live consolidated dashboard per municipality and province-wide
• ✓Needs board with request-fulfillment status tracking
• ✓Report timestamping and versioning for the official record
• ✓OCD/NDRRMC-format sitrep generation at municipal and provincial levels
• ✓Alert broadcast downward with acknowledgment tracking per barangay
• ✓Post-event archive with full reporting timeline per disaster
• ✓GovLink-native: barangay evacuation systems and municipal operations centers feed this chain automatically as they join

Popular custom additions

Quoted per feature in the configurator — typically ₱3,000–₱18,000 each.

• +Map overlays of incidents and evacuation centers across the chain
• +Media/photo attachments with bandwidth-aware compression
• +Mutual-aid asset request board across municipalities
• +Rainfall and river gauge feed integration where sensors exist

Tech stack

Frontend

Next.js (React)

Backend

Next.js API / Node.js

Database

PostgreSQL

Integrations

Offline-first sync, SMS structured intake, Barangay/municipal DRRM system feeds, Map dashboards