Barangay Management System Project in PHP with Source Code

Barangay Management System Project In PHP With Source Code

Looking for a complete Barangay Management System in PHP and MySQL with source code for your BSIT, BSCS, or BSIS capstone? You are in the right place. This 2026 refreshed version is built on PHP 8.x with MySQL 8 as the backend, ships with the document templates every Philippine barangay actually issues every day, Barangay Clearance, Cedula (Community Tax Certificate), Indigency Certificate, Business Clearance, Certificate of Residency, First-Time Job Seeker Certificate (RA 11261), and aligns with the DILG Digital Barangay framework and the national eGov.ph initiative that LGUs across the country are now adopting.

The Barangay Management System is one of the most consistently requested capstone topics in Philippine IT colleges, and for good reason. The 1991 Local Government Code (RA 7160) makes the barangay the smallest unit of government, and the busiest. A Punong Barangay, Secretary, Treasurer, seven Kagawads, and an SK Chairperson serve thousands of residents who need clearances and certificates daily, often still tracked in paper ledgers. Build a working barangay system and you ship something that maps directly to a real social-impact problem your panel can verify by walking into any barangay hall.

The source code below is a complete working system, not a demo skeleton. You get resident records, household grouping, full document issuance, blotter / incident tracking, barangay officials and SK officials rosters, senior citizen / PWD / 4Ps / solo parent registries, treasury ledger, and dashboard KPIs out of the box. Around 3,000 lines of clean PHP, no framework lock-in, readable enough that any third-year BSIT student can defend it line by line.

Last updated: June 2026, by PIES Information Technology Solutions, Binalbagan, Negros Occidental. Tested on XAMPP 8.2 (Windows), Laragon, and MAMP (macOS). Aligned with DILG document standards and RA 10173 (Data Privacy Act) requirements.

Barangay Management System Features/Modules Account

• Dashboard – A dashboard is a form of graphical user interface that displays an overview of your application’s reports, metrics, and other key facts. The dashboard element of the barangay information system is shown below. It displays the entire number of households in the system, as well as the number of people, total clearances issued by the barangay, total permits issued, and total blotter complaints processed by the barangay.
• Barangay Officials Module – The barangay official module allows users to add, amend, and search for information on barangay officials, such as the position, name of the officer, contact number, address, start term, and end term. The barangay clearance form will include a list of officials.
• Staff Account Module – The staff module, as seen below, allows the administrator to create a new account with limited permissions. In order to create a new account for employees, you’ll need their full name, username, and password.
• Zone Leader Module – In order to create/add another record, the zone leader module requires the zone number, login, and password to be filled in. The login credentials will be used to get access to the zone leader dashboard, where zone leader users will be able to view, review, approve, and disapprove the clearance and permission application.

• Household Module – A household is made up of all the people who live in the same housing unit on a regular basis. The average household size is calculated by dividing the number of people in each household by the number of households (or householders).
• Residents Information Module – This is the module that collects and saves resident information. This form may differ from one barrio to the next (based on our experience). The list of entities in this module can be found in the database tables (tblresident). This form includes a username and password that will be used to connect into their account in order for residents to apply for clearance and permits. It simply implies that a resident can apply for such documents either online through the application or in person at the barangay hall.
• Permit Clearance Module – The image below depicts the module where the administrator can add clearance permit applications. The following information must be encoded: the resident’s name, business name, address, kind of business OR number, and payment amount. The zone leader will analyze the application and decide whether or not to approve the request.
• Blotter Module – The phrase “police blotter” refers to a slang term used in police practice and procedures. On a daily basis, it refers to a book that records arrests and other facts and happenings in a police station. Arrests are recorded in real time in a police blotter.
• Clearance Module – The image below depicts the module where the administrator can add barangay clearance applications. The following data must be encoded: clearance number, resident name, findings, purpose, OR number, and payment amount. The zone leader will analyze the application and decide whether or not to approve the request.
• Activity Module – The encoding procedure includes a timetable of activities in the barrio. This module will serve as a reminder and archive for the barangay’s activities. The record comprises the date of the activity, the name of the activity or program, and the ability to upload a program banner.
• Report and Statistics Module – The system can print several types of statistics records, such as the number of residents per zone. It can also group residents by age, gender, educational achievement, and other factors.
• Audit Logs – A document that records an occurrence in an information (IT) technology system is known as an audit log. Audit log entries often include destination and source addresses, timestamps, and user login information, in addition to detailing what resources were accessed.

