RERA Rules for Location and Connectivity Claims in Ads

The "5 Minutes to Metro" That's Really 25

A hoarding along Hyderabad's outer growth corridor once promised "5 minutes to the nearest metro station." A prospective buyer who visited the site during evening traffic clocked the actual drive at 25 minutes — and that was before accounting for the fact that the metro line referenced in the ad wasn't operational yet; it was a planned extension still under approval. The buyer filed a complaint. The developer's defense — that "5 minutes" referred to a straight-line, as-the-crow-flies distance rather than an actual travel time — didn't satisfy the regulator, because nothing in the ad disclosed that the "5 minutes" wasn't a real commute estimate.

This is the most common failure pattern in location and connectivity advertising for Indian real estate: developers advertise proximity using whichever measurement makes the number look best — straight-line distance instead of road distance, off-peak drive time instead of realistic commute time, or a planned/proposed piece of infrastructure presented as if it already exists. Buyers, understandably, read "5 minutes to metro" as "my daily commute will take about 5 minutes" — and when reality diverges sharply from that expectation, the gap is exactly the kind of misleading representation RERA and ASCI both exist to prevent.

What RERA and ASCI Expect From Location and Distance Claims

RERA requires that a promoter's advertisements not contain information that's incorrect, false, or misleading about the project — and a location or connectivity claim is squarely part of "the project" as buyers experience it, even though it technically describes surrounding infrastructure rather than the building itself. If a buyer's purchase decision was influenced by a distance or connectivity claim that turns out to be materially inaccurate, that's a live basis for a complaint to the state RERA authority.

ASCI's advertising code layers on top of this with a general substantiation principle: any factual claim in an advertisement — including a distance, travel time, or the existence of nearby infrastructure — must be capable of being substantiated with evidence at the time the claim is made. For location claims specifically, this typically means:

• Disclosing the measurement basis — straight-line distance versus road distance versus estimated drive time are three different numbers, and an ad should be clear about which one is being cited.
• Disclosing infrastructure status — a metro line, expressway, or IT park that is "proposed," "under construction," or "planned" must be clearly labelled as such; presenting it as operational or complete when it isn't is a core misleading-claim risk.
• Using a dated, verifiable source — a mapping tool screenshot, a government infrastructure authority's official timeline, or a municipal planning document, kept on file with the date it was captured.

According to the IBEF Real Estate Industry in India report (Feb 2026), India's real estate sector continues to expand rapidly toward a projected US$1 trillion market by 2030, and much of that growth is concentrated in peripheral growth corridors precisely where infrastructure is still catching up to development — which is exactly why location and connectivity claims in these corridors draw disproportionate regulatory and buyer scrutiny compared to established, fully-serviced neighborhoods.

Step-by-Step: Substantiating a Connectivity Claim Before It Goes in an Ad

1. Identify the exact landmark and the exact measurement type before writing any copy. Decide upfront: is this straight-line distance, road distance, or drive time? Pick one, and state which one it is in the ad itself if there's any ambiguity risk.

2. Pull the measurement from a mapping tool and screenshot it with a visible date. A Google Maps or equivalent route screenshot, captured and dated, is the baseline evidence a developer should have on file for every distance claim before it's published.

3. Check whether the referenced infrastructure is operational, under construction, or merely proposed. For metro lines, expressways, or interchanges, check the relevant state infrastructure authority's official status update — never rely on a media report alone for construction-status claims, and never assume a sanctioned project is the same as an operational one.

4. If the infrastructure isn't operational yet, label it clearly as "proposed" or "under construction" with, where available, an official expected-completion timeframe — and avoid stating a completion date more precisely than the source itself commits to.

5. Re-measure travel-time claims at a realistic time of day, not the best-case scenario. If a claim is going to be based on drive time, using an off-peak 11 pm measurement to advertise a "10-minute commute" that's actually 30 minutes at 9 am is exactly the kind of gap that draws complaints.

6. File every claim's source and date alongside your project's marketing brief, so if a claim is questioned months later, you can show precisely what was known and verifiable at the time the ad ran.

Claim Type vs Required Substantiation vs As-Of/Proposed Disclosure

Metro, ORR, and Expressway Claims by City

Connectivity marketing patterns differ meaningfully across India's fastest-growing residential corridors, and each carries its own substantiation nuance:

• Bengaluru — Outer Ring Road (ORR) proximity and Namma Metro extension claims are extremely common in Whitefield, Sarjapur Road, and Hebbal-adjacent launches; several metro extensions remain phased over multi-year timelines, so "near the upcoming metro" claims need a clear phase and expected-operational-date disclosure sourced from the metro corporation.
• Hyderabad — claims referencing the Outer Ring Road, the airport corridor, and IT-corridor proximity (HITEC City, Financial District) are common in the western growth belt; airport-distance claims in particular should be checked against realistic peak-hour drive times rather than late-night best-case routes.
• Pune — Hinjewadi and the upcoming metro extensions toward the IT corridor are frequent reference points; given ongoing phased construction, "metro-connected" claims for projects near still-under-construction stations need explicit "under construction" labelling.
• Gurugram — Dwarka Expressway and NH-48 proximity claims are dense in this corridor precisely because so many competing projects sit along the same stretch; straight-line versus service-road driving distance differences here can be significant and should be disclosed.
• Chennai — IT corridor (OMR/ECR) and metro-extension proximity claims follow a similar pattern; monsoon-season drive-time variability is a genuine factor worth accounting for if travel-time claims are made.

In every one of these markets, the underlying discipline is the same: state what's operational as operational, state what's proposed as proposed, and always disclose the measurement basis for any distance or time figure.

