PWDIMS

The PWD member lifecycle at one desk: intake, requirements, approval, ID issuance, and renewal.

FastAPI · React · PostgreSQL · Docker Stack

19,245 lines

7,448 React lines

Built · Local State

Built locally: it runs on a laptop or LAN, not a hosted demo.

PWDIMS dashboard with member and application stat cards, a monthly applications chart, and breakdowns by barangay, disability, sex, and age. — PWDIMS dashboard: member counts, pending applications, renewals, and registry charts.

Inside the system

1 / 3

PWDIMS applications table listing application numbers, applicants, barangays, types, statuses, and filing dates. — Applications register with applicant, barangay, type, status, and filing date.

PWDIMS application record showing a Draft, For review, Approved workflow, a requirements checklist, generated application form, applicant details, and history. — An application record with its workflow, requirements checklist, generated form, and history.

PWDIMS reports page showing the Masterlist of Persons with Disabilities with PWD ID numbers, disability types, barangays, statuses, and validity dates. — Reports with status, barangay, and disability filters, exportable to Excel or PDF.

How it is built

PWDIMS is a municipal PWD registry built with FastAPI, PostgreSQL, and React. The desk handles intake, application requirements, assessment, approval, PWD ID issuance, renewals, and member records. Each application keeps its requirements checklist, generated form, documents, status history, and assigned barangay.

The system also covers bulk masterlist import, audit logs, and report exports with the municipal letterhead. The screens use a generated demo dataset, not a client's records.

Surfaces

PWD registryIntake, requirements, approval, ID issuance, imports, and renewals.

→

Your system

The next entry is the work still done by hand. How a build runs.