DHMS
For local government in Bangladesh

Digital Holding Management System

A holding register for Bangladeshi local government — every property, its owners and its ward in one record, kept by the institution that is responsible for it.

Built for City Corporations, Pourashavas and Union Parishads — every holding, the people attached to it, and the ward it sits in, kept by the institution responsible for it and reachable by the residents it serves.

সিস্টেমের অবস্থা দেখুন

One system, three tiers of local government

The statutory form is not a label. It decides where the institution sits in the national geography and how its territory is drawn, and the system enforces the difference rather than leaving it to convention.

City Corporationসিটি কর্পোরেশন
Hundreds of thousands of holdings across dozens of wards, several tax circles, and a staff roster large enough that who may change what has to be a rule rather than an understanding.

Local Government (City Corporation) Act, 2009

Pourashavaপৌরসভা
A municipality with its own wards and its own numbering conventions, run by an office small enough that the system has to be usable without a training department behind it.

Local Government (Pourashava) Act, 2009

Union Parishadইউনিয়ন পরিষদ
The rural tier, where a holding is found by mouza and locality rather than by street address, and where the register is often the first complete list the union has ever held.

Local Government (Union Parishad) Act, 2009

What the system keeps

Registers an office can run day to day, and a public surface the people on the register can use without an account.

The holding register
Every holding with its buildings, its construction and condition, its use and occupancy, and the ward and locality it belongs to. Numbering follows the institution's own convention rather than one imposed on it.
Owners and occupants
The people and organisations attached to a holding, held once and referenced everywhere. Ownership and occupancy carry the dates they began and ended, so the register answers who was responsible in a given year rather than only who is responsible today.
Wards, areas and localities
The institution's own territory, built on the national geography of divisions, districts and upazilas. Wards are authored where they belong — inside the institution — and every holding resolves to one.
A QR code on every holding
Each holding has a public page a resident can reach by scanning it: which ward it sits in, and how to contact the office responsible. No sign-in, and nothing published that a passer-by should not see.
Reports from residents
A resident who finds something wrong — a holding recorded against the wrong owner, a building that no longer stands — can say so from that same page. Reports arrive in a worklist the office decides on, with the decision recorded.
A public page for the institution
Each institution publishes its own page: its identity, a message from its chairman or mayor, and the channels a resident can actually reach it through. Authored by the institution, in Bangla.
Access that follows the role
Permissions attach to a role, with per-member exceptions where an office needs one. An operator can never grant authority they do not hold themselves, and the last person able to administer access cannot be removed.
An audit trail that answers questions
Every change is attributable and timestamped, and the record keeps what a field held before as well as after. A dispute about a holding is settled by reading the trail rather than by reconstructing it.

How an institution starts

In this order, because the order is real: a holding cannot be recorded until there is a ward for it to belong to.

  1. 01

    The institution is provisioned

    It is created with its statutory form, the district or upazila it belongs to, and its own address on the platform. Its roles come with it.

  2. 02

    Its territory is authored

    Wards, areas and localities, drawn from the national geography beneath them. This comes first because every holding must resolve to a ward.

  3. 03

    The register is filled

    Holdings, their buildings, and the owners and occupants attached to them — entered by the office's own staff, each under their own account.

  4. 04

    Residents can see their own record

    Holdings carry a QR code, the institution publishes its page, and a resident who finds an error has somewhere to report it.

Built to be run by the institution that owns the data
A register of who owns what is a public record. These are properties of the system as built, not commitments to be arranged later.

  • Bangla first

    The consoles are written in Bangla, with English available. Not a translation layer over an English product — the Bangla is the interface.

  • One institution cannot read another

    Separation is enforced in the database and in the type system, not by remembering to filter. Every institution's data is reachable only from that institution's own address.

  • It runs on your infrastructure

    DHMS runs against a PostgreSQL instance you control, on a server you choose. Nothing about it assumes a shared store outside the country.