Real-World Mini Scenario: A Hyderabad Developer Fixing an Airport-Distance Claim

A developer near Hyderabad's western growth corridor originally advertised "30 minutes to Rajiv Gandhi International Airport" based on a single off-peak measurement taken late at night. A buyer complaint pointed out that a realistic morning commute measured closer to 55–60 minutes. Rather than simply removing the claim, the developer's marketing team re-measured the route at three different times of day (early morning, midday, evening peak), averaged the peak-hour figures, and revised the ad to read: "Approx. 45–60 minutes to the airport depending on time of day (peak-hour drive-time estimate, [month/year])."

The revised claim is less flattering than the original — but it's defensible, transparent, and actually more persuasive to sophisticated buyers who've learned to distrust suspiciously optimistic commute claims in growth-corridor marketing. It also removed the developer's exposure to a repeat complaint, since the range and its basis are now explicitly disclosed rather than implied as a single best-case number.

Advertising Proposed vs Operational Infrastructure Honestly

The single highest-risk category in location marketing is presenting proposed or under-construction infrastructure as if it's already delivering value today. A metro line that has been announced, or even one with a sanctioned Detailed Project Report, is not the same as a metro line carrying passengers — and advertising copy needs to reflect that distinction plainly, not through fine print that contradicts a bold headline claim.

A workable standard: if a buyer reading only the headline claim (without reading any disclaimer text) would reasonably conclude the infrastructure already exists and is usable today, and it isn't, the ad has a misleading-claim problem regardless of what a smaller-print disclaimer says elsewhere. The safest practice is to build the "proposed" or "under construction" status directly into the primary claim itself — "upcoming metro station (under construction, expected [timeframe] per [authority])" — rather than relegating it to a footnote.

Pro Tips for Location and Connectivity Claims

• Standardize your measurement methodology across every ad in a campaign — mixing straight-line distance in one asset and drive-time in another for the same project invites confusion and inconsistency complaints.
• Re-verify infrastructure status every time you reuse an old ad asset — a "proposed" metro line's status can change (approved, under construction, delayed, operational) well before a reused campaign's next print run.
• Measure travel times at realistic hours, and disclose the basis rather than hiding it — buyers respect a transparent range more than they trust a suspiciously perfect single number.
• Keep a dated screenshot or official source for every distance and status claim in a single claims file per campaign, so a RERA or ASCI inquiry can be answered within days.
• When in doubt, understate rather than overstate — a conservative, disclosed estimate rarely draws a complaint; an optimistic, undisclosed one frequently does.

Common Mistakes to Avoid

• Advertising straight-line distance as if it were drive time without disclosing which measurement is being used.
• Presenting a proposed or under-construction metro line, expressway, or interchange as already operational.
• Using a single best-case, off-peak travel-time measurement instead of a realistic range across the day.
• Reusing an old connectivity claim in a new campaign without re-checking whether the underlying infrastructure's status has changed.
• Letting a claim about a landmark's proximity go unverified because "everyone knows it's nearby" — informal familiarity isn't a substantiation record.

Where DrawMagic Fits Into Fact-First Location Marketing

Location claims are only as strong as the record backing them. On DrawMagic's builder listings, developers can record a project's location attributes — distances, nearby landmarks, and connectivity notes — as structured, source-backed data rather than a marketing adjective, giving sales and marketing teams a single accurate reference point to draw claims from. Capturing this at project setup means the coordinates and nearby-landmark facts are established accurately from day one, before any ad copy gets written around them.

For developers building out a broader marketing presence from the builders portal, keeping location claims consistent with the underlying project record reduces both the compliance risk of a stray ad claim and the reputational cost of a buyer discovering a gap between the ad and reality on a site visit. DrawMagic's help center is a good resource for questions about documenting a location claim's source before a campaign goes live, and developers scaling across multiple projects may find a higher-tier pricing plan useful for keeping this discipline consistent project-to-project.

Key Takeaways

• RERA's misleading-advertisement standard applies fully to location and connectivity claims, not just claims about the building itself.
• Every distance or travel-time claim should disclose its measurement basis — straight-line distance, road distance, or drive time are three different numbers.
• Infrastructure that is proposed or under construction must be clearly labelled as such; presenting it as operational when it isn't is a core misleading-claim risk.
• Travel-time claims should be measured at realistic times of day, not a best-case off-peak scenario, and the estimate basis should be disclosed.
• Keep dated, sourced evidence (map screenshots, official infrastructure-authority timelines) on file for every location claim before an ad runs.
• Reused ad assets need their infrastructure-status claims re-verified each time, since a "proposed" project's status can change between campaigns.
• A transparent, slightly conservative claim ("45–60 minutes depending on time of day") is more defensible and often more persuasive than an optimistic, undisclosed single number.
• Structured, source-backed project location data reduces the risk of ad copy drifting away from the facts on the ground.

FAQ

Is it acceptable to advertise distance to a metro station that hasn't opened yet? Yes, as long as the ad clearly discloses that the metro line or station is proposed or under construction, along with an official expected timeframe where available — presenting it as already operational is the compliance risk, not mentioning it at all.

What's the difference between straight-line distance and the distance I should actually advertise? Straight-line ("as the crow flies") distance is almost always shorter than actual road distance or drive time, and advertising it without disclosure creates an expectation gap for buyers who assume the number reflects a real commute — always disclose which measurement type is being used.

How often should I re-check connectivity claims in an ongoing campaign? Re-verify infrastructure status and, ideally, travel-time estimates at least at the start of each new print or digital run of a reused campaign asset, since infrastructure timelines and traffic patterns can shift meaningfully over months.