RERA-Compliant Launch Event Marketing Checklist

Seven days out, and the invites aren't cleared yet

The launch is in a week. The agency has sent over the hoarding artwork, a WhatsApp broadcast draft for the channel-partner network, and three influencer-reel scripts for the sales-gallery opening. The founder is proud of the creative — it's punchy, it drives urgency, it names a launch price. But sitting in the inbox is a nagging question nobody on the marketing side has definitively answered: does every piece of this actually carry what RERA requires, and is the project even cleared to solicit bookings at this event?

This is the exact moment a mid-size developer's launch either becomes a clean, high-conversion event or a compliance headache that surfaces weeks later as a state RERA notice. The good news is that RERA-compliant launch marketing isn't complicated once it's reduced to a checklist — the risk almost always comes from treating disclosure as an afterthought bolted onto creative that was designed without it in mind.

This is that checklist: what has to be true before the invites go out, what every piece of launch collateral needs to carry, and where state rules diverge enough that "confirm on your state RERA portal" has to be the standing instruction to your agency.

What RERA Section 3 actually requires before a launch

Section 3 of the Real Estate (Regulation and Development) Act, 2016 is unambiguous on one point: a promoter cannot advertise, market, book, sell, offer for sale, or invite persons to purchase a plot, apartment, or building in any real estate project without first registering that project with the state RERA authority. This is the single most consequential rule for any launch event — it isn't a disclosure requirement layered onto an otherwise-fine event; it's a gate that determines whether the event can solicit bookings at all.

Beyond the registration gate, once a project is registered, ongoing advertising rules require that:

• Every advertisement and marketing piece prominently displays the project's RERA registration number.
• The state RERA authority's website URL appears alongside the registration number, so a prospect can independently verify the project's registered status.
• The advertised facts (unit sizes stated as carpet area, amenities, completion date) match what's on file with the authority — not an aspirational or informal version.

Exact placement norms for the registration number and website URL — font size, position on the creative, whether it must appear on every frame of a video reel or just at the closing card — differ by state authority and are worth confirming directly against MahaRERA's, Karnataka RERA's, or UP-RERA's current advertising guidelines before your agency finalises artwork, since these have been refined over time in more than one state.

Step-by-step: confirm the registration gate before anything else

1. Verify the RERA registration certificate is in hand, not "in process." A launch event cannot solicit bookings or EOIs for a project that is registered-pending or unregistered — this applies even to soft, informal expressions of interest collected at a tele-launch.
2. Cross-check the registration number appearing on every creative against the actual certificate — a stale number carried over from a previous phase or project is a surprisingly common, avoidable error in multi-phase developments.
3. Confirm the registered completion date matches what the event will state. If the launch event's messaging implies a possession timeline, it has to be the RERA-registered date, not an internal target.
4. Lock the base specification and carpet-area figures that will appear in launch collateral against the specification schedule filed with the authority — this is the same discipline covered for show flats and sample units, and it applies equally to launch-event materials.
5. Set up the project record once, centrally. Use your project profile setup to capture the RERA number, registered completion date, and specification details in one place, so every piece of launch collateral — hoarding, invite, reel, WhatsApp message — pulls from the same source rather than being manually re-typed by the agency for each format.
6. Brief the agency in writing that no creative goes to print or publish without the registration number, website URL, and current registered facts checked against the project profile.
7. Run a 72-hour pre-event audit (see the mini scenario below) across every collateral type before the event goes live.

Launch collateral checklist: disclosures and common gaps

State-by-state disclosure differences to confirm before printing

• Maharashtra (MahaRERA): Has issued detailed, specific advertising guidelines on registration-number and website-URL placement across print, digital, and hoarding formats — among the more prescriptive state frameworks, so Mumbai and Pune launch creative should be checked directly against the current MahaRERA advertising circular.
• Karnataka RERA: Applies the same core Section 3 registration gate; Bengaluru's high volume of "expression of interest" pre-launch tele-marketing makes the registration-confirmation step especially important, since EOI campaigns can start informally well before a physical launch event.
• UP-RERA (NCR): Given the region's well-documented builder-buyer trust history, UP-RERA and Haryana RERA scrutiny of launch advertising in NCR townships tends to be active; disclosure completeness at launch is one of the more visible early signals buyers and RWAs in the region look for.

The instruction for a multi-city developer's marketing team should be blunt and repeatable: do not assume a template that cleared review in one state clears automatically in another — confirm placement norms on the specific state RERA portal, as of the launch date.

A mini scenario: fixing the invite 72 hours before doors open

A Pune-based developer's marketing head runs a pre-launch audit three days before a tower launch event and finds:

• The email invite carries the RERA number in 8-point grey text at the very bottom — technically present, practically invisible.
• Two of the three influencer-reel scripts never mention the registration number on-screen, only in the caption.
• A channel partner's own WhatsApp broadcast, drafted independently, omits the registration number entirely and states a completion date one quarter earlier than what's registered.

The team pulls all three pieces back within 48 hours: the email is redesigned with the registration number and RERA website URL at a legible size near the top, the reel scripts are revised to display the disclosure card at both the start and end of each video, and the channel-partner broadcast is replaced with a centrally-approved version pulled directly from the confirmed project profile in the builder dashboard. The launch proceeds on schedule, with every consumer-facing piece — regardless of who produced it — carrying consistent, accurate disclosure.

Channel-partner and influencer compliance at the event

A launch event's exposure isn't limited to what the developer's own marketing team produces. Two categories deserve explicit attention:

