Databus Logo
Blog Login →
The Building-Compliance Layer for RWAs, Societies & Builders

The building insurance was 14 days from lapsing — and it was sitting in a cardboard box nobody had opened in years.

This is the compliance layer that catches it before it bites — tracking OC, Fire NOC, structural audit, lift safety, insurance and bye-laws, with a warning 30 and 7 days before any one expires. The compliance outcome, distinct from the document vault, the lease, and the ledgers.

For RWA office bearers, society secretaries & builders · 11 compliance-doc types · 30+7-day alerts · society-owned · §3A e-sign.

See the expiry tracker →
In plain English

Building document & compliance management makes sure a society or building's statutory documents are never found to have lapsed after the fact. It tracks the eleven compliance-document types a building must keep current — OC, Fire NOC, structural audit, lift safety, AMCs, building insurance, property tax, bye-laws, lease renewals, AGM minutes and Form 7/12 — and warns the office bearers 30 and 7 days before any one expires. This is the compliance-outcome layer. The underlying vault mechanism — the role-based access matrix, folder categories, §65B audit-log internals and retention stack — is the document-repository feature; the lease document and its lifecycle are tenant-lease-management; financial-record retention is accounting-finance. Documents are society-owned — not on the Hon. Secretary's personal Gmail — with §3A e-sign legal validity.

11 doc types
each with its own
expiry clock
30 + 7 days
twin-tier warning
before any lapse
Society-owned
not the Secretary's
personal Gmail
§3A e-sign
Aadhaar eSign / DSC
legally valid signing
A real weekend · Dwarka CGHS · 168 flats · 26 years of paper

Seven boxes of paper became a compliance calendar — and caught a ₹47 lakh near-miss.

Mr Khurana inherited 26 years of records from the outgoing committee — seven cardboard boxes. Digitising them over one weekend, the system didn't just store them; it read each document's expiry and immediately surfaced what was about to go wrong.

Compliance tracker · Hari Kunj CGHS · 11 document types · post-upload Caught at upload
Document typeValidityStatus at upload (Sat 19:00)
Occupancy Certificate (OC)PermanentOn file · permanent
Building insuranceAnnual▲ 14 days to lapse — ₹47L cover at risk · caught
Fire NOC1–3 years⚠ Renewal due in 38 days
Structural audit (15+ yr bldg)5 yearsCurrent · next due 2028
Lift safety certificateAnnualCurrent
AMC contractsPer contract▲ 12 AMCs already expired · auto-discovered
Property tax receiptAnnualPaid · current
Bye-laws (versioned)On amendmentv3 on file
Lease renewalsPer leaseTracked → tenant-lease
AGM minutesPermanentArchived · permanent
Form 7/12As updatedOn file
The amber line at the top is why this is an outcome page, not a storage page. The building insurance — 14 days from lapsing — was in one of those boxes, and a refused claim on an uninsured building could have cost the society ₹47 lakh. The system flagged it at 19:00 on the Saturday of the migration, before anyone had even finished uploading. Twelve dead AMCs surfaced the same way.
Where a society's compliance quietly fails

Four ways a building is non-compliant without anyone realising.

The lapse found during the incident

The Fire NOC expired eight months ago, and the society learns this during a fire drill or an inspection — exactly when it's most expensive. A document that lapses silently is worse than one that was never filed.

Records that leave with the Secretary

The compliance files live in the outgoing Honorary Secretary's personal email. The committee changes, and the new team inherits a partial pile and a lot of guesswork about what's current.

One pile, eleven different clocks

OC never expires, Fire NOC renews in a year or three, the structural audit every five — but treated as one undifferentiated folder, the only one anyone notices is the one that already caused a problem.

The refused insurance claim

A building incident happens, the claim goes in, and the insurer points out the policy lapsed weeks earlier. The cover everyone assumed was in place wasn't, and the cost lands on the society's members.

How the compliance loop runs

From a box of paper to a living compliance calendar.

1

Get the documents out of the boxes

Every compliance document is uploaded into a society-owned store — not a cupboard, not the Hon. Secretary's personal email. At upload, anything already expired or close to it is surfaced immediately, the way 12 dead AMCs and a 14-day-to-lapse insurance policy surfaced in the Dwarka migration.

2

Record each document's expiry clock

Each of the eleven types carries its own validity rule — OC permanent, Fire NOC 1–3 years, structural audit 5 years for older buildings, lift safety annual — so the system knows when each is due, rather than treating all paper the same.

3

Get the twin-tier warning

30 days before a document lapses, and again at 7 days, the responsible office bearers are alerted — so a Fire NOC renewal or an insurance premium is handled in advance, not discovered missing during an incident or after a claim is refused.

4

Sign and renew with legal validity

