Land Purchase Document Checklist for India

Buying land in India without a complete document set is not just a compliance risk — it is a deal-killing operational failure. Missing a single document at the Sub-Registrar office forces a rescheduled registration appointment, and in states with heavy booking queues, that means 2–4 weeks of added delay. This guide covers every document your team needs to collect before a land purchase, what each proves, how to verify it by state, and how to build a repeatable tracking process for active pipelines.

Why document readiness is an operations problem, not just a legal one

Document gaps are most commonly an operations failure, not a title defect. The legal team typically knows what is required. The problem is that document collection is distributed across multiple portals, government offices, and counterparties — the seller, the Sub-Registrar, the revenue department, the local municipality — and no single person tracks completion status in real time.

In a team managing 15–20 active parcels across two or three cities, it is routine for a parcel to reach the offer or LOI stage before anyone has confirmed that the seller’s patta reflects current ownership or that the EC is fresh enough for the planned registration date. By that point, delay is not a risk — it is a scheduled event.

The land due diligence checklist covers document collection as one of 15 checks across the full due diligence process. This guide goes one layer deeper: what to collect, in what order, from which source, and how to handle gaps before they compound.

The end-to-end document workflow runs as follows:

1. Deal enters pipeline.
2. Request the document set from the seller.
3. Pull revenue records online — Patta, Chitta, FMB, EC.
4. Cross-verify survey numbers across all documents.
5. Check the title chain:
   • Complete: continue to step 6.
   • Gap: identify the missing deed, request it from the seller, then continue.
6. Collect originals plus certified copies.
7. Legal review and opinion letter.
8. Verify the full document set is complete:
   • Complete: schedule SRO registration.
   • Deficient: resolve before booking the appointment.

The core document set every land transaction requires

Every residential and commercial land purchase in India requires the same base set regardless of state. State-specific requirements are additions on top of this foundation, not replacements.

1. Title deed chain (parent deeds)

The title deed is the registered sale deed transferring ownership to the current seller. “Chain” means all prior transfers going back 30 years minimum — ideally back to the original government grant or settlement. Each transfer must be a document registered at the Sub-Registrar office. Unregistered agreements-to-sell in the chain are a structural red flag.

What to check: the survey number must be consistent across every deed in the chain, the stated consideration must be at or above the guideline value applicable at the time of each transaction, and each transferor must appear as the owner in the immediately prior deed. A gap — a period where ownership is not documented — is a title defect requiring a legal search, and sometimes a court-rectified deed to cure.

2. Encumbrance Certificate (EC)

The EC from the Sub-Registrar’s office lists every registered transaction affecting the property: mortgages, sale deeds, court decrees, lease agreements, and charges. It does not capture unregistered encumbrances but is the standard legal check for registered claims. The SRO with jurisdiction is decided by the village the property sits in.

Minimum required: 13 years. Professional standard: 30 years. The EC must be current to within 30 days of the planned registration date — a stale EC does not cover transactions registered in the intervening period. In Tamil Nadu, online ECs via tnreginet.gov.in can be requested within minutes; the offline SRO process takes 7–10 working days. For a detailed breakdown of EC entries and red flags, the patta chitta FMB and EC guide covers what each section means.

3. Patta (Record of Rights)

Patta is the revenue record that recognizes ownership at the village revenue level. It shows the pattadar (owner) name, survey number, land extent, and classification. For any transaction, the patta must be in the seller’s name. A patta in a prior owner’s name means mutation was not done after the last sale — a warning about document hygiene that reliably predicts downstream complications.

If the patta shows a different extent than the sale deed, that discrepancy must be formally reconciled before proceeding. Even a 2–3% area difference causes registration objections at most SROs.

4. Chitta

Chitta records the land type classification: wet land (irrigated paddy), dry land, or house-site (natham). This classification determines whether conversion orders are required before construction, and affects the stamp duty rate applicable. An agricultural chitta without a Land Use Conversion (LUC) order means the parcel legally cannot be developed — regardless of what the seller claims about actual use.

5. Field Measurement Book (FMB) sketch

The FMB is the survey department’s official sketch of the parcel showing boundaries, adjacent survey numbers, dimensions, and internal features. It is the reference document for boundary disputes. Cross-verify FMB dimensions against actual ground measurements on site — a 5–10% variance is common in rural and peri-urban parcels due to decades-old survey records and encroachments that have not been formally recorded.

6. Adangal / village revenue extract

