RERA Rules for Comparative and Competitor Property Ads

The "We're Better Than [Rival Project]" Ad That Invites a Complaint

A mid-sized Whitefield developer once briefed its agency with a single line: "Just show we're better than the project next door." The resulting hoarding read something like — "Better connectivity. Bigger clubhouse. Faster possession than [Rival Project Name]." It went up on a Friday. By Tuesday, the rival's legal team had sent a cease-and-desist, a complaint had landed with the Advertising Standards Council of India (ASCI), and the local RERA authority had asked for the sanctioned plan and possession timeline that supposedly proved the "faster possession" claim. None of it existed in writing. The campaign was pulled in nine days, the printing cost was sunk, and the developer's brand — the one thing the ad was supposed to build — took the actual hit.

This is the recurring pattern in comparative real-estate advertising in India: the marketing instinct to compare is completely reasonable — buyers do cross-shop competing projects in the same micro-market — but the execution slides from "comparison" into "disparagement" the moment a specific rival is named without every claim being independently substantiable. RERA doesn't regulate comparative advertising by name, but it does prohibit "misleading" and false representations in a project's marketing, and ASCI's comparative-advertising guidelines fill the rest of the gap for how far a developer can go when naming or clearly identifying a competitor. Understanding where that line sits — and building comparisons that survive scrutiny — is the difference between a campaign that builds credibility and one that ends in a legal notice.

This guide walks developers and marketing leads through what's safe, what's risky, and how to build a comparison campaign entirely from your own disclosed, sourced facts rather than claims about someone else's project.

RERA + ASCI: The Two-Layer Framework for Comparative Claims in India

India doesn't have a single "comparative advertising law" for real estate. Instead, two frameworks stack on top of each other, and a compliant ad has to satisfy both.

Layer 1 — RERA's misleading-advertisement provisions. Under the Real Estate (Regulation and Development) Act, a promoter's advertisements and prospectus must not contain any information that is "incorrect, false or misleading," and any statement made in an advertisement about the project (specifications, amenities, possession date, area) is treated as binding on the promoter for that specific project. RERA's focus is on protecting the buyer from being misled about the promoter's own project — so if a comparative claim rests on an inaccurate description of your own project's attributes, that's squarely a RERA compliance failure independent of any dispute with a rival.

Layer 2 — ASCI's comparative-advertising code. ASCI's guidelines (which self-regulate the advertising industry across sectors, real estate included) permit comparative advertising in principle, but set conditions: the basis of comparison must be on facts that are capable of substantiation; the comparison must not be misleading; it must not unfairly denigrate or attack the competitor's product, trade, or reputation; and if a specific competitor is identifiable — named directly or through strong visual/contextual cues like "the project next door" or a recognizable logo silhouette — the bar for substantiation rises sharply. According to the IBEF Real Estate Industry in India report (Feb 2026), India's real estate sector is on a trajectory toward a US$1 trillion market by 2030, and that scale is precisely why competitive intensity — and complaint volume — around marketing claims keeps rising in fast-growing micro-markets.

The practical takeaway: a comparison ad isn't automatically illegal. It becomes a problem when (a) the comparison can't be substantiated with evidence you can produce on demand, (b) it disparages rather than informs, or (c) it misstates facts about your own project to make the comparison look better than reality.

Step-by-Step: Building a Defensible Comparison From Your Own Disclosed Facts

The safest and most durable comparative strategy is one that never actually needs to name a rival at all — it just presents your project's facts so clearly and so verifiably that the comparison writes itself in the buyer's head.

1. Start with your RERA registration record, not your marketing deck. Your project's sanctioned carpet area, approved amenities, RERA registration number, and promised possession date are already a matter of public record. Build your comparative narrative ("more usable space," "faster timeline") only from what's in that filing — never from aspirational specifications that haven't been sanctioned yet.

2. Convert vague superiority claims into measurable, sourced facts. "Bigger clubhouse" becomes "12,000 sq ft clubhouse (RERA-sanctioned plan, [project] registration no. XX/XXX)." A number with a source survives an ASCI inquiry; an adjective does not.

