A sale in a housing society rarely fails on the agreement. It stalls on a letter: the no-objection certificate. The buyer, the bank, and often the registrar want the committee to say the outgoing member has cleared their dues and the society does not object to the transfer.
This page is for secretaries and treasurers who keep that letter in a WhatsApp thread, and would rather have a sequence they can stand behind at the AGM.
What the NOC is actually saying
A society NOC is not a blessing of the deal. It is a statement of the society's own position: this member's account is clear (or the outstanding is listed), the transfer fee if your bye-laws levy one has been dealt with, and the committee does not object to the new name on the share certificate.
If your bye-laws are silent on a point, do not invent a charge in the letter. The NOC should match the rules the society already passed.
Why sales stall
The bottleneck is almost never the signature. It is the dues check.
Maintenance, sinking fund, parking, penalty, a festival collection from two years ago: if those sit in a spreadsheet and a passbook, the office spends days reconciling before anyone can type "no objection". Meanwhile the member forwards the same request to four people.
A clean NOC is only as fast as a trustworthy ledger.
A sequence that holds up
Four steps, in this order:
- The resident applies. The outgoing member files a transfer request with the sale details the bye-laws ask for, not a screenshot in the secretary's chat.
- The office checks dues. Outstanding maintenance, interest if your rules levy it, deposits held, and any transfer or NOC fee the bye-laws actually contain. The answer is a number, not a feeling.
- The NOC is issued. Dated, on society letterhead (or the society's digital equivalent), with the dues position stated. If something is unpaid, say so. A vague "subject to clearance" letter is how disputes start after registration.
- The transfer is recorded. New owner on the register, share certificate, parking, and the prepaid wallet or deposit account if the society keeps one. The NOC without this step is a letter that does not match the books.
That shape is what a bank and a buyer can follow. It is also what an auditor can follow.
What goes wrong on WhatsApp
- Requests that never become a file, so nobody can say when they arrived.
- Dues "cleared" in one conversation and disputed in another.
- An NOC issued, then a transfer recorded weeks later under a different spelling of the name.
- A new resident at the gate whose flat is still in the old owner's account.
None of this is a character problem. It is a missing sequence.
Holding the sequence in the society's software
A society operating system can take the same four steps without inventing new rules. The resident applies in the app. The office sees the dues on the same ledger it uses for monthly billing. The NOC is issued against that position. The transfer is recorded so the gate, the wallet, and the register move together.
If the software treats your bye-laws as configuration, transfer fees, notice windows, and what "clear dues" means are the society's settings, not a generic template. That is the test: the letter matches the books, and the books match the rules you actually passed.
A checklist before you sign the letter
- The request is on file, dated.
- Dues position is from the ledger, not from memory.
- Any fee in the letter exists in the bye-laws.
- The letter states the dues position in numbers.
- After issue, the register, gate list, and deposits are updated in the same motion.
If those five are true, the NOC is doing its job. If any one is missing, pause the letter, not the sale conversation.