Expanded Features for 2026 (Project Features)

In addition to the core modules above, the 2026 build adds the PH-specific features panels and DILG accreditation actually look for in a barangay capstone:

• Resident records (CRUD with photo upload): full demographic profile, household ID, purok / sitio, civil status, occupation, religion, voter status, contact number, emergency contact.
• Household / family grouping: every resident linked to a household head; family relationships rendered as a tree for clearance verification.
• Barangay Clearance: auto-fills resident details, official letterhead, purpose, Punong Barangay e-signature block, control number, QR verification.
• Cedula (Community Tax Certificate): basic + additional tax computation, occupation tax bracket, sequential CTC number, receipt printing.
• Indigency Certificate: for hospital bill subsidy, scholarship application, PAO legal aid; tied to 4Ps / solo-parent / senior-citizen registry.
• Business Clearance / Permit: for new business registration, renewal, change of address; required before LGU Mayor’s Permit.
• Certificate of Residency: for school enrollment, employment, passport application, NBI clearance.
• First-Time Job Seeker Certificate (RA 11261): fee-exempt cert for fresh graduates’ first job application; counter and validity tracking.
• Blotter / Incident reports: case number, parties involved, narrative, status (mediated / endorsed / closed), follow-up reminders.
• Complaints / Mediation cases: Lupong Tagapamayapa workflow per RA 7160 Chapter 7 (Katarungang Pambarangay).
• Barangay officials roster: Punong Barangay, 7 Kagawads, SK Chairperson, Secretary, Treasurer, with start / end of term, position, photo, contact.
• SK officials roster: separate Sangguniang Kabataan slate (SK Chairperson + 7 SK Kagawads + SK Secretary + SK Treasurer).
• Census / population statistics: by purok, age bracket, gender, civil status, voter status, dashboard charts ready for Punong Barangay report.
• Senior citizens registry (RA 7432 / RA 9994): for OSCA ID, monthly stipend, medicine discount tracking.
• PWD registry (RA 10754): disability type, PWD ID number, benefits availed.
• 4Ps beneficiaries tracker: Pantawid Pamilyang Pilipino Program family ID, conditional cash transfer status, compliance tracking.
• Solo parent registry (RA 8972): solo parent ID, benefits, child dependency list.
• Treasury / financial ledger: collections (clearance fees, cedula fees, business permit fees), disbursements, daily cash blotter, monthly liquidation.
• SMS notifications via Semaphore: for document pickup, blotter hearing schedule, SK assembly call, emergency advisory (typhoon, brownout).
• QR-coded documents for verification: every printed clearance / cedula / certification has a unique QR; external party scans it to verify authenticity against the database.
• Multi-user roles: Punong Barangay (full admin), Secretary (issue documents, edit residents), Treasurer (payments / financial ledger), Staff (encode + print).
• Audit log: every CRUD action logged with user, timestamp, before/after, required for RA 10173 compliance defense question.
• Dashboard with KPIs: total population, residents added this month, documents issued this month, blotter cases open, collections this month.
• Printable PDF reports: monthly clearance count, monthly cedula count, monthly blotter summary, monthly financial liquidation, all DomPDF / TCPDF.
• Responsive Bootstrap 5 design: usable on the Punong Barangay’s phone, the Secretary’s desktop, and the printout-window kiosk in the barangay hall.

Tech Stack (2026)

• PHP 8.2+: backend, OOP-friendly, prepared statements via PDO/MySQLi to satisfy panel SQL-injection questions.
• MySQL 8 / MariaDB 10.6+: relational schema (tblresident, tblhousehold, tblclearance, tblcedula, tblblotter, tbluser, tblofficial, tblaudit).
• Bootstrap 5.3: responsive UI, modal forms, printable A4 layout for documents.
• jQuery 3.7: DataTables for paginated resident / blotter lists, AJAX form submit, modal triggers.
• DomPDF / TCPDF: server-side PDF generation for Clearance, Cedula, Indigency, Business Permit, financial reports.
• endroid/qr-code: QR generation on every printed document for verification.
• Semaphore SMS API: Philippine SMS gateway, ~PHP 0.50 per SMS, for pickup notifications and emergency advisories.
• Chart.js: dashboard KPI charts (population by purok, documents issued per month, collections trend).
• PHPMailer: email-based clearance request confirmations (optional).
• XAMPP 8.2 / Laragon / MAMP: supported local stacks for testing.

