Open the committee group of any Indian housing society at eleven at night and you will find the same three threads running at once: a photo of water leaking through a ceiling, a discussion about whether the guard was sleeping, and someone sharing a good-morning image over both.

By morning the leak has scrolled past. In two weeks the resident asks why nothing happened. Nobody can find the message, nobody was assigned, and the honest answer — that it was seen by nine people and owned by none — is not one a committee can say out loud at the AGM.

This is not a discipline problem. It is a tool problem, and it is worth being precise about which parts of the tool are actually failing, because the group chat is doing several jobs and it is genuinely good at some of them.

What the group chat does well, and why it will not die

Any plan that starts with deleting the group will fail in a week. Be honest about what it earns its place doing.

Everyone already has it. No onboarding, no download, no explaining to a resident in her seventies what an app store is.
It is instant. When the water tanker has not arrived and the overhead tank is empty at 8pm, chat is the correct tool.
It carries photos, which is how most maintenance problems are actually reported.
It costs nothing, and a society that argues about a fifteen-hundred-rupee expense at every meeting notices that.
It is where the community actually lives — the festival planning, the lost cat, the plumber recommendation. That has real value and no software replaces it.

So keep the group. The question is not whether to have one. It is which four jobs you should stop asking it to do.

Complaints: raised in chat, resolved never

A complaint in a group chat has no owner, no status and no closure. It has an audience. Those are different things, and the difference is the whole reason residents believe the committee does nothing.

Consider what happens to the same leak in a helpdesk. It arrives as a ticket with a category and a flat number. It gets assigned to a person — the plumber, the secretary, the facility manager. It carries a status the resident can see without asking. It gets closed with a note on what was done, and the note stays attached to that flat forever, so when the same ceiling leaks next monsoon nobody starts from zero.

Every complaint has one owner, named, from the moment it is raised
Categories that mean something to the committee: plumbing, electrical, lift, security, housekeeping, common area, parking
A status the resident can check herself, which removes most of the follow-up messages the committee currently answers
A closure note, so resolution is a recorded fact rather than a claim
A history per flat and per category, which is how you find out that the third-floor pipe has been repaired four times and needs replacing

The committee benefit is not administrative tidiness. It is that at the AGM you can say a number — this many complaints raised, this many closed, average time to close — instead of defending yourself against the three that people remember.

A complaint that was seen by everyone and owned by nobody is not a complaint. It is a message.

The gate: visitors, deliveries and a diary nobody can search

The gate register is the oldest record in the society and the least used. A guard writes a name, a flat number and a time in handwriting that varies by shift. In three years nobody has ever read it — until the one day somebody needs to know which cab entered at two in the morning, and the answer is forty pages of biro.

A digital gate log changes three things at once. The entry is legible and timestamped. The resident is notified when a visitor or a delivery arrives for her flat, which is the first benefit residents actually feel. And the record is searchable, so a security question that used to take an evening takes a minute.

Visitors logged against the flat they are visiting, with in and out times
Deliveries and cabs recorded, because those are most of the traffic and none of the current register
Domestic staff and vendor entries, which is the log societies wish they had after an incident
The resident notified at entry rather than discovering the visitor at her door
A searchable in-and-out history the committee can actually use

One caution worth writing into your own rules: a visitor log is personal data about people who are not members of your society. Keep it because you need it for security, keep it for a period you have decided on, and do not circulate it in a chat group.

Money in a group chat is how disputes start

This is the job the group should never have been given. Maintenance collected on a treasurer's personal UPI, receipts issued as replies, payment proof as a screenshot, and a running total that lives in one person's head.

A screenshot is not a receipt. It proves a transfer happened, not which bill it settled.
Part payments get applied to whichever month the treasurer had in mind, so the member and the society hold different balances and both are sincere
There is no numbered receipt trail, which is the first thing an auditor asks for
The treasurer becomes the society's bank, personally, which is unfair to him and structurally unsafe for everyone else
When the committee changes, the payment history changes phone

