Change of Land Use (CLU) in India: Full Process Guide

What CLU Actually Is

In Indian land-revenue systems, every parcel carries a recorded land-use classification, most commonly "agricultural" by default across rural and peri-urban India. Change of Land Use — used interchangeably in different states with "Non-Agricultural conversion," "NA conversion," or simply "land conversion" — is the formal administrative process by which the competent planning or revenue authority changes that recorded classification to permit a different use: residential, commercial, industrial, institutional, or a specific hybrid like a farmhouse or resort use in states that define one.

CLU is not a single national law with one process, one fee schedule and one authority. Land is a State subject under India's Constitution, and each state has built its own legal and administrative machinery around it — some through a dedicated Town & Country Planning department, some through Development Authorities exercising delegated powers, some through revenue-side officers (Tehsildars, Sub-Divisional Magistrates) acting under a state Land Revenue Code. What's consistent across all of them is the underlying logic: land-use decisions are treated as a planning function the state controls directly, not as something a private owner or buyer can decide unilaterally by simply changing how they use their own land.

Why It's Required Before You Build

Three separate reasons converge to make CLU a hard legal requirement rather than a bureaucratic suggestion:

• Revenue and taxation. Agricultural and non-agricultural land are taxed differently, and many state stamp-duty and registration frameworks price transactions differently depending on recorded land use — converting use without formal reclassification creates a genuine tax and registration-value mismatch, not just a paperwork gap.
• Planning control. Master plans and development plans allocate land across a region into zones — residential, industrial, green belt, agricultural — specifically to manage infrastructure load (roads, water, drainage, power) and prevent unplanned sprawl. A CLU application is, functionally, a request to bring one specific parcel's classification in line with what the applicable master plan actually permits at that location — which is also why CLU can be refused even where the applicant is willing to pay every fee, if the master plan simply doesn't allow that use there.
• Legal exposure for the owner. Constructing on agricultural land without CLU exposes the owner to demolition orders, penalty proceedings, and — critically for a buyer — a structure that cannot be legally mortgaged, insured against certain risks, or sold with clean title as the "built" asset it appears to be. Multiple state High Courts have upheld demolition and penalty action against unauthorised construction on unconverted agricultural land; the structure being physically complete does not make it legal.

It's worth being direct about how this plays out for a buyer rather than a developer. A plot marketed as "residential" or "commercial potential" that is still recorded as agricultural land is, legally, still agricultural land — the marketing description changes nothing about its actual classification. If you buy it on that basis and later discover the applicable master plan doesn't permit the conversion you assumed was routine, you're left holding agricultural land at a price that reflected non-agricultural expectations, with no straightforward way to recover that gap. This is a different and generally larger risk than a delayed approval — a delay costs you time; a genuine zoning mismatch can mean the intended use was never achievable at all.

This is also precisely why the price-appreciation story around any infrastructure-driven corridor — including the one covered in our Jewar Airport land guide — should never be read as "the land will be worth building on" without a separate, specific check on whether that land can legally be converted to the use being imagined for it.

The General Step-by-Step Process

Despite the state-by-state variation covered in the next section, nearly every CLU process in India follows the same underlying sequence:

