Tamil Nadu’s recent building-approval reforms were intended to reduce clearance delays by expanding local-body powers, allowing third-party certification and increasing permissible building heights in specified cases. But in Chennai, the reforms have collided with an online planning system that has not yet been updated and a separate Chennai Metropolitan Development Authority (CMDA) portal facing recurring technical failures. The result is a digital bottleneck at the very point where regulatory simplification was meant to make construction approvals faster.
The Times of India reported that builders are facing delays on two fronts. Local bodies, including the Greater Chennai Corporation, have not incorporated the latest regulatory changes into the single-window planning portal. At the same time, developers using CMDA’s existing online approval system have reported problems with submissions, document uploads, revised drawings, statutory no-objection certificates, payments, digital signatures and application tracking.
This is not simply a software inconvenience. Planning permission is the administrative gateway through which a project becomes legally buildable. When the rules available to applicants, the software used to assess them and the departments responsible for issuing connected approvals do not operate from the same framework, a reform can exist on paper without becoming usable in practice. The reported delays show how dependent construction activity has become on the reliability of the state’s digital approval infrastructure.
The government rolled out Government Orders 179, 180 and 194 nearly a month before the report was published. GO 179 allows registered architects and Grade-I engineers to certify specified residential, commercial and industrial buildings. GO 180 delegates approval powers to local bodies for residential projects up to 1,500 square metres of floor space index and commercial buildings up to 500 square metres of floor space index. GO 194 revises certain building height limits from 18.3 metres to 19.5 metres and changes provisions related to road width, setbacks and parking.
Each of these changes requires more than a notification. The approval portal must recognise the revised thresholds, accept the relevant documents and route applications to the correct authority. Its scrutiny rules must also reflect the new requirements. If the system continues to apply earlier parameters, applicants cannot access the relaxation even when they are legally entitled to seek it. That gap between regulation and software has reportedly left more than 1,000 proposals in limbo.
S Ramaprabhu of the Builders’ Association of India said the government should have updated the portal software before rolling out the portal. According to him, applicants are unable to submit proposals under the revised provisions or access the intended relaxations. The problem therefore concerns both stalled applications and the credibility of the single-window model itself. A portal that brings multiple approvals into one digital interface only reduces friction when the underlying rules and workflows are current.
The Greater Chennai Corporation has acknowledged that the update is pending. Commissioner G S Sameeran said the update would be done soon. The statement indicates that the immediate obstacle is known to the administration, but the report does not specify a completion date, the number of local bodies still awaiting the update or whether applications already filed under earlier rules will be automatically migrated to the revised framework.
The separate CMDA portal problems are broader than a missing rule update. CREDAI Chennai, in a representation dated October 26 to CMDA, listed difficulties involving initial application submission, document uploads, revised drawings, statutory no-objection certificates, payment of charges and tracking of application status. Developers also reported issues with completion-certificate acknowledgements and access to essential services after completion certificates had been obtained.
A developer quoted in the report said the failures were recurring and were not limited to particular applications. The reported problems extend across initial submission, scrutiny, fee payment, receipt generation, digital signature, issuance of planning permission and completion-certificate applications and approvals. This pattern matters because it suggests a chain of operational failures rather than a single defective screen or isolated application error. Every stage creates a possible delay, and an application may be affected again even after an earlier technical issue has been resolved.
The consequences also extend beyond the planning authority. According to the developer, some applicants who had obtained completion certificates and approached the Chennai Metropolitan Water Supply and Sewerage Board for connections were told that infrastructure development charges payable by CMDA had not been transferred. The account presented in the report links the planning approval process to the delivery of essential utility connections. In practical terms, a project can move through one approval milestone and still face a further administrative obstacle before it can receive services.
The developer called for government intervention so that applicants are not charged interest or penalties when delays are caused solely by technical failures in the portal or related systems. The source material does not establish whether such charges have been imposed in specific cases, but the request highlights an important allocation-of-risk question: when a public approval system fails, applicants may still bear the financial consequences through delayed launches, extended borrowing periods and postponed access to services.
The reported financing impact is significant for the construction sector. Developers said the twin problems are affecting project schedules, increasing financing costs and holding up new launches. The report does not provide a total value for the projects involved or quantify the additional cost. It does, however, identify the mechanism clearly. A stalled submission delays approval; a delayed approval postpones construction or launch activity; and the resulting extension increases the period for which project capital remains tied up.
The reform architecture also reveals a division of responsibility. The state government issued the regulatory changes. Local bodies must update the single-window planning portal and exercise the approval powers delegated to them. CMDA operates its own online approval system and is responsible for addressing technical problems affecting applications and completion certificates. CMWSSB becomes relevant when applicants seek water and sewerage connections and related charges have to be transferred. The applicant experiences this as one approval journey, but the administration manages it through several institutions and digital systems.
That institutional fragmentation is central to the Chennai case. A single-window portal can simplify the applicant’s interface without necessarily creating a single administrative system behind it. If rule changes are issued by one authority, implemented in software by another and connected services depend on financial or digital transfers between agencies, the speed of the final approval depends on coordination across the entire chain. The reported failures show that digital governance cannot be assessed only by whether an application can be submitted online.
CMDA has formed a special team headed by its chief planner and senior planner for e-governance to address the issues. A senior CMDA official also said the authority was floating a tender for a new artificial-intelligence-based online planning permission application. These are the two stated administrative responses: immediate troubleshooting through a dedicated team and a longer-term replacement or upgrade of the existing system.
The available information does not establish the scope, cost, procurement timeline or functionality of the proposed AI-based system. It also does not indicate when the current portal’s recurring failures will be fully resolved. Those details will determine whether the new system addresses the reported problems or adds another layer to an already divided approval architecture.
Chennai’s experience underlines a wider governance problem in building regulation: policy reform is only as effective as the operational systems that deliver it. Third-party certification, delegated powers and revised development standards can shorten approval timelines only when applicants, officials and connected agencies are working with the same rules and reliable digital tools. In this instance, the reform has moved faster than the systems meant to implement it.
The immediate facts are therefore clear but incomplete. More than 1,000 proposals were reported to be stuck, regulatory updates had not yet been incorporated into the relevant planning portal, CMDA’s online system was facing failures across multiple stages, and a special team had been formed to respond. The next measurable milestones are the software update for the revised government orders, the resolution of CMDA’s existing portal problems and the tendering and implementation of the proposed new online planning permission system.
