Running a housing society in India is harder than most people realise - until they join the committee.
An RWA (Resident Welfare Association) committee is typically made up of volunteers - an engineer, a retired teacher, a doctor, a businessperson. They have full-time jobs, families, and no formal training in property management. And yet they're responsible for collecting dues from 200 households, managing security guards, handling complaints, maintaining common areas, and keeping the accounts straight for an AGM that's 11 months away.
It's a significant operational responsibility, done entirely on goodwill, usually with tools that were never designed for the job.
This article is about the eight problems that come up in nearly every RWA committee we've spoken to - and why each one is harder to solve than it first appears.
1. Maintenance billing is a monthly ordeal
The single most time-consuming task for most committees is collecting maintenance dues.
The typical process looks like this: the treasurer generates an amount (sometimes from memory, sometimes from a spreadsheet), sends a reminder to the WhatsApp group, waits a few days, then follows up individually with residents who haven't paid. Cash is collected at the gate or transferred to the treasurer's personal UPI ID. A note is made in a notebook or Excel sheet. This repeats every month.
The problems compound over time:
- Residents claim they paid when there's no record
- Late fees are inconsistently applied
- Tracking who owes arrears across multiple months becomes complex
- The treasurer changes, and the new one inherits an Excel file they don't fully understand
Why it's hard to fix: It's not just a billing problem. It's a trust problem. Residents need to feel confident that their payment is recorded accurately, and the committee needs a system both sides can refer to. A simple UPI QR code doesn't solve this without a proper ledger attached to it.
2. Complaints disappear into group chats
When a resident has a complaint - a broken lift, a leaking pipe, a dog-fouling common area, a dispute with a neighbour - they post it in the WhatsApp group.
The group might have 150 members. By the evening, the complaint is buried under 40 other messages. The relevant maintenance person may or may not have seen it. Nobody takes ownership. Nobody follows up.
Three weeks later, the resident posts again, now frustrated. The committee is embarrassed. The maintenance person says they never received the complaint.
Why it's hard to fix: Complaints need to be assigned, tracked, and closed with confirmation - not just acknowledged. A group chat has no mechanism for any of that. Even a shared Google Sheet requires someone to manually update it, which means it's always out of date.
3. Gate security is a notebook nobody reads
Most gated communities have a security guard who maintains a visitor register - a physical notebook where names, contact numbers, vehicle numbers, and entry/exit times are written by hand.
This register almost never gets reviewed. Entries are illegible. Dates are sometimes wrong. Nobody checks it unless something goes wrong, at which point it's rarely helpful.
Meanwhile:
- Residents have no way to pre-approve visitors
- There's no way to flag an unauthorised entry in real time
- Delivery and service staff walk in and out with no record
Why it's hard to fix: Replacing the paper register requires the security guard to use a device and a software interface - which means training, consistency, and willingness. Guards change frequently. Without the right tool and the right workflow, digital records get abandoned within weeks.
4. Nobody really knows the society's financial position
Ask any committee treasurer how much was collected this month, and they'll tell you - with varying degrees of confidence. Ask them how much is outstanding in arrears across all units, and most will have to go back to their spreadsheet.
Ask them what the society's bank balance is, and how that compares to committed maintenance expenses for the next quarter, and you'll get a long pause.
RWA finances are genuinely complex:
- Multiple income streams (maintenance, parking, amenity fees, interest)
- Ongoing expenses (security, housekeeping, repairs, utilities)
- One-time expenses (AMC renewals, equipment replacement, events)
- Arrears management across dozens of defaulting households
Presenting this clearly at an AGM requires hours of manual work to compile a report that most members question anyway.
Why it's hard to fix: Accounting requires consistency from the start. If three months of data is in one format and the rest is in another, reconciliation becomes a project in itself. Most committees don't have time to build a proper system mid-year.
5. WhatsApp group fatigue is real
The RWA WhatsApp group starts with good intentions. It becomes, over time:
- A place where every complaint is aired publicly
- A venue for personal disputes between neighbours
- A channel where important notices get buried under chatter
- A source of anxiety for committee members who feel obligated to respond
Many residents mute the group entirely, which means they miss important announcements - water shutdowns, security alerts, AGM notices, lift maintenance schedules.
Committees that create separate groups for "announcements only" find that residents don't check them. Committees that try to enforce group rules face pushback.
Why it's hard to fix: WhatsApp is where residents are. Moving them to a different platform requires a compelling reason. A separate app that just replicates what WhatsApp does won't be adopted. The integration has to add something WhatsApp can't - like payment receipts, complaint tracking, or visitor approvals.
6. Staff management runs on trust and luck
A well-run society typically employs or contracts:
- Security guards (often 2-3 in shifts)
- Housekeeping staff
- A gardener
- A maintenance person or plumber
Managing these people is a daily operational task. Attendance is tracked by the guard on duty signing other staff into a register. Salary is calculated at month end, often with disputes about leave or overtime. Complaints about staff performance go unaddressed because there's no formal system for raising them.
When a specific maintenance task needs to be done, the committee member or manager calls the relevant person directly. There's no task management, no record of what was done, no way to verify completion.
Why it's hard to fix: Staff management software is designed for HR departments in companies. It's overkill for a 6-person ground staff, and too complex for a volunteer to administer. The system needs to be simple enough for a security guard or electrician to use on their phone without training.
7. Vendors are managed through personal relationships
Every society has a preferred plumber, electrician, pest control company, and lift maintenance vendor. These relationships exist in the phone contact list of the current committee treasurer or secretary.
When the committee changes, these contacts are lost. The new committee has to start from scratch, often using vendors who are more expensive or less reliable. Past service history - what was repaired, when, at what cost - is nowhere on record.
AMC (Annual Maintenance Contract) renewals are tracked, if at all, in a reminder someone set on their personal phone. They get renewed late, or not at all, until something breaks.
Why it's hard to fix: Nobody sets out to manage vendors badly. It happens because there's no centralised place to store this information that persists across committee changes. Email and WhatsApp are person-specific, not organisation-specific.
8. Society documents live in someone's hard drive
Bye-laws. Society registration certificate. Fire NOC. Meeting minutes from the last three AGMs. Insurance policy. Lift inspection certificate.
Ask any committee member where these are, and the honest answer is usually: "I think Ramesh has them," or "they should be in the email from 2019."
Critical documents are scattered across personal email accounts, USB drives, and WhatsApp conversations. When a new committee takes over, documents get lost. When a resident needs a NOC for a bank loan, it takes days to locate the right file.
Why it's hard to fix: Document management sounds easy until you try to standardise it across a committee where members have different habits, different devices, and different levels of comfort with technology.
The common thread
Every problem above has the same root cause: housing societies have no operating system.
Companies have ERP software, CRM systems, accounting tools, and HR platforms. The individual tools talk to each other, and there's a single source of truth for any piece of information.
RWA committees have WhatsApp, Excel, and a paper register. Nothing is connected. Nothing persists across committee changes. Every incoming committee starts over.
This isn't a criticism of committees - they're doing the best they can with tools that weren't designed for this job. It's an observation about a gap in the market that has existed for far too long.
What a proper system looks like
A well-designed management system for a housing society needs to do a few things well:
Work for every role - not just the committee, but residents, security guards, and maintenance staff. If any one group isn't using it, the system breaks down.
Be simple enough to actually use - committee members are volunteers, not tech professionals. Maintenance staff may have limited smartphone experience. The UI has to be forgiving.
Handle money properly - billing, collection, receipts, and reconciliation need to be built around UPI, the way India actually pays.
Meet residents where they are - WhatsApp notifications, not just in-app. Residents shouldn't have to log in to learn that the water will be off tomorrow morning.
Persist across committee changes - the data belongs to the society, not to the current treasurer's Excel file.
A closing thought
If you're on an RWA committee, you probably recognise most of this. The problems aren't new. They've existed for decades, and most committees have found some workaround for each one.
The question is whether workarounds are good enough when there's a better alternative available.
We built Twnship to be that alternative - four connected apps for every role in a housing society, designed from scratch for how Indian societies actually work. If you'd like to see what that looks like in practice, book a free demo and we'll walk you through it.