1. Eligibility and zoning check. Before filing anything, confirm the parcel actually sits in a zone the relevant master/development plan permits to be converted to your intended use. If the plan designates the area as permanent agricultural land, green belt, or a restricted/protected zone, no fee or application will secure a conversion — this check should happen before you buy the land, not after.
2. Document preparation. Standard requirements across states include the ownership document (sale deed/title), the revenue record (variously called Jamabandi, Khatauni, or Records of Rights depending on the state), a mutation extract confirming the applicant's name is correctly recorded, a site plan and location map (often required at a specified survey scale), a certified non-encumbrance certificate, and — for commercial, industrial or larger residential proposals — a project report describing the intended development.
3. Application filing. Filed with the Town & Country Planning (TCP) department, the relevant Development Authority, or (in states/areas following a revenue-code route) the Sub-Divisional Magistrate or Tehsildar, depending on jurisdiction — increasingly through a state-specific online portal alongside the traditional paper-file route.
4. Site inspection. A department official — commonly a District Town Planner, Patwari, or equivalent revenue officer — physically inspects the site to verify ownership on the ground, confirm the land is being used as recorded, check access/road-width compliance, and note anything (existing structures, disputes, encroachments) relevant to the application.
5. Conversion fee / conversion charge calculation. The core fee is typically calculated off the land's value — most commonly the government-notified circle rate or collector rate for that location — combined with the category of use being sought (residential conversions are usually charged at a lower rate than commercial, and industrial fee structures vary further by project scale). Several states layer additional charges on top: External Development Charges (EDC) and Infrastructure Development Charges (IDC) toward the cost of extending roads, water and power to the site, and separate licensing or scrutiny fees for larger colony/project-scale conversions.
6. NOCs from other departments, where applicable. Depending on the proposed use, location and scale, additional no-objection certificates may be required — environmental clearance for larger projects, fire safety, pollution control board clearance for certain industrial uses, and (as covered in our Jewar Airport land guide) an Airports Authority of India height clearance for land near an operational airport.
7. Issuance of the conversion order / CLU certificate. Once fees are paid and inspection/NOC requirements are satisfied, the authority issues a formal conversion order or CLU certificate specifying the survey/khasra numbers covered, the approved land-use category, the total approved area, and — in most states — a validity period (commonly 2–3 years) within which construction must actually commence.
8. Mutation of the revised classification in revenue records. The final step, and one buyers frequently overlook, is ensuring the new land-use classification is actually updated in the underlying revenue record (mutation/dakhil-kharij) — not just reflected in the standalone CLU certificate. Until that mutation happens, the government's own primary land record can still show the parcel as agricultural, which creates exactly the kind of document mismatch that causes problems at resale or at a subsequent building-plan approval stage.

Who Actually Needs CLU (and Common Exemptions)

Not every non-agricultural use on agricultural-classified land requires the full CLU process described above, and understanding the actual boundary matters both for buyers trying to gauge how much process a project needs and for anyone tempted to assume an exemption applies when it doesn't.

• Genuinely agricultural uses stay exempt by definition. A farm shed, irrigation infrastructure, a tube well, or fencing directly in service of cultivation generally doesn't trigger CLU, because it isn't a change of use at all — it's an extension of the agricultural use the land is already classified for.
• Several states carve out a limited exemption for a farmer's own residential structure on their own agricultural holding — typically capped at a small defined area and tied to the applicant actually being a bona fide agriculturist cultivating that land, not a purchaser intending a farmhouse-style weekend property. This exemption is easy to misread as a general "farmhouses don't need CLU" rule; it isn't one, and relying on it without checking the specific state provision and its area cap is a common and costly misunderstanding.
• Land already recorded in revenue records under a non-agricultural category — commonly termed abadi (habitation) land, gair mumkin (unfit for cultivation) land, or similar state-specific classifications — doesn't need CLU for uses consistent with that existing classification, because the reclassification already happened, sometimes generations ago, and is simply carried forward in the record. This is also precisely why confirming a parcel's actual current revenue classification, rather than assuming "agricultural" by default, is one of the first things worth checking before assuming CLU is even required at all.
• Government and institutional land use changes follow their own separate administrative channels rather than the private-applicant CLU process described here.
• Everything else — residential plotting, commercial construction, industrial use, resort/hospitality development, and farmhouse projects that go beyond a bona fide agriculturist's own limited-area exemption — needs the full process. This covers the overwhelming majority of what buyers in Farmland India's corridor are actually trying to do with agricultural land.

The practical rule of thumb: if you're buying land specifically because of what you plan to build on it, assume full CLU applies unless a specific, verified exemption says otherwise for your exact situation — never the reverse.

How the Process Differs by State

The six states in Farmland India's corridor each run CLU through a different combination of authority, statute and procedure. Here's the shape of each, at a level meant to orient a buyer — not to substitute for the state-specific deep dives some of these deserve on their own.

This table is an orientation summary, not a substitute for checking the current process directly with the relevant authority — statutes, delegated powers and portal names are periodically updated by each state.

Uttar Pradesh

UP runs two parallel tracks depending on location. Inside the jurisdiction of a Development Authority (Noida, Greater Noida, YEIDA, Lucknow Development Authority and similar bodies), land-use conversion is handled by that authority directly, under the Uttar Pradesh Urban Planning and Development Act, against its own approved master plan and sector layout — this is the track relevant to land inside YEIDA's jurisdiction near Jewar, as covered in our Jewar Airport land guide. Outside a Development Authority's jurisdiction, conversion of agricultural land to non-agricultural use is generally handled under Section 80 (commonly still referred to by its predecessor numbering, Section 143) of the Uttar Pradesh Revenue Code, 2006, through the Sub-Divisional Magistrate (SDM) or Tehsildar, following broadly the same document-and-inspection sequence described above.

