Running a building with software
From the notebook to a system — which jobs in an 84-flat building are worth digitising, and which are not.
The problem is bookkeeping, not technology
Running a building is mostly repetition: raise the same 84 bills every month, reconcile who has paid, take complaints about broken things and close them out, keep a record of who came in, and show income against expenditure at the end of the year.
Every one of those can be done on paper, and has been for decades. The failure mode is not the paper — it is that the notebook lives with one person, and when that person gets busy or leaves the committee, the information leaves too.
The jobs worth digitising
Service charge billing and collection
Eighty-four bills a month on the same formula is not work for a human. Set the formula once and the bills raise themselves, the arrears list falls out on its own, and there is a permanent record of who paid when. Payments made by bKash or Nagad land in the same ledger as everything else.
Maintenance complaints
A stuck lift, a dead pump on the third floor, a corridor light out — raised verbally, these get lost. Raised as tickets, each has a number, an owner and a state: open, in progress, done. At the end of the month you can see which faults keep coming back.
Visitors and security
The difference between a name in the guard’s register and an entry in a digital log is whether you can search it. Who comes regularly, who visited which flat, when they left — the value is being able to find it when it matters.
Notices
Water off tomorrow, lift servicing on Friday, a meeting on Saturday. Not everyone reads the noticeboard. The same notice on a phone at least removes the excuse.
Accounts and reporting
The annual statement is the committee’s least popular job. If every transaction has been recorded in one place all year, the statement does not have to be assembled — it already exists.
What to look for when choosing
In Bangladesh the people operating this are volunteers, not professional managers. Software here has to be simple enough for a non-technical committee member to run without training — that constraint matters more than any feature list.
- Does it work in Bengali — not just the menus, but the bills and receipts.
- Can local payments — bKash, Nagad, bank deposit — be recorded against a flat.
- How easily does it hand over when the committee changes.
- Can the data be exported, so the accounts remain yours if you change system.
- Can residents see their own bill and arrears without asking anyone.
- Is the monthly cost sensible next to what the building collects in service charge.
Not all at once
Digitising everything simultaneously usually ends with nothing digitised. Start with whichever job takes the most time and causes the most argument — almost always the service charge ledger. Add the next one only once that is steady.
Common questions
- Does a small building need software at all?
- The more flats, the more errors and arguments a paper ledger produces. Buildings in this project hold 84 flats each, which is past the point where one place for the records pays for itself.
- Which job should we start with?
- Service charge billing and collection. It consumes the most time and generates the most mistrust.
- Will the records survive a change of committee?
- That is the main benefit — provided the data can be exported and the account belongs to the building rather than to an individual’s phone.
ruap.net is an independent portal and is not affiliated with RAJUK. What is written here follows RAJUK’s published notices and prospectus, but prices, dates and conditions are revised from time to time. Check your own allotment letter and RAJUK’s latest notice before acting on any of it.