Revenue Department Records: An Agent Use Case

A district wanted an agent that could do mutations faster. The sentence treated a transfer of rights in land as if it were a helpdesk ticket. Mutation, in Indian revenue practice, is a quasi-judicial or at least a high-integrity administrative act. It changes who the State will listen to about a parcel. An agent that posts that change without a competent officer is not a use case. It is a title defect factory.

This is a case-study-shaped field guide, not a report of a named district's confidential stack. Digital India Land Records Modernisation Programme (DILRMP) and state land-records systems (often branded locally — Bhu-Naksha, RoR portals, Bhulekh-class sites) have digitised records to very different degrees across states. Some registers are clean. Some are a scan plus a quarrel. Hedge the live state of the district you are in.

The honest use case is retrieval, explanation of notified procedure, mismatch flags for an officer, and drafts of notices the officer will edit. The dishonest use case is auto-mutation. This article is written on 17 August 2026. It is not legal advice and not a revenue-code commentary. Read the state's land revenue Act, the mutation circular, and the district's actual software before you write a tool.

Why integrity is the product

A Record of Rights (or the state's equivalent) is relied on by citizens, banks, courts and later officers. A wrong name, a wrong share, a wrong khata is not a UX bug. It is a fight that can last a generation. Spatial layers (cadastral maps, Bhu-Naksha-class services where they exist) and textual RoR can disagree. An agent that answers from one without the as-of of the other will sound certain. Personal data sits next to property data: phone numbers, Aadhaar references in some workflows, photographs. DPDP applies to the personal part. Property integrity applies to all of it.

Revenue workflows versus an agent. Mutation stays human.

Workflow	Agent may	Agent may not
Explain mutation procedure	Retrieve the notified circular / citizen charter	Promise a timeline the circular does not state
RoR / extract status	Read a signed or official-API extract with as-of	Re-type a name more correctly
Mismatch flag	Show officer that text and map or two systems disagree	Pick a winner
Notice / hearing draft	Fill a template the collectorate owns	Issue or serve the notice
Mutation order	No	No. Competent officer only, in the system of record.
Partition / conversion / acquisition	Retrieve procedure	Any dispositive act

The use case that actually pays

Officers spend hours hunting the live circular, the last mutation number, and whether a stay exists. A pinned retrieval over the district's own orders, plus a read wrap of the official extract, cuts that hunt. Measure hours on a sample of files, not mutations per hour — speed of mutation is the wrong KPI because it invites skipped hearings. Citizen-facing, the honest bot explains documents required and points at the official portal for the certified extract. It does not WhatsApp a JPEG of someone else's khata. A mismatch queue — text versus map, unpaid demand versus claimed sale, stay versus proceeding — is valuable if an officer works it. It is harmful if the queue auto-stays or auto-advances files.

What the wrap must look like

Read replica or official extract API. SELECT-only. Village-level dumps forbidden as a tool. Query logs kept. No free-text correction of names. If the extract is wrong, the path is a correction proceeding, not a helpful rewrite. As-of stamps on every answer. Land databases batch. Yesterday's RoR is not today's. Default deny on any tool whose name includes mutate, approve, reject, digitally sign, or SMS-serve.

Politics and the hearing

Land is political. An agent that appears to favour a purchaser's story in a disputed village will be treated as a party. Keep the tone procedural. Cite the circular. Do not summarise likely outcome. Hearings still happen in rooms. The agent's draft notice must leave blanks the officer must fill — especially the gist of the other side. A completed narrative is how bias enters.

Two rooms you can walk into

Two districts. One treated mutation as a court-shaped act.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note.

Simple heirship mutations are obvious.

They are obvious until they are not. The file you will be asked about is the exception. Keep the officer.

Citizens already download unofficial PDFs from aggregators.

That is a reason to make the official extract easier, not a reason to let a chat issue a lookalike. Do not compete with aggregators by becoming one.

DILRMP means the record is clean enough to automate.

DILRMP is a programme with uneven residual error. Clean enough to retrieve is not clean enough to auto-mutate. Survey the district, do not cite a national slogan.

Banks want instant encumbrance answers.

Then integrate the official certified extract, with as-of, through a channel the revenue department already authorises. An agent paraphrase is not an encumbrance certificate.

A six-week revenue-records agent that cannot mutate

If the legacy audit found two systems of record, stop and reconcile. Do not wrap a quarrel.

1. Week 1: counsel and the ADM (revenue) write the sentence: mutation is not an agent action. List dispositive acts the same way.
2. Week 2: pin procedure circulars and citizen-charter pages. Design three read views: extract as-of, stay/caveat flag if it exists, demand as-of.
3. Week 3: replica wrap, village-dump tool forbidden, query logs, Indic name tests.
4. Week 4: officer UI for mismatch flags. Notice templates with mandatory blanks.
5. Week 5: quality sample on procedure answers. No public land-parcel chat.
6. Week 6: collectorate standing order: refuse-list of tools, press language, kill-switch.

How this shows up in the file

Subject: Agent assistance on revenue records. Mutation, partition, conversion and any speaking order remain acts of a competent officer in the system of record. The agent may retrieve notified procedure and official extracts with an as-of stamp, and may flag mismatches for an officer. It may not correct names, serve notices, or post status. DILRMP or state portal status does not alter this sentence. Personal data in the wrap is purpose-limited.

What we will and will not claim

Prcept AI will wrap reads and refuse mutation tools. If a district asks us to just post the simple ones, we will decline. Title defects are not a software milestone. They are a later officer's nightmare.

This article is informational field guidance for Indian universities and public institutions, not legal, procurement, audit or engineering advice. Confirm against the live Gazette, GFR, state financial rules, GeM terms, UGC text, GIGW, DPDP commencement, departmental manual and your counsel before you file it.

How to sequence this in a state, not a slide

“Revenue Department Records: An Agent Use Case” is a department problem. A P1 CIO/CTO should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “land revenue records AI”.

Revenue records are high-integrity public registers. An agent can retrieve a signed RoR extract and flag mismatches. Mutation is not an agent action without a competent officer. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “Revenue Department Records: An Agent Use Case” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “land revenue records AI” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Revenue Department Records: An Agent Use Case” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “land revenue records AI”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “land revenue records AI” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.