RERA Rules for Agent and Broker Social Media Posts

The reel had 40,000 views. It also had a price the developer never approved.

A channel-partner manager at a mid-sized developer got a screenshot forwarded from a colleague: an Instagram Reel, shot by a broker who'd never signed a formal agreement with the project, walking through a still-under-construction tower with the caption "Starting ₹58L — book now, limited units!" The actual starting price on the registered price sheet was ₹68L. There was no RERA number in the post, no disclosure that the visuals were of an unfinished unit, and the broker's own RERA agent registration number was nowhere to be found. The reel wasn't malicious — the broker genuinely believed the older, pre-revision price was still current — but by the time the developer's marketing team saw it, it had already been reshared by two other local brokers chasing the same lead volume.

This is the reality of channel-partner marketing in Indian residential real estate today: a developer's project reputation is being shaped, in real time, by dozens or hundreds of individual agents posting on Instagram, YouTube Shorts and WhatsApp status — most of it created without the developer's review, using renders, price claims and possession timelines the agent may not have verified. Under RERA, this isn't just a brand-management headache; it's a compliance exposure, because inaccurate claims about a registered project can trigger scrutiny of the project itself, even when the developer didn't create or approve the specific post.

This guide is for the channel-partner or marketing manager who has to keep a large, motivated, loosely-affiliated network of agents posting content that helps sales without creating liability. It draws on the reality that IBEF's Real Estate Industry in India report (Feb 2026) describes as a sector heading toward a market that could be worth up to US$1 trillion by 2030 — growth that is, in no small part, being driven through exactly this kind of digital, agent-led distribution, which means the partner-post problem is only going to scale with the industry, not shrink.

What RERA requires of agents — and why it matters to you as the developer

RERA requires real estate agents to register with their state's RERA authority before facilitating the sale of a registered project. A registered agent is expected to disclose their own RERA registration number and the project's RERA number in their promotional material and transactions. When an unregistered person, or a registered agent who simply omits the RERA number, posts promotional content about your project, two separate compliance threads open up: the agent's own registration status (their problem, mostly), and the accuracy of claims made about your registered project (which lands on your desk, because your project's name and RERA number are what buyers associate the content with).

State RERA authorities have, at various points, issued notices to agents over unregistered brokering activity and misleading claims — MahaRERA in particular has a track record of action against non-compliant agents. The exact enforcement posture varies by state (MahaRERA, K-RERA, TG-RERA, UP-RERA, HRERA all administer this somewhat differently), so a specific claim about what any one state authority has done recently should be confirmed on that state's RERA portal rather than assumed to apply everywhere.

There's a second layer here that isn't RERA-specific: the Advertising Standards Council of India (ASCI) has guidelines on influencer and paid-partnership disclosure that increasingly get applied to real estate content — an agent posting a "paid promotion" reel without disclosing it as such, or presenting an AI-generated or heavily edited render as an actual, current photo of the site, sits in a gray zone that both RERA-style deceptive-advertising norms and ASCI's disclosure norms would flag.

Step-by-step: building an enforceable partner-post policy

1. Inventory who's actually posting about your project. Before writing a policy, search your project name and RERA number across Instagram, YouTube and any WhatsApp broadcast groups you have visibility into. Most developers are surprised by the volume of unofficial content already live.

2. Separate "approved creative" from "approved facts." A partner-post policy works best when it gives agents two things: a kit of pre-approved creative assets (renders, floor plans, price sheets) they can reshare as-is, and a short list of facts (current starting price, RERA number, possession timeline) they must use verbatim if they create their own content. Trying to control every creative choice an agent makes is unrealistic; controlling the facts they state is achievable.

3. Require the disclosure line, not just the RERA number. A minimum disclosure template — project RERA number, agent's own RERA registration number (where applicable), and a note that renders are representational — should be part of the kit, not left to each agent's judgment.

4. Set an update cadence for the facts sheet. Price and possession timelines change. If your facts sheet isn't updated the same day pricing changes internally, agents will keep quoting stale figures in good faith — the ₹58L-vs-₹68L example above is exactly this failure mode.

5. Give agents a compliant lead-routing path. Part of why agents post informally is that it's the fastest way for them to generate and claim a lead. If your lead pipeline can accept partner-sourced, consented leads with attribution, agents have less incentive to post unverified claims just to move fast — you're giving them a legitimate channel that's also trackable.

6. Set consequences and communicate them once, clearly. Most policies fail not because they're unreasonable but because they're never actually communicated to the full partner network, or because enforcement is inconsistent (one agent gets a warning, another with the same violation gets ignored).

Post type, required disclosure, and who's liable

Handling AI renders and edited visuals

AI-generated and heavily edited renders are now common in broker content — a partner might take a developer-supplied render and edit it further (adding furniture, changing lighting, exaggerating the view) to make it more shareable. The compliance risk here is specific: presenting an edited or AI-generated image as an actual, current photo of a unit or the site is the kind of claim regulators and consumer forums have treated as misleading, regardless of who created the edit.

