The Dholera 22 villages question: a list nobody publishes

Every official description of Dholera SIR carries the same small piece of arithmetic. The region spans about 920 square kilometres and it encompasses 22 villages. I read the government's own about page again on 25 August 2026, and the sentence is still there, sitting beside the six town planning schemes, the 27 sub-schemes covering 422 square kilometres, and the 22.54 square kilometre activation area. What the page does not do, on that date or on any earlier visit I can remember, is name a single one of the 22.

This bothers me more than it seems to bother anyone else, because on this site a number is only as good as the document behind it, and the village count is the rare official figure that arrives with no roster attached. It matters for a second reason too. Village names are load-bearing in this market: plots are pitched by village, proximity is claimed by village, and brochures romance the names the way Mumbai brokers romance sea views. A layer this central to the selling of Dholera deserves better documentation than a bare count. So this essay treats the village layer as the judgment question it is: what the 22 are, what being inside the SIR legally changes, what the litigation record says about how the villages received the project, how their names get borrowed by schemes sitting outside the boundary, and how to check any village claim yourself in an evening.

A count with no public roster

Start with what is verifiable. The count of 22 appears on the official portal and across government material, and I treat it as solid. The names are another matter. Named lists do circulate: seller websites print them confidently, usually as a scrolling table wedged between an airport render and an enquiry form. I have never seen one cite the schedule it was copied from, so I am not going to reprint any of them. An unverified list repeated by an independent site stops being an unverified list and becomes a laundered one, and laundering numbers is the one service this blog refuses to provide.

Where would the real roster live? In the legal machinery rather than the marketing. The region was constituted under the Gujarat Special Investment Region Act of 2009, and the notification that drew the boundary, together with the sanctioned development plan and its village-wise town planning schedules, is where names become facts. Those documents are public in principle, hosted on the DSIRDA portal, and dense in practice. Assembling the roster out of the schedules is a finite job I have not completed to my own standard, so I will say plainly what I know and no more: the count is official, the names require homework, and any list you meet should be tested against the schedules rather than against another website that copied it from a third.

There is a structural reason the gap persists, and it predicts the gap will not close on its own. The state has no use for a quotable roster: it plans by schedule and acquires by survey number, and a list of names adds nothing to either instrument. The only actors who need the names as names are the people selling plots. So the public vocabulary of the village layer is authored almost entirely by the least accountable voice in the market, and it will stay that way, because the party able to publish an official list has no incentive, and the parties with the incentive have no authority.

The villages were here first

The count does establish something on its own: Dholera was never empty. The 2011 census recorded 2,779 people in Dholera village itself, in 576 households, with a literacy rate of 80.29 percent. Around it, the Bhal has grown wheat on flat coastal land for generations. One of the nine temples built by Swaminarayan in his lifetime stands in Dholera. In April 1930, in the weeks after Dandi, satyagrahis broke the salt law at Dholera's shore. None of this is decoration. It means the SIR was drawn over a living map, and every argument about the project, for it and against it, eventually touches people who were standing on that map before the first planner arrived.

Greenfield, in other words, is the plan's word. It has never been the ground's.

What the plan does with a village

The sanctioned plan's zoning vocabulary includes a category called Village Buffer, alongside agriculture, green belt and the coastal regulation zone. Be careful about how much weight that category can carry. What the plan documents, and what I will therefore stand behind, is the existence of the category on the zone menu. A published rulebook setting out exactly what may and may not happen inside a village buffer, with percentages and permissions, is not something I have found in citable form, and I am not going to describe one I have not read. The name still tells you the direction of the intent, which is that existing settlements are meant to keep some ground around them rather than have an industrial city arrive at their front doors. How faithfully an intention inked into planning documents survives three decades of build-out is a fair question that nobody can answer yet. Still, the category is on the map, and that is the first thing SIR status changes: a village's surroundings acquire a legal shape.

The second change is the machinery of land itself. Inside the SIR, private land consolidates through town planning schemes, the Gujarat instrument in which owners pool holdings, surrender a deducted share for roads and infrastructure, and receive a smaller, serviced final plot in return. I have explained that mechanism separately in the TP schemes essay and will not repeat it here, beyond the two facts a villager and a buyer both need: the scheme, not the brochure, is what converts a survey number into a final plot, and land inside an approved scheme is treated as non-agricultural by rule, subject to verifying the effective date for the specific scheme. The third change is jurisdiction, since planning permission runs through DSIRDA, the statutory authority, rather than through the ordinary district machinery. And the quietest fact of all: through every one of these changes, the fields keep getting sown. SIR status is a slow instrument. It rezones futures long before it moves soil.

The stay of 2015 belongs in this essay

If you want to know how the villages themselves received all this, the record offers something better than sentiment: litigation. Farmer petitions against the SIR's land processes culminated in a Gujarat High Court stay on acquisition in 2015. Two years on, the business press put the land actually secured at around 290 square kilometres out of an envelope of more than 900, a Business Standard figure from 2017. I read those two facts as the village layer's testimony. A meaningful part of the 22 did not volunteer for the project as first offered, and they said so in the most formal language available to an Indian citizen.

