Why every housing society must get this right every single time
Most Managing Committees worry about three things when approving expenditure: Is the work necessary? Is the cost reasonable? Is the vendor reliable? Very few committees ask a fourth, equally important question: Is our decision process legally compliant?
Under the Maharashtra Cooperative Societies (MCS) Act, Section 79A guidelines govern how housing societies must invite, compare, and approve tenders above a prescribed value. These guidelines are not advisory. They are mandatory directions issued by the Registrar of Cooperative Societies. Yet in practice, many societies—especially well-intentioned ones—violate these norms unknowingly. The risk is not theoretical. Contracts have been challenged, payments stalled, and committees questioned for procedural lapses.
This article explains what the 79A tendering guidelines are, why they exist, what they require in practice, and how societies can comply without turning governance into bureaucracy.
1. Why the 79A guidelines exist
Section 79A empowers the Registrar to issue directions to cooperative societies “in public interest.” The tendering guidelines were introduced to address a persistent problem in society management: opaque spending decisions. Historically, many societies approved large expenses based on personal relationships with contractors, single quotations, informal negotiations, and decisions taken without documented reasoning. This created room for overpricing, favoritism, disputes among members, and allegations of fund misuse.
The 79A guidelines were designed to standardise decision-making, not to burden committees. Their intent is simple: when member money is being spent, the process must be transparent, comparable, and defensible.
2. When do the 79A guidelines apply?
In Maharashtra, the guidelines apply to society expenditures above ₹25,000 (the threshold specified in the circular, subject to updates and interpretations). This includes painting contracts, waterproofing work, structural repairs, lift AMC and upgrades, major plumbing or electrical projects, and security, housekeeping, and facility management contracts. In short, most significant societal expenses fall within this scope.
Importantly, compliance is about process, not outcome. Even if the selected vendor is competent and fairly priced, a flawed process can still be questioned.
3. The first requirement: inviting sealed bids from qualified contractors
The guidelines require societies to invite sealed quotations from eligible contractors. The intent is to prevent price manipulation and post-submission changes. In practice, many societies unknowingly violate this by accepting WhatsApp quotes, allowing verbal revisions, comparing emails with different scopes, or taking “ballpark” figures.
A compliant approach requires clear scope definition shared with all bidders, quotations received in a secure and time-bound manner, and no negotiation or alteration after submission. This does not mean contractors must physically submit envelopes anymore. What matters is controlled, traceable submission, not the medium itself.
4. The second requirement: preparing a comparative statement
Once bids are received, the committee must prepare a comparative statement. This is not a formality-it is the heart of the 79A framework. A valid comparative statement must allow committee members to see scope alignment, cost differences, material specifications, timelines, and taxes and exclusions.
Merely listing total amounts is not sufficient. If one vendor quotes partial repair and another quotes full-system work, the comparison is misleading, even if unintentionally so. The purpose of the comparative statement is to ensure the committee is making an informed decision, not a price-driven guess.
5. The third requirement: recording reasons for selection
Perhaps the most overlooked—and most important—requirement is this: the committee must record why a particular vendor was selected. This is where many societies falter. Choosing the lowest bidder is allowed but not mandatory. Choosing a higher bidder is also allowed, but only if the reasons are documented.
Valid reasons could include better material specifications, shorter execution time, stronger warranty, proven track record, or lower long-term risk. What is not acceptable are reasons such as “committee felt comfortable,” “known contractor,” or “used earlier” without a performance context. Minutes of the meeting must clearly reflect the rationale. This protects the committee if the decision is later questioned.
6. What happens if societies ignore these norms?
Non-compliance with 79A guidelines carries real consequences. The Registrar has the authority to question expenditure approvals, invalidate contracts, direct recovery of amounts, and issue notices to committee members. In disputes between members and the committee, procedural lapses often become the weakest link even if the work itself was necessary.
Importantly, liability does not disappear after the committee’s term ends. Past decisions can still be examined. This is why compliance is not about fear-it is about protection.
7. Why compliance is hard with manual processes
Most violations are not intentional. They happen because manual systems are fragile. Typically, scope is loosely discussed, quotes arrive in different formats, comparisons are done manually, decisions are rushed in meetings, and records are scattered. In such an environment, even well-meaning committees struggle to maintain procedural discipline consistently. The law expects structure. Manual tools create variability.
8. How BlockPilot addresses 79A compliance by design
BlockPilot’s approach to tendering is built around a simple idea: if the process is structured, compliance becomes automatic. Instead of asking committees to remember the rules, the platform embeds them into the workflow. This includes standardised scope definition shared across vendors, controlled quotation submission, automated comparative views across identical parameters, clear audit trails of who submitted what and when, and decision records linked directly to data.
When the committee approves a vendor, the rationale is recorded alongside the comparison—not as an afterthought. This reduces dependency on individual diligence and creates system-level compliance.
9. A shift from reactive to responsible governance
79A compliance should not be seen as a regulatory hurdle. It is a signal that housing societies are no longer informal collectives, they are asset managers of multi-crore properties. As buildings age and costs rise, scrutiny will only increase. Societies that adopt structured decision-making early will reduce internal conflict, improve member trust, protect committee volunteers, and execute projects more smoothly.
The goal is not paperwork. The goal is confidence—confidence that decisions are fair, defensible, and future-proof.
10. Closing note for Managing Committees
Committee members are custodians of shared assets and shared money. The law recognises this responsibility, and so should the systems used to manage it. Compliance done manually depends on people. Compliance done structurally depends on the process. BlockPilot exists to support societies in making that shift quietly and effectively, so committees can focus on what to decide, not worry about how to justify it later.
Good governance is not about avoiding trouble.
It is about doing the right thing—correctly, every time.