What happened
On 11 July 2018, the SIR Apex Authority (GIDB) sanctioned Preliminary Town Planning Scheme No. 2/A (Dholera–Mundi–Rahtalav–Bhimtalav) vide notification SIRAA/26/2018/321 and Preliminary TP Scheme No. 4/A (Dholera–Mundi) vide SIRAA/25/2018/320, both published in the Gujarat Government Gazette the same day. Both gazette PDFs are on the official portal and were read for this entry — which is why this archive carries it at high confidence.
The background
To read the date correctly, it helps to know the machinery. In Gujarat, a town-planning scheme is a statutory instrument under the Gujarat Town Planning and Urban Development Act, 1976: a defined patch of land is redrawn, with some land becoming roads, utilities and civic reservations, and the remainder returned to original owners as reshaped, serviced final plots. A scheme moves through fixed stages — draft, preliminary sanction, final sanction, implementation — and preliminary sanction is the operative stage: original plots reconstitute into final plots, and the scheme's broad structure becomes law. TP1 and TP2, the region's first two parent schemes, had been drafted back in 2012–2013 covering the first development phase; 2/A and 4/A are the split sub-schemes that operationalise TP2 and TP4 for the activation area.
The details
The sub-scheme split is the detail worth understanding. Parent schemes at Dholera's scale are too large to implement in one pass, so they are divided into lettered sub-schemes with their own boundaries, reconstitution arithmetic and sanction cycles. What the two 11 July 2018 notifications did was bring specific patches of the activation area — the Dholera–Mundi–Rahtalav–Bhimtalav and Dholera–Mundi areas — to the stage where actual development permissions and construction land first became available. Both notifications were published in the Government Gazette, giving them the highest evidentiary tier this archive uses: primary legal documents, not reporting about them.
Why it matters to Dholera
Preliminary sanction is the operative TP stage — original plots reconstituted into final plots. These two sub-schemes operationalise TP2/TP4 for the 22.5 sq km activation area, making them the schemes where actual development permissions and construction land first became available. Every road, utility corridor and plot boundary later built inside the activation area sits on land whose legal existence as final plots dates to sanctions like these. Without this gazette moment, the trunk infrastructure would have had nothing lawful to build on.
The gazette date deserves one further note on method. Because both notifications were published in the Government Gazette on 11 July 2018, the sanction date is not reconstructed from reporting — it is the state's own legal record, downloadable and checkable by any reader. That is the standard this archive holds every land entry to, and it is why this entry's confidence rating differs from media-based entries elsewhere in the timeline. Where a milestone can be verified against a primary document, we say so and link the document; where it cannot, we lower the confidence and say that too.
The bigger picture
Land pooling through TP schemes is Dholera's answer to the hardest problem in Indian greenfield development: assembling land without the bitterness of pure acquisition. Owners keep a share as serviced final plots; the scheme captures part of the value gain to fund the works. The mechanism would face judicial scrutiny — as our January 2019 High Court entry records — but the July 2018 sanctions show it functioning as designed, converting farmland into developable urban land through geometry and statute rather than displacement.
What came next / What we watch next: the sub-scheme splits of 2025–2026, culminating in ten preliminary sanctions in a single day (30 March 2026) — the same machinery, at larger scale. The full mechanism is explained in Chapter 10 — TP schemes and Chapter 9 — land pooling.
Verified sources
This is an archive entry from our milestone backfill — verified against the sources below, with the event date kept true to history.