• Channel-partner (broker) agents working the event floor must themselves be RERA-registered as real estate agents, and any collateral they distribute — flyers, business cards with project details, their own WhatsApp forwards — inherits the same disclosure obligation as the developer's own materials. A developer cannot outsource the compliance gap to an independent partner's booth.
• Influencers and content creators invited to cover the launch should be briefed with the same disclosure requirements as any other advertisement — a sponsored reel promoting the project is, functionally, an advertisement under the Act's broad definition, and needs the registration number and website URL visible, not buried in a caption.

Capturing consented leads at the event — rather than reselling or bulk-purchasing contact lists — also ties into the DPDP Act 2023 and its 2025 Rules, which (per Deloitte India's coverage of the DPDP Rules 2025) require consent before third-party data sharing and carry penalties that can run into hundreds of crores for non-compliance. Using /builder/leads to capture launch-event interest directly, with consent built into the capture flow, sidesteps both the RERA disclosure question on borrowed lists and the separate data-privacy exposure.

Pro tips

• Build the disclosure block into the creative template itself, not as a late add-on — a template with a fixed, non-removable registration-number placement is harder for an agency or partner to accidentally drop.
• Give every stakeholder the same source data. Pull the registration number, completion date, and specification facts from your project profile once, and share that exact text block with the agency, channel partners, and influencers rather than letting each party re-type it.
• Audit collateral by format, not just by piece. A single approved static ad doesn't guarantee the video-reel cutdown or the WhatsApp-forward version carries the same disclosure.
• Treat the 72-hour pre-event window as mandatory, not optional — it's the last checkpoint before creative is irreversibly in market.
• Log what launched, when, and where — a simple record of which creative versions ran on which channels is useful evidence if a later question arises about what was actually disclosed.

Common mistakes to avoid

• Soliciting EOIs before registration is confirmed. Even informal, non-binding interest capture at a pre-registration stage can fall foul of Section 3's plain language.
• Assuming a partner's registration covers the project's disclosure obligation. Channel-partner agent registration and project-level advertising disclosure are two separate requirements.
• Letting influencer content skip the disclosure block. A visually clean reel without the registration number on-screen is still an advertisement missing a required disclosure.
• Using stale project data on new creative. Reused templates from an earlier phase or project are a common source of mismatched registration numbers and completion dates.
• Treating the pre-event audit as optional under launch-week time pressure. This is precisely the point where gaps get waved through.

Integrating this into DrawMagic

DrawMagic presents project information; it does not file RERA registrations, review your creative for legal sufficiency, or certify that a launch event is compliant — that responsibility sits with the developer, their legal counsel, and the state RERA authority. What the platform supports is keeping the underlying facts consistent and captured once:

• /builder/projects/new — set up the project profile so the RERA number, registered completion date, and specification facts are captured once and reused across every piece of launch collateral, rather than re-entered by the agency for each format.
• /builder/leads — capture consented launch-event leads directly, aligned with DPDP expectations, instead of relying on resold or bulk-purchased contact lists.
• /builders — the broader builder-portal overview, for developers who want a structured project profile feeding every downstream ad from one disclosed set of facts.

For developers running multiple launches across a year, the underlying /pricing plans are worth a look if project-profile management is becoming a recurring, multi-person workflow rather than a one-time setup.

Key takeaways

• A launch event cannot solicit bookings or EOIs — even informally — before the project's RERA registration is confirmed; this is the single non-negotiable gate under Section 3.
• Every piece of launch collateral (invite, hoarding, reel, WhatsApp broadcast, sales-gallery signage) must carry the RERA registration number and the state RERA website URL, in a legible, prominent placement.
• Placement norms differ by state authority — confirm MahaRERA, Karnataka RERA, and UP-RERA's current guidelines directly rather than assuming a template clears everywhere.
• Channel-partner agents and their booth collateral inherit the same disclosure obligation as the developer's own materials.
• Sponsored influencer content promoting a launch is functionally an advertisement and needs the same registration-number disclosure, visible on-screen.
• Run a formal pre-event audit — ideally 72 hours out — across every collateral format before the launch goes live.
• Capture launch-event leads with consent, aligned with DPDP Act 2023 and its 2025 Rules, rather than relying on resold contact lists.
• Centralise the RERA number, registered completion date, and specification facts in one project profile so every downstream ad pulls from the same source.
• DrawMagic presents project information only — it does not file registrations or certify compliance; confirm current requirements with your state RERA authority and legal counsel.

FAQ

Can we collect "expressions of interest" before RERA registration is confirmed, as long as we don't call it a booking? This is exactly the grey area Section 3 is written to close — the Act's language covers inviting persons to purchase, not just formal bookings. Treat any interest-capture mechanism at a pre-registration event as high risk and confirm with legal counsel before running it.

Does the RERA registration number need to appear on every frame of a video reel, or just once? Placement specifics vary by state authority guidance; the safer practice is a visible disclosure card at both the start and end of the reel, checked against your specific state RERA's current advertising norms.

What penalties apply for launch advertising that omits required disclosures? RERA advertising violations can attract penalties that scale with the estimated project cost, alongside potential directions from the authority — the specific quantum and process depend on the state authority and case facts; this is not a fixed, universal figure, and any exposure should be assessed with a licensed professional.

Ready to run your next launch off one disclosed, consistent project profile? Set it up at /builders, starting with your registered completion date and specification in /builder/projects/new.