A PWD registry is often described as a list of persons with disabilities. The list is the output. The system is the lifecycle that decides who is on it, what evidence they supplied, and when the ID has to be renewed.

The stages

Intake is not the same as approval. Requirements are not the same as assessment. Approval is not the same as issuance. Each stage has a different actor, a different document, and a different question:

  • Intake: who is applying, where they live, and what they are asking for.
  • Requirements: which documents are present, which are missing, and what the staff still needs.
  • Assessment and approval: the decision, who made it, and when.
  • ID issuance: the number, the card, and the record that it was released.
  • Renewal: the next date, the new evidence, and the history of the previous ID.

Why one status is not enough

A single "approved" flag collapses the history. It cannot tell you whether the requirements were complete, who approved the application, or whether the card was printed and released. When a resident comes back for a renewal, the old record has to explain itself.

Each application should keep its requirements checklist, generated form, documents, status history, and assigned barangay. The current state is useful, but the path to it is what makes the record defensible.

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. Open full size

The desk, not the dashboard

The system is used at a desk, often by one person, often with a queue of applicants. The screen has to show what is pending, what is missing, and what is ready to issue. Reports are secondary to the next action.

That is why the application record matters more than the chart. The record is the working surface: requirements, documents, history, and the next step. The dashboard is a summary of the queue, not a replacement for it.

Imports and exports

Most offices already have a masterlist in a spreadsheet. A bulk import is the bridge, but it is not a free pass. Imported rows still need requirements, status, and a path to issuance. The import should create work, not pretend the work is done.

On the other side, reports need the municipal letterhead and the filters the office actually uses: status, barangay, disability. An export that cannot be attached to a memo is not finished.

The screens on the PWDIMS page use a generated demo dataset. The lifecycle is the product; the ID is one output.