DPI Deep Dive — Wednesday | October 07, 2026

Focus layer: L3 — Documents & Data Exchange (DigiLocker, National Academic Depository, API Setu and eSign)

Coverage period: 30 September–7 October 2026 (IST)

Executive summary

This week’s clearest L3 signal is credential portability moving into skills and recruitment: reports say Uttar Pradesh Skill Development Mission certificates have been linked to DigiLocker and the National Academic Depository. GATE 2027’s application deadline also put the document wallet into the exam-registration journey, though the official handbook’s language is not a clean “mandatory” rule. Two government process updates show the other side of the document story: PIB accreditation renewal accepts online uploads but still asks for an original letter in person, while a Health Ministry campaign targets review of thousands of electronic files. The common test is no longer whether a document can be digitised; it is whether it can be verified, corrected, shared by consent and used without trapping the person who needs it.

1. Uttar Pradesh puts skill certificates on the academic-document rail

On 4–5 October, two news outlets reported that certificates issued under the Uttar Pradesh Skill Development Mission (UPSDM) had been integrated with DigiLocker and the National Academic Depository (NAD). They said candidates can access, download and share skill-training records with employers or educational institutions; the reports also say UPSDM completed institutional registration, prepared digital certificate formats and digitised earlier records, with support from the National e-Governance Division and Digital India Corporation.^{1 2}

This is a useful expansion of what counts as a portable credential. Academic repositories are often imagined as a degree-and-marksheet service. Skill awards can instead document short courses, occupational competencies and assessment outcomes that matter when a worker applies for a job or continues training. If an employer can check a digitally issued certificate with its issuer, the applicant need not depend on a photocopy, a training-centre contact or a slow letter confirming completion. Putting prior awards online also matters: otherwise a new digital pathway benefits only the latest cohort while people who trained earlier remain stuck with paper.

There is an important evidence limit. The integration is reported by media, but I did not find a directly linked UPSDM, Uttar Pradesh government or MeitY announcement confirming the number of records uploaded, the certificate types covered, or the date on which employers could begin verification. The claims should therefore be read as a reported integration, not as a measured rollout. DigiLocker and NAD’s published model is institution-issued credentials that a learner can access and share, with verification by authorised organisations; that model does not mean every employer automatically gets access to a person’s file.³

The next proof points are practical, not celebratory: a public issuer listing, a working sample credential, a documented verification path, a correction channel for a misspelt name or wrong course record, and clear terms for sharing. A QR code or a portal lookup is only useful if it points back to the recognised issuer and reports whether the credential is valid, superseded or withdrawn. The holder should be able to show one certificate without exposing unrelated education or identity records. That is where the L3 promise meets L1 identity and the DPDP-era expectation of purpose-limited disclosure.

2. GATE’s DigiLocker wording deserves a precise reading

The GATE 2027 application window’s extended deadline fell on 5 October. DigiLocker appeared in the registration guidance and in coverage of the deadline, but the official information brochure is more qualified than headlines saying it is compulsory. In its application guidance, the brochure says a verified DigiLocker account is “recommended” for a smoother process; elsewhere it says Indian nationals “may need” to register through DigiLocker. The same document requires live facial details during registration and an original photo ID at the exam centre.⁴ Some coverage compressed this into an unconditional requirement, so applicants should follow the live GOAPS instructions rather than assume that every report accurately describes the rule.⁵

That distinction is consequential. A recommended identity wallet can reduce repeated entry and make a trusted document easier to present. A compulsory wallet turns the account, its phone-number linkage and its recovery process into part of the exam’s eligibility infrastructure. Any failed verification, stale mobile number, name mismatch or inaccessible account could then become a deadline problem for a candidate who is otherwise eligible. The handbook’s “recommended” and “may need” formulations leave room for more than one reading; a high-stakes national exam should publish a plain-language answer on who must use DigiLocker, what alternative route exists, and how a candidate can appeal a mismatch.

GATE is also a useful reminder that the “document wallet” and the identity layer are not the same thing. The exam’s process combines a credential source with face capture, application particulars and a physical ID check at the test centre. That may strengthen fraud controls, but it creates several points where records can disagree. Candidates need a way to correct the source record before the final edit window, see which data was pulled into the application, and know which organisation is responsible for fixing an error. Portability is not a substitute for redress.

The official schedule listed the October 5 extended close date and later application correction dates. For this cycle, the practical question is whether candidates who encounter a locker or identity mismatch can still correct their application through the stated process. For future cycles, the better standard is to define the fallback before registration opens, not after applicants discover it in the help queue.

