⚖️ Polity & GovernanceMAINS · GS2.15 · GS2.10

Data stays with the ministry; only the standards and identifiers travel

MoSPI convened the Statistical Advisers and Chief Data Officers of all Central Ministries, launched a quarterly data-harmonisation reporting portal, and put interoperability ahead of centralisation.

What happened

MoSPI convened the Statistical Advisers and Chief Data Officers of all Central Ministries, Departments and Organisations (MDOs) on 8 September 2026 at Rang Bhawan Auditorium, New Delhi, on data harmonisation for the use of administrative data.
Shaktikanta Das, Principal Secretary-2 to the Prime Minister, launched the Quarterly Progress Report (QPR) portal on Data Harmonisation at qpr.mospi.gov.in.
MDOs will use the QPR portal to report cataloguing of datasets, metadata preparation, use of standards, classifications and common unique identifiers, and quality checks under the Statistical Quality Assurance Framework (SQAF), with automated validation and cross-verification against the NMDS portal.
Saurabh Garg, Secretary MoSPI, separated the two posts: Statistical Advisers for statistical leadership and quality assurance, Chief Data Officers for data governance and interoperability, supported by the National Data Governance Committee.
Ministries were asked to constitute Data Governance Committees, publish data-sharing frameworks, maintain live dataset inventories and use API Setu, data.gov.in, NDAP, AI Kosh, DigiLocker, Entity Locker and e-Sankhyiki rather than build afresh.

For Prelims

QPR Portal on Data Harmonisation: launched 8 September 2026 at qpr.mospi.gov.in; every Central MDO reports its own data-readiness progress on it, with automated validation, dashboards and cross-verification against the NMDS web portal.
SQAF: the Statistical Quality Assurance Framework, the standard against which each MDO performs quality checks on its own datasets before dissemination.
NMDS 2.0: named among MoSPI's initiatives alongside SQAF, statistical classifications, data lifecycle guidelines, e-Sankhyiki, the Microdata Portal and the QPR; the release does not expand the abbreviation.
Statistical Adviser vs Chief Data Officer: the SA carries statistical leadership and quality assurance, the CDO carries data governance and interoperability - two distinct posts in each Central MDO, described as complementary.
Data governance structure: a National Data Governance Committee at the top, with every Ministry asked to constitute its own Data Governance Committee, publish a data-sharing framework and maintain a live dataset inventory.
Eight existing platforms named: API Setu, data.gov.in, NDAP, AI Kosh, DigiLocker, Entity Locker, e-Sankhyiki and the microdata portal - Ministries were told to use these rather than build new ones.
Model Data Sharing Framework: presented by MeitY for secure digital data sharing; the Ministry of Corporate Affairs demonstrated API-based interoperability including beneficiary-validation use cases.
The three stated shifts: from structural to semantic interoperability, from isolated datasets to linked data ecosystems, and from data availability to data readiness - the 'road ahead' set out by the Director General (Data Governance), MoSPI.

For UPSC: The best current illustration of how India is choosing to build a state data system: not one warehouse, but common standards, unique identifiers and APIs across systems that stay where they are. Use it on e-governance and evidence-based policymaking, on the administrative-data versus survey-data question in the statistical system, and on inter-departmental coordination as the real constraint on digital governance. The SA-CDO division of labour is a concrete institutional detail worth naming in an answer.

What it is NOT: The release gives no count of anything: not how many datasets have been catalogued, how many of the MDOs actually have a Chief Data Officer or a Data Governance Committee in place, and not when the first quarterly report on the new portal falls due. It names no statute or data protection law governing the sharing of administrative data, though it says privacy and security are to be preserved.

For Mains

Syllabus: GS2.15 · GS2.10 · Linkage L2

Anchor

The interesting decision in Indian data governance is one that has been taken quietly: the state is not building a central data lake. The message from this workshop is that data need not be centralised to generate value, and that departmental ownership is to be preserved. Open with the architecture, not with the portal.

Substantiation (data)

The machinery is nameable. A Quarterly Progress Report portal at qpr.mospi.gov.in on which every Central Ministry reports its own cataloguing, metadata and identifier work; quality checks under SQAF; cross-verification against NMDS; eight existing platforms from API Setu to DigiLocker that Ministries were told to use instead of building new ones.

Exemplification

Two working demonstrations were presented rather than described. The Ministry of Corporate Affairs showed API-based interoperability for beneficiary validation, and the Government of NCT of Delhi's Data DHARA, with the National Urban Digital Mission, showed harmonised data used for real-time urban governance. Both are single-sentence examples that carry a whole paragraph.

Counterpoint

The justification offered was not statistical integrity but artificial intelligence: MeitY's position was that high-quality data is fundamental to deploying AI in governance, and MoSPI's that harmonised data is fundamental to an AI-ready government. Note that a statistical system reformed to feed models is being asked to serve an objective it was not designed for.

Problematisation

The portal asks Ministries to self-report progress, and the release publishes no baseline, no target and no due date against which that reporting can be read. Preserving departmental ownership of data preserves the departmental veto over sharing it, which is the thing that produced the silos in the first place.

Position

The gain here is not more data but legibility of the data the state already holds as a by-product of administering schemes. Argue that the binding constraint on this reform is administrative rather than technical: common identifiers and APIs are solved problems, and a Ministry's willingness to be cross-checked is not.

Deploys into: Governance and e-governance (GS2.15): interoperability without centralisation as a design choice for a national data system · Government policies and interventions (GS2.10): using administrative data for policy formulation, monitoring and outcome assessment · The statistical system: administrative data alongside surveys, and the quality framework that governs it · Inter-departmental coordination and breaking data silos in a whole-of-government approach · Digital Public Infrastructure: what standards, identifiers and APIs do that a central database does not

Ministry of Statistics & Programme Implementation · 2026-09-08 · PRID 2307982 · PIB source ↗