DPI Deep Dive — Saturday | October 03, 2026
Focus Layer: L6 — Governance & Grievance
Coverage Period: September 26–October 3, 2026 (IST)
India’s governance layer had a campaign-heavy week: the Centre began Special Campaign 6.0 on Gandhi Jayanti, more than 2.42 lakh Gram Sabhas were scheduled for local deliberation, the Labour Ministry took its new Shram Samvad programme into industrial districts, and CPGRAMS continued publishing daily disposal totals. The common story is not that a new portal appeared. It is that government is trying to make administration more measurable and more participatory—while still leaving open the hardest question: can a citizen see what changed after a file, meeting or complaint was marked complete?
1. Special Campaign 6.0: A cleanup drive with a records-management test
The implementation phase of Special Campaign 6.0 began on October 2 and runs through October 31. DARPG’s stated agenda combines cleanliness and pendency reduction with records management, better use of office space and scientific disposal of electronic waste. The Department of Pharmaceuticals’ October 2 implementation note gives an unusually concrete example of how the campaign is being translated into a departmental ledger: it listed 2,716 physical files and 20 e-files for review, 1,011 obsolete electronic assets for disposal through MoEFCC-empanelled recyclers, and a tracked queue that included 72 CPGRAMS grievances and 18 public-grievance appeals. Those figures are baselines and targets, not completed outcomes.1 2
At the launch, the Minister also cited the previous five campaigns’ cumulative totals: ₹5,102.91 crore earned from scrap and e-waste disposal, more than 1,049.54 lakh square feet of office space cleared, 180.48 lakh files closed or weeded out, and 24.20 lakh cleanliness sites identified and cleaned.1 These are government-reported programme outputs; the release does not give a denominator or verification method alongside the headline figures. Publishing that underlying ledger would make this year’s progress easier to assess rather than simply extending the scorecard.
That distinction matters. A campaign dashboard can make accumulated work visible and give senior officials a reason to clear it. But its success should not be measured by how many files are reviewed, how much floor space is freed, or how many cases receive a closure code. For a grievance, the relevant test is whether a remedy was delivered and whether a dissatisfied complainant could appeal. For a record, it is whether the file was retained, digitised or lawfully destroyed—and whether the decision itself remains auditable.
The e-waste target brings a genuine public-interest benefit: obsolete equipment should not linger in offices or leak into informal disposal chains. The same release says the target includes IT and telecommunications devices, consumer electronics, appliances, laboratory instruments and other electronic assets, to be processed through authorised recyclers. The chain should be traceable from inventory to handover and final treatment. “Disposed” is not proof of safe recycling unless the receiving facility and the material’s fate can be checked.
Records clearance needs an equivalent audit trail. The government’s drive can reduce search costs and expose neglected files, but paper destruction is irreversible. Each department should publish its retention schedule, the classes and quantities of records reviewed, exceptions for litigation or pending information requests, and a destruction certificate. That is not an argument against weeding files; it is the condition for distinguishing orderly records management from opaque deletion. A cleaner office is an administrative output. A preserved, searchable record of why a file was closed is a governance outcome.
2. Gandhi Jayanti’s 2.42 lakh Gram Sabhas: participation meets portals
The Ministry of Panchayati Raj said more than 2.42 lakh Special Gram Sabhas were scheduled through the GPDP Portal and Panchayat NIRNAY Portal for Gandhi Jayanti on October 2. Its account says the gatherings were held across the country and that they opened the 2026–27 People’s Plan Campaign, under which Panchayats are to prepare development plans for financial year 2027–28. The ministry described discussion of local priorities alongside national schemes—water, sanitation, food security, land rights, livelihoods, consumer protection and women’s economic empowerment. It also said more than 2.55 lakh Gram Panchayats prepare and upload development plans through eGramSwaraj.3
This is a notable Layer 6 design: a village meeting is the deliberative venue; portals provide a schedule and a place for plans to be recorded. The distinction between those functions matters. The ministry’s headline number is a count of meetings scheduled on two systems, not a published attendance or quorum count. It does not tell a resident whether their particular Sabha took place, who was able to speak, what proposals were accepted, or whether a rejected proposal received reasons. Digital scheduling can widen visibility, but cannot itself establish participation.
The pipeline should be legible end to end: notice and agenda; attendance and minutes; proposals and decisions; the Panchayat Development Plan; funding and implementation; then an accessible status showing what happened. eGramSwaraj’s plan repository and the meeting portals are useful parts of that chain, but they are not interchangeable. Citizens should be able to move from a Sabha’s minutes to the plan line and budget that reflect—or omit—their request without having to infer the connection from separate databases.
The scale also creates a data-quality question. “2.42 lakh scheduled” is a strong reach indicator, but the more meaningful civic measure is the share of scheduled meetings held with a recorded quorum and published minutes, disaggregated in ways that show whether women, marginalised communities and remote hamlets had a voice. This is not a demand to turn local democracy into a leaderboard. It is a request to make the government’s own claim verifiable and to preserve room for local disagreement.
The cross-layer connection is unusually direct. Gram Sabhas discussed land rights and welfare; those depend on records, identity and payment systems elsewhere in the DPI stack. The Panchayat is where a resident encounters those systems as a service problem. A plan that records “tap connection,” “land record” or “wage delay” as a priority can connect the citizen’s account to a responsible office. Without the recorded follow-through, consultation risks becoming a one-day broadcast of central schemes rather than a way to set local priorities.
3. Shram Samvad: outreach is not yet a remedy
On September 28, the Ministry of Labour and Employment launched Shram Samvad, a 90-day awareness and capacity-building campaign it says will reach 316 districts across all 36 States and Union Territories, with emphasis on industrial clusters. By October 1, the ministry reported programmes held on September 30 in Bhiwadi and Bhilwara, East Delhi, Dehradun and Chhatrapati Sambhajinagar. Officials, state labour departments, industry associations, employers, HR and legal professionals discussed the four Labour Codes, compliance obligations, social-security initiatives and practical questions. The ministry said sessions included representatives of EPFO, ESIC and the Central Labour Commissioner’s office.4
The choice of district-level sessions is sensible: labour rules are experienced through local workplaces, payrolls and inspectors, not just a central explainer. The reported question-and-answer sessions give employers and other participants an opportunity to raise issues about thresholds, records, returns, wages, working hours and benefits. The design also connects legislation to administrative institutions that workers may need to navigate.
But the release describes an awareness channel, not an individual worker grievance mechanism. It does not publish a way for a worker who attends—or cannot attend—to register a complaint, receive a case number, protect themselves against retaliation, track an inspection or appeal an outcome. Nor does the reported participant count tell us whose questions were heard: the examples emphasise employers, industry bodies and compliance professionals. That may be appropriate for an employer-compliance session, but it is not a substitute for a worker-facing channel.
The next step should be a public follow-through ledger: common questions, the authority responsible for answering them, written clarifications, referrals to EPFO/ESIC or labour offices, and a time-bound route for unresolved individual cases. Aggregate reporting can protect workers’ identities while still showing which issues recur and whether district offices respond. Awareness can reduce confusion; only an accessible and safe remedy can resolve a wage or social-security dispute.
There is a cross-layer dependency here too. Employment and social-security claims increasingly rely on digital records and identifiers, while the Shram Samvad release says little about what happens when a worker’s records are missing, inconsistent or inaccessible. The campaign’s practical value will be judged not by the number of sessions alone but by whether a worker can convert a question into a correction or an enforceable decision.
4. CPGRAMS daily totals: useful signals, incomplete scorecards
DARPG’s public account reported that CPGRAMS disposed of 18,040 grievances on September 28, 16,519 on September 29, and 18,704 grievances and appeals on September 30 across Central Ministries and Departments and States/UTs.5 6 7 These daily posts make the machinery more visible than a monthly report alone. They also illustrate the limits of a throughput metric: the September 30 wording combines grievances and appeals, while the earlier posts refer to grievances. The figures are therefore not a clean like-for-like series, and adding them together would produce a count of reported disposals, not a measure of people helped.
The Department of Pharmaceuticals’ Special Campaign baseline makes the institutional point tangible: its list separates 72 public grievances from 18 appeals and places both inside an active-resolution tracker. That separation matters because an appeal is a citizen saying that the first answer did not settle the issue. If the dashboard counts a first disposal as success while the appeal remains unresolved, it can reward the very outcome the second-tier process exists to correct.
A credible grievance scorecard needs at least four public signals alongside volume: how many cases were received, how many were resolved with a substantive remedy, how many were reopened or appealed, and how satisfied complainants were after closure. It should also publish backlog age and department-level performance so a fast-moving average cannot hide a long tail of unresolved cases. Each figure needs a clear definition and an auditable date range.
The campaign and the daily feed point in the same direction: the state is measuring activity more often. The next improvement is to measure whether that activity changed the citizen’s position. Until then, “disposed” should be read literally as an administrative status—not as proof of redress.
The week’s test: connect the count to the consequence
Four strands—file and e-waste targets, Gram Sabha planning, labour-code outreach and CPGRAMS disposal reporting—show a governance stack being assembled from portals, meetings and campaign dashboards. Their shared opportunity is traceability: the citizen should be able to find the record behind a decision and the official responsible for the next step. Their shared risk is substituting a countable activity for an answerable institution.
For the month ahead, watch whether Special Campaign 6.0 publishes completed results separately from targets; whether Gram Sabha minutes and attendance can be checked against plans on eGramSwaraj; whether Shram Samvad reports worker-originated questions and referrals rather than only sessions; and whether CPGRAMS distinguishes closed tickets from upheld remedies and successful appeals. Those are modest reporting changes, but they would make the difference between a government that can count its work and one whose residents can verify it.
Scorecard — September 26–October 3, 2026
| System | This week’s development | What to verify next |
|---|---|---|
| Special Campaign 6.0 | Implementation began Oct 2; DoP published file, e-waste and grievance baselines 1 2 | Report completed work separately from targets; preserve record-disposal audit trails |
| Gram Sabhas / eGramSwaraj | 2.42 lakh Sabhas scheduled for Gandhi Jayanti; People’s Plan Campaign opened 3 | Publish meeting-held, attendance, minutes and decision-to-budget links |
| Shram Samvad | 90-day labour-code outreach announced across 316 districts 4 | Add safe worker complaint, referral and follow-up routes |
| CPGRAMS | Three verified daily posts reported 16,519–18,704 disposals 5 6 7 | Define “disposal”; publish appeal, backlog-age and outcome measures |