LRS 2020: processing the regularisation pile

LRS is the state’s standing bargain with its own planning failure: lakhs of plots were sold from unapproved layouts over decades, and the Layout Regularisation Scheme lets a plot owner pay a charge and have the plot regularised — bringing it inside the planning system instead of leaving it permanently illegal. The 2020 edition of the scheme generated an enormous application stock, froze in litigation and policy limbo for years, and is now being cleared at pace. A Deputy Collector meets LRS from two seats: the Tahsildar’s verification role in the flow, and the Additional Collector (Local Bodies) desk where layout-level approvals conclude — a post held by senior Deputy Collectors.

The scheme and the stock

LRS 2020 issued as G.O.Ms.No. 131, MA&UD, dated 31-08-2020, inviting applications to regularise plots in unapproved/unauthorised layouts. Eligibility is keyed to plots registered on or before 26-08-2020 — the cut-off that defines the scheme’s universe and blocks fresh subdivision from riding in.

Roughly 25 lakh applications were filed — and then sat frozen for years through the PIL era (the Rahul Bajaj/NALSAR litigation window) and the policy limbo that followed. The present government resumed processing with fresh guidelines in late 2024/early 2025, directing clearance of pending applications within three months. Processing runs on CGG-built portals: lrs.telangana.gov.in generally, and lrsbrs.hmda.gov.in for the HMDA area. MA&UD is the nodal department — this is a municipal scheme with a revenue interface, not a revenue scheme.

The four-level flow

Every application walks the same ladder:

1. Level 1 — portal scrutiny. The CGG platform runs the first check: documents, registration date against the 26-08-2020 cut-off, plot particulars, computed charges. The revenue interface sits here: 1% of cleared applications go to the jurisdictional Tahsildar for random verification — principally government-land and prohibited-land checks. The sampling logic is deterrence: any application may be pulled, so the portal record had better match the revenue record.
2. Level 2 — the ULB’s Town Planning officer. The planning scrutiny proper: road width, master-plan and zoning conformity, open-space position. This is where the plot’s physical and planning reality is judged.
3. Level 3 — the Municipal Commissioner, including review of rejections — the check against Level-2 refusals that are careless or worse.
4. Level 4 — layout-level approvals: the Additional Collector (Local Bodies) in the districts, or the City Planner / Director (Planning) in GHMC/HMDA. Where a whole layout’s regularisation is in question — not just a single plot — the file concludes here. For a Deputy Collector this is the seat to understand: the Additional Collector (Local Bodies) post is part of the cadre’s own ladder.

The Tahsildar’s verification — doing the 1% properly

When a random-verification case lands in the Tahsil office, the check is a land-status enquiry, not a planning one:

• Is any part of the plot or its layout government land? Trace the survey number through the pahani and RoR; check for poramboke, assigned land, ceiling, endowment or wakf history.
• Is the survey number on the prohibited list? The 22-A flag on the Bhu Bharati portal is decisive — a prohibited-list parcel cannot be regularised into private title by a municipal scheme.
• Does the ground match the record? Where the layout has swallowed a nala, a tank margin or a road poramboke, the revenue report is the only place that fact enters the LRS file.

The report should be specific and survey-number-wise. “No objection” on a layout that later turns out to sit on shikam is a finding with the officer’s name on it; equally, a lazy adverse report that misreads a sub-division freezes a citizen’s plot for years. The 22-A page’s discipline — decide at the sub-division, not the survey number — applies here in full.

Refusals: FTL, buffer and prohibited lands

The perennial sticking points, and the cases that reach a Deputy Collector as grievances:

• Plots in FTL or buffer zones of tanks and nalas are refused, or held for extra verification — regularisation cannot cure a plot that stands in a tank’s water spread or inside the G.O. 168 buffer. The overlay check against lakes.hmda.gov.in and the FTL notifications is standard scrutiny.
• Plots on prohibited (22-A) land — assigned, government, endowment, wakf — are refused; where the listing itself is a Dharani-era error, the owner must first win the correction through the Bhu Bharati channel, then pursue LRS.
• Open-space (14%) charge disputes — layouts that provided no open space attract the charge, and applicants contest it perennially.
• Portal glitches — payment failures, name mismatches — generate a steady grievance stream that is administrative, not legal; the answer is escalation through the CGG helpdesk chain, documented.

A refusal on FTL or prohibited-land grounds should say so precisely — which notification, which tag, which sub-division — because these refusals are litigated, and a refusal that names its basis survives where “not eligible” does not.

