India’s CSS Puzzle: Why Welfare Delivery Gets Lost in Paperwork
#CentrallySponsoredSchemes #FiscalFederalism #IndiaGovernance #SNASPARSH #Berrybeat Somewhere in a district office, a block-level official has three portals open at once. One asks for a geotagged photo from a work site. Another wants the same expenditure figures in a different format. A third demands a utilisation certificate for money that has not yet reached the people it was meant for.
The scheme was designed in Delhi. The file landed in the district. The beneficiary waits in between.
This is the everyday administrative puzzle of India’s Centrally Sponsored Schemes. They fund some of the country’s most important welfare programmes, from MGNREGA to Pradhan Mantri Awas Yojana and Jal Jeevan Mission. They also reveal a long-standing tension in Indian fiscal federalism: the Centre controls scheme design and reporting, while states and districts carry the burden of delivery.
PRS Legislative Research data shows that CSS grants formed roughly 25 to 29 percent of all transfers to states between 2015-16 and 2022-23. That is not a marginal channel. It is a major part of how welfare money moves in India.
Yet the problem is not only the amount transferred. It is the way the money, rules, formats, approvals, and proof of compliance move. Policy Circle has noted that district administrations often juggle dozens of schemes, each with its own guidelines, portal, and reporting cycle. The result is a system where compliance can crowd out delivery.
Centrally Sponsored Schemes are built for national goals but delivered locally
Centrally Sponsored Schemes sit at the centre of India’s welfare architecture. They are funded jointly by the Union and state governments, though the cost-sharing ratio varies by scheme and category of state. The Centre usually sets the broad design, eligibility conditions, operational guidelines, data requirements, and monitoring systems. States implement the schemes through their departments, districts, blocks, panchayats, contractors, frontline workers, and local institutions.
This model has clear advantages.
A large country needs national minimum standards. A poor household in Bihar, Assam, Rajasthan, or Tamil Nadu should not lose access to basic welfare only because state finances differ. National schemes also help direct funds to priority areas such as rural employment, drinking water, housing, nutrition, sanitation, health, education, and livelihood support.
Programmes such as MGNREGA, PMAY, and Jal Jeevan Mission show why the model matters. MGNREGA creates a legal entitlement to wage employment. PMAY supports housing for rural and urban households. Jal Jeevan Mission aims to provide household tap connections. These are not small add-ons to governance. They shape the everyday relationship between citizens and the state.
The structure also gives the Union government a way to pursue national development goals while using state and local machinery. In theory, this is cooperative federalism in action.
The difficulty begins when national design becomes too prescriptive for local delivery. A district in the North East, a drought-prone block in Maharashtra, a tribal area in Odisha, and a fast-growing peri-urban belt near Bengaluru may face very different ground realities. Their staffing levels, banking access, internet connectivity, treasury systems, contractor markets, and social conditions vary sharply.
Yet a centrally designed scheme may ask each of them to follow the same reporting structure, upload the same evidence, use the same portal logic, and meet the same timelines.
That is where the CSS compliance burden starts to grow.
The paperwork problem is not just paperwork
It is tempting to see paperwork as a small irritation. In welfare delivery, it can become a structural bottleneck.
A district official does not merely “fill forms”. The official must show that:
the right beneficiary was identified
the activity followed scheme guidelines
the state share and central share were booked properly
expenditure matched approved heads
physical progress matched financial progress
photos, location tags, bank details, audit trails, and certificates were uploaded
previous instalments were accounted for before new funds were released
Each step has a reason. Public money needs safeguards. Leakage, ghost beneficiaries, duplicate claims, inflated works, and delayed audits are real risks. No serious reform can ignore accountability.
The problem is that accountability in many schemes is measured through process evidence rather than outcome evidence. The system asks, “Was the form uploaded?” more often than it asks, “Did the household receive water?” or “Did the worker receive wages on time?”
That changes administrative behaviour.
When the incentive is to satisfy portals, officials spend more time producing proof of activity than solving delivery failures. A missing geotag can delay a payment. A mismatch in naming format can hold up approvals. A late utilisation certificate can block the next instalment. A portal downtime can become a field-level crisis.
The burden is not evenly distributed. Senior ministries may see consolidated dashboards. State departments may see scheme-wise progress. District and block offices see fragmented work.
A typical district may have to deal with:
separate logins for different schemes
scheme-specific file formats
physical and digital documentation running in parallel
multiple audit requirements
repeated beneficiary verification
different definitions of progress
fund release rules that do not match field realities
last-mile connectivity issues
pressure to meet targets before review meetings
The beneficiary sees none of this. The beneficiary only sees delay.
This is why the paperwork question is not administrative trivia. It determines whether welfare becomes an entitlement, a favour, or a queue.
Pruning schemes has not automatically reduced the burden
The Union government has tried to reduce the number of Centrally Sponsored Schemes over time. The count fell from about 130 to roughly 70 by 2023. On paper, that looks like rationalisation.
But PRS has pointed out that spending through these schemes stayed at a similar level. That means fewer scheme names did not necessarily mean a lighter administrative load.
This distinction matters.
If 10 schemes become five but retain separate sub-components, separate portals, separate reporting formats, and separate fund release conditions, the workload may remain almost unchanged. A renamed or merged scheme can still carry the same compliance architecture.
For administrators, the practical question is not only, “How many schemes exist?” It is:
How many fund flows must be tracked?
How many approvals are needed?
How many times must the same beneficiary data be entered?
How many portals need updating?
How many audits ask for overlapping evidence?
How many formats must be reconciled at the end of each month?
A scheme count is easy to announce. A file count is harder to reduce.
This is the difference between scheme rationalisation and administrative rationalisation. The first reduces labels. The second reduces actual work.
India has often done more of the first than the second.
That is why the current review of 54 Centrally Sponsored Schemes and about 260 central sector schemes matters. The government has asked ministries to examine whether schemes should continue, merge, or close. This could be a meaningful reform if it reduces duplication, removes outdated components, and gives states more room to adapt implementation.
But if the review only changes names and budget heads, the district-level burden will survive.
The better test is simple: after reform, does a block office spend fewer hours proving compliance and more hours solving delivery issues?
SNA-SPARSH aims to fix fund flow, but transition costs are real
Fund flow has long been one of the most difficult parts of CSS implementation. Delayed releases, money parked in accounts, incomplete utilisation certificates, and uncertainty over state shares have all affected delivery.
The Single Nodal Agency system was introduced to bring greater control over scheme funds. SNA-SPARSH now takes the logic further by moving towards a just-in-time fund release mechanism for Centrally Sponsored Schemes. In principle, this can reduce idle funds and improve tracking.
The idea is clear. Funds should not sit unused across layers of government. Releases should align more closely with actual expenditure needs. Better visibility should help the Centre and states monitor money in real time.
For public finance, this is an important shift. It can improve cash management and reduce the problem of unspent balances.
But implementation depends on the state’s digital and treasury capacity. An IMPRI analysis found that only 50 of 81 notified schemes had been onboarded to SNA-SPARSH, and it warned that states with less digitised treasuries face the steepest adjustment.
That warning is important.
A just-in-time system works only when the underlying machinery is ready. It needs reliable integration between scheme portals, treasuries, banks, public financial management systems, and implementing agencies. It also needs trained staff who can troubleshoot errors without freezing delivery.
If a district faces poor connectivity, weak data quality, or treasury integration gaps, then a fund-control reform can become another compliance layer.
The risk is not in SNA-SPARSH as an idea. The risk lies in uneven readiness.
For a digitally stronger state, the shift may improve visibility and reduce idle balances. For a state with old treasury systems, staff shortages, or patchy block-level internet, the same reform can slow payment cycles until systems stabilise.
This creates a familiar federal problem. A uniform national system lands on unequal state capacity.
That does not mean India should avoid digital public finance reforms. It means reforms should include transition support, fallback mechanisms, state-specific timelines where needed, and clear responsibility for resolving payment failures.
Digital control should not become digital delay.
India’s fiscal federalism creates a design-delivery gap
The CSS puzzle is also a federal puzzle.
The Union government raises more revenue than states in many major tax categories and has more control over national borrowing and macro-fiscal policy. States carry large responsibilities for public services such as health, education, agriculture, local infrastructure, policing, and welfare delivery. The Finance Commission transfers a share of central taxes to states, but CSS grants remain a major route through which the Centre influences expenditure priorities.
This arrangement creates a design-delivery gap.
The Centre wants national visibility, comparable data, and assurance that money is spent as intended. States want flexibility, timely funds, and space to adjust schemes to local needs. Districts want simpler rules, workable timelines, and enough staff. Beneficiaries want the promised service without procedural delay.
All four expectations are valid. They are not always aligned.
A central ministry may design a scheme with tight conditions to prevent misuse. A state may find those conditions too rigid for local geography or social realities. A district may comply on paper but struggle in practice. A beneficiary may meet the spirit of eligibility but fail a documentation test.
This gap explains why India fiscal federalism often becomes a debate over control rather than outcomes.
Global federal systems offer another model. Many use broader block transfers where the higher level of government fixes the goal, sets broad accountability standards, and leaves the route to sub-national governments. The details vary by country, and no model is perfect. But the principle is useful: the funder should not always prescribe every step of delivery.
India often does the opposite. It prescribes the route and then audits adherence to the route.
That makes sense in sectors where minimum technical standards are essential. Drinking water quality, school infrastructure, health procurement, and nutrition delivery need safeguards. But not every scheme component requires highly detailed central control.
The key question should be: what must be standardised, and what can be left flexible?
For example, the Centre may set outcome targets for household tap connections, school attendance, wage payment timelines, or housing completion. It may also set core financial rules and public disclosure norms. But states could receive more flexibility in staffing models, sequencing, local partnerships, community verification, and state-specific delivery methods.
That would shift accountability from “Did you follow every procedural step?” to “Did people receive the promised benefit, with verifiable safeguards?”
The last mile is where compliance becomes visible
Policy debates often treat implementation as a final stage. In practice, implementation is where policy becomes real.
A welfare scheme may look clean in a Cabinet note or budget document. It becomes messy at the last mile because real households rarely fit neat categories.
Names differ across Aadhaar, ration cards, bank accounts, land records, and local registers. Migrant workers may not be present during verification. A rural household may have a bank account but no easy access to a bank branch. A work site may have connectivity issues. A contractor may delay material supply. A panchayat secretary may handle several schemes with limited staff support.
Each scheme adds its own data demands to this reality.
MGNREGA requires careful tracking of demand for work, muster rolls, attendance, work measurement, and wage payments. PMAY requires beneficiary identification, house sanction, instalment release, construction-stage verification, and often geotagged progress. Jal Jeevan Mission requires physical verification of tap connections, water supply status, quality checks, and village-level reporting.
Each requirement has a policy logic. Together, they can produce MGNREGA PMAY paperwork pressure that overwhelms block and district capacity.
This is why frontline capacity matters as much as scheme design. A block office with trained data entry support, stable connectivity, clear escalation channels, and well-integrated systems can handle compliance better. A block office with vacancies and poor internet may struggle with the same rules.
The same scheme can perform differently across states because capacity differs. Some states invest more in local administrative support, digital infrastructure, social audits, and grievance redress. Others depend heavily on overworked officials and temporary staff.
This also affects equity. Communities with better documentation and stronger local mediation may access benefits faster. Those with weaker literacy, mobility, caste position, language access, or digital familiarity may be pushed to the back of the queue.
A compliance-heavy system can unintentionally reward those who are easiest to verify, not those who are most in need.
Better accountability means fewer duplicate proofs and more outcome checks
Public finance cannot run on trust alone. India needs strong controls because welfare spending is large, politically salient, and vulnerable to misuse. The answer is not to remove accountability. The answer is to make accountability smarter.
A useful reform agenda would focus on five shifts.
One, reduce duplicate data entry.
If a beneficiary has already been verified under one government database, schemes should avoid asking districts to enter the same core details repeatedly. Interoperability must be designed with privacy safeguards, consent rules where relevant, and clear limits on data use.
Two, standardise common reporting fields.
Schemes can differ in goals, but basic fields such as location, expenditure, work status, beneficiary category, bank payment status, and completion stage should not need entirely different formats across portals.
Three, separate critical controls from low-value paperwork.
Not every certificate has equal value. Some documents prevent fraud or verify delivery. Others only reproduce information already available elsewhere. Ministries should classify reporting requirements by risk and remove low-value duplication.
Four, measure outcomes alongside process.
A housing scheme should not stop at instalment release. It should track whether the house is completed and occupied. A water scheme should not stop at tap installation. It should track functionality, water quality, and regular supply. A wage scheme should not stop at muster roll closure. It should track payment timeliness.
Five, give districts problem-solving support.
Dashboards often show red flags, but district teams need authority and help to fix them. A payment failure, land dispute, missing document, or portal error should have a clear escalation path. Monitoring without resolution only produces pressure.
A better CSS system would not mean fewer safeguards. It would mean fewer meaningless hurdles.
The review of schemes must ask the right questions
The Centre’s current exercise to review, merge, or discontinue schemes is timely. But the outcome will depend on the questions ministries ask.
A narrow review may ask:
Is the scheme still politically or administratively relevant?
Is expenditure high or low?
Does the scheme overlap with another scheme?
Can two schemes be merged under one umbrella?
Those questions matter, but they are not enough.
A delivery-focused review should also ask:
How many reporting formats does the scheme require?
How many staff hours does compliance take at district and block levels?
Which documents are repeated across schemes?
How often do portal issues delay payments or approvals?
Which fund release conditions create avoidable bottlenecks?
Can states adapt implementation while meeting national outcomes?
Does the scheme measure real service delivery or only file completion?
Are grievance systems linked to fund and approval systems?
This would move reform from naming schemes to redesigning delivery.
The government should also distinguish between central sector schemes and Centrally Sponsored Schemes. Central sector schemes are fully funded and implemented by the Centre or its agencies. CSS require state participation and state machinery. The compliance cost of CSS is more complex because it travels through multiple layers of government.
For CSS, state consultation cannot be a formality. States know where reporting formats fail, where fund flows slow down, and where central guidelines conflict with local constraints. Districts know which documents consume time without improving delivery.
A serious review should capture that knowledge before schemes are merged or closed.
A simpler CSS system would still need strong public scrutiny
Reducing paperwork should not become an excuse for reducing transparency. India has seen enough leakages and ghost entries in welfare systems to know that public scrutiny matters.
The right goal is a system where transparency is easier, not weaker.
That means public dashboards should show information that citizens can understand. Social audits should remain meaningful. Gram sabhas and local bodies should have access to relevant data. Payment delays should be visible. Contractors, implementing agencies, and officials should remain accountable for quality and timelines.
But scrutiny should focus on what matters.
If a road exists only on paper, the system must catch it. If wages are delayed, the system must flag it. If a tap connection is installed but water does not flow, the system must record that failure. If a house is sanctioned but the instalment is stuck due to a technical error, the system must identify the blockage quickly.
This is different from asking field staff to upload multiple versions of proof for the same fact.
A simpler system can be more transparent if it produces cleaner data, clearer responsibility, and faster correction.
The best test is whether a citizen can know three things without navigating a maze:
Am I eligible?
Has my benefit been approved?
If it is delayed, who must fix it?
If welfare systems cannot answer these questions clearly, they are accountable upward but not outward.
The real measure is the beneficiary’s waiting time
India’s welfare state has expanded in scale, ambition, and technological capacity. That is a major achievement. Few countries manage programmes of this size across such varied geography and population.
But scale has created its own burden. Every new scheme, portal, certificate, dashboard, and audit layer may make sense in isolation. Together, they can produce a delivery system that is hard to navigate even for officials, let alone citizens.
The CSS challenge is not simply that there are too many schemes. It is that too many schemes carry too many separate instructions for the same administrative machinery.
A better model would keep national goals but reduce procedural clutter. It would give states more flexibility where local variation matters. It would use SNA-SPARSH and other fund systems to speed up payments, not merely tighten control. It would ask districts for fewer duplicate proofs and more meaningful evidence of delivery.
The Centre’s review of schemes is a chance to move in that direction. Success should not be judged only by how many schemes are merged or discontinued. It should be judged by whether a district official can spend less time reconciling formats and more time clearing bottlenecks.
Most of all, it should be judged by the person waiting at the end of the chain.
Until the form that proves the waiting is simpler than the waiting itself, the beneficiary stays last in the queue.
