Writing RERA-Safe Property Listings: AI-Drafted Copy That Doesn't Get You Fined

Why listing copy is the product, not the wrapper

A property listing on 99acres, MagicBricks, Housing, or a brokerage's own site is a sales asset disguised as a description. Buyers read three listings side-by-side before they call. The listing whose copy answers their unspoken question — 'will this place fit my family?' — gets the call. The listing whose copy reads like a translated spec sheet does not. That is true of every listing format in the world, but it is doubly true in India because the same property gets re-listed by three brokers and the difference in copy is the only differentiator the buyer sees.

The temptation, once you accept this, is to write listings as marketing copy. The compliance team then catches you the next quarter when a RERA inspector points out that the listing left out the project registration number, or implied a possession date that does not match the disclosed one, or showed an amenity that the developer never committed to. The fix is not 'write more carefully'. The fix is a structured copy workflow that prevents the mistake from being possible in the first place.

The anatomy of a RERA-safe disclaimer

Every state authority has a slightly different format for what a property listing must disclose. The common floor, across MahaRERA, K-RERA, TG-RERA, and most others, is six elements that must appear together in any communication that markets the property:

• Project RERA registration number, in full (P51800000001, not P518…)
• State authority short code (MahaRERA, K-RERA, TG-RERA)
• Carpet area in square feet — RERA-disclosed, not super-built
• Possession date as disclosed in the RERA portal
• Developer's RERA registration number, separate from the project's
• Public URL of the RERA project page — link, not screenshot

AI-assisted first drafts: what to keep and what to throw away

A first draft from a language model is roughly 60% usable for an Indian property listing. The 60% you keep: the headline angle, the rhythm of the amenity description, the flow from neighbourhood to building to apartment. The 40% you throw away: any number the model invented (school distance, metro distance, builder track record), any amenity it inferred without being told, and any tone that sounds like 'luxury living redefined'. The discipline is not avoiding the AI draft — it is editing the AI draft with a structured checklist instead of a vibe check.

Carpet area vs super-built: never let the AI confuse them

The single most common AI-drafting error in Indian real-estate copy is the silent swap between carpet area and super-built-up area. The model has read a billion listings on the open web, most of which used the terms loosely, and it will happily generate '3 BHK with 1,450 sq ft of space' when the carpet is actually 1,050 and the super-built is 1,450. The result is a listing that a buyer reads as one thing and the RERA portal says is another. The fix is to feed the model both numbers, prompt it to use only the carpet, and check the draft against the source two-number record. Listing systems that do not separate the two numbers as required fields are forcing this error into existence.

The two-person review loop that catches every fine risk

Brokerages that have stopped getting RERA notices share one workflow detail: every listing copy passes through two people before it goes live. The first is the listing coordinator (who knows the property), and the second is the compliance reviewer (who knows the rules). The AI does the heavy lifting on draft generation; the two-person review handles approval. Brokerages that try to skip either reviewer eventually find themselves explaining to an inspector why their Instagram caption claimed a clubhouse the developer never disclosed.

An AI-drafted listing without a RERA disclosure block is a press release, not a listing. Always check the block first, the copy second.

Compliance review notes, MahaRERA brokerage panel, 2024