Checking for Encroachment on a Plot Remotely

Suresh, an engineer based in Riyadh, had shortlisted a plot on the outskirts of Bengaluru through a broker's photos and a video call. The seller was friendly, the price was fair, and the plot "looked" exactly like the boundary description in the sale documents. What Suresh couldn't see from a video call was that a neighbouring structure had, over several years, crept a few feet onto the edge of the plot — encroachment invisible on camera but sitting right there in the survey records, if anyone had thought to check them before making an offer.

This is the specific fear that keeps NRIs from committing to plot and independent-house-land purchases: not fraud in the dramatic sense, but a quieter risk — a boundary that doesn't match what's on paper, a survey number that's been subdivided since the last time anyone updated the physical fencing, or a structure that has slowly encroached over years while nobody with a legal stake was watching closely. You can't walk the boundary from another country. But you can, in most Indian states today, pull the public land record for a plot's survey number and compare it against what's being shown to you — and that comparison catches a meaningful share of the problems before you ever need to travel.

This article walks through what a remote record check can actually verify, what it cannot, and how to combine it with a trusted on-ground step so you're not relying on records alone.

Encroachment vs. Boundary Dispute vs. Survey Mismatch — Three Different Problems

These terms get used interchangeably, but they describe three distinct situations, and the remote check for each is slightly different:

Encroachment is when a person or structure occupies part of a plot without legal title to it — a wall built a few feet over the line, a shed extending onto a neighbouring survey number, or informal occupation of an undeveloped portion. Encroachment is a physical, on-ground fact; land records show the legal boundary, not necessarily where a wall or fence actually sits today.

Boundary dispute is when two parties (often neighbouring landowners) disagree about where the legal boundary actually falls — sometimes because old survey markers have been lost or moved, sometimes because a subdivision was recorded imprecisely. This shows up in records as unresolved litigation or a discrepancy between two adjoining survey records.

Survey mismatch is when the survey number quoted in the sale documents doesn't correspond to a plot with the dimensions, shape, or location you're being shown — sometimes an honest clerical carryover from an old record, sometimes a sign the seller doesn't hold clean title to the specific physical plot being pointed out.

Remote record checks are strongest against survey mismatches and reasonably useful for surfacing recorded disputes; they are weakest against physical encroachment, because a record shows the boundary as recorded, not necessarily what's standing on the ground today.

Step-by-Step: The Remote Record Check

1. Get the exact survey number, sub-division number, and village/taluk/district from the seller — not just an address. Indian land records are indexed by survey number within a village, not by street address, so this is the non-negotiable starting point.