Where a document needs signing, §3A e-sign — Aadhaar eSign via NeSL, Protean or NSDL, or a Class 2/3 DSC from a CCA-licensed authority — gives it legal validity, so renewals don't wait on circulating paper and physical signatures.

5

Hand over without losing the records

When the committee changes, the documents stay with the society because they were never in any individual's personal account. A builder hands over the RERA, OC, NOC and structural-drawing set the same way. The compliance record survives the people who maintained it.

The statutory frame this runs inside

The documents Indian buildings are legally required to keep.

The compliance document set

OC, Fire NOC, structural audit (mandatory at 5-year intervals for buildings over 15 years in many states), lift safety, building insurance, property tax, versioned bye-laws, AGM minutes and Form 7/12 — the statutory paper a society or building is required to hold and keep current.

IT Act 2000 §3A — e-sign validity

Electronic signing via Aadhaar eSign (through NeSL / Protean / NSDL) or a Class 2/3 Digital Signature Certificate from a CCA-licensed certifying authority gives a signed document legal standing — so renewals and resolutions don't stall on physical signatures.

Builder handover + society ownership

The builder-handover set (RERA, OC, NOCs, structural drawings, environment clearance) is assembled in a society-owned store, so the incoming RWA inherits a complete record. Resident data is handled under DPDP Act 2023 §6 with masked Aadhaar.

Framework references: Occupancy Certificate / Fire NOC / structural audit / lift safety statutory requirements (state-specific); IT Act 2000 §3A e-sign + Aadhaar eSign (NeSL / Protean / NSDL) + Class 2/3 DSC from CCA-licensed CAs; RERA builder-handover document set; DPDP Act 2023 §6 + UIDAI Aadhaar masking; IT Act 2000 §65B (admissibility — mechanism owned by the document-repository feature). Specific renewal intervals vary by state and building age; verify locally.

Outcome vs mechanism · what this page owns

Compliance outcome ≠ the vault ≠ leases ≠ ledgers.
This page owns the outcome; the vault mechanism is a feature.

EstateDeck keeps the building-compliance outcome and the document-vault mechanism as separate pages on purpose, so the buyer reading for "stop my Fire NOC lapsing" and the evaluator reading for "how does the access matrix work" each land in the right place.

This page owns

  • The building-compliance outcome — 11 statutory doc types kept current.
  • The 30+7-day expiry warning as a buyer outcome (lapse caught before it bites).
  • The society-owned positioning — records survive a committee handover.
  • §3A e-sign legal validity for renewals and resolutions.
  • The builder-handover document set (RERA / OC / NOCs / drawings).

This page defers to

  • The vault mechanism — 4-tier role-based access matrix, 6 folder categories, §65B audit-log internals, version control, watermarking, the full retention stack — lives in Document Repository (feature). This page is the outcome; that page is the vault.
  • The lease document + lifecycle (e-stamp, renewal, deposit, escalation) — lives in Tenant & Lease Management.
  • Financial-record retention + P&L/TDS/GST — lives in Accounting & Finance.
  • AMC visit scheduling + vendor work orders — the maintenance side of an AMC — lives in Maintenance & Facility Operations. This page tracks the AMC's document validity, not the visit calendar.
Three compliance realities in Indian buildings

The same compliance layer, three kinds of owner.

The document set is the same; who's responsible and what's at stake shifts with the building.

Cooperative society / RWA

A volunteer committee, rotating

An honorary committee that changes every year or two needs the compliance record to outlive its members. Society-owned storage plus 30+7-day alerts mean a Fire NOC or insurance renewal doesn't fall through the gap of a handover.

Builder at handover

Passing a project to its RWA

A builder assembles the RERA, OC, NOC and structural-drawing handover set in one society-owned place, so the incoming committee inherits a complete, current compliance record instead of a partial pile — and the same tracking keeps it current afterwards.

Landlord / facility manager

Several buildings, one calendar

A landlord or facility manager across buildings keeps every building's statutory documents on one expiry calendar, so no single property's Fire NOC or lift certificate is the one that quietly lapses while attention is elsewhere.

From the field

Dwarka, New Delhi · cooperative group housing society · 168 flats, 4 blocks.

"When I took over as Honorary Secretary, the previous committee handed me twenty-six years of our society's papers in seven cardboard boxes. I spent a weekend scanning them in. The software did something I didn't expect — as the documents went in, it read the dates and started telling me what was wrong. The one that made my blood run cold was our building insurance: fourteen days from lapsing, and I'd had no idea, because it was just a paper in a box. On an uninsured building, one accident and the society would have been looking at forty-seven lakh rupees of exposure. It also found twelve AMC contracts that had quietly expired. Now everything sits in the society's own account, not my personal Gmail, so when I hand over to the next Secretary it all stays put. I want to be clear it's the catching-before-it-lapses that matters to me — the detailed vault settings are their own thing; for us this is about never being caught out again."
Mr. Pankaj Khurana Hon. Secretary · Hari Kunj Cooperative Group Housing Society Ltd. · 168 flats / 4 blocks · Dwarka Sector-13, New Delhi-110078
26-year weekend digitisation · ₹47 lakh insurance lapse caught at upload · 12 expired AMCs auto-discovered · 11 compliance-doc types now on 30+7-day alerts
Quick answers