The safe posture is a standing rule in your partner-post policy: all renders, whether developer-supplied or partner-created, must carry a visible "representational image" label, and no partner-created visual should be presented as an actual photograph of a completed or under-construction unit unless the developer has verified it as such. This is a low-cost rule to state and a genuinely hard one to enforce across a large partner network — which is exactly why the approved-creative-kit approach (giving partners something better to use than what they'd otherwise create) tends to work better than a prohibition alone.

Mini scenario: issuing an approved-creative kit to 30 partners

A developer selling a mid-rise residential project in a growing suburban micro-market had roughly 30 active channel partners generating leads, each posting independently. After a compliance review flagged inconsistent price claims across partner posts, the marketing team built a simple kit: five pre-approved video clips of the actual site (not renders), a one-page facts sheet with the current price, RERA number and possession date, and a short WhatsApp-distributed update whenever any of those facts changed.

Partners were told they could repost the kit content freely with attribution, or create their own content as long as it matched the facts sheet. Within a month, the volume of independently-created broker content with outdated pricing dropped noticeably — not because partners were forced to stop posting, but because reposting the approved kit was less work than creating new content from scratch, and it consistently outperformed self-made content in early engagement because it used real site footage.

Pro tips

1. Make the facts sheet a single shareable link, not a PDF that goes stale in someone's downloads folder — update the link's content, not its URL, whenever price or timeline changes.
2. Ask your top 5–10 producing partners for feedback on the kit before rolling it out network-wide — their buy-in shapes whether the rest of the network actually adopts it.
3. Review partner posts monthly, not just after a complaint — a light spot-check catches drift before it becomes a pattern.
4. Never ask a partner to remove content publicly in a way that looks punitive — a private, factual correction request preserves the relationship and avoids amplifying the original mistake.
5. Keep a dated archive of the facts sheet versions you distributed — if a partner posts an outdated price, you can show what was current and communicated at the time.

Common mistakes to avoid

• Assuming a verbal or informal understanding with partners counts as a "policy" — without a written, distributed reference, every partner interprets the rules differently.
• Letting the facts sheet lag behind actual pricing or timeline changes by even a few days during an active sales push.
• Treating all partner posts as equally risky — a reshared, unedited developer asset carries far less risk than an independently created claim.
• Responding to a non-compliant post only after it's already been widely reshared, instead of catching it in an early spot-check.
• Disparaging or publicly calling out a specific partner's mistake instead of correcting privately and updating the kit to prevent repeats.

Bringing this into your DrawMagic workflow

The core fix for partner-post drift is giving your network one place to pull current, accurate facts from — rather than relying on memory or a group-chat message from three weeks ago. Publishing your unit-level facts, current pricing and RERA disclosures through your listings gives partners a single, always-current source they can screenshot or link to instead of inventing figures. And when a partner's post does generate a genuine buyer inquiry, routing it through your leads pipeline turns an untracked DM or comment into a consented, attributable lead you can actually follow up on and measure — which also gives partners a reason to route leads properly instead of just posting and hoping.

Why one approved source of facts protects the brand

Every inconsistent partner post is a small trust cost — a buyer who sees three different starting prices for the same project across three different Reels starts to wonder which one, if any, to believe. A developer that can point every partner to the same current facts, hosted in the same place, removes the raw material for those inconsistencies before they happen. DrawMagic's builder portal is built to be that shared source — a place where your project's disclosed facts stay current and your channel-partner network has one thing to check before they hit post.

Key Takeaways

• Registered real estate agents are required to carry their own RERA registration number and the project's RERA number in promotional material — enforcement varies by state, so confirm current expectations with your state RERA authority.
• Inaccurate broker content about your registered project can create compliance exposure for the project even when the developer didn't create the post.
• A workable partner-post policy separates "approved creative" (reshareable as-is) from "approved facts" (must be used verbatim in any partner-created content).
• AI-generated and edited renders should always carry a "representational image" label and never be presented as an actual current photo of a unit or site.
• ASCI's paid-partnership and disclosure norms increasingly apply to real estate influencer/agent content alongside RERA considerations.
• Keeping a single, current facts sheet — updated the same day pricing or timelines change — prevents the most common source of partner-post errors: stale information repeated in good faith.
• Publishing disclosures through /builder/listings and routing partner-sourced inquiries through /builder/leads gives partners a legitimate, trackable alternative to informal posting.
• This guidance is informational; confirm agent-registration and disclosure requirements with your state RERA authority, ASCI guidelines and a licensed legal professional.

Frequently Asked Questions

Is the developer legally responsible for what an independent broker posts about the project? Liability generally depends on the specifics — whether the developer supplied or approved the content, whether the broker is a registered agent acting for the project, and what claim was made. Regardless of formal liability, inaccurate claims about a registered project tend to create reputational and inquiry-handling costs for the developer, which is why a proactive facts-sharing policy is worth the effort even absent a legal mandate.

Should we require every partner to sign a formal agreement before they can post about our project? Many developers do require a channel-partner agreement for lead attribution and commission purposes, and it's a reasonable place to also include a posting policy — but confirm the specific structure with your legal counsel, since requirements and enforceability vary by state and by the nature of the partner relationship.

How often should we update the facts sheet we give partners? Immediately when price, possession timeline or RERA registration details change — even a few days' lag is enough for outdated figures to circulate through the partner network and outlive the correction.

See how a consistent, disclosure-ready listing supports your whole partner network — start with the DrawMagic builder portal.