3. If you must reference a category or micro-market rather than a named project, do that instead. "Among the largest clubhouses in [micro-market]" is a defensible category claim if you can show the comparison set and your basis for it. Naming one specific rival and claiming superiority over that one project raises the substantiation bar to project-specific proof.

4. Pre-clear every distance, timeline, and amenity claim with a dated source. If you reference a metro station, an upcoming expressway, or a school within X minutes, keep the source (Google Maps screenshot with date, official infrastructure authority notification, RERA-filed possession schedule) in a claims file before the ad runs, not after a notice arrives.

5. Run the ad past a "would this read as an attack?" test. Comparative facts inform; comparative adjectives ("shoddy," "cramped," "delayed developer") attack. If your copy uses value-laden language about the rival rather than neutral facts about yourself, redraft it.

6. Keep a claims-substantiation file for every campaign, updated with as-of dates. This is the single most useful habit for surviving both a RERA inquiry and an ASCI complaint — you're not scrambling to find proof after the fact, you already have it filed.

Claim Type vs Safety vs Required Substantiation

Where Micro-Market Rivalries Get Developers Into Trouble

Comparative ads cluster in specific, fast-growing corridors precisely because that's where competing projects sit close enough for buyers to cross-shop them directly — think competing towers in Whitefield or Sarjapur Road in Bengaluru, rival phases along Hinjewadi in Pune, or adjacent launches in Gurugram's Dwarka Expressway belt. In these corridors, sales teams often brief marketing with informal comparisons pulled from site-visit conversations ("buyers keep asking why theirs is priced higher") — and that informal framing is exactly what leaks into hoardings and social ads without going through a substantiation check.

The fix isn't to avoid competitive positioning in these corridors — it's structurally unavoidable when projects are metres apart — but to route every comparative instinct through the "does this rest on our own disclosed, RERA-backed facts" filter before it becomes a public claim. A developer with an accurate, complete project record on a platform like DrawMagic's builder portal has a ready reference point for exactly this kind of fact-first comparison, because the underlying specifications are already structured and sourced rather than living in a marketing deck that drifts from the sanctioned plan over time.

Real-World Mini Scenario: A Bengaluru Developer's Connectivity Comparison, Redone Compliantly

Consider a project near the Outer Ring Road in Bengaluru whose original ad copy read: "Closer to the IT corridor than [Rival Project] — save 20 minutes daily on your commute." The claim named a specific competitor, asserted a specific time saving without a stated methodology, and implied the developer had measured the rival's actual commute times — which it hadn't.

The compliant rewrite: "X minutes from [named IT park] via [named route], based on Google Maps drive-time estimates as of [date]." This version drops the named rival entirely, states the developer's own project's connectivity as a verifiable fact with a source and date, and lets the buyer draw their own comparison against whatever else they're considering. It's arguably more persuasive, too — buyers increasingly discount vague superiority claims and respond better to specific, sourced numbers they can verify themselves.

Disparagement vs Fair Comparison — The Line RERA and Consumer Forums Draw

Indian consumer-protection and advertising jurisprudence (developed largely through ASCI rulings and consumer-court precedent rather than RERA itself, since RERA's core mandate is disclosure accuracy about the promoter's own project) draws the disparagement line at roughly this point: you may compare on objective, verifiable attributes of your own product; you may not denigrate, mock, or make unsubstantiated negative claims about a competitor's product, business practices, or reputation. A claim like "unlike some developers, we deliver on time" edges toward disparagement if it's clearly aimed at an identifiable rival with a known delivery history — even without naming them.

RERA disparagement-adjacent complaints in practice tend to arise from three patterns: (1) a named or clearly identifiable rival's project is criticized without evidence, (2) a developer's own claims about superiority turn out to rest on specifications that were never actually sanctioned, and (3) a testimonial or "comparison" implies the rival's buyers are dissatisfied without any factual basis. Any of these can trigger both an ASCI complaint (industry self-regulation) and a RERA inquiry (regulatory, tied to the misleading-advertisement provisions) simultaneously, since they're independent tracks that a single ad can trip at once.

Pro Tips for Compliant Comparative Marketing

