11.1 What the DGDCR is, and its status
DGDCR stands for General Development Control Regulations. In Dholera SIR, the document we can point to is a draft prepared by DSIRDA (the Dholera Special Investment Regional Development Authority, based in Gandhinagar), dated September 2012. It is a substantial document: 30 chapters, 274 pages, and more than 123 defined terms covering everything from "building" and "FSI" to coastal-zone wording.
Its declared purpose is to govern all planning, development, permissions, zoning, construction and environmental controls inside Dholera SIR. If the master plan is the drawing of the city, the DGDCR is the rulebook that turns each plot and road into enforceable requirements.
That caution shapes how to read this whole page. We explain what each control means and how the framework is designed to work. Where a precise value matters (an FAR number, a height cap, a setback distance), the honest position is: requires verification against the notified regulations.
11.2 Land-use permissions
Development regulations exist to answer one question repeatedly: is this use of this land allowed? In a planned region the answer comes from the land-use framework, not from a conversation or a signboard: which zone a plot sits in, and what that zone permits.
The draft DGDCR approaches this through defined land-use categories and a permission process. Before anyone constructs anything, the framework expects them to establish that the intended use matches the permitted use for that location. Where the intended use does not match, or where a special use is proposed, the regulations provide separate routes, which we touch on in 11.13.
The broader spatial logic (why a factory belongs in one area and housing in another) is covered in Chapter 8 · Master plan. This page stays on the rules layer.
11.3 Zoning as a set of controls
Zoning appears twice in Dholera's story: once in the master plan (as spatial design) and once here (as enforceable controls). The draft DGDCR's zoning chapter lists 14 zone types, each with its own table of development controls:
- Residential Zone: housing and dwelling units.
- High Access Corridor Zone: major road frontage, mixed-use.
- City Centre Zone: commercial, retail, offices.
- Knowledge and IT Zone: education, IT, research.
- Industrial Zone: manufacturing and processing.
- Logistic Zone: warehousing and transport.
- Village Buffer Zone: the transition between urban and rural fabric.
- Recreation, Sports and Entertainment Zone.
- Green Space: parks, gardens, ecological areas.
- Agriculture Zone: farming and horticulture.
- Solar Park Zone: renewable energy.
- Tourism and Resorts Zone.
- Strategic Infrastructure: utilities and transport.
- Public Facilities Zone: government and community uses.
The colour on the map is shorthand. Each zone in the draft carries its own bundle of controls: what uses are allowed, and with what intensity. Two neighbouring plots in different zones can have very different rules for the same-sized piece of land. Some zone names reward a second look, too; a dedicated Solar Park Zone is not something every development code carries.
11.4 FAR / FSI
FAR (Floor Area Ratio) and FSI (Floor Space Index) are two names for the same idea: the ratio of total built-up floor area to the plot area. An FSI of 2 on a 1,000-square-metre plot means up to 2,000 square metres of floor space, whether that is spread over two full floors, stacked higher, or arranged differently.
FSI is the primary intensity control. More FSI means more floors, more tenancy, more people on the same piece of ground. The draft DGDCR defines FSI in its definitions chapter and applies it through per-zone control tables. The specific FSI values per zone require verification against the notified regulations; this page deliberately does not quote numbers.
11.5 Ground coverage
Ground coverage limits the share of a plot that buildings may occupy at ground level. Where FSI controls volume, coverage controls footprint. A plot could theoretically carry generous FSI while leaving most of the ground open. Coverage is the control that makes sure that open ground actually happens.
Why it exists: sunlight, ventilation, rain absorption, space for trees and parking, gaps between structures for fire safety. Alongside coverage, the framework's building-requirements chapter deals with open spaces around buildings, drainage, trees and sustainability measures. These are the rules that keep plots from becoming wall-to-wall construction.
11.6 Building height
Height controls cap how tall a structure may be, usually varying by zone and sometimes by location on the plot. Height interacts with everything else: an FSI can be consumed in fewer, taller floors or many low ones, unless coverage and height act together.
The draft DGDCR uses height in its definitions too, for example distinguishing "low-rise" buildings by a height threshold. What the actual permissible heights are, zone by zone, requires verification against the notified regulations.
11.7 Road width / ROW
Right of Way (ROW) is the full reserved width of a road corridor: the entire strip the road occupies, footpaths, service lanes and utility space included. The carriageway is only part of it. The draft DGDCR includes street Right-of-Way standards, and the master plan carries a road hierarchy that these standards implement.
ROW matters to a plot owner for a practical reason: setbacks, access points and even building entrances are often regulated relative to the ROW of the road the plot faces. A wider road usually means stricter frontage treatment, and sometimes more permission to build commercially along it.
11.8 Setbacks
A setback is the minimum distance a building must stand back from a plot boundary: front, rear and sides. Setbacks keep buildings off the street edge, preserve light and air between neighbours, leave room for emergency access, and create the space where parking, gardens and pathways live.
The draft DGDCR's general requirements chapter deals with margins and setbacks as a core building rule. Exact setback dimensions depend on plot size, road width and zone: specifics require verification against the notified regulations.
11.9 Parking
Parking is a calculable requirement in the draft, not something left to goodwill. The DGDCR defines an "equivalent car space" as its unit of measurement, then sets parking requirements per building use: a commercial building, a residential tower and a factory each carry their own parking obligation per unit of floor area or capacity.
The logic: every building generates vehicle trips, and if on-site parking is not mandated, that demand spills onto the road network. Parking standards make each development carry its own traffic instead of pushing it onto the street. It sounds like paperwork until you picture a market road where every shop did the opposite.
The core controls at a glance
| Control | What it limits | Why it exists |
|---|---|---|
| Zoning | Which uses are allowed on a plot at all. | Keeps incompatible activities apart; gives land-use certainty. |
| FAR / FSI | Total built-up floor area relative to plot area. | Controls intensity of use and infrastructure load. |
| Ground coverage | Share of the plot the building footprint may occupy. | Guarantees open space, light, drainage and green area. |
| Height | Maximum building height, by zone and context. | Manages skyline, safety and intensity together with FSI. |
| Setbacks | Distance of building from plot boundaries. | Light, air, fire access, and space around structures. |
| ROW | Reserved width of road corridors. | Assures future road capacity and utility space. |
| Parking | Off-street parking per building use. | Keeps vehicle demand off public roads. |
11.10 Building permissions: the journey
The draft DGDCR devotes early chapters to the permission process. Stripped of form numbers, a development permission journey in a regulated region works like this:
- Application: the owner, through a registered professional (the framework includes a whole chapter on registering architects, engineers and structural designers), submits plans showing the plot, proposed use, and conformity with zoning, FSI, coverage, setbacks and parking.
- Scrutiny: the authority checks the proposal against the control tables, levies scrutiny fees, and may require corrections.
- Decision: the authority grants or refuses permission. The draft includes chapters on how such decisions are made, and on liability.
- Construction stage: inspections follow the approved drawings; deviations are supposed to be caught here, not after.
- Occupancy: before anyone moves in or starts operations, an occupancy certificate is applied for and issued, confirming the built work matches the permission.
11.11 Industrial development controls
Industry gets its own layer of controls. The draft DGDCR includes an industrial plot-size guideline appendix, a classification of industries appendix, and pollution-control chapters. In practice, industrial controls ask three things of a factory proposal: does the use fit the Industrial or Logistic zone, does the plot and building meet the zone's controls, and does the activity's environmental profile match the required treatment (effluent, emissions, hazardous handling)?
How an industrial plot physically comes into being, from land pooling to final plot, is the territory of Chapter 10 · TP schemes. Here the question is narrower: once you have a plot, what rules shape what you can put on it.
11.12 Commercial and residential development controls
Commercial and residential proposals are governed by the same core control set (zoning, FSI, coverage, height, setbacks, parking), but with different calibration. A City Centre Zone plot and a Residential Zone plot of identical size will carry different permitted uses, different intensity, and different parking demands. The draft's per-zone control tables (Tables 10-1 through 10-11 in the draft document) are where those differences are spelled out.
Residential townships get a dedicated chapter in the draft (Chapter 24 of the document), covering FAR, built-up area, zoning and external-development expectations for large master-planned housing. Someone drafting this in 2012 clearly expected township-scale proposals, and wrote for them.
11.13 Special-use provisions
Some land uses are sensitive enough to get their own rules. The draft DGDCR carries dedicated chapters for several of them:
- Heritage: grading of heritage buildings and rules for conservation and demolition.
- CRZ (Coastal Regulation Zone): classification of coastal land, high-tide-line reference, and prohibited activities near the coast. In a low-lying region bordering the Gulf of Khambhat this is not decorative; it interacts directly with the environmental constraints covered in the master plan.
- Fuel stations: traffic, entry and exit design.
- Signs and hoardings: permission and design rules, with prohibited sign types.
- Mining and quarrying, including brick kilns.
- Grey water reuse: recycling byelaws and water-related incentives for non-potable reuse.
- Slum rehabilitation, hospitals, hotels, and accessibility requirements for physically handicapped users.
The pattern is worth noticing: a development-control framework of this ambition does not only regulate the normal case. Coast, heritage, fuel, industry, housing, accessibility each get their own rulebook.
11.14 Regulatory approvals: how the layers stack
A building permission is one approval among several. In practice, a development in Dholera may also touch environmental clearance, pollution-control consent, CRZ clearance where the coast is relevant, and industrial-activity approvals depending on the use. The draft DGDCR's own chapters on pollution, fire protection and structural safety exist partly so that building-level requirements align with those external regimes rather than duplicating or contradicting them.
Who holds which approval power (DSIRDA, the state, national bodies) belongs to the section's governance chapter: see Chapter 7 · Governance. The approval status of any specific project today belongs in Chapter 6 · Ground reality.
11.15 How to read development regulations
Anyone who has squinted at a regulation PDF at midnight knows the feeling: 274 pages, every ordinary word redefined, and the number you need hiding in a table on page 190. A few habits make documents like this readable instead of intimidating:
- Start with the definitions chapter. The draft DGDCR opens with 123+ defined terms, and in these documents "building", "FSI" and "low-rise" never mean quite what you assume. Reading definitions first prevents most misreadings.
- Read the control tables, not the prose, for numbers. Per-zone control tables are where the actual limits live. Prose explains intent; tables carry values.
- Check applicability chapters. Almost every regulation says whom it applies to and what is exempt. That chapter decides whether the rule reaches your plot at all.
- Distinguish draft from notified. The five-layer rule applies hard here: a draft regulation is plan-status. Values quoted from a draft are proposals, not law, until a notification says otherwise.
- Trace every limit to its table and date. If someone quotes an FAR, a height or a setback, the right response is a question: which regulation, which table, which version, notified when?
That last habit is the reason this page explains concepts and withholds numbers. In a framework still anchored to a 2012 draft, the responsible statement about any specific limit is that it requires verification against the notified regulations. That verification, against DSIRDA records, is exactly what our verification method is built for.