The fix is not complicated: bills raised on a cycle, delivered the same way to everyone, and gap-free numbered receipts issued against them, in the society's name, in a ledger the next committee inherits. Chat can carry a reminder. It cannot be the ledger.

See what the society workspace covers

Notices, polls and AGM communication that must be provable

Some society communication is social. Some of it has legal weight, and the two look identical inside a chat window.

A general body notice has to be issued, dated and delivered in the manner your bye-laws require. A message dropped into a group that fourteen members have left, three have muted and two were never added to is not delivery, however sincerely it was sent. The same applies to resolutions: a thumbs-up from eleven people in a chat is not a vote, and if a decision worth several lakh rupees rests on it, the committee can find itself answering for that decision with nothing better than a scroll-back when someone challenges it.

Notices issued to every member of record, with a record of what was sent, when and to whom
Circulars kept in one place a member can look back at, instead of scrolled past
Polls run as polls, with who was eligible and what the result was preserved — with the formal resolutions still done the way the bye-laws prescribe
Share certificates and transfers maintained in a proper register, which is a statutory record and not a folder of photographs
The minutes book kept as the actual decision record, with the chat treated as what it is: conversation

The test is simple. If a decision were questioned two years from now by a member, a buyer's lawyer or a registrar, could you produce what was decided, who decided it and how everyone was informed? If that evidence is a screenshot, you do not have evidence.

What a society system has to do to earn committee adoption

Here is the part software vendors underestimate. The committee is not a management team. It is four or five people with day jobs and families who took this on reluctantly and will drop anything that adds work. Any system has to pay for itself in the first month, from their point of view, not the owner-of-a-business point of view.

The bill run for every flat has to take minutes, not an evening, or the treasurer will go back to the spreadsheet
Receipts must issue themselves when payment is recorded, because nobody wants a second manual step
The defaulter position must be a report you can generate, not a reconciliation someone performs
It has to work on a phone, standing at the gate, because that is where committee work actually happens
It must survive handover: the account belongs to the society, not to whoever is treasurer this year
It must need no training. A committee member who requires a session before he can use it will simply not use it.

If the first month does not visibly reduce the treasurer's workload, the group chat wins by default and you have paid for the privilege.

Resident adoption is the second, harder problem

Committees forget that residents never asked for any of this. To a member, the society software is one more thing to install because a committee she did not vote for decided something. She will use it if it gives her something she wants, and ignore it otherwise.

Her own dues and receipts, visible without asking anyone — the single most requested thing in every society
A notification when a visitor or delivery arrives for her flat
A complaint that comes back with a status instead of silence
Notices in a place she can search when she needs the AGM date
No obligation: keep the printed notice on the board and keep answering the phone, because a chunk of every society will never move and they are usually the oldest residents

Adoption is not a training problem, it is a value problem. Give residents two things they genuinely want and the rest follows quietly.

Roll it out at the gate first

If you are going to change one thing, change the gate. It is the least controversial part of the society, the guard has exactly one screen to learn, and residents receive the benefit passively — a notification arrives and they did nothing to get it. Nobody has to be convinced of anything, and within a fortnight you have a real visitor record.

Month one: gate and visitor logging, with resident notifications switched on
Month two: complaints, so the monsoon list stops living in chat
Next billing cycle boundary: maintenance billing and receipts — start at a cycle, never mid-cycle, and carry opening arrears across carefully
After one clean cycle: the member registry tidied properly, with owners, tenants and contacts verified
Then: notices, share certificate register and the accounting heads, in time for the audit rather than during it
Keep the group throughout, for exactly what it is good at

The society workspace is built around that order: gate and visitor management in every plan from the community tier up so security adopts it from day one, a complaints helpdesk that assigns and tracks to resolution, maintenance billing with numbered receipts and interest on arrears, a member registry with one-click no-dues certificates, notices, polls and a share certificate register, and double-entry books with sinking and repair fund heads that export to Tally for the auditor.

None of it makes the committee's job glamorous. What it does is make the job survivable, handover-able and defensible at the AGM — which, for four volunteers with day jobs, is the entire point.

Compare plans for your society