• Build your claims file before the campaign, not after the complaint. Every number in the ad should map to a document you can produce within 48 hours if asked.
• Default to category comparisons over named-rival comparisons. "Among the best-connected projects in the corridor" survives scrutiny far more easily than "better connected than [X]."
• Train your sales and social-media teams, not just your ad agency. Most disparagement complaints originate from an off-the-cuff sales pitch or a social comment reply, not the formal print campaign.
• Route infrastructure claims (metro, expressway, IT park) through an "operational vs proposed" check every single time — a claim that was true when drafted can go stale fast if the underlying infrastructure timeline shifts.
• Keep tone factual even when the comparison favors you strongly. Confident, sourced facts read as credible; adjectives read as marketing spin and invite more scrutiny, not less.

Common Mistakes to Avoid

• Naming a specific competitor project and asserting a subjective superiority claim ("better quality," "nicer location") with no measurable basis.
• Using a rival's sales shortfall, delay, or legal trouble as an implicit or explicit selling point.
• Letting a claim about your own project (amenity size, possession date) drift ahead of what's actually in your RERA filing.
• Treating a verbal sales-team comparison as low-risk just because it isn't in print — regulators and rivals both increasingly monitor site-visit scripts and WhatsApp marketing too.
• Assuming "everyone in this micro-market does it" is a defence — ASCI and RERA both evaluate each complaint on its own facts, not on industry norms.

Where DrawMagic Fits Into a Fact-First Comparative Strategy

A comparison campaign is only as strong as the underlying project record it draws from. On DrawMagic's builder portal, developers maintain their project's RERA number, carpet area, sanctioned amenities, and connectivity details as structured, source-backed data through project setup — the same data set your marketing team should be pulling comparative claims from. Presenting that record accurately on your project listing gives your sales and marketing teams a single source of truth, so a comparative claim in an ad and the claim in your RERA filing never drift apart. If a compliance question comes up mid-campaign, DrawMagic's help center is a useful first stop for clarifying what documentation to have ready before a claim goes live.

For developers weighing how deep to invest in a structured project record versus ad-hoc marketing decks, it's worth noting that as project pipelines scale, the cost of a single retracted campaign — reprinting, legal correspondence, brand damage — usually outweighs the modest ongoing effort of keeping one accurate, portal-hosted project record that both sales and marketing draw from.

Key Takeaways

• RERA prohibits misleading claims about a promoter's own project; ASCI's comparative-advertising guidelines govern how far you can go when comparing against an identifiable rival — a compliant ad satisfies both.
• The safest comparative strategy avoids naming a specific rival and instead builds claims entirely from your own RERA-sanctioned, disclosed facts.
• Category comparisons ("among the best-connected in the corridor") carry far lower risk than named-rival comparisons ("better than [X]").
• Every distance, timeline, or amenity claim needs a dated, producible source before the ad runs — not after a complaint lands.
• Disparagement — denigrating a competitor's product or reputation without evidence — is the line that turns a fair comparison into a legal or regulatory problem.
• Sales-team scripts and social-media replies carry the same compliance risk as formal print or digital campaigns.
• A structured, source-backed project record (RERA number, carpet area, amenities, connectivity) is the foundation every defensible comparative claim should be built from.
• Keep a claims-substantiation file per campaign so you can respond to a RERA inquiry or ASCI complaint within days, not weeks.

FAQ

Can I compare my project to "other projects in the area" without naming anyone? Yes — category-level comparisons based on your own disclosed, sourced facts carry much lower risk than naming a specific competitor, provided the comparison set and basis are reasonably defined and not misleading.

What happens if a rival files an ASCI complaint against my ad? ASCI typically asks the advertiser to substantiate the claim within a set timeframe; if the claim can't be substantiated or is found misleading or disparaging, ASCI can recommend the ad be modified or withdrawn, and a parallel RERA inquiry can follow if the ad also misstates your own project's specifications.

Is it ever acceptable to name a competitor directly in an ad? It's legally possible but high-risk in the Indian real-estate context, since any named comparison requires solid, producible evidence for every claim made about the rival's project — evidence developers rarely have legitimate access to. Most compliant campaigns avoid naming a rival altogether.

Does keeping accurate records on a platform reduce my compliance risk? It doesn't eliminate the need for legal review of specific ad copy, but a single accurate, structured project record used consistently across your builder profile and marketing materials significantly reduces the risk of a claim drifting from what's actually sanctioned.