The Adangal is the village-level revenue record showing cultivation history, possession details, tax entries, and water access rights. It supplements the Chitta (which records classification) with operational possession data. Tamil Nadu uses Adangal; Karnataka uses the crop register section of the RTC. Discrepancies between the Adangal and the patta on possession or area are a trigger for additional inquiry.

7. Property tax receipts

Current property tax receipts from the relevant Urban Local Body (Corporation, Municipality, or Town Panchayat). Unpaid property tax does not legally block registration in most states, but the liability transfers to the buyer. Verify payment for the last 3 years minimum; in some states (Maharashtra, Karnataka), outstanding dues create a statutory charge on the property.

8. Legal opinion letter

A written legal opinion from a qualified property lawyer covering the title chain, EC, patta, and survey documents. For professional land acquisition this is not optional — it is the documented due diligence record that protects the buyer in any future dispute and is required by most lenders for project finance.

State-specific additional documents

Tamil Nadu

Tamil Nadu’s portal ecosystem (eservices.tn.gov.in, tnreginet.gov.in, Tamil Nadu Geoportal) makes digital document collection faster than most states. Core additional requirements:

• Adangal extract: Pull from the online portal or tehsildar office. Verify that cultivator/possessor aligns with seller identity.
• Natham patta: If the land is within a habitation area, a separate natham patta is required, issued by the Revenue Department at the village level.
• NOC from local body: For plots within Urban Local Body limits — confirmation of no outstanding civic dues and no structural objections from the municipal authority.
• CMDA / DTCP layout approval: For subdivided plots within the Chennai Metropolitan Area or DTCP jurisdiction, the approved layout plan showing the specific plot number. Without this, individual plot registration cannot proceed.
• NA order (if applicable): For agricultural land converted to residential, the government order from the Collector’s office authorizing non-agricultural use.

Karnataka

Karnataka’s Bhoomi portal is one of India’s more robust land records systems. Additional documents required:

• RTC (Record of Tenancy and Crops) / Pahani: The Karnataka equivalent of patta + chitta combined. Shows owner, tenant if any, survey number, area, classification, and crop details. Available via bhoomi.karnataka.gov.in.
• Mutation Register (MR) extract: Confirms the last mutation (revenue ownership transfer) is current. A mutation that has not been formally closed after the last sale is a process deficiency.
• DC conversion order (Section 95): For agricultural to non-agricultural conversion, the Deputy Commissioner’s order under the Karnataka Land Revenue Act. Verify the conversion order is for the current survey number and extent — partial conversions on split parcels are a common source of ambiguity.
• Tippani: The survey department’s sketch for the parcel, equivalent of the FMB in Tamil Nadu.
• EC via KAVERI: Karnataka’s sub-registrar portal (kaveri.karnataka.gov.in) provides online EC. Verify the search covers all survey numbers associated with the parcel.

Maharashtra

Maharashtra land records are accessed through Mahabhulekh (mahabhulekh.maharashtra.gov.in). Key additional documents:

• 7/12 (Satbara) extract: The combined record of ownership (rights) and cultivation details. The 7 (saat) section shows ownership; the 12 (baara) section shows agricultural use. Both are necessary for complete verification.
• 6/12 (Mutation register) extract: Documents all ownership mutations for the survey number. Cross-check with the title deed chain to confirm every transfer has a corresponding registered mutation.
• NA order (Section 44, Maharashtra Land Revenue Code): For agricultural to non-agricultural conversion, issued by the Collector’s office. Mandatory for construction on agricultural land. Obtain the certified copy from the Collector’s record room — a registered copy does not always exist in private hands.
• Index II: A summary of all registered documents for the property, issued by the Sub-Registrar with each registered deed. Should exist for every transaction in the chain. Missing Index II for any link in the chain is a verification gap.
• Search report: Maharashtra SROs issue a formal search report covering registered encumbrances, equivalent to the EC in Tamil Nadu and Karnataka. Required for registration.

Document collection sequence and timeline

The 15-day end-to-end runs in four phases. Stages 1 and 2 should run in parallel, not sequentially.

Phase 1 — Days 1–3: Initiate in parallel

• Seller: request the title deed chain.
• Online: pull EC from TNREGINET, Kaveri, or MahaBhulekh.
• Online: pull Patta + Chitta + FMB, or RTC + Tippani, or Satbara.

Phase 2 — Days 3–10: Seller provides

• Original deed chain — all links.
• Property tax receipts — last 3 years.
• Conversion order or NA order, if applicable.
• Layout approval or CMDA plan, if applicable.

Phase 3 — Days 10–15: Verify and clear

• Cross-verify survey numbers across all documents.
• Check the patta name matches the seller.
• Confirm the EC covers 30 years and is current within 30 days.
• Legal opinion letter.

Phase 4 — Day 15+: Register

• Book SRO appointment with the complete set.
• Registration date.

For a clean plot in Tamil Nadu with no conversion requirements: 12–15 working days end-to-end. The constraint is almost never document availability — it is legal review turnaround. Start the legal review the moment the title deed chain is in hand, not after all documents are assembled. That sequencing choice alone recovers 3–5 working days.

Common gaps that derail deals at the last stage

Teams that have processed 50+ parcels recognize a recurring set of document deficiencies. Each one either causes SRO refusal or creates post-purchase legal risk.

Patta mutation not done after last sale. The seller purchased 6 years ago but never applied for mutation. The patta still shows the previous owner. The seller must complete mutation before registration — a 30–60 day process at the Tehsildar’s office. Either build this timeline into the deal, or make completed patta mutation a condition precedent in the LOI.

EC gap year. The EC covers 1990–2010 and 2015–present, with a 5-year window missing. This happens when a specific SRO’s records were not digitized for that period. The gap requires an offline EC request for the missing years. A gap in EC coverage is not the same as a gap in encumbrances — but it is indistinguishable without the physical records. Do not accept an EC with an unresolved coverage gap.

Missing link in title chain. The seller holds a deed from 2016 and the next deed in the chain is from 1988. The 28-year gap is either unregistered transfers (a structural defect) or a different transaction mechanism: succession, family partition, or court decree. Each mechanism has its own document set — succession certificate, registered partition deed, or certified court decree. Identify which applies and collect the corresponding instrument.

Conversion order missing or lapsed. An agricultural parcel that was converted 14 years ago, but the NA order cannot be located and was never registered. The municipal authority will treat the land as agricultural for construction approval purposes — blocking permits regardless of actual use for decades. A certified copy of the NA order must be obtained from the Collector’s record room before proceeding.

Area mismatch across documents. The sale deed says 4,350 sq ft, the patta says 4,200 sq ft, and the FMB shows 4,180 sq ft. These variances are common in older parcels where measurements were taken at different times with different instruments. Resolution requires either a re-survey (2–6 weeks) or a legally drafted reconciliation statement that acknowledges the variance and establishes the agreed measurement for registration purposes. The document readiness checker flags these mismatches automatically when you enter data from each document.

Building a systematic process for active pipelines

For teams running 15+ active parcels, document tracking via a shared spreadsheet creates three consistent failure modes: status updates that lag reality, checklist items that get modified by individual team members, and no audit trail for when items were completed or by whom.

A systematic document readiness process requires three elements:

Centralized status by parcel, not by person. Every document on the checklist has a current status (not requested / requested / received / verified / deficient) and is visible to the full team without asking anyone. Parcels that are 85% document-complete show their specific blockers — not just a generic “in progress.”

Verified receipt, not just acknowledged receipt. Receiving a document and verifying it meet the standard are two distinct steps. A received EC that has not been checked for coverage period and current date is a false positive in your pipeline. The verification step must confirm specific criteria: EC covers 30+ years and is dated within 30 days, patta name matches the seller, survey numbers match across all instruments.

Exception tracking with owners and deadlines. When a document is deficient, the system must log the specific issue (what is wrong, not just that something is wrong), who is responsible for resolution, and a target date. Without this, gaps migrate into email threads and WhatsApp messages and surface as surprises on registration day.

Proquiro’s document verification software for land acquisition teams handles this centrally across all active deals — tracking completion percentage by parcel, flagging specific deficiencies with status labels, and logging verification history with timestamps. For teams currently coordinating document collection through a combination of checklists and messaging apps, centralizing this layer typically recovers 4–6 hours per parcel in coordination overhead.

For a unified approach to managing your entire pipeline, explore Proquiro’s land acquisition software for Indian real estate teams.

For standalone use before committing to a full platform, the document readiness checker is an interactive tool that walks through each document category, accepts status inputs per parcel, and flags deficiencies against the required standard for your target state. Run it in parallel with the title risk checklist to cover both document completeness and title risk evaluation in a single pre-offer assessment.

Document readiness is the execution test that most land teams fail quietly — not because the document list is unknown, but because there is no system tracking whether each item is actually complete and verified, not just started. Build the tracking layer first. The individual document collection follows.