๐Ÿ›๏ธ Polity & GovernanceMAINS ยท GS2.15

UIDAI saturates 100,000+ schools for Aadhaar biometric update

A mission-mode drive links Aadhaar's Mandatory Biometric Update to school records through the UDISE+ education database.

What happened

Background & context

Aadhaar is a 12-digit unique identity number issued to residents of India on the basis of their demographic and biometric data. The system is administered by UIDAI, a statutory authority established under the Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act, 2016. UIDAI functions under the Ministry of Electronics and Information Technology (MeitY). Before the 2016 Act gave it statutory backing, UIDAI had been set up in 2009 as an attached office of the erstwhile Planning Commission, so the body long predates the law that now governs it โ€” a distinction examiners like to test.

The biometric data captured for an adult Aadhaar holder includes the ten fingerprints, both iris scans and a facial photograph. The problem this drive addresses is biological: a young child's fingerprints and iris patterns are not yet stable, so biometrics captured in early childhood stop matching as the child grows. To keep an Aadhaar usable for the holder's lifetime, UIDAI therefore requires the biometrics to be refreshed twice in childhood โ€” once when the child turns 5 and again at 15. This refresh is the Mandatory Biometric Update (MBU). A child below 5 is enrolled using only the parent's biometrics and the child's photograph (this enrolment is sometimes called the "Bal Aadhaar" or Blue Aadhaar), which is precisely why a full biometric capture becomes due once the child crosses 5.

The novelty of the 2025โ€“26 campaign is the delivery channel, not the rule. The MBU requirement has existed for years, but uptake lagged because families had to travel to an Aadhaar enrolment centre and many simply did not, leaving large numbers of school-age Aadhaar records with stale biometrics. The fix was to take the service to where the children already are โ€” the school โ€” and to find them through the system that already lists every school child. That system is UDISE+, the Unified District Information System for Education Plus, maintained by the Department of School Education and Literacy under the Ministry of Education. UDISE+ is the country's principal administrative database for school education, capturing data on schools, teachers and enrolled students across the school system; it is the online, near-real-time successor to the older DISE/UDISE system. Integrating UIDAI's MBU status with UDISE+ let officials see, school by school, which enrolled children still owed a biometric update, converting an open-ended public appeal into a trackable, saturation-style campaign.

It helps to place UIDAI in its institutional family. India's regulatory and statutory landscape contains several authorities that aspirants routinely confuse. UIDAI is a statutory body created by an Act of Parliament; it is distinct from a constitutional body (such as the Election Commission or the Finance Commission, named in the Constitution itself) and from an ordinary executive/non-statutory body set up only by a government resolution (as UIDAI itself was between 2009 and 2016, before the Act gave it a statutory foundation). The chain of authority around Aadhaar runs from Parliament (which enacted the Aadhaar Act, 2016, originally passed as a Money Bill) to MeitY (the administrative ministry) to UIDAI (which enrols residents, issues Aadhaar numbers, sets the standards and operates the Central Identities Data Repository), with the Supreme Court having upheld Aadhaar's constitutional validity in 2018 while reading down compulsory linking for several private uses. Knowing this who-creates-whom chain is what the "statutory vs constitutional body" questions test.

For Prelims

What it is NOT: MBU is not a fresh Aadhaar enrolment and not a demographic (name/address) update โ€” it is a biometric refresh of an existing Aadhaar. It is not mandatory annually; it is due only at ages 5 and 15. UIDAI is not a constitutional body and not a regulator of the telecom or banking sector โ€” it is the statutory ID authority under MeitY. UDISE+ is not a UIDAI product; it belongs to the Ministry of Education. Aadhaar is a proof of identity, not a proof of citizenship.
The Aadhaar update set (carry the full list): (1) biometric update โ€” the MBU at 5 and 15, and the optional adult re-capture; (2) demographic/document update โ€” name, address, date of birth, gender, mobile, email, the periodic document refresh UIDAI urges every 10 years; (3) enrolment for those without an Aadhaar. The MBU belongs only to bucket (1).

Why it matters

Aadhaar sits at the base of India's digital public infrastructure. It is the authentication layer beneath Direct Benefit Transfer, subsidy delivery, scholarship disbursal, the Public Distribution System, pension and welfare programmes, and increasingly beneath private services that rely on Aadhaar-based e-KYC. A child whose biometrics have drifted out of date is, in practice, a child whose identity may fail to authenticate at the very moment it is needed โ€” when a scholarship is to be credited, a subsidised entitlement claimed, or an examination form submitted. The MBU therefore protects the usability of the foundational ID for the cohort most likely to need it for education-linked benefits.

The deeper governance point is the delivery model. By routing a UIDAI obligation through the education system's own database, the campaign demonstrates inter-departmental data integration as a tool of last-mile service delivery: two arms of government (MeitY's UIDAI and the Ministry of Education's UDISE+) joined so that the citizen need not chase the service. Doing it at the school removes the travel and access barrier that had suppressed voluntary updates, and the "saturation" framing โ€” covering every school in a district rather than waiting for walk-ins โ€” converts a passive entitlement into an actively delivered one. This is the same governance logic seen in other saturation-mode campaigns, and it is exactly the kind of administrative example a Mains answer on citizen-centric, technology-enabled governance can deploy.

For Mains

Exemplification
A concrete, current example of technology-enabled, citizen-centric service delivery: a statutory ID obligation (MBU) delivered at the doorstep โ€” the school โ€” by integrating two government databases (Aadhaar and UDISE+) so the beneficiary does not have to travel to claim a service.
Substantiation
Hard figures for any answer on e-governance scale: 103,000+ schools saturated and ~1.2 crore children served in a single mission-mode drive, with 4,000+ enrolment machines and a six-month window from September 2025.
Problematisation
The drive implicitly admits the prior gap: that a mandatory biometric update existed on paper but went uncompleted at scale because the service was not brought to the citizen โ€” a reminder that mandates without accessible delivery channels under-perform.
Way-forward
Illustrates a replicable template โ€” inter-operable government databases + saturation mode + service at the point of presence โ€” for closing last-mile gaps in welfare authentication and digital identity.
Position
Government's stated approach: keep the foundational ID lifelong-usable for children by removing the access barrier, and use a child-friendly free window (ages 7โ€“15) to drive completion rather than relying on penalties.
Deploys into: e-governance and citizens' charters; technology in last-mile service delivery; government policies and interventions for vulnerable sections (children); India's digital public infrastructure and the Aadhaar ecosystem.

Source

Ministry of Electronics & IT ยท 2026-03-03 ยท PRID 2234902 ยท PIB source โ†—