Haryana

Haryana's process is the most procedurally developed in the corridor and is covered in a full dedicated deep-dive below and, in even greater depth, in a forthcoming dedicated article — CLU in Haryana: Process and Fees — because it draws by far the highest CLU-related search volume of any state in this corridor.

Punjab

Punjab's regional and town planning framework rests on the Punjab Regional and Town Planning and Development Act, 1995, which established the planning authorities (PUDA and, in the Mohali region, GMADA, alongside other regional development authorities) empowered to prepare development plans and regulate land use changes against them. In practice, CLU-type approvals for private land are processed through these authorities' town-planning wings, with a separate but related statute — the Punjab Apartment and Property Regulation Act (PAPRA), 1995 — governing promoter/colonizer registration for group-housing and colony-scale projects specifically; a developer converting land for a licensed colony typically deals with both frameworks, not just one. Punjab has increasingly moved routine CLU processing online through a common application portal, with reported processing timelines around three to four weeks for straightforward cases once a complete file is submitted, and separate, inspection-dependent conversion charges assessed after the file is accepted. Punjab's DTCP structure and process are similar in spirit to Haryana's neighbouring system but run under distinct legislation — don't assume a Haryana precedent transfers directly to a Punjab file.

Rajasthan

Rajasthan's conversion process runs primarily through the Rajasthan Land Revenue Act framework at the district/Tehsildar level for most rural agricultural land, alongside Urban Improvement Trusts (UITs) and Development Authorities (such as the Jaipur Development Authority) for land inside their planning areas. Rajasthan is also notable for publishing some of its planning and cadastral data through a live GIS portal, which can be a useful independent cross-check on a parcel's zoning before filing — though the portal itself carries an explicit disclaimer that it is for viewing purposes only and not a substitute for verification against official records.

Uttarakhand

Uttarakhand's process broadly mirrors the UP revenue-code model it inherited at formation (also frequently referenced by its own Section 143 provision), run through the Tehsildar/SDM at the district level outside Development Authority areas such as Dehradun's, with the same core document set and circle-rate-linked fee logic. Hill-district parcels carry an additional practical wrinkle worth flagging: slope, forest-boundary proximity and eco-sensitive-zone overlap are checked more strictly during inspection than in plains districts, and can be an independent basis for rejection even where the paperwork is otherwise complete.

Himachal Pradesh

Himachal Pradesh applies some of the tightest land-conversion controls in the corridor, shaped significantly by the state's own land-ceiling and non-agriculturist land-purchase restrictions (see our state-wise agricultural land laws guide for the ownership-eligibility side of this). Conversion approvals run through the state's Town & Country Planning department for land inside planning areas, and through the Deputy Commissioner's office at the district revenue level elsewhere, with particular sensitivity around forest-boundary, slope-stability and eco-fragile-zone restrictions given the state's hill terrain and tourism-driven construction pressure.

Haryana's DTCP Process — A Closer Look

Haryana's CLU process draws the highest search volume of any state in this corridor, and for good reason — it is the most heavily documented, most actively contested, and arguably the most procedurally mature CLU system among the six. A full dedicated treatment lives at CLU in Haryana: Process and Fees; here is the shape of it.

The Director, Town and Country Planning (DTCP), Haryana is the primary authority, operating under the Haryana Development and Regulation of Urban Areas Act, 1975 (with roots also in the earlier Punjab Scheduled Roads and Controlled Areas Restriction of Unregulated Development Act, 1963, which Haryana inherited and continues to apply in controlled areas). The process runs largely online through the department's e-CLU system: an applicant registers on the DTCP Haryana portal, files Form CLU-I with a survey/site plan (commonly required at a 1-inch-to-40-feet scale), the sale deed, an Intkal (mutation) copy, a Shajra (village map extract), a land-utilisation plan, and — for commercial or industrial proposals — a project report, then pays the prescribed fee online. A District Town Planner conducts the site inspection and submits a departmental report before the file moves toward approval.

