E-Government · Municipalities of Pinamalayan, Roxas and Bulalacao, Oriental Mindoro

Legislative Information Management System

A digital platform for ordinances, resolutions, agendas, sessions and legislative-document management, deployed across three local government units.

Deployed at three LGUsMeasured Result
Public access to enacted legislationMeasured Result
Complete voting recordMeasured Result
Illustration: three council members at the session dais beneath a screen showing a document, with three municipal halls connected to it.
The project

What changed, and what came of it

Sanggunian secretariats run on documents: notices, agendas, minutes, ordinances, resolutions and the voting record behind each one. We built a system that holds all of it in one place, tracks each measure through its readings and committee stages, and gives the public a way to find enacted legislation without going through the secretariat. It is in use at three LGUs.

Before

Legislative records were kept manually, in files and spreadsheets held by individual staff. Finding the current version of an ordinance meant asking the person who happened to have it. Tracking what stage a measure had reached, or reconstructing how a member voted, took time the secretariat did not have — and constituents had no self-service route to the record at all.

What we built

We delivered a legislative tracking and transparency platform. Every measure is registered once and moves through defined stages, carrying its documents with it. The secretariat manages agendas and sessions in the system, voting is recorded against each measure, and enacted documents are published to a public-facing view.

Measured Result
Deployed at three LGUs

The same platform is in use at three separate local government units, each with its own legislative process configured.

Measured Result
Public access to enacted legislation

Constituents can retrieve enacted ordinances and resolutions directly, without going through the secretariat.

Measured Result
Complete voting record

Votes are recorded against each measure and are reportable, replacing reconstruction from minutes.

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

  • Measure trackingOrdinances and resolutions registered once and tracked through readings, committee referral and enactment.
  • Document managementStorage, versioning and retrieval of the documents attached to each measure.
  • Agenda and session managementAgendas built from pending measures; minutes and attendance recorded against each session.
  • Voting recordsVotes recorded per member per measure, and reportable afterwards.
  • Public document accessA public view of enacted ordinances and resolutions, searchable without secretariat assistance.
  • Workflow and routingReferral to committees and routing between offices, with status visible to the secretariat.
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
Secretariat workspacePublic document searchSession view
Application
Measure trackingDocument managementAgenda & sessionVoting recordsAccess control
Data
Legislative registerDocument 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 separating secretariat staff, committee members and the public view.
Tamper-evident audit trail: who changed a measure or its documents, and when.
Document versioning so a superseded text can never be silently replaced.
Retention aligned to the LGU's records-retention obligations.
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. First LGUDelivered to one municipality first, working through its actual secretariat process before generalising anything.
  2. Records migrationExisting ordinances and resolutions loaded so the system was useful from day one rather than starting empty.
  3. Public viewPublic document access opened once the register was complete enough to be authoritative.
  4. Additional LGUsDeployed to two further municipalities, each with its own numbering and committee structure.
Questions

Frequently asked questions

It already does — the system is deployed across the municipalities of Pinamalayan, Roxas and Bulalacao in Oriental Mindoro. Each unit keeps its own records and its own workflow; what is shared is the platform, which is why the second and third deployments cost far less than the first.

They are brought into the document register as part of deployment, which is normally the point at which gaps and conflicting versions surface. The register then becomes the authoritative copy, so finding the current text of a measure stops depending on which staff member happens to hold it.

Public document access is part of the platform. What is actually published remains the council's decision — the system separates the internal working record from the public view so that drafts and deliberative material are not exposed by default.

Measures are tracked through their stages, with agenda, session and voting records attached, so the current status of a measure and the path it took are both recoverable. That is the capability manual filing loses first as volume grows.

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.