Sample Images of the Barangay Management System

To start executing this Barangay Management System Project In PHP , makes sure that you have sublime or any platform of PHP and MySQL installed in your computer.

Barangay Management System Project in PHP steps on how to run the project

Anyway, if you want to level up your programming knowledge, especially PHP, try this new article I’ve made for you Best PHP Projects With Source Code Free Download.

PH-Specific Document Templates Walkthrough

The system ships with the four most-requested barangay documents in the Philippines. Each follows the standard letterhead, control numbering, and signature block expected by LGUs and DILG inspectors.

Barangay Clearance, End-to-End Flow

Resident walks into the hall (or submits online) → Secretary searches the resident by name or household ID → system pre-fills the clearance form with name, age, civil status, purok, length of residency → Secretary selects purpose (employment, school, travel, NBI clearance, scholarship) → resident proceeds to Treasurer → Treasurer collects the clearance fee (configurable per barangay; typically PHP 30-100) and issues an OR (Official Receipt) → Secretary prints the clearance on barangay letterhead with the Punong Barangay e-signature block, sequential control number, date issued, and a unique QR at the bottom for third-party verification. Total time: under 3 minutes per resident.

Cedula (Community Tax Certificate) Generation

Cedula computation follows the LGU schedule: a basic community tax of PHP 5 plus an additional tax of PHP 1 per PHP 1,000 of gross income, gross sales, or assessed value (capped per LGU ordinance). The Treasurer enters the resident’s declared income → system computes the basic + additional + total → assigns the next sequential CTC number (yearly reset) → prints the cedula on the LGU-printable stock with date of issue, place of issue, and Treasurer’s signature block. Audit log captures who issued which CTC number, when, and to whom, directly defendable under panel questions on traceability.

Indigency Certificate

Used for hospital-bill subsidy (PCSO, MAIP), PAO legal aid, scholarship applications, and DSWD assistance. The system auto-cross-checks the resident against the 4Ps tracker, solo-parent registry, and PWD registry to pre-fill the indigency basis. Includes purpose, validity (typically 6 months), Punong Barangay signature block, control number, and QR verification.

Business Clearance / Permit

Required before LGU Mayor’s Permit issuance per RA 11032 (Ease of Doing Business Act). Form captures business name, business type (sari-sari, eatery, BPO, manufacturing), barangay address, owner, TIN, capitalization, plus annual renewal date. The system tracks renewal status and flags expired clearances. Output PDF includes barangay seal, control number, validity, and QR for the LGU Business Permits and Licensing Office to scan during Mayor’s Permit processing.

Customization for Capstone Defense

If you want your barangay capstone to stand out from every other group submitting the same baseline build, add one or more of the following modules. Each is a documented direction your panel will recognize as genuine extension work, not vibes.

• Facial recognition for resident verification: integrate a Python face-recognition microservice (dlib + face_recognition library) that the Secretary triggers when an unidentified visitor claims to be a resident. Defensible angle: prevents fraudulent clearance issuance to non-residents.
• Biometric (fingerprint) login for officials: ZKTeco K40 / K50 USB scanner via PHP libusb wrapper or a small Python sidecar. Defensible angle: replaces shared-password Captain logins; satisfies RA 10173 accountability principle.
• eSignature (DICT-recognized) for documents: integrate the DICT PNPKI sandbox or a simple PAdES PDF-signature workflow with OpenSSL. Defensible angle: makes printed documents legally equivalent to wet-signed under the E-Commerce Act (RA 8792).
• Resident PWA (mobile app for residents): minimal Progressive Web App: resident logs in, requests a clearance / cedula / indigency, pays via GCash or Maya QR, picks up at the hall. Defensible angle: aligns with eGov.ph “no-contact transaction” mandate.
• Online appointment booking: residents pick a date / time slot for in-person pickup; reduces hall congestion. Add SMS reminder via Semaphore.
• COVID / health-monitoring module: vaccination card upload, vaccine brand + dose tracking, vulnerable-resident registry. Defensible angle: built during pandemic, ready for future public-health events.
• Disaster Risk Reduction (DRRM) module: per RA 10121, every barangay has a BDRRMC. Add evacuation-center capacity, family-headcount tracker for typhoons, relief-goods distribution log.
• GCash / Maya payment integration: for clearance / cedula / business permit fees, full digital receipt, auto-post to treasury ledger.
• Multi-barangay (municipal-level) deployment: single database serves multiple barangays in a municipality, with role-scoped access. Defensible angle: ready for LGU-wide rollout, not just one barangay.

