On 18 August 2026, the Unique Identification Authority of India (UIDAI) announced that its nationwide mission-mode drive for Mandatory Biometric Updates (MBU) has completed over 2 crore (20 million) updates for school children, covering over 1.56 lakh schools.
The drive, initiated in September 2025, was enabled by UIDAI's technological integration with UDISE+ — the Unified District Information System for Education Plus — which gives visibility of the MBU status of children at their schools. Updates were delivered through school-level camps and coordinated outreach by UIDAI and State and UT education departments.
This is administratively unglamorous and analytically excellent. It is a clean case study in something CDS/OTA papers increasingly reward: how a delivery system fails quietly, and what fixing it actually requires.
Why MBU exists at all — the biology
The reason is physiological, and stating it precisely is what separates a good answer from a vague one.
When a child under five is enrolled for Aadhaar, the enrolment captures demographic information and a photograph only. Fingerprints and iris biometrics are not captured, because at that age those biometrics are still developing and are not yet stable enough to serve as a reliable lifelong identifier.
The child's biometrics therefore have to be added — and later refreshed — as they mature. Hence two mandatory updates:
- at age 5, and
- again at age 15.
The rationale for the second is the same: biometric features continue to change through childhood and adolescence, and a template captured at five will not reliably match a fifteen-year-old.
Why it matters — the failure mode
Here is the consequence, and it is the heart of the story.
Aadhaar's value in service delivery comes from authentication — matching a live biometric against the stored template. If the stored template is out of date, authentication fails. And an authentication failure does not present itself as a technical problem to the person affected; it presents as a denial.
The Authority is explicit about where this bites. A child without an updated Aadhaar may face difficulty in:
- receiving benefits under various government schemes, and
- registering for competitive and university examinations such as NEET, JEE and CUET.
Read that second one carefully, because it is the sharpest point available here. A stale biometric record can prevent a seventeen-year-old from sitting an entrance examination. The failure is invisible until the precise moment it is most costly, and it falls hardest on exactly the households least able to navigate a correction process. This is the recurring critique of authentication-dependent delivery — the same failure mode documented in Aadhaar-based PDS authentication — and it is why exclusion error is a more serious concern than inclusion error in welfare design.
Why the schools route is the interesting part
The obvious solution — tell parents to visit an enrolment centre — is what had been tried, and it under-delivers, for ordinary reasons: a parent must know the requirement exists, take time off work, travel, and queue.
The drive inverts the logic. Instead of requiring the citizen to reach the service, the service is taken to where the children already are, every day, in a known and enumerable location. The mechanism has three components worth naming:
- UDISE+ integration — the education database that makes MBU status visible per school, converting an unknown backlog into a worklist. You cannot close a gap you cannot see.
- School-level camps — delivery at the point of aggregation.
- Inter-departmental coordination — UIDAI working with State and UT education departments rather than in parallel to them.
That combination — use an existing database to locate the gap, then deliver at the point where the population is already assembled — is a transferable governance principle, and a genuinely good one to cite in an essay on last-mile delivery. It also connects to the broader logic of local governance and service delivery.
And the fee design. UIDAI waived the charge for MBU for the 7–15 age group from 1 October 2025 for one year. MBU for the 5–7 and 15–17 groups is already free. The practical effect is that MBU is free between ages 5 and 17 until 30 September 2026. Removing a small fee matters more than its size suggests, because a nominal charge is a real deterrent for a low-income household and adds a payment step to a process that otherwise has none.
The Aadhaar framework
UIDAI is a statutory authority established under the Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act, 2016, functioning under the Ministry of Electronics and Information Technology (MeitY). It was originally constituted as an executive body in 2009 and given statutory status by the 2016 Act.
The constitutional backdrop is essential context:
- K.S. Puttaswamy v. Union of India (2017) — a nine-judge bench held that the right to privacy is a fundamental right, protected under Article 21.
- Puttaswamy (Aadhaar judgment), 2018 — a five-judge bench upheld the constitutional validity of the Aadhaar Act while reading down Section 57, thereby restricting the ability of private entities to demand Aadhaar authentication. The Court sustained Aadhaar for subsidies, benefits and services funded from the Consolidated Fund of India.
Related instruments. The Digital Personal Data Protection Act, 2023 now governs personal data processing generally. UDISE+ is run by the Ministry of Education and is the principal school-education database, covering enrolment, infrastructure and teachers.
The honest balance, for a group discussion. Aadhaar-linked delivery has demonstrably reduced duplication and leakage. It has equally demonstrably produced exclusion where authentication fails — and the fair conclusion is not that authentication is wrong, but that any system which makes a benefit conditional on a successful biometric match must carry a robust, well-publicised exception route for when the match fails. A drive like this one reduces failures; it does not remove the need for that fallback.
🔑 Revision block
The announcement. 18 August 2026 — UIDAI completed over 2 crore (20 million) Mandatory Biometric Updates for school children, across over 1.56 lakh schools. Drive initiated September 2025, enabled by integration with UDISE+ (Unified District Information System for Education Plus), delivered through school-level camps with State/UT education departments.
The biology — why MBU exists. For children below five, Aadhaar captures demographic information and a photograph only; fingerprints and iris are not captured because those biometrics are still developing. Updates are therefore mandatory at age 5 and again at age 15.
The failure mode — the analytical core. Aadhaar's value in delivery comes from authentication; a stale template means authentication fails, and to the person affected that appears not as a technical fault but as a denial. Consequences named: difficulty receiving scheme benefits, and registering for NEET, JEE and CUET. A stale record can stop a seventeen-year-old sitting an entrance exam — invisible until the moment it is most costly, and hardest on households least able to fix it. Exclusion error matters more than inclusion error in welfare design.
Why the schools route works. Instead of requiring the citizen to reach the service, take the service to where children already are. Three components: UDISE+ integration turns an unknown backlog into a visible worklist · school-level camps deliver at the point of aggregation · inter-departmental coordination with State/UT education departments. The transferable principle: use an existing database to locate the gap, then deliver where the population is already assembled.
The fee design. MBU charges waived for ages 7–15 from 1 October 2025 for one year; 5–7 and 15–17 already free. Net effect: MBU free for ages 5–17 until 30 September 2026. A nominal fee deters low-income households more than its size suggests.
The institutional frame. UIDAI — a statutory authority under the Aadhaar Act, 2016, functioning under MeitY; originally constituted as an executive body in 2009. UDISE+ is run by the Ministry of Education.
The case law — asked in its own right. K.S. Puttaswamy (2017) — nine judges — privacy is a fundamental right under Article 21. Puttaswamy (Aadhaar judgment, 2018) — five judges — upheld the Aadhaar Act but read down Section 57, restricting private entities from demanding authentication; Aadhaar sustained for subsidies, benefits and services from the Consolidated Fund of India. Data processing generally now governed by the DPDP Act, 2023.
The honest balance, for GD. Aadhaar-linked delivery has reduced duplication and leakage, and has produced exclusion where authentication fails. The conclusion is not that authentication is wrong, but that any benefit made conditional on a biometric match needs a robust, well-publicised exception route. Drives like this reduce failures; they do not remove the need for the fallback.
🎯 Practice MCQs
Q1. Mandatory Biometric Update in Aadhaar is required at ages: (a) 5 and 15 (b) 5 and 18 (c) 7 and 15 (d) 10 and 18 → (a).
Q2. For children below five, Aadhaar enrolment captures: (a) demographic details and a photograph (b) fingerprints only (c) iris only (d) full biometrics → (a) — those biometrics are still developing.
Q3. UIDAI's school drive was enabled by integration with: (a) UDISE+ (b) DIKSHA (c) PM e-Vidya (d) NDEAR → (a).
Q4. UDISE+ is maintained by the: (a) Ministry of Education (b) MeitY (c) UIDAI (d) NITI Aayog → (a).
Q5. The number of MBUs completed under the drive is over: (a) 2 crore (b) 1 crore (c) 5 crore (d) 50 lakh → (a) — across about 1.56 lakh schools.
Q6. MBU is currently free for the age group: (a) 5–17 years until 30 September 2026 (b) 0–5 years (c) 15–18 years (d) all ages permanently → (a).
Q7. UIDAI functions under the: (a) Ministry of Electronics and Information Technology (b) Ministry of Home Affairs (c) Ministry of Finance (d) Ministry of Education → (a).
Q8. UIDAI was given statutory status by the: (a) Aadhaar Act, 2016 (b) IT Act, 2000 (c) DPDP Act, 2023 (d) RTI Act, 2005 → (a).
Q9. The 2017 Puttaswamy judgment was delivered by a bench of: (a) nine judges (b) five judges (c) seven judges (d) three judges → (a) — the 2018 Aadhaar judgment was five.
Q10. Puttaswamy (2017) held that the right to privacy flows primarily from: (a) Article 21 (b) Article 14 (c) Article 19(1)(a) (d) Article 32 → (a).
Q11. The 2018 Aadhaar judgment read down which section, limiting private use? (a) Section 57 (b) Section 7 (c) Section 33 (d) Section 139AA → (a).
Q12. Aadhaar authentication was upheld for subsidies drawn from the: (a) Consolidated Fund of India (b) Contingency Fund (c) Public Account (d) State funds only → (a).
Q13. Failure to complete MBU may affect registration for: (a) NEET, JEE and CUET (b) passport renewal only (c) voter registration (d) driving licences only → (a).
Q14. The drive was initiated in: (a) September 2025 (b) August 2026 (c) January 2026 (d) October 2025 → (a).
Q15. In welfare design, the error type of greater concern with authentication is: (a) exclusion error (b) inclusion error (c) sampling error (d) rounding error → (a).
📋 How this gets asked (PYQ pattern)
Aadhaar and digital identity are asked in four ways. The case-law item — the 2017 nine-judge privacy judgment against the 2018 five-judge Aadhaar judgment, and Section 57; mixing up the bench strengths is the classic trap. The statute item — the Aadhaar Act 2016, UIDAI's parent ministry, and the DPDP Act 2023. The procedural item — MBU ages, what is captured below five, and which database drives the school integration. The concept item — exclusion versus inclusion error, and authentication failure as a delivery risk, which recurs in governance questions generally. The fresh 2026 hook is the 2 crore MBUs across 1.56 lakh schools and the free-until-30-September-2026 window. We reference the pattern, not any exact past question.
Preparing for CDS or OTA? "Taking the service to where the population already is" is a principle you can reuse across half a dozen governance answers — from vaccination drives to enrolment camps. Follow our daily CDS/OTA current affairs and prepare with our faculty in the upcoming Cavalier courses in Delhi.
✍️ Written by Aditya Tiwari — Economy, governance & current-affairs faculty at The Cavalier. Reviewed by the Cavalier Faculty Desk. The Cavalier, founded by ex-Army officers, has trained NDA/CDS/SSB aspirants since 2001 (Facebook · YouTube).
Source: PIB / Ministry of Electronics & IT, 18 August 2026. Facts cross-verified with independent sources.