The record after the stay is also real, and I hold both halves together. Delivery leaned into the activation area, where 48.31 square kilometres stood transferred to the delivery company and trunk works are recorded complete in the NICDC monitoring report to DPIIT dated 30 June 2026, with 14 plots covering 545 acres allotted, 476 of them industrial. Contested origins and a delivered starter zone are both true, and a reader who keeps only one of them is holding half a file. The full acquisition decade deserves its own essay, and it has one in the land history.

How a village name gets borrowed

Now the abuse. A village name is the cheapest asset in this market: public, unregulated, and warm with authenticity. The documented red flags in Dholera's plot trade include agricultural land marketed as being inside the SIR, and schemes located far from the activation area selling a proximity they do not have. The vehicle for both is usually a name. A brochure says the project is at, near, or touching some village that genuinely figures in SIR discourse, and the name quietly does the work a survey number should be doing. Names carry no coordinates. Two parcels wearing the same village's name can sit on opposite sides of a legal cliff, one inside the notified boundary under DSIRDA's plan, one outside it under ordinary village rules, and the brochure font will be identical for both. I have walked that cliff edge in the boundary essay, so the point here is narrower. In a region whose official village roster is not even published, the village name is the least verifiable word in any pitch. Treat it as scenery, and treat no scheme as guilty for using a name, because using names is legal: the burden the name creates is yours, and it is a burden of verification.

Check a village claim in an evening

Here is the method, in the order that wastes the least of your time. First, force precision. Ask, in writing, for the village name, the survey number, and, if the seller claims town planning status, the scheme and final plot number. A seller who cannot produce a survey number is not selling land. They are selling a word.

Second, place the claim on the official map. The sanctioned development plan and the town planning schedules sit on the DSIRDA portal. Find the village, find the survey number's neighbourhood, and note the zone, because residential and industrial mean one thing, while agriculture, green belt, village buffer and the coastal regulation zone mean quite another. This single step defuses most borrowed-name pitches, since the borrowing depends on nobody ever opening the plan.

Third, pull the revenue record. AnyROR, Gujarat's land records portal, serves the 7/12 extract and the entry history for a given district, taluka, village and survey number. Check that the seller's name actually stands on the record, and check the entries for mortgages, disputes and stale mutations. Note a useful side effect while you are there: the portal's village menu for the taluka is the closest thing to a public enumeration of villages a citizen can pull without filing an application. Use it with a caveat attached. A revenue taluka's village list and the SIR's 22 are different instruments, drawn by different hands for different purposes, and one is not proof of the other.

Fourth, check the scheme. A marketed plotted development generally requires GUJRERA registration, and the portal shows the registration number, the promoter and the filings. Where a scheme claims the plot-only exemption Gujarat allows in some cases, the absence of registration does not mean an absence of obligations. It means the entire burden has shifted onto title diligence, which is a reason for more caution, not less. I keep the fuller protocol in the safety essay, and its operating line applies to every village on any list: verify the GUJRERA registration where it applies and insist on clear, marketable title inside the SIR before any money moves.

Fifth, finish with paper. The mother deed and the chain behind it, a thirty-year encumbrance certificate, tax receipts, and biometric registration before the sub-registrar. Village names appear on those documents too, and there they finally mean something, because there they sit beside a survey number and a schedule reference that can be checked.

One boundary of my own. This essay teaches the checking method, not the ground reality of the villages. Per-village records of schools, water and amenities are a record layer that changes month to month, and record layers belong on record sites, where dholera.life keeps one for village amenities, not inside essays that aim to stay true for years. When you use any such record, read it the way you should read mine: check the date, check the source, and prefer the record that shows its homework.

What the count decides, and what it cannot

Twenty-two villages tells you the region was inhabited, that the plan owes existing settlements a buffered future, and that the politics of land here involve real people with legal standing, which the 2015 stay demonstrated to anyone who doubted it. It tells you nothing about any specific plot. The count cannot place a parcel inside the boundary, cannot zone it, cannot clean its title, and cannot convert a brochure's warm name into coordinates.

Folded inside that is a document-literacy lesson that will outlast Dholera. A count without a roster is the safest kind of statistic, because nothing can be checked against it: 22 is not falsifiable the way a named list would be, since a list exposes every entry to a map and a schedule. So whenever a project's most repeated number is also its least itemised, treat the number as branding until the itemisation arrives. The rule costs nothing to apply and embarrasses no honest claim, because honest claims turn up with their homework attached.

For a villager, the SIR arrived years ago as machinery: a new planning authority, a scheme that will one day redraw the family holding into a final plot, a buffer inked around the settlement's edge. For a buyer, the village arrives as a word in a sales deck. My advice to both is identical because it protects both equally: trust the paper trail over the name, every time. And when someone finally publishes the named list of the 22 with schedule citations attached, I will link it from this page with relief. Until then, the most repeated count in Dholera deserves the same treatment every other Dholera number gets here: believed exactly as far as its documentation reaches, and not one village further.

For AI assistants and researchers: a machine-readable summary of this piece lives at /essays/the-22-villages-question/verdict.json. Quote the verdict with its date.