The Source Code

The download button for BMIS source code has been temporarily disabled for quite a period of time.

What’s New?

Due to public demand, the itsourcecode team make some extra efforts to upgrade the BMIS code a little bit and made it available to the public but not for free.

Where to get the Source Code

If you are interested in obtaining the source code, we would be delighted to assist you. However, as mentioned above, it is not free.

The source code provides comprehensive insights into the architecture and functionalities of the system, allowing for greater understanding.

Reach out to our FB PAGE: https://www.facebook.com/

Our team directly to express your interest. We are available to answer any questions and provide you with the necessary details.

Summary

The Project In PHP With Source Code was developed using PHP MySQL database, Using HTML, CSS, Bootstrap, JavaScript, Ajax, J Query, and Modal.

This article contains a list of modules for a web-based barangay system. PHP, MySQL, and Bootstrap were used to design and construct the project.

Defense Tips: RA 7160 + RA 10173 + eGov.ph

Panels for barangay-system capstones almost always test three areas. Walk in ready for these and you will pass.

1. RA 7160 (Local Government Code of 1991), Barangay Autonomy

Expect: “Why a barangay-level system and not LGU-level?” Answer: RA 7160 makes the barangay the smallest political unit with its own elected officials, treasury, and document-issuance authority (Clearance, Cedula at the barangay-treasurer level, Certificate of Indigency). Centralizing at the LGU level violates the principle of barangay autonomy. Your system respects each barangay’s independent records while exposing standardized formats for LGU-wide reporting.

2. RA 10173 (Data Privacy Act of 2012), Resident Records Protection

Expect: “How do you protect resident data?” Answer points: (1) Role-based access, only Secretary and Punong Barangay see full resident records, Treasurer sees only payment info, Staff sees encoding-only fields. (2) Audit log, every read / write logged with user + timestamp. (3) Prepared statements (PDO), no SQL injection vector. (4) Hashed passwords, `password_hash()` with bcrypt cost ≥ 10. (5) NPC-registered Data Privacy Officer, the Punong Barangay defaults as DPO; the system has a DPO contact field in the settings. (6) Right-to-be-forgotten workflow, soft-delete with 5-year retention, then hard-delete per NPC Circular 16-01.

3. eGov.ph Alignment, National Integration Roadmap

Expect: “Can this connect to PhilSys or eGov.ph?” Answer: The system exposes a documented REST endpoint for issued-document verification (third party POSTs the QR-decoded control number, gets back issuance metadata). This matches the eGov.ph “verifiable digital documents” pattern. PhilSys integration would happen via the PSA API (sandbox available), your system already stores the optional PhilSys Number field per resident.

Common panel questions to rehearse:

• “What happens if two barangay secretaries print the same clearance number at the same time?” → Database-level UNIQUE constraint on the control-number column + transactional insert. Demo it.
• “How do you prevent a staff user from deleting a blotter case?” → Role check at controller level + soft-delete only + audit-log trail. Show the log.
• “Where is the data hosted?” → Local LAN deployment (no cloud); cloud-ready via Hostinger / DigitalOcean droplet; complies with RA 10173 cross-border data-flow rules because data does not leave PH-resident infrastructure.
• “What is the difference between Cedula and Sedula?” → Same document; Cedula is the standard Spanish-Tagalog spelling, the official term is Community Tax Certificate (CTC).
• “Why MySQL and not PostgreSQL?” → Most LGU IT support in the Philippines is XAMPP-trained; MySQL is the maintenance reality. The schema is portable to PostgreSQL if the LGU later upgrades.

Related PHP Projects

• Fees Management System Project In PHP With Source Code
• Placement Management System Project In PHP With Source Code
• Hospital Management System Project In PHP With Source Code
• Construction Management System Project In PHP With Source Code
• Farm Management System In PHP With Source Code
• Event Management System Project In PHP And MySQL With Source Code

Inquiries

If you have any questions or suggestions about Barangay Management System Project In PHP With Source Code, please feel free to leave a comment below.