Master Plans & Development Plans

Start with what a statutory plan actually is, because the word 'plan' misleads. In casual speech a plan is an intention; in Indian urbanism it is a legal instrument with the force of law behind it. A development plan or master plan is a map, adopted under a state Town and Country Planning Act, that divides a city into zones and says, plot by plot, what each parcel of land may be used for and how intensely it may be built. Once notified in the official gazette, that map binds every owner, every builder and the government itself. You cannot lawfully put a factory on land the plan marks residential, nor build ten floors where it permits three. This is a remarkable transfer of power: the plan converts private land into a public question, subordinating the owner's wishes to a collective vision of how the city should grow. Patrick Geddes, working in Indian cities a century ago, insisted that such a vision must begin with 'survey before plan', a diagnosis of the living city before any prescription. The master plan is the modern, statutory descendant of that idea, though as we will see it often forgets Geddes's humility. Understanding the plan as law, not aspiration, is the first move: it explains why development control feels rigid, why deviations require formal permission, and why the plan is fought over so bitterly by owners, builders and citizens alike.

Indian planning is organised as a nested hierarchy, each tier broader and longer in horizon than the one below, each meant to guide and contain the next. At the top sits the perspective plan, a twenty to twenty-five year statement of vision, policy and broad spatial strategy, light on detail. Below it, the regional plan covers a whole region or metropolitan area, coordinating growth across many local bodies, deciding where satellite towns, major transport corridors and green belts should go; the National Capital Region plan, which reaches across Delhi and parts of neighbouring states, is the best-known Indian example. Then comes the layer most people mean when they say 'the plan': the development plan or master plan, which covers a single city or urban area over roughly twenty years and fixes the land-use zoning that governs each plot. Beneath it, the zonal plan or local area plan refines a district of the city to a finer grain, and at the base the town-planning scheme or layout plan works at the level of a few hundred hectares, laying out actual roads, plots and reservations. The URDPFI Guidelines, issued by the Town and Country Planning Organisation, codify this stack and recommend the horizons and contents of each tier. The logic is elegant on paper: broad vision narrows step by step into buildable detail, and each plan should nest cleanly inside the one above, so that a decision taken at the plot level can always be traced up to a regional intention. In reality the tiers are unevenly present: many cities have a master plan but no functioning regional plan above it, and few have the finer local-area tier below it, so the master plan is asked to do work at scales it was never designed for. The figure shows the tiers as a pyramid, strategic at the top, on-ground at the base, and the missing middle tiers are exactly where much of Indian planning quietly breaks down.

Open an actual master plan and you find two things: a set of maps and a book of proposals. The core map is the land-use plan, which colours the city into zones, residential, commercial, industrial, public and semi-public, recreational, transport, agricultural and so on, each with a permitted list of activities. Overlaid on it are the road network and hierarchy, reservations for public purposes such as schools, hospitals, parks and markets, and often a floor space index or FSI regime that caps how much floor area may be built per unit of plot. The accompanying report sets population and employment projections, the assumptions behind them, and the standards, so many hectares of park per thousand people, so many schools per neighbourhood, drawn from URDPFI norms. The Master Plan for Delhi, prepared by the Delhi Development Authority, is the most famous Indian example, running through successive editions that have reshaped the capital's growth, its density and its notorious controversies over unauthorised colonies. Mumbai's Development Plan, prepared by the Municipal Corporation of Greater Mumbai, plays the same role for that city, and its FSI and reservation battles are followed like a spectator sport, because in a land-starved island city every decimal point of floor space translates into enormous value. Note too that the map is only as good as its base: an existing land-use survey drawn from stale imagery, or a road network that ignores how people already move, bakes error into every downstream decision. The master plan, in short, is where a city's demographic guesses, its infrastructure ambitions and its politics of land all get written into a single, litigable document, which is why reading one well means reading its assumptions as carefully as its colours.

The plan-making process follows a broadly common sequence, though its details vary by state statute. It begins with the existing land-use survey, a painstaking mapping of how every parcel is currently used, increasingly done with satellite imagery and GIS. Then come the studies: population projection over the plan period, economic base analysis, traffic and infrastructure assessments, and an inventory of what the city lacks. From these the planners prepare a draft plan, allocating land to uses for the projected population and reserving parcels for public needs. Crucially, the draft is then published for public objections and suggestions, a statutory window in which any citizen may formally object, followed by hearings. The plan is revised in light of objections, sent to the state government for sanction, and finally notified in the gazette, at which point it becomes law. Implementation and enforcement follow, and periodic review, typically as the plan nears the end of its period, feeds the next cycle. The figure traces this loop. In practice each stage is fraught: surveys go stale, projections miss the mark, the objection process is dominated by organised interests, and sanction can take years, so that a 'twenty-year' plan may be notified when a quarter of its horizon has already elapsed. Understanding the process explains both the plan's legitimacy, it is participatory and legally sanctioned, and its sluggishness.

For all its authority, the master-plan model draws sustained criticism, and a serious planner must hold both its value and its flaws in mind. The central charge is that it is a static, end-state blueprint imposed on a dynamic, uncertain city. It fixes a picture of the city twenty years hence and assumes growth will politely fill the coloured zones, when real cities grow in surges, informally, and in directions no projection foresaw. It tends to under-provide for the poor: by zoning generously for formal development and ignoring how the majority actually house and employ themselves, it can render much of a city's real economy 'unauthorised' overnight. Its rigidity invites the very violations it condemns, since the gap between the plan and the ground is bridged by ad hoc regularisation, discretion and, too often, corruption. Critics point out that the model was borrowed from mid-century Britain and never fully adapted to Indian realities of informality, weak enforcement and rapid growth. The response has not been to abandon planning but to reform it: toward more flexible, phased and strategic plans, toward local area plans and town-planning schemes that deliver serviced land rather than merely colouring maps, and toward continuous planning that updates rather than freezes. Some states have begun experimenting with hybrid approaches that pair a strategic long-range plan with rolling, shorter local plans and with land-pooling schemes that actually assemble and service land, so that the plan produces development rather than merely permitting it. The master plan remains indispensable as the legal backbone of the city, giving zoning its authority and citizens a document to contest, but the thoughtful planner treats it as a framework to be steered, not a prophecy to be fulfilled, and never mistakes a coloured map for a built city.

For anyone who designs or builds in an Indian city, the master plan is not abstract theory but the first document you must read. It tells you the zone your site sits in and therefore what you may build, the FSI you are allowed, the setbacks and road lines that constrain your footprint, and any reservation that may cut across your plot. It also reveals the city's intentions around you, where a new road or metro is planned, where density is being pushed, where a green belt forbids growth. A designer who reads the plan early designs with the grain of the city's legal future; one who ignores it discovers the constraints late and expensively. But reading the plan also means reading its silences and its lag: the notified plan may be years old, amendments may be pending, and the local development authority holds the authoritative, current interpretation. The professional habit, then, is to obtain the sanctioned plan and its zoning for the specific plot, check for amendments, and confirm the reading with the planning authority before committing a design. The plan is powerful precisely because it is law, and law rewards those who read it carefully and defer, on the specifics, to the body that administers it.