Community-Based Inclusive Development Information System

Every person counted once, and counted right.

One register for persons with disabilities. Each record is checked for duplicates before it is saved, validated by a second person, and shared only with the people who need to see it.

See how it works Privacy and access

This is a preview of the registration and validation module. Sign in opens when the National Council on Disability Affairs releases the system. No personal data is held on this page.

Checked before savedExact and close matches surface while the record is typed.
A second person validatesThe person who registers never approves their own record.
Sensitive details protectedID numbers are encrypted and masked by role.

How a record moves

From first contact to a validated record

Four steps, each with a named person responsible, and every step written to the audit log.

  1. Register

    An encoder or social worker records the person, the address down to the barangay, and a guardian for a minor.

  2. Check

    An exact government ID match stops the registration. A close match needs a recorded decision before it can be saved.

  3. Validate

    A different person approves the record, returns it with reasons, or marks what is still missing.

  4. Pending assessment

    Approved records wait for assessment, with priority cases first and a timeline of everything that happened.

Privacy and access

Built so people see what they need, and no more

Personal information about persons with disabilities is sensitive. The rules below are enforced by the system itself, not left to habit.

Each person once

Duplicate checks on name, birth date, sex, guardian and barangay run as the record is typed, before it is saved.

Two people, always

The person who registers a record and the person who validates it are never the same person.

Only your area

Each user sees the records in the areas they are assigned. A record outside that area simply does not appear.

Sensitive details protected

Government ID numbers are encrypted. Read-only roles see masked details, and small groups are never shown in reports.

Every action on the record

Creating, changing, approving and overriding are written to a tamper-evident audit log that can be verified at any time.

The system records, people decide

CBID records assistance and decisions. It never releases money, and every override needs a named person and a reason.

Fourteen roles, each with only what its work needs

EncoderSocial workerValidatorApproving OfficerLGU focal personRegional coordinatorClinical assessorPartner agencyProgram managerData Protection OfficerAuditorViewerSystem administratorTechnical support