Community Fund Tracker

The old version of this tool multiplied households by a contribution, called it the target, subtracted what had been collected, and divided the remainder to guess how many people were still pending. Two of those three steps were the user’s own arithmetic, and the third was a guess that assumed everyone who had paid had paid in full.

The real defect was the target itself. Every household paying in full is not a forecast, it is a ceiling, and no collection drive in the country hits it. Sizing a budget against that number means the fund is short from the day it is written, and the shortfall lands on whoever is holding the receipt book. So the tool now asks what participation you actually expect — 60% to 85% is the ordinary range — and reports what that collects.

On the defaults it collects ₹30,000 against a ₹41,000 budget. The old tool would have shown a ₹40,000 target and a ₹13,500 pending figure, both of which are true and neither of which tells you the drive is ₹11,000 underwater before anyone has been approached.

The single most useful number here is the break-even turnout: how many households have to pay in full for the budget to be covered. On the defaults it is 82 of 80, which is 102.5% — more households than exist. The drive is unfundable even if every door opens and every person pays, and the arithmetic says so before a single rupee is collected.

This is not an unusual mistake. It is what happens when the budget is built from quotes and the contribution is set by what feels askable, with nobody multiplying the two. The tool prints the three levers instead of a verdict: raise the ask to ₹683.33 a household, which is what ₹41,000 needs at 75% turnout; trim the budget to the ₹30,000 you will actually have; or improve participation, which is the lever everyone reaches for first and the only one that does not work on demand.

Below 100% break-even the reading is softer but still worth having. A drive needing 68% when you expect 75% has a real margin. One needing 74% against the same expectation is a coin flip, and the difference between those two is invisible in a target and a pending figure.

The second tab exists because the argument never happens during collection. It happens afterwards, when ₹34,000 was collected, ₹41,000 was spent, and somebody has to say so out loud.

That ₹7,000 shortfall has two honest splits and the tool shows both, because the choice is a decision rather than arithmetic. Across the 48 households who already paid it is ₹145.83 each — easy to collect, and it charges the shortfall to the people who were least responsible for it. Across all 80 units it is ₹87.50 — obviously fairer, and you will not collect it from the 32 who ignored the first request. Most committees end up with two or three people quietly covering the gap, which is worth naming as the likely outcome rather than discovering it.

A surplus needs the opposite discipline. ₹3,000 split back across 48 payers is ₹62.50 each, which costs more in effort than it returns, so carrying it forward is nearly always right. The condition is that it is announced. An unannounced surplus is not an accounting question, it is how a committee loses the ability to collect next year.

The tool also prints participation achieved and the average per paying household, next to what the same money would be if it had come from everyone. The gap between those two figures is exactly what the non-payers shifted onto the payers, and it is the number to quote when setting next year’s contribution.

The person most exposed in a community collection is whoever holds the money. Contributors risk ₹500. The collector risks being the one who cannot account for ₹41,000 in a WhatsApp group of 80 people, and a suspicion of that kind never fully clears.

Which makes the record-keeping self-interest rather than bureaucracy. A list of who paid what and when, receipts or photographs of every expense, and one published statement at the end are the whole requirement, and they matter most in the ordinary case where nothing went wrong. Digital collection produces most of that list automatically.

Whether a residents association needs to register, maintain formal books or file returns depends on how it is constituted and what it receives, and that is a question for a local accountant. The cash limit above applies regardless of any of it.

One contribution figure across the units you enter. Tiered drives need one run per slab, and the break-even reading is then per slab rather than for the whole fund — useful, but not the same as a single answer.

That everyone who pays, pays in full. Partial payments are common and the tool cannot see them, which is why the settlement tab asks for the total collected and the number who paid separately instead of inferring one from the other.

That the budget is known. It usually is not: pandal and sound quotes firm up late, food scales with attendance nobody can predict, and the last-week additions are what turn a funded drive into a short one. Re-run it when the quotes change rather than treating the first answer as settled.

Nothing here is a view on whether an association must register or file, and the tax reference is the cash receipt limit only. Anything about the association’s own status belongs with an accountant who can see its constitution.

Everything runs in your browser and nothing is stored between visits, so no resident names, flat numbers or amounts leave the device. Keep the actual list of who paid in your own records — the arithmetic here is the easy part, and the list is what protects you.