The 2026 rebate window

To move the pending stock, a 25% fee rebate window ran from 01-05-2026 to 31-07-2026 for pending LRS-2020 cases; new applications pay full charges, and eligibility remained keyed to the 26-08-2020 registration cut-off. The post-31-07-2026 position — whether the rebate lapsed finally or was extended — is UNVERIFIED as of 22 August 2026; check the current MA&UD orders before advising any applicant on fees, and date-stamp any answer you give.

A worked example

An application in the random-verification queue reaches a Tahsildar in a district abutting HMDA: plot 46 of an unapproved layout in Sy.No. 88, registered in 2018, charges computed and paid at Level 1. The Tahsil enquiry finds Sy.No. 88 subdivided decades ago: 88/1 and 88/3 are clean patta; 88/2 is a recorded nala poramboke cutting the layout’s north edge; and the portal’s prohibited-lands search shows the whole of Sy.No. 88 flagged — a classic whole-number tag for one government sub-division.

The report, survey-number-wise, says exactly that: plot 46 falls in 88/3 (patta, no bar); the layout’s plots 1–9 overlap 88/2 (nala poramboke — regularisation barred, encroachment action recommended); and the 22-A flag needs sub-division-wise correction through the Bhu Bharati channel. On that report, plot 46 proceeds at Level 2 — where the Town Planning officer finds it also sits 6 metres from the nala’s edge, inside the 9-metre buffer for a nala wider than 10 metres, and refuses, citing G.O. 168. The owner’s grievance lands, eventually, with the Additional Collector (Local Bodies): the refusal stands, because it is precise — and the owner at least leaves knowing which two facts (the buffer, not the tag) actually decide his plot.

Edge cases and common mistakes

• Regularisation as title-washing. LRS regularises the layout violation; it does not create or launder title. A plot on government or prohibited land gains nothing from an LRS receipt — and an officer who clears it has signed away government land.
• The whole-number 22-A block. As everywhere, one government sub-division often flags the whole survey number. The verification report must map sub-divisions, or genuine plots stay frozen and the grievance becomes yours.
• The cut-off shuffle. Documents engineered to show pre-26-08-2020 registration — unregistered agreements dressed up, or plots re-carved after the date — are the scheme’s standard fraud. The registered document’s date, verified on the registration record, is the only anchor.
• Refusing without the record. An FTL-ground refusal where the tank is only preliminarily notified must say so and rest on the shikam record too; a refusal citing a line that was never fixed invites the writ the state keeps losing.
• Treating the three-month direction as licence for haste. The clearance deadline pressure is real; the 1% verification and the FTL/prohibited checks are precisely what must not be pencil-whipped to meet it. A wrongly cleared plot is permanent; a delayed one is not.
• Forgetting the fee position moves. Rebate windows open and close; quoting last quarter’s charges is a grievance generator. Date-stamp every fee answer.

Questions you’ll actually get

“I paid the LRS fee in 2020 — why is my plot still not regularised?” The stock froze in litigation and policy limbo until the 2024–25 resumption; processing is now running through the four levels. Check the application’s live status on the portal — and if it is stuck at a named level beyond the guideline timelines, a written representation to that level’s officer is the next step.

“My application was rejected saying prohibited land, but this is our patta land.” Then the 22-A tag is likely a Dharani-era error — the remedy is the Bhu Bharati correction channel first (Tahsildar/RDO enquiry, Collector’s deletion order), and LRS after the flag lifts. The LRS system cannot overrule the revenue flag.

“Can I get the 25% rebate now?” The notified window ran 1 May to 31 July 2026. Whether anything survives it is unverified as of August 2026 — the current MA&UD order, not memory, answers this.

“The layout developer promised regularisation was included — whom do I chase?” LRS applications are plot-wise and the charge is the applicant’s; the developer’s promise is a private claim against him. What the officer can give you is the application’s factual status and the reason for any hold.

“Why is my neighbour’s plot cleared and mine held, in the same layout?” Plot-wise scrutiny: his plot may fall outside the FTL/buffer overlap or the flagged sub-division while yours falls inside. Ask for the specific ground of the hold in writing — you are entitled to that.

What to watch in the field

If you sit anywhere in this flow, keep your own one-page map of the layouts in your jurisdiction that touch water bodies or flagged survey numbers — those two overlays predict virtually every LRS refusal, grievance and litigation you will see. And when the Tahsil’s 1% verification files come, treat each as the audit it is: the sampling only deters if the sample is actually checked.