Chennai’s proposed street design guidelines could change how the city plans and builds roads by requiring vehicles, pedestrians, trees, public transport, utilities and drainage to be considered as parts of one cross-section rather than as separate projects. The draft, being prepared by the Chennai Unified Metropolitan Transport Authority (CUMTA), is an attempt to address a basic weakness in urban infrastructure: different government agencies often build different elements of the same street without a common design governing how they fit together.
The draft guidelines are under discussion among departments and are expected to be released in the next four to six weeks, according to a senior CUMTA official quoted by DT Next. The proposal is also expected to receive legal backing through a government notification. As the official put it, “Once the GO is issued, it will become the rule.” Until that notification is issued, however, the framework remains a proposal rather than an enforceable citywide standard.
That distinction matters because Chennai already has several requirements governing roads. The CUMTA official acknowledged that provisions exist in Indian Roads Congress guidelines and in earlier guidelines issued by different agencies. The stated problem is not necessarily the absence of every individual requirement. It is that these requirements are dispersed across documents, departments and established practices. CUMTA’s intervention is to bring them together into a single, road-width-wise checklist that can guide future works.
This is an institutional change as much as a design exercise. A road is rarely delivered by one agency from start to finish. Its carriageway, footpaths, stormwater drains, utility lines, trees, public transport facilities and parking arrangements may involve different authorities and different project decisions. When those decisions are made independently, the finished street can have disconnected footpaths, utilities placed where future works will disturb them, inadequate space for trees or drainage, and road widths that exist on planning documents but cannot be delivered on the ground.
The proposed framework divides roads into widths ranging from 9 metres to 60 metres. It provides different requirements for local streets, collector streets, sub-arterial roads and arterial roads. The checklist identifies which elements can be accommodated at each width, including footpaths, cycle tracks, tree corridors, medians, service lanes, public transport infrastructure, Metro-related infrastructure, parking and multi-utility zones.
The use of road width as the organising principle is significant. It acknowledges that a narrow local street cannot be designed like a major arterial road, while also setting out how limited space should be divided. The intention, as described by CUMTA, is not simply to reserve space for moving vehicles. It is to establish the relationship between the carriageway, footpath, utility zone, tree corridor and drainage infrastructure before construction or redevelopment takes place.
A 12-metre local street such as Conron Smith Road and Prakasam Salai illustrates the proposed approach. Under the draft example, the street would have a six-metre, two-lane carriageway, two-metre footpaths on either side and one-metre tree corridors on both sides. On-street parking would not be included in that cross-section. The example shows how the framework could turn a broad principle—sharing street space—into a measurable layout.
The provision for drainage is another important feature. Under the proposed approach, the carriageway, footpath, utility space and stormwater drain would be positioned in relation to one another so that water naturally moves towards the drain. This treats drainage as part of the street’s geometry rather than as an installation added after the road has been designed.
For Chennai, where the condition and performance of urban streets depend on several systems operating together, that coordination is central. A road can be structurally sound and still perform poorly if its drainage is disconnected, its footpaths are interrupted, its utilities repeatedly require excavation or its tree space is not protected. The draft guidelines place these elements in one planning conversation, although their eventual effectiveness will depend on how departments apply the checklist in project preparation and execution.
The proposed framework also responds to a more permanent problem: development can make planned road widening or road protection difficult after the surrounding area has been built. The CUMTA official described cases where a road may be shown as 36 metres wide on paper, but houses have subsequently come up on the road alignment. Creating the planned road later can then require relocation and substantial expenditure.
This makes the draft relevant to land-use control and development management, not only to engineering design. If a road network identified during planning is protected through subsequent development, future projects may have a clearer right of way. If it is not protected, the city can be left with a gap between the road shown in planning documents and the road that can actually be constructed. CUMTA says the single checklist is intended to prevent that gap by ensuring that planned road space is preserved as development proceeds.
The scope of the framework is primarily forward-looking. It would guide new assets and future works. Existing streets could be brought under it when major projects alter their geometry. This limits the immediate reach of the proposal but also reflects the physical difficulty of retrofitting fully compliant streets into already built-up neighbourhoods. Existing roads contain established buildings, property edges, utility networks, parking practices and travel patterns. Applying a new cross-section to them may require changes beyond resurfacing or lane marking.
That distinction creates two different implementation tracks. New roads and new assets can potentially be designed around the framework from the beginning. Existing roads would encounter the guidelines mainly when a major project creates an opportunity to change their geometry. The source material does not establish how compliance will be monitored in either case, which agency will arbitrate conflicts between project requirements, or what process will apply when the recommended elements cannot fit within the available right of way.
The draft’s proposed legal backing could address one part of that problem by giving the framework a common administrative status. At present, the requirements are described as being spread across different guidelines and practices. A government notification could make the CUMTA framework a common reference for departments. But the notification alone would not resolve the practical questions of funding, land protection, coordination, construction sequencing or maintenance responsibility. Those questions will determine whether the rulebook changes streets on the ground.
The checklist also brings different policy priorities into the same physical space. Footpaths and cycle tracks relate to non-motorised movement. Public transport infrastructure and Metro facilities require space and operational access. Tree corridors introduce a long-term landscape and environmental function. Multi-utility zones seek to organise services that would otherwise compete for space or require repeated excavation. Stormwater drains connect street design to rainfall management. Parking and service lanes affect how the available width is used and how vehicles interact with the street edge.
The draft therefore treats road width as a finite urban resource. Every additional function requires space, and the proposed road categories make those trade-offs visible before construction. The 12-metre example demonstrates that this is not an exercise in assigning every possible feature to every street. The available width determines what can be included, while the checklist is intended to make that decision consistent rather than leaving it entirely to individual projects.
The evidence currently available is limited to the draft framework and the explanation provided by the CUMTA official. The proposed road-width range is 9 metres to 60 metres. The expected release window is four to six weeks. The example local street is 12 metres wide, with a six-metre carriageway, two-metre footpaths and one-metre tree corridors on both sides. The source does not provide a citywide inventory of roads, a cost estimate, an implementation budget, a compliance mechanism or a timetable for the government notification.
Those missing details are important because a design standard becomes an urban governance tool only when it is connected to decisions about land, money and accountability. Protecting a planned road may require development controls. Aligning utilities may require departments to share project schedules and drawings. Providing tree corridors may require a maintenance arrangement. Integrating drainage may require coordination with broader stormwater planning. The draft identifies the physical relationship between these elements, but the supplied material does not yet explain how institutional responsibilities will be divided.
The larger question raised by Chennai’s proposed street design guidelines is whether the city can move from project-by-project construction to coordinated street management. CUMTA’s draft recognises that streets are not just carriageways for vehicles. They are shared infrastructure corridors that carry people, water, trees, utilities and public transport systems at the same time. Its proposed value lies in placing those functions within one design framework before agencies commit to separate works.
The next test will come when the draft is released, departments complete their discussions and the government decides whether to issue the proposed notification. At that point, the framework’s practical strength will depend on the clarity of its checklists, the protection of planned rights of way, the treatment of existing streets and the institutional process for enforcing a common design across agencies. For now, CUMTA has identified the coordination gap; the pending rulebook and notification will show whether Chennai can close it.
