Before you vote — read the record for last year
This is not opinion. Every number below is counted from 17,967 messages posted in our own residents' WhatsApp group between 10 Aug 2025 and 12 Aug 2026. Names have been removed. The record has not.
A committee can be unlucky once. It cannot be unlucky 1,012 times. Reports arrived on 1,012 separate occasions across 368 days, and 290 of them explicitly said “again”, “still”, “third time” or “months now”. Repetition at this scale is not bad luck. It is the absence of a process.
Where the year went wrong
Resident fault reports by category. Hover any bar for the number of separate days affected.
There was never a clean month. Not one.
Eight separate systems — water, power, lifts, housekeeping, security, drainage, parking and the amenities — generated complaints in every one of the 13 months on record. When the same eight systems fail every single month for a year, the problem is not the systems.
This is the clearest single measure of a maintenance regime: not how many problems arrive, but how long they stay. Each bar below runs from the day residents first raised an issue to the day they were still raising it. The shortest ran 205 days. The longest ran 363 — effectively the entire year.
First reported → still being reported
Bar length = days the issue stayed live in the group. Hover for message counts.
Both times the cause was the same, and it was not a burst pipe. It was money that had not been paid to the people who keep the taps running.
13 January 2026 — the day the tanks ran dry
404 messages from 138 residents in a single day.
Plumbers and electricians had gone unpaid for two to three months and had walked out. With nobody monitoring, the overhead tanks emptied overnight and all three borewells sat switched off. The President was out of Bangalore; residents asked repeatedly who else they could contact, and got no answer.
6 August 2026 — ten days before this election
262 messages from 116 residents in a single day.
The water tanker vendor parked across the main gate and blocked residents from leaving for work, over an unpaid bill he put at ₹75 lakh. The society went without water for the day. Fire-tank water was pumped into the domestic supply as an emergency measure.
Seven months apart. Same cause. Nothing changed in between.
A committee that had already lived through January and still let August happen is telling us, plainly, what the next two years look like. This is what “no process” costs a household on a working Thursday morning.
A maintenance failure is a problem you can fix. A culture that discourages the people who report failures is a problem that compounds — because the next failure arrives unreported.
Yes, the committee are volunteers. That is exactly why this matters.
Every resident here knows the Management Committee gives its time for free, and
is grateful for it. Nobody is asking for servants. But volunteering is a reason to
offer help — it has never been a defence against accountability, and it is not
a licence to silence the people you volunteered to serve.
A resident who reports a broken lift, a dry tank or a dead fire alarm is not
attacking anyone. They are doing the one thing that makes a community
self-correcting. When raising a concern earns a public warning, a
“WhatsApp warrior” jibe, or a deleted message, the problem does not go
away — only the report does. And the next resident, watching, simply stops
speaking up.
That is the real cost on this page. Not any single failure, but a
year of teaching 600 households that it is safer to stay quiet. Whoever wins on
Sunday inherits that lesson — and has to undo it.
Tenants live with these failures daily and have no vote. Owners have the vote — and, increasingly, the bill. Here is why this is a financial question, not a comfort one.
Every prospective tenant and buyer checks reviews, asks the broker about water, and talks to residents before signing. The events on this page are the answers they get. Two total water failures in one year. Lift breakdowns reported in every one of the thirteen months. Court floodlights still dark eleven months after the first complaint on this record. Fire alarms flagged by residents as non-functional against high-rise NOC requirements. These are the specifics that move a rent negotiation and a resale price.
Vacancy between tenants. Rent held flat while comparable projects raise theirs. Discounts demanded at renewal. A resale that sits on the market while the buyer “checks with a few residents”. A corpus spent twice on the same repair because the first fix was never a fix. And a fire-safety exposure that lands on the association — which means on owners.
“How can such issue occur in a premium society like Mantri? These are basic amenities we all expect — otherwise what's the difference from living in a chawl?”
A resident, 13 January 2026The strongest protection for your asset is not a louder complaint in the group. It is a committee that runs a maintenance calendar, pays its vendors on time, publishes its books, and answers the people who raise problems.
1. Which of the 12 chronic issues on this page was closed out this year?
2. What changed in the process between the January water failure and the August one?
3. If you had reported a problem here, would you have expected an answer — or a warning?
Ask every candidate. Accept specifics, not assurances. Then vote for whoever gives you the better answer — because for the next two years, you live inside it.
The timeline
The same data, arranged by time. The point of this view is not any single month — it is that there is no good month. The line never returns to a baseline, because nothing was ever fixed at the root.
Resident fault reports per month
Crisis-level reports shown separately. Aug 2025 and Aug 2026 are part months. Hover for values.
Every category, every month
Darker = more reports. Values are printed in each cell, so the table reads without colour.
The moments where the pattern is clearest.
The same twelve issues, on the calendar. Each row starts the day it was first raised.
Method. Every figure on this page is derived by script from a standard WhatsApp export of the Lithos residents' group covering 10 Aug 2025 to 12 Aug 2026 — 17,967 messages from 758 participants. Messages were classified into 14 service categories by keyword and fault-phrase matching. A message counts as a “fault report” only when it names a shared service or common-area asset and describes a problem with it. Messages from Management Committee and managing-agency accounts are excluded from resident report counts, as are personal requests and classifieds.
Anonymity. No resident is named, identified, or linked to a flat number anywhere on this page. Quotations are lightly cleaned for spelling and typing errors only; wording, meaning and dates are unchanged. Statements from the Management Committee are attributed by office rather than by individual, because the argument here is about how the office was run, not about any person.
Scope and limits. This covers one year, not the committee's full term. Automated classification is approximate: some reports will have been missed and a small number miscategorised, so these counts should be read as a robust floor rather than an exact census. The response-time figure measures the first message from any committee or agency account after a report — a reply in the group, not a repair. Nothing here is a claim about anyone's motives.
Record and corrections. The Management Committee referred to throughout is the committee whose term is covered by this data, chaired by the incumbent MC President. This page is published by a resident so that owners can weigh the record before voting. Corrections are welcome and will be made.