Building compliance, asked and answered.

What every RWA office bearer, society secretary and builder asks before they trust their compliance to software.

What does building document & compliance management do?
It makes sure a society or building's statutory compliance documents are never found to have lapsed after the fact. It tracks the eleven compliance-document types a building has to keep current — OC, Fire NOC, structural audit, lift safety, AMCs, building insurance, property tax, bye-laws, lease renewals, AGM minutes and Form 7/12 — and warns the office bearers 30 and 7 days before any one of them expires. This is the compliance-outcome layer; the underlying document-vault mechanism (role-based access, folders, audit log, retention stack) is the separate document-repository feature.
How is this different from the document repository feature?
They are the outcome and the mechanism. The document-repository feature is the vault itself — the four-tier role-based access matrix, the six folder categories, the §65B audit-log internals, version control, watermarking, and the full statutory record-retention stack. This solution page is the compliance outcome a society actually buys: the eleven document types kept current, the lapse caught before it bites, the society-owned positioning, the e-sign validity. If you want to know how the vault works, read the feature; if you want to stop a Fire NOC lapsing, this is the page.
Which compliance documents does it track?
Eleven types, each with its own validity clock: Occupancy Certificate (permanent), Fire NOC (one to three years), structural audit (five years for buildings over fifteen years old), lift safety certificate (annual), AMC contracts, building insurance, property tax receipts, versioned bye-laws, lease renewals, AGM minutes (permanent), and Form 7/12. The point of naming them individually is that they do not share an expiry rhythm — treating them as one undifferentiated pile of paper is exactly how a Fire NOC quietly lapses.
How does the expiry alert work?
It is a twin-tier cadence: a first alert 30 days before a document expires, and a second at 7 days, sent to the responsible office bearers. Thirty days gives time to start a renewal — to file for a Fire NOC or pay an insurance premium — and the seven-day alert is the safety net for anything that slipped. The aim is that a lapse is caught while it is still a renewal task, not after it has become an incident, a refused insurance claim, or a compliance notice.
Why does it matter that the documents are society-owned?
Because in too many societies the compliance records live in the Honorary Secretary's personal email or a drawer, and when the committee changes, the records effectively leave with them. A society-owned store means the documents belong to the society as an entity — a committee handover transfers control without losing a single file. The positioning is deliberately not "replace your Google Drive"; it is "stop running the RWA's statutory compliance out of one volunteer's personal Gmail."
Is the e-signing legally valid in India?
Yes. E-signing uses §3A of the IT Act 2000 — either Aadhaar eSign through a licensed provider (NeSL, Protean or NSDL) or a Class 2/3 Digital Signature Certificate from a CCA-licensed certifying authority. That gives a signed document the same legal standing as a wet-ink signature for the purposes the Act recognises, so renewals, approvals and resolutions do not stall waiting for committee members to be physically present with a pen.
How is this different from lease management and accounting?
Three different jobs that all touch "documents." This page owns building-compliance documents — the OC, Fire NOC, structural audit, bye-laws, the statutory paper a building must keep current. The tenant-lease-management solution owns the lease document and its lifecycle (e-stamp, renewal, deposit, escalation). The accounting-finance-management solution owns financial records and their tax retention. Keeping them on separate pages stops "compliance," "lease," and "accounting" from being treated as one blurry category.
Does it help a builder hand over a project?
Yes. A builder handing over to an RWA or society can assemble the handover document set — RERA registration, Occupancy Certificate, the various NOCs, structural drawings, and environment clearance — in one society-owned place, so the incoming committee inherits a complete, current compliance record rather than a partial pile. From there the same expiry tracking keeps those documents current under the society's ownership.
Who in the committee can see and edit the documents?
Access is role-based, but the detailed mechanism — the four-tier matrix of who can view, download or edit which folder, the audit log of every action, and watermarking — is part of the underlying document-repository feature, which this solution sits on top of. At the outcome level, what matters is that the Treasurer, Secretary and unit owners each see what they should and the record is tamper-evident. For exactly how the access tiers are configured, the document-repository feature page is the reference.

Stop finding the lapse during the incident.
Catch it 30 days out.

We'll show you the 11 compliance-document types on one expiry calendar, the 30+7-day twin-tier alerts, §3A e-sign, and the society-owned handover — in a demo on your building's actual documents.

Book the Compliance Demo →