Fees combine a conversion charge (reported ranges commonly cited run roughly ₹1–8 lakh per acre for residential use, with commercial rates set higher and industrial charges assessed on a project-specific basis) with separate External Development Charges (EDC) and Infrastructure Development Charges (IDC) payable toward the state urban development authority. Reported processing timelines run roughly 60–90 days for a standard, complete application, with a faster 30–45 day track reported for projects in already-notified industrial zones. We were not able to verify a single authoritative, current fee schedule directly from DTCP's own published rate notification for this article — conversion charges are revised periodically and vary meaningfully by district and zone (a Gurugram-area file, for instance, is priced very differently from a rural district one) — so treat the ranges above as indicative, and always request DTCP's current, zone-specific rate schedule directly before budgeting a real project.

One structural bottleneck is worth understanding on its own terms because it's specific to Haryana and genuinely well documented: reporting has quantified roughly ₹3,000 crore in investment — projects expected to generate close to 5,876 jobs — stuck behind pending CLU applications, with the large majority of those delayed files concentrated in agriculture-zone conversions rather than pre-cleared industrial-zone ones. The reason is procedural rather than merely administrative backlog: Haryana's deemed-approval mechanism (which allows an application to be treated as approved if the department doesn't act within a set window) currently applies only to industrial-zone projects, not agricultural-zone ones — and investors disproportionately prefer agricultural-zone land precisely because it's cheaper and carries no pre-existing development charges, which is exactly the category of application without a deemed-approval safety valve. If you're evaluating a Haryana agricultural-zone CLU timeline, price in the real possibility of a multi-month-to-multi-year wait beyond the department's own stated processing window, not just the headline 60–90 day figure.

Common Reasons Applications Get Rejected

A fuller, dedicated treatment of this topic — including state-specific rejection patterns — lives at Why CLU Applications Get Rejected. The patterns that recur across states, based on the process mechanics above and reported case coverage, are:

• Zoning mismatch. The single most fundamental rejection reason: the applicable master or development plan simply doesn't designate that location for the use being requested. No fee or documentation fixes a plan-level mismatch — this is why the eligibility check in step one of the process above needs to happen before purchase, not after filing.
• Title and ownership disputes. An application filed while the underlying ownership is contested, incompletely mutated, or where multiple claimants exist on the revenue record will typically be held or rejected until the title question is independently resolved — CLU authorities generally aren't positioned to adjudicate an ownership dispute themselves.
• Incomplete or inconsistent documentation. Survey numbers, area figures or ownership names that don't match cleanly across the sale deed, the Jamabandi/revenue record and the site plan are a routine and avoidable cause of delay or rejection.
• Restricted or ecologically sensitive land. Proximity to a forest boundary, eco-sensitive zone, floodplain, or a notified restricted/protected category of land is an independent basis for rejection regardless of how complete the paperwork otherwise is — this is a particular risk factor in hill-state applications (Uttarakhand, Himachal Pradesh) and near notified ecological zones elsewhere in the corridor.
• Missing NOCs from other departments. Where environmental clearance, fire-safety approval, pollution-control clearance, or (near an airport) an AAI height NOC is a precondition, an application without that separate clearance in hand is routinely held pending it rather than rejected outright — but the practical effect on your timeline is the same.
• Road-width and access non-compliance. Several states' planning norms set a minimum approach-road width for a given category of conversion; a landlocked parcel or one accessed only by a sub-standard village road can fail this specific check even when everything else about the file is in order.
• Pending dues or violations elsewhere on the applicant's record. Some authorities check for outstanding development charges, penalty dues, or unresolved violations tied to the same applicant or promoter on other parcels before clearing a new file — a pattern more visible in states with a mature developer-licensing system like Haryana's and Punjab's.
• Applying at the wrong authority entirely. Filing a Development-Authority-track application through the general revenue-code route (or vice versa) in a state that splits jurisdiction — Uttar Pradesh being the clearest example — leads to the file being rejected or redirected rather than processed, simply losing time rather than reflecting any real defect in the underlying request.

A pattern worth naming explicitly: several of these reasons are things a buyer can check independently, before ever filing an application — the applicable master plan's zoning for that location, the parcel's current revenue classification, road access, and proximity to an ecologically sensitive or restricted zone. Doing that homework before purchase, rather than treating CLU filing as the point at which these questions first get asked, is the single biggest lever a buyer has over their own risk in this entire process.

Timelines and Costs — What We Can and Can't Verify

We're stating this plainly rather than hiding behind vague language: CLU timelines and fees are genuinely difficult to pin to a single reliable figure, and any source — including this one — that states one confident nationwide number should be treated with suspicion.

Timelines. Reported ranges across the states covered here run roughly 30 to 90 days for a straightforward, complete application, extending well beyond that for commercial/industrial-scale proposals, applications requiring multiple external NOCs, or — as documented for Haryana above — agriculture-zone files that don't qualify for a deemed-approval fast track. A validity period of roughly 2–3 years on the approved CLU itself, within which construction must commence or the approval can lapse, is broadly consistent across the states reviewed here, though the exact figure and renewal process differ by state and should be confirmed on the specific certificate issued.

Costs. The underlying fee logic — a conversion charge tied to circle rate/collector rate and use category, plus separate development charges (EDC/IDC where applicable) — is consistent across the corridor's states. The actual rupee figures are not: they vary by state, by district and zone within a state, by category of intended use, and they are revised periodically by the relevant department or authority. We were able to find indicative ranges for Haryana (cited above) and Punjab's flat processing-fee component, but were not able to independently verify a single current, authoritative fee schedule for any of these states directly from that state's own published, dated rate notification within the scope of this article's research. Anyone budgeting a real project should request the current rate schedule directly from the relevant Town & Country Planning department or Development Authority — not rely on a marketing site's quoted range, including the ranges cited in this article, without confirming them against an official, dated source first.

CLU vs. RERA, Mutation and Other Approvals

CLU is frequently confused with a handful of adjacent approvals that serve different purposes:

• CLU vs. RERA registration. CLU changes what a parcel of land is legally classified as being used for. RERA registration is a separate requirement for a developer marketing and selling units in a real estate project once that project is actually being built and sold — a project can have valid CLU and still be operating illegally if it isn't RERA-registered where required, and vice versa. See our Farmhouse Projects and Government Policies guide for how these interact specifically for farmhouse developments.
• CLU vs. mutation (dakhil-kharij). As covered in the step-by-step process above, mutation is the final step that actually updates the revenue record to reflect a CLU's new classification — a CLU order without a corresponding mutation is an incomplete conversion in practical terms, even though the certificate itself is genuine.
• CLU vs. building-plan/map approval. Even after a CLU is granted, the specific structure you intend to build (its layout, height, setbacks, floor-area ratio) still needs its own separate building-plan approval from the local municipal or development authority — CLU settles the land-use question; building-plan approval settles the construction-specifics question.
• CLU vs. environmental clearance. For projects above certain size thresholds, environmental clearance under the EIA notification framework is a separate, parallel requirement that can run alongside CLU processing but isn't satisfied by it.

Common Mistakes

• Buying agricultural land on the assumption CLU is a formality that can be sorted out later. Zoning mismatch is unresolvable by any amount of paperwork or fee payment — verify feasibility before purchase, not after.
• Treating a CLU certificate as complete without confirming the corresponding mutation in the revenue record. This is the single most common gap between "technically converted" and "actually reflected in the government's own primary record."
• Letting an approved CLU lapse by not starting construction within its validity window (commonly 2–3 years) — an expired CLU generally has to be renewed or re-applied for, not assumed to remain valid indefinitely.
• Assuming a process or fee figure from one state applies in another. Haryana's DTCP process, Punjab's PUDA/PAPRA framework, and UP's Development-Authority-vs-Section 80 split are genuinely different legal systems, not regional variations on one national rule.
• Skipping the road-width, ecological-zone and other site-specific checks that can independently sink an otherwise complete application — particularly relevant in hill-state and airport-proximity contexts covered elsewhere on this site.
• Relying on a marketing site's quoted fee range instead of the current official rate notification when actually budgeting a project.

How Farmland India Helps

Every developer project and individually listed parcel on Farmland India carries a Farmland India Reviewed status, and for any listing marketed with CLU already in place, that review specifically includes checking for the corresponding mutation entry in the revenue record — not just the standalone conversion certificate — against the parcel's actual survey/khasra number. Where CLU is not yet in place, listings are described accordingly rather than implied to already carry development rights they don't yet have.

Frequently Asked Questions