2. Pull the record from the relevant state land-record portal. According to the NoBroker guide on legal due diligence for NRIs, most states now offer some form of online land-record access — for example MahaBhulekh (Maharashtra's 7/12 extract), Karnataka's RTC/Bhoomi portal, Telangana's Dharani, and West Bengal's Banglarbhumi — where you can look up ownership and survey details tied to a specific survey number (NoBroker, Legal Due Diligence for NRIs, 2025).

3. Compare the record's stated boundaries and dimensions against what you're being shown — photos, videos, or a site plan the seller has provided. Look specifically for whether the recorded area matches the claimed plot size, and whether the ownership name on record matches the seller.

4. Cross-check against a village or cadastral map where the state offers one. Some states publish a Bhu-Naksha-style cadastral map layer showing the plot's shape and its position relative to neighbouring survey numbers — useful for spotting whether a claimed plot's shape looks unusually irregular compared to its recorded map shape, which can be an early signal worth investigating further.

5. Flag anything inconsistent for a local professional to physically verify — a mismatch you find remotely is a reason to dig deeper, not a final verdict either way.

What Each State Portal Typically Reveals

Portal names, coverage, and the exact fields shown vary by state and change over time, so treat this as an orientation table, not a guarantee of what you'll see when you check — confirm current portal capability for your specific state as-of the date you search.

Geographic and Demographic Specifics: What Peri-Urban Buyers Should Watch For

Survey-number mismatches show up more often in fast-growing peri-urban corridors — the Noida/Greater Noida belt, Bengaluru's outer ring areas, and parts of Pune's expansion zones — where agricultural land has been subdivided and converted for residential use over a relatively short period, and where record updates sometimes lag the pace of physical development on the ground. If your shortlisted plot sits in one of these corridors, treat the survey-number cross-check as a mandatory step rather than an optional extra, precisely because subdivision records in these areas are more likely to be a step behind reality.

There's also a category check worth doing early, before you get attached to a specific plot: the RBI's FAQ on the Purchase of Immovable Property in India is explicit that NRIs and OCIs cannot purchase agricultural land, plantation property, or a farmhouse in India, regardless of how the transaction is structured (RBI FEMA FAQ, ongoing). If the land record shows an agricultural classification that hasn't been formally converted to non-agricultural (NA) use, that's a separate, more fundamental eligibility problem than encroachment — worth ruling out before you invest more diligence time.

A Real-World Scenario: Catching a Mismatch from Abroad

Meera, based in Dubai, was evaluating a plot near Bengaluru's outer ring road that a broker had shown her over a video call. Before agreeing to a site visit by a trusted uncle, she asked the seller directly for the survey number and sub-division number and looked it up on the Karnataka RTC/Bhoomi portal. The recorded area came back noticeably smaller than what the broker had quoted her, and the ownership name on the record didn't match the person she'd been told was the seller. Rather than travel or send her uncle to inspect a plot that might not even be the one being sold, she raised the discrepancy directly and asked for an explanation and updated documentation. The seller's side eventually clarified that the plot had been informally sub-divided among family members after the original record was created and the "seller" she'd spoken to held only a portion of the original survey number — a materially different transaction than what she thought she was evaluating. Catching this from a desk in Dubai meant she avoided sending someone to inspect the wrong plot, and it reframed the entire negotiation before any money changed hands.

Where Remote Checks Stop — and the On-Ground Step You Still Need

This is the honest limit of everything above: a land record shows the recorded boundary, not necessarily the physical boundary as it exists today. A neighbour's wall that has crept two feet over the line won't show up as an anomaly in a 7/12 extract or an RTC record — it will only show up if someone physically walks the boundary with a surveyor, or at minimum with a trusted local representative holding the site plan against the actual fencing.

The realistic sequence for a remote buyer is:

1. Do the record-and-map cross-check above first, remotely, to filter out survey mismatches and obvious documentation problems.
2. If the plot clears that filter, engage a local surveyor or a trusted representative to physically walk the boundary against the recorded dimensions before you commit further.
3. Treat any inconsistency found at either stage as a reason to pause and investigate, not as something to resolve informally with the seller alone.

Remote checks and a physical survey are complementary, not substitutes for each other — skipping either one leaves a real gap.

Pro Tips

• Get the survey number and sub-division number in writing from the seller before you agree to anything else — this is the single piece of information that unlocks every other remote check.
• Screenshot and date-stamp what you find on the state portal — portals get updated, and having a dated record of what you saw is useful if a discrepancy surfaces later.
• Check the land-use classification, not just ownership — an agricultural classification that hasn't been converted matters both for encroachment context and for NRI/OCI purchase eligibility.
• Ask specifically about recent sub-divisions — a plot that's been informally split among family members after the original survey record was created is a common, easy-to-miss source of mismatch.
• Don't skip the physical survey step just because the records look clean — clean records are a necessary filter, not a complete answer.

Common Mistakes to Avoid

• Relying on an address instead of insisting on the exact survey number — Indian land records don't index by street address, and a vague address makes any remote check impossible.
• Treating a clean land-record check as proof there's no encroachment — records show the recorded boundary, not physical occupation on the ground.
• Skipping the eligibility check on agricultural land classification for NRIs/OCIs before falling in love with a specific plot.
• Assuming portal capability is the same across states — some states offer richer cadastral map layers than others; confirm what your specific state's portal actually shows before relying on it.
• Not engaging a local surveyor at all, on the assumption that a remote records check alone is sufficient due diligence for a plot purchase.

How DrawMagic Fits Into This

Catching a survey-number or boundary problem early, before you've invested travel time and emotional commitment in a specific plot, is exactly the kind of remote-diligence step DrawMagic's evolving Buyer Intelligence hub is designed to help organise as the feature continues rolling out — bringing readiness signals and official-record context together for buyers evaluating property from a distance. When you're actively comparing shortlisted plots or listings, DrawMagic's property discovery and shortlist tools help you keep the survey-number and record details attached to each listing rather than scattered across messages and screenshots. And because any information DrawMagic surfaces — like any public-record lookup — is a starting point to confirm independently rather than a certification of anything, it's worth understanding DrawMagic's approach to responsible AI before treating any automated summary as the final word on a plot's boundary status.

DrawMagic does not verify, certify, or guarantee any plot's boundary or title status — it is an information and software platform, not a surveyor, broker, or legal authority. Facts should always be confirmed against the primary state portal and, where a mismatch appears, against a licensed local surveyor or lawyer.

Key Takeaways

• Encroachment, boundary disputes, and survey mismatches are three different problems, and a remote record check is strongest against survey mismatches, weaker against physical encroachment.
• Get the exact survey number, sub-division number, and village/taluk/district from the seller before attempting any remote check — Indian records are indexed by survey number, not street address.
• State portals like Maharashtra's MahaBhulekh, Karnataka's RTC/Bhoomi, Telangana's Dharani, and West Bengal's Banglarbhumi let you check ownership and survey details tied to a specific parcel, but exact coverage and fields vary by state and change over time.
• Cadastral or village map layers, where available, help you compare a plot's recorded shape against what you're being shown.
• Peri-urban corridors around Noida, Bengaluru, and Pune see survey-number mismatches more often, since record updates can lag fast physical development.
• NRIs and OCIs cannot buy agricultural land, plantations, or farmhouses under FEMA rules — check the land-use classification before investing further diligence time.
• A clean remote record check is a necessary filter, not proof against physical encroachment — you still need an on-ground surveyor or trusted representative to walk the boundary.
• Screenshot and date-stamp what you find on any portal, since records and portal capability both change over time.
• Treat any discrepancy between records and what you're shown as a reason to pause and investigate, not something to resolve informally.
• Combine the remote record check with a physical survey step — the two are complementary, not substitutes for each other.

FAQ

Can I fully verify a plot's boundary from abroad without ever visiting? No. A remote record check can catch survey-number mismatches and surface some recorded disputes, but it cannot confirm the physical, on-ground boundary — that still requires a surveyor or a trusted local representative to walk the site.

What if the state portal for my plot's location doesn't show cadastral map data? Not every state currently offers a map layer alongside its ownership/survey record — rely on the ownership and survey-number data that is available, and lean more heavily on a local surveyor for the boundary confirmation.

Is an old survey record still valid if the plot has been informally sub-divided since? Not necessarily — informal sub-divisions among family members after the original record was created are a common source of mismatch. Always ask directly whether any sub-division has occurred and confirm the current record reflects it.

Ready to keep your remote diligence organised in one place? Explore DrawMagic's buyer resources and browse properties with record context attached before you commit travel time to a plot that a five-minute portal check could have flagged.