Where Does This Sit in Government?

Where Does This Sit in Government?

Large national digital initiatives rarely fail because of software.

They fail because no institution is clearly accountable for them.

Before architecture diagrams, APIs, or pilot projects are discussed, every ministry and department asks a quieter, more consequential question:

Who owns this—and who carries the risk?

If that question is not answered unambiguously, initiatives do not collapse publicly.
They slow down, fragment across departments, and eventually become optional.

The Saptarishi Framework faces this exact test.

The built environment touches nearly every arm of the state: urban development, land records, transport, environment, finance, municipal governance, and disaster response. This breadth creates a structural challenge. Systems of this kind are too operational for pure policy bodies, too cross-sectoral for a single line ministry, and too consequential to be treated as pilot software.

Without deliberate institutional placement, such initiatives drift. They are overseen by committees, trialled repeatedly, but owned by no one.

India has seen this pattern before.

India’s most successful Digital Public Infrastructure systems—Aadhaar, UPI, DigiLocker—followed a clear and consistent logic. They were anchored centrally, executed federatively, and owned institutionally rather than personally. Policy authority and technical stewardship were separated. Adoption followed because friction was reduced, not because compliance was forced.

The lesson is simple: placement determines longevity.

The Saptarishi Framework is not a sectoral IT platform. It is governance infrastructure for the built environment. That distinction matters.

Its placement must reflect three realities. First, national policy authority is required for consistency. Second, digital standards stewardship is required for interoperability. Third, state and municipal autonomy must be preserved for adoption.

What it must not become is equally important. It cannot be a “smart cities” sub-project. It cannot be a standalone BIM mandate detached from land, finance, and municipal systems. It cannot be a project-management-unit experiment without statutory continuity.

Land, planning, and municipal approvals are state subjects in both law and practice. Any national digital system that threatens this control—even unintentionally—will face quiet resistance.

The design principle therefore has to be explicit:

States own their data.
The Centre owns interoperability.

This is not a political compromise. It is a technical necessity for national scale.

Once platforms are built, placement becomes political. Once pilots run without ownership clarity, failures are blamed on “technology.” The correct sequence is non-negotiable: institutional anchoring first, clear stewardship roles second, federated execution design third, and only then pilots and platforms.

Skipping this order does not accelerate reform. It makes reversal easy.

This discussion is not really about ministries or organisational charts. It asks a deeper question: is India prepared to treat the built environment as critical national infrastructure—digitally?

If the answer is yes, institutional placement becomes obvious. If not, fragmentation persists regardless of technical sophistication.

Next in the series — 31 March 2026
What Changes First — Law, Policy, or Software?