---
title: "Buying Land in India: Document Readiness Checklist"
description: "A controlled way to collect, verify and approve land-purchase documents without treating a generic national list as a parcel-specific legal requirement."
author: "Vignesh Nagarajan"
author_profile: https://proquiro.com/authors/vignesh-nagarajan
date: 2026-04-21
updatedDate: 2026-08-09
category: guide
methodology: "This checklist models document states and provenance rather than claiming a universal mandatory set. It uses government sources for registration and Tamil Nadu record availability, removes unsupported time, age, variance and savings benchmarks, and requires local counsel to define transaction-specific requirements."
sources: [{"title":"The Registration Act, 1908","publisher":"India Code","url":"https://www.indiacode.nic.in/handle/123456789/2190?view_type=browse","evidence_type":"primary-source","checked_date":"2026-08-09"},{"title":"View Land Records of Patta / Chitta / FMB (Rural), Tamil Nadu","publisher":"National Government Services Portal","url":"https://services.india.gov.in/service/detail/view-land-records-of-patta--chitta--fmb-rural-tamil-nadu","evidence_type":"primary-source","checked_date":"2026-08-09"}]
corrections: [{"date":"2026-08-09","summary":"Removed unsupported mandatory-document lists, title-chain periods, EC freshness rules, turnaround times, SRO refusal claims, state-specific legal conclusions, variance tolerances, mutation delays, coordination savings, and product automation claims."}]
tags: ["land documents", "document checklist", "land purchase", "due diligence", "title verification"]
canonical_url: https://proquiro.com/blog/document-readiness-land-purchase-checklist
---
Document readiness is not the number of files in a folder. It is the ability to show what each document is, where it came from, which parcel and period it covers, whether it was verified, what exception remains, and who approved the next step.

## Direct answer

Create a parcel-specific register after local counsel defines the required evidence. Give each item a controlled state: **not requested**, **requested**, **received**, **verified**, **deficient**, **superseded**, or **not applicable with reason**. Do not let “received” satisfy a stage that requires verification.

## Document groups to consider

The exact list varies, but most workflows need to consider these groups:

| Group                     | Examples of evidence                                                                                      | Verification question                                                  |
| ------------------------- | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Parcel identity           | Survey number, subdivision, boundaries, extent, address                                                   | Do all documents describe the same land?                               |
| Conveyance chain          | Sale, gift, partition, settlement, release, succession or court instruments                               | Does each claimed transfer connect, and what is its legal effect?      |
| Seller authority          | Identity, entity records, board or trustee authority, power of attorney, heirship evidence                | Can every required party execute this transaction?                     |
| Registration search       | EC, index or certified search selected for the jurisdiction                                               | Do returned entries and coverage reconcile with the chain?             |
| Revenue records           | Patta, RoR, mutation, [A-Register](/states/tamil-nadu/a-register), Adangal, RTC, 7/12 or state equivalent | What does the current revenue system record, and where does it differ? |
| Survey evidence           | FMB, TSLR, village map, Tippan, survey report                                                             | Does the official record relate to the ground and possession?          |
| Planning and development  | Zone, layout, planning permission, conversion or reclassification, building approval                      | Is the proposed use permitted, and what conditions apply?              |
| Tax and public dues       | Relevant land, property and transaction records                                                           | What liability or clearance must be addressed?                         |
| Restrictions and disputes | Court, acquisition, environmental, coastal, forest, heritage, road or utility evidence                    | What separate search or approval is required?                          |
| Closing documents         | Agreed instrument, valuation inputs, duty and fee calculation, payment and registration evidence          | Is the execution package current and approved?                         |

The [Registration Act, 1908](https://www.indiacode.nic.in/handle/123456789/2190?view_type=browse) is a central statutory source for registered documents. State rules, amendments, forms and authority procedures still matter.

## Record provenance

For every file, store:

- document type and title;
- issuing authority or counterparty;
- reference or document number;
- issue, execution and registration dates where relevant;
- survey numbers and subdivisions covered;
- period covered;
- retrieval source and date;
- whether it is an original, certified copy, digitally authenticated record, portal view or private copy;
- verifier, verification date and method; and
- current status and exception.

A renamed PDF is not provenance. Keep the official reference and retrieval route.

## Tamil Nadu online records

Tamil Nadu's government service exposes [Patta, Chitta, FMB and TSLR-related lookups](https://services.india.gov.in/service/detail/view-land-records-of-patta--chitta--fmb-rural-tamil-nadu) using rural or urban parcel identifiers. Use those records as current revenue or survey evidence within their stated scope. Do not label them a complete title report.

Use the [Patta/Chitta](/tools/tamil-nadu/patta-chitta), [FMB/TSLR](/tools/tamil-nadu/fmb-tslr-sketch), and [EC](/tools/tamil-nadu/encumbrance-certificate-verification) routes to reach the relevant official systems. Retain the official output.

## A controlled collection sequence

### 1. Define the requirement

Counsel and the transaction team should specify the document, acceptable form, scope, date or period, authority, verifier and stage gate.

### 2. Request in parallel where safe

Assign each request an owner and reference. Separate seller-supplied documents from records retrieved independently.

### 3. Reconcile parcel identifiers first

Do not begin substantive comparison until survey numbers, subdivisions and boundaries are mapped across old and current descriptions.

### 4. Verify, do not merely collect

Compare names, authority, extent, dates, conditions and related documents. A document can be authentic but irrelevant to the target subdivision or proposed use.

### 5. Resolve exceptions before the gate

Every exception needs a factual description, required evidence, responsible person, deadline and decision consequence. “Legal to confirm” is not an actionable exception.

### 6. Freeze the closing set

Before execution, recheck items whose status can change, confirm the final instrument and parcel schedule, retain approvals, and record sign-off. Counsel and the registering authority should determine what must be presented.

## What this guide does not prove

It does not prescribe a national title-chain period, EC period, acceptable document age, collection timeline, area tolerance, mandatory state document, or outcome at a Sub-Registrar office. It also does not prove that a complete-looking folder establishes title or development eligibility.

Use the [document readiness checker](/tools/document-readiness-checker) to structure status, and the [land due diligence checklist](/blog/land-due-diligence-checklist-india) for the wider decision process. Evaluate any workflow product against the current source-of-truth and evidence requirements rather than relying on promised time savings.

## Sources and editorial notes

### Methodology

This checklist models document states and provenance rather than claiming a universal mandatory set. It uses government sources for registration and Tamil Nadu record availability, removes unsupported time, age, variance and savings benchmarks, and requires local counsel to define transaction-specific requirements.

### Sources

- [The Registration Act, 1908](https://www.indiacode.nic.in/handle/123456789/2190?view_type=browse) — India Code; primary-source; checked 2026-08-09
- [View Land Records of Patta / Chitta / FMB (Rural), Tamil Nadu](https://services.india.gov.in/service/detail/view-land-records-of-patta--chitta--fmb-rural-tamil-nadu) — National Government Services Portal; primary-source; checked 2026-08-09

### Updates and corrections

- 2026-08-09: Removed unsupported mandatory-document lists, title-chain periods, EC freshness rules, turnaround times, SRO refusal claims, state-specific legal conclusions, variance tolerances, mutation delays, coordination savings, and product automation claims.