3. PIB accreditation goes online—but keeps one paper handoff

A 5 October PIB media advisory opened the renewal window for 2027 accreditation cards. Existing accredited journalists were told to sign in to the accreditation portal with their current user ID and password, submit the renewal form online and upload essential documents online only. The advisory also says the editor’s recommendation letter must be submitted in original at the National Media Centre when the card is collected; PIB may ask for further supporting documents in physical or online form.⁶

This is not DigiLocker integration, and it should not be marketed as such. It is a narrower but revealing document workflow: an online application and digital uploads coexist with a physical original at the final handoff. That may be justified for this credential, but the public notice does not explain why a paper original is needed after online submission, how a journalist can track document acceptance, or how to challenge a rejection caused by a supposedly “wrong/irrelevant” upload. It also states that alternative documents will not be considered at any stage, which makes clarity about the accepted list especially important.

The lesson for data exchange is that a portal can move the form online without making the underlying proof reusable. An applicant may still have to upload scans the government already holds elsewhere, then carry an original to a counter. A mature document system would state what evidence is required, allow an authorised issuer check where possible, disclose the review status, and explain how to fix a rejected attachment. If the paper handoff remains necessary, the rule should say what it verifies and provide a receipt. “Online-only upload” and “digital end-to-end” are not synonyms.

There is also an access implication: the renewal is restricted to journalists resident in Delhi and nearby named cities, but the advisory provides telephone and email support for form-filling problems. A digital process can reduce travel for routine steps while still shifting costs onto applicants who have poor connectivity, inaccessible scans or trouble with an old account. The support channel and the correction process are part of the service, not incidental customer care.

4. The e-file campaign is about record management, not public exchange

Special Campaign 6 began on 2 October across the Department of Health and Family Welfare’s offices and institutions. The ministry’s PIB release says 60,012 physical files and 10,020 e-files were identified for review, alongside targets at 2,017 sites and 12 rules or processes for simplification. The campaign runs through 31 October and includes grievance disposal and office-record review.⁷

The e-file count connects this week’s document theme to L6 governance, but the distinction matters: reviewing an electronic administrative file is not the same as making a citizen’s record portable across departments. The target is a record-management exercise—reduce unnecessary files, improve handling and streamline office functioning. It tells us that government offices have a substantial digital file inventory; it does not tell us whether those files use interoperable formats, have retention schedules, carry reliable audit histories or can be accessed by the people affected by decisions recorded inside them.

The ratio is also easy to overread. The release identifies roughly one e-file for every six physical files for review, but it does not say these are all the department’s records or that digitisation is only one-sixth complete. Nor does “review” establish that a file has been lawfully disposed of, retained under a schedule, or made searchable. Those are separate outcomes. A useful campaign dashboard would report completed reviews, disposal and retention decisions, e-waste handling, grievance closures and the safeguards used to preserve records needed for audits, appeals or litigation.

What links these developments

The week’s document infrastructure is advancing at three different points in a record’s life: an issuer publishes a credential; an applicant presents it to a high-stakes process; and an office reviews its internal files. A response issued on 12 August provides scale context, not a new event: MeitY told the Rajya Sabha that, as of 31 July, DigiLocker offered 5,437 document types or services—661 Central and 4,776 State.⁸ That breadth makes the quality of each issuer’s data and the user’s ability to contest it more important, not less.

The cross-layer links are clear. Aadhaar and face checks support identity assurance; DigiLocker and NAD carry records; API Setu can enable service-to-service connections; eSign can bind an action to a person and a document; grievance systems determine whether a bad record can be corrected. This week surfaced activity around credentials and files, but no new primary-source API Setu or eSign launch was identified in the material reviewed. The useful measure of L3 progress is not another registration count. It is whether the person can access an authoritative record, consent to a narrowly scoped share, understand what was checked, and correct an error before it costs them a job, exam or entitlement.

What to watch

• Whether UPSDM’s certificates appear in the official issuer catalogue, with a public verification path and a correction process.
• A definitive GATE 2027 clarification on whether DigiLocker use is required for Indian applicants and what fallback applies to account or record mismatches.
• Whether PIB publishes an accepted-document checklist, status tracking and a rationale or alternative for the original editor’s letter.
• Special Campaign 6’s final figures: e-file reviews completed, retention/disposal decisions and grievance closures—not only files identified.
• Any dated MeitY or NeGD release on API Setu or eSign that turns this week’s document activity into a verifiable data-exchange change.