Public Safety · Municipality of Pinamalayan, Oriental Mindoro

Citizen Incident Reporting & Response System

A mobile app and web system for citizens to report public-safety and infrastructure issues, and for the municipality to route, track and resolve them.

Photo evidence on reportsMeasured Result
Geographic view of incidentsMeasured Result
Routing to the responsible departmentMeasured Result
Illustration: a resident reporting an issue on a phone, a street map with pins, and an operator tracking tickets on a screen.
The project

What changed, and what came of it

Residents see problems before the municipality does — a broken streetlight, a flooded road, an unsafe structure. We built the channel for them to report it with a photo and a location, and the back-office system that gets the report to the department that can act on it and keeps the resident informed.

Before

Reports arrived by phone call, social media message and word of mouth. There was no single queue, no way to tell whether an issue had already been reported, and no record of what had been done about it. Residents had no visibility after reporting, so the same issue was reported repeatedly.

What we built

We developed an incident management system with a mobile app and a website. Citizens report in real time with photo evidence and a description; reports land in one queue plotted on a map; municipal staff triage, prioritize and assign to the responsible department; and the status is tracked through to resolution.

Measured Result
Photo evidence on reports

Responding departments assess from the report before dispatching.

Measured Result
Geographic view of incidents

Reports plotted on a map, making repeat locations visible.

Measured Result
Routing to the responsible department

Each report has a named owner rather than sitting in a shared inbox.

Each outcome carries the label that describes what kind of claim it is. We never present a target as a measured result — see the Ledger and our claims policy.

The system

What the system does

  • Citizen reportingReport from mobile or web with a description and location.
  • Photo evidencePhotographs attached to the report so the responding department can assess before dispatch.
  • Map viewReports plotted geographically, making clusters and repeat locations visible.
  • Department routingAssignment to the responsible department, with ownership recorded.
  • PrioritisationTriage so that safety issues are not queued behind routine ones.
  • Status trackingProgress tracked from report to resolution, visible to staff and reporter.
Architecture

How it fits together

A layer-level view. We do not publish hostnames, addresses, credentials, firewall rules or topology detail for systems in production.

Presentation
Citizen mobile appCitizen web formMunicipal triage consoleMap view
Application
Report intakeTriage & prioritizationDepartment routingStatus trackingAccess control
Data
Incident recordsPhoto evidence storeAudit log
Infrastructure
Application serverDatabase serverBackup and recovery
Security and rollout

How it is protected, and how it went live

Controls in the delivered system

Delivered under ITDC’s information security practices, which follow ISO/IEC 27001 and NIST guidance.
Role-based access: citizens see their own reports, departments see their queue, administrators see all.
Photo evidence stored server-side with access controlled by role rather than by link.
Audit trail on assignment, status change and resolution.
Encrypted transport for report submission including photo upload.
Scheduled backups with a documented restore procedure.

High-level controls only. Detailed security design is shared under NDA with the client organization, not published.

How it was rolled out

  1. Intake and triageReporting channel and municipal queue delivered first, so reports were captured in one place.
  2. Routing to departmentsAssignment and ownership introduced once report volume was understood.
  3. Mobile app releaseCitizen app published to widen the reporting channel.
  4. SupportPost-implementation support and tuning of categories and priorities.
Questions

Frequently asked questions

By having a single queue and a map view, so a report arriving about an issue already logged is visible as such. Before that, reports came by phone call, social media and word of mouth, and there was no way to tell whether something had already been raised.

Department routing plus a status record. Every report lands in one queue, is routed to an owning department, and carries a state — so 'what was done about it' has an answer months later. That record is also what makes workload across departments measurable for the first time.

Status tracking is part of the system, and visibility is what sustains reporting: residents who never learn the outcome stop submitting, and the municipality loses the data. Photo evidence attached at submission also reduces the follow-up needed to understand what was reported.

No. This is a routing and record system that runs on ordinary municipal staffing. A command center is a separate class of project — see the Command Center and City Network case study — and the two are frequently confused during scoping.

Let's talk

Planning a similar project?

Tell us the organization, the process and the constraint you are working against. We can help shape the architecture, the implementation approach and the next step.