Significant portions of Indian regulation operate on rules whose design assumptions have lapsed. The system does not revise; it grants case-level exemptions, and exemption ossifies into a parallel regime, punctuated by quiet workarounds that change the math without touching the rule. Why is framework revision so rare, and how should a CXO decide which aged-out rule will move on the horizon they care about?
The persistence is not accident; it is calibrated institutional behaviour. Framework revision in the Government of India requires three things, each costly. Multi-ministerial coordination demands that the Department of Public Enterprises, the Ministry of Finance, the administrative ministry, and consulted policy bodies converge on a single revised text, which serialises across calendars and revisions. Fresh political ownership requires a Minister or Secretary to expend reputational capital on a reform that yields no visible programme, no ribbon-cutting, no sectoral constituency. Visible recalibration signals that the previous design was inadequate, which carries its own cost for the institutional memory of the architects.
Granting an exemption requires only the file in front of you. An individual approval for a CPSE investment cap, an individual delegation order, an individual one-time clarification, an individual notification carving a specific use case from a general rule. Each is locally rational. The cumulative cost shows up only at the system level, in regulatory drag, in compliance complexity, and in the accumulation of precedents that bind future decisions. The exemption route is a coordination good for the institution and a coordination cost for the economy, and the institutional choice that follows from this asymmetry is structural rather than discretionary. Once a class of cases starts running through the exemption channel, the channel takes on a life of its own. Standard operating procedures evolve. Internal templates form. A working knowledge accumulates among officers who specialise in the exemption rather than in the rule. The exemption becomes the regime.
Where institutional risk-taking does happen on outdated rules, it rarely takes the form of revision. It takes the form of quiet workarounds. An omnibus order from a regulator that reclassifies a class of cases without changing the underlying rule. A class-level template approved at apex that allows a category of routine instruments to be cleared without per-case adjudication. A regulatory sandbox that permits experimentation outside the prevailing rule for a defined cohort. A blanket clarification that effectively narrows the rule's reach to a smaller subset of facts. These are not framework reforms; they are framework circumventions executed inside the institution, and they often deliver more practical change than the stalled revision they substitute. A CXO who watches only for legislative or regulatory amendment, and ignores the omnibus orders and the templates, misses where most movement actually happens.
Most outdated rules in India will not be revised on a five-year horizon. Planning a market entry, a capacity expansion, or an investment thesis on the assumption that an aged-out rule will be revised is a planning error. The two productive postures are: prepare for the case-level pathway that the system actually offers, and watch the regulator and apex bodies for the quiet workarounds, because these change the operating math more reliably than reform expectations. The CXO who treats the exemption pipeline and the workaround channel as the actual locus of regulatory change in India navigates the system; the one who waits for reform pays the carrying cost of the wait.