Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 73 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]Code Context
trigger_error($message, E_USER_DEPRECATED);
}
$message = 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 73 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php.' $stackFrame = (int) 1 $trace = [ (int) 0 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ServerRequest.php', 'line' => (int) 2421, 'function' => 'deprecationWarning', 'args' => [ (int) 0 => 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead.' ] ], (int) 1 => [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 73, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) {}, 'type' => '->', 'args' => [ (int) 0 => 'catslug' ] ], (int) 2 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Controller/Controller.php', 'line' => (int) 610, 'function' => 'printArticle', 'class' => 'App\Controller\ArtileDetailController', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 3 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 120, 'function' => 'invokeAction', 'class' => 'Cake\Controller\Controller', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 4 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 94, 'function' => '_invoke', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(App\Controller\ArtileDetailController) {} ] ], (int) 5 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/BaseApplication.php', 'line' => (int) 235, 'function' => 'dispatch', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 6 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Http\BaseApplication', 'object' => object(App\Application) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 7 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/RoutingMiddleware.php', 'line' => (int) 162, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 8 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\RoutingMiddleware', 'object' => object(Cake\Routing\Middleware\RoutingMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 9 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/AssetMiddleware.php', 'line' => (int) 88, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 10 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\AssetMiddleware', 'object' => object(Cake\Routing\Middleware\AssetMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 11 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Middleware/ErrorHandlerMiddleware.php', 'line' => (int) 96, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 12 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Error\Middleware\ErrorHandlerMiddleware', 'object' => object(Cake\Error\Middleware\ErrorHandlerMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 13 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 51, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 14 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Server.php', 'line' => (int) 98, 'function' => 'run', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\MiddlewareQueue) {}, (int) 1 => object(Cake\Http\ServerRequest) {}, (int) 2 => object(Cake\Http\Response) {} ] ], (int) 15 => [ 'file' => '/home/brlfuser/public_html/webroot/index.php', 'line' => (int) 39, 'function' => 'run', 'class' => 'Cake\Http\Server', 'object' => object(Cake\Http\Server) {}, 'type' => '->', 'args' => [] ] ] $frame = [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 73, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) { trustProxy => false [protected] params => [ [maximum depth reached] ] [protected] data => [[maximum depth reached]] [protected] query => [[maximum depth reached]] [protected] cookies => [[maximum depth reached]] [protected] _environment => [ [maximum depth reached] ] [protected] url => 'latest-news-updates/on-the-nipfp-response-reetika-khera-19725/print' [protected] base => '' [protected] webroot => '/' [protected] here => '/latest-news-updates/on-the-nipfp-response-reetika-khera-19725/print' [protected] trustedProxies => [[maximum depth reached]] [protected] _input => null [protected] _detectors => [ [maximum depth reached] ] [protected] _detectorCache => [ [maximum depth reached] ] [protected] stream => object(Zend\Diactoros\PhpInputStream) {} [protected] uri => object(Zend\Diactoros\Uri) {} [protected] session => object(Cake\Http\Session) {} [protected] attributes => [[maximum depth reached]] [protected] emulatedAttributes => [ [maximum depth reached] ] [protected] uploadedFiles => [[maximum depth reached]] [protected] protocol => null [protected] requestTarget => null [private] deprecatedProperties => [ [maximum depth reached] ] }, 'type' => '->', 'args' => [ (int) 0 => 'catslug' ] ]deprecationWarning - CORE/src/Core/functions.php, line 311 Cake\Http\ServerRequest::offsetGet() - CORE/src/Http/ServerRequest.php, line 2421 App\Controller\ArtileDetailController::printArticle() - APP/Controller/ArtileDetailController.php, line 73 Cake\Controller\Controller::invokeAction() - CORE/src/Controller/Controller.php, line 610 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 120 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51 Cake\Http\Server::run() - CORE/src/Http/Server.php, line 98
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 74 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]Code Context
trigger_error($message, E_USER_DEPRECATED);
}
$message = 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 74 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php.' $stackFrame = (int) 1 $trace = [ (int) 0 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ServerRequest.php', 'line' => (int) 2421, 'function' => 'deprecationWarning', 'args' => [ (int) 0 => 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead.' ] ], (int) 1 => [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 74, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) {}, 'type' => '->', 'args' => [ (int) 0 => 'artileslug' ] ], (int) 2 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Controller/Controller.php', 'line' => (int) 610, 'function' => 'printArticle', 'class' => 'App\Controller\ArtileDetailController', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 3 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 120, 'function' => 'invokeAction', 'class' => 'Cake\Controller\Controller', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 4 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 94, 'function' => '_invoke', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(App\Controller\ArtileDetailController) {} ] ], (int) 5 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/BaseApplication.php', 'line' => (int) 235, 'function' => 'dispatch', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 6 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Http\BaseApplication', 'object' => object(App\Application) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 7 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/RoutingMiddleware.php', 'line' => (int) 162, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 8 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\RoutingMiddleware', 'object' => object(Cake\Routing\Middleware\RoutingMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 9 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/AssetMiddleware.php', 'line' => (int) 88, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 10 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\AssetMiddleware', 'object' => object(Cake\Routing\Middleware\AssetMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 11 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Middleware/ErrorHandlerMiddleware.php', 'line' => (int) 96, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 12 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Error\Middleware\ErrorHandlerMiddleware', 'object' => object(Cake\Error\Middleware\ErrorHandlerMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 13 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 51, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 14 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Server.php', 'line' => (int) 98, 'function' => 'run', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\MiddlewareQueue) {}, (int) 1 => object(Cake\Http\ServerRequest) {}, (int) 2 => object(Cake\Http\Response) {} ] ], (int) 15 => [ 'file' => '/home/brlfuser/public_html/webroot/index.php', 'line' => (int) 39, 'function' => 'run', 'class' => 'Cake\Http\Server', 'object' => object(Cake\Http\Server) {}, 'type' => '->', 'args' => [] ] ] $frame = [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 74, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) { trustProxy => false [protected] params => [ [maximum depth reached] ] [protected] data => [[maximum depth reached]] [protected] query => [[maximum depth reached]] [protected] cookies => [[maximum depth reached]] [protected] _environment => [ [maximum depth reached] ] [protected] url => 'latest-news-updates/on-the-nipfp-response-reetika-khera-19725/print' [protected] base => '' [protected] webroot => '/' [protected] here => '/latest-news-updates/on-the-nipfp-response-reetika-khera-19725/print' [protected] trustedProxies => [[maximum depth reached]] [protected] _input => null [protected] _detectors => [ [maximum depth reached] ] [protected] _detectorCache => [ [maximum depth reached] ] [protected] stream => object(Zend\Diactoros\PhpInputStream) {} [protected] uri => object(Zend\Diactoros\Uri) {} [protected] session => object(Cake\Http\Session) {} [protected] attributes => [[maximum depth reached]] [protected] emulatedAttributes => [ [maximum depth reached] ] [protected] uploadedFiles => [[maximum depth reached]] [protected] protocol => null [protected] requestTarget => null [private] deprecatedProperties => [ [maximum depth reached] ] }, 'type' => '->', 'args' => [ (int) 0 => 'artileslug' ] ]deprecationWarning - CORE/src/Core/functions.php, line 311 Cake\Http\ServerRequest::offsetGet() - CORE/src/Http/ServerRequest.php, line 2421 App\Controller\ArtileDetailController::printArticle() - APP/Controller/ArtileDetailController.php, line 74 Cake\Controller\Controller::invokeAction() - CORE/src/Controller/Controller.php, line 610 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 120 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51 Cake\Http\Server::run() - CORE/src/Http/Server.php, line 98
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]Code Contextif (Configure::read('debug')) {
trigger_error($message, E_USER_WARNING);
} else {
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-trace').style.display = (document.getElementById('cakeErr67ed7599951f2-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr67ed7599951f2-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-code').style.display = (document.getElementById('cakeErr67ed7599951f2-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-context').style.display = (document.getElementById('cakeErr67ed7599951f2-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr67ed7599951f2-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr67ed7599951f2-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 19587, 'metaTitle' => 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera', 'metaKeywords' => 'aadhaar,uid', 'metaDesc' => ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...', 'disp' => '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 19587 $metaTitle = 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera' $metaKeywords = 'aadhaar,uid' $metaDesc = ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...' $disp = '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/on-the-nipfp-response-reetika-khera-19725.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera | Im4change.org</title> <meta name="description" content=" -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>On the NIPFP Response-Reetika Khera</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /><br />In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $maxBufferLength = (int) 8192 $file = '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php' $line = (int) 853 $message = 'Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853'Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 48 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]Code Context$response->getStatusCode(),
($reasonPhrase ? ' ' . $reasonPhrase : '')
));
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-trace').style.display = (document.getElementById('cakeErr67ed7599951f2-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr67ed7599951f2-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-code').style.display = (document.getElementById('cakeErr67ed7599951f2-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-context').style.display = (document.getElementById('cakeErr67ed7599951f2-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr67ed7599951f2-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr67ed7599951f2-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 19587, 'metaTitle' => 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera', 'metaKeywords' => 'aadhaar,uid', 'metaDesc' => ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...', 'disp' => '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 19587 $metaTitle = 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera' $metaKeywords = 'aadhaar,uid' $metaDesc = ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...' $disp = '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/on-the-nipfp-response-reetika-khera-19725.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera | Im4change.org</title> <meta name="description" content=" -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>On the NIPFP Response-Reetika Khera</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /><br />In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $reasonPhrase = 'OK'header - [internal], line ?? Cake\Http\ResponseEmitter::emitStatusLine() - CORE/src/Http/ResponseEmitter.php, line 148 Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 54 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]Notice (8): Undefined variable: urlPrefix [APP/Template/Layout/printlayout.ctp, line 8]Code Context$value
), $first);
$first = false;
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-trace').style.display = (document.getElementById('cakeErr67ed7599951f2-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr67ed7599951f2-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-code').style.display = (document.getElementById('cakeErr67ed7599951f2-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr67ed7599951f2-context').style.display = (document.getElementById('cakeErr67ed7599951f2-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr67ed7599951f2-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr67ed7599951f2-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 19587, 'metaTitle' => 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera', 'metaKeywords' => 'aadhaar,uid', 'metaDesc' => ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...', 'disp' => '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /> <br /> In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 19587 $metaTitle = 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera' $metaKeywords = 'aadhaar,uid' $metaDesc = ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...' $disp = '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated &ldquo;rate of return&rdquo; on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), &ldquo;without disclosure&rdquo;.<br /><br />In spite of these limitation, the conclusions (&ldquo;50% rate of return&rdquo;) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see &ldquo;Large Returns Expected from Aadhaar&rdquo;, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed &ldquo;conservative&rdquo; or &ldquo;modest&rdquo;.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use &ldquo;overall leakages&rdquo; (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and &ldquo;Aadhaar-relevant leakages&rdquo; (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not &ldquo;conservative&rdquo;.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states &ldquo;The study has steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a &ldquo;Scheme Brief&rdquo; by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of &ldquo;overall leakages&rdquo; (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of &ldquo;Aadhaar-relevant leakages&rdquo; for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the &ldquo;affiliation&rdquo; between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors&rsquo; proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month &ndash; which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is &ldquo;careful analysis that is mindful of difficulties in available research&rdquo;. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the &ldquo;path to rational policymaking&rdquo; lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: &ldquo;Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work&rdquo;. &ldquo;Inflated days of work&rdquo; is due to collusion which is not an Aadhaar-leakage. &ldquo;Fake names&rdquo; can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a &ldquo;discount&rdquo; factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that &ldquo;the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist&rdquo;. (This also contradicts an earlier statement that they &ldquo;steered away from relying exclusively on analyses of isolated and small sample sets&rdquo;.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): &ldquo;Estimating Leakages in India&rsquo;s Employment Guarantee&rdquo; in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/on-the-nipfp-response-reetika-khera-19725.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera | Im4change.org</title> <meta name="description" content=" -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>On the NIPFP Response-Reetika Khera</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /><br />In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $cookies = [] $values = [ (int) 0 => 'text/html; charset=UTF-8' ] $name = 'Content-Type' $first = true $value = 'text/html; charset=UTF-8'header - [internal], line ?? Cake\Http\ResponseEmitter::emitHeaders() - CORE/src/Http/ResponseEmitter.php, line 181 Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 55 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
<head>
<link rel="canonical" href="<?php echo Configure::read('SITE_URL'); ?><?php echo $urlPrefix;?><?php echo $article_current->category->slug; ?>/<?php echo $article_current->seo_url; ?>.html"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /> <br /> In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 19587, 'metaTitle' => 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera', 'metaKeywords' => 'aadhaar,uid', 'metaDesc' => ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...', 'disp' => '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /><br />In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 19587, 'title' => 'On the NIPFP Response-Reetika Khera', 'subheading' => '', 'description' => '<div align="justify"> -Economic and Political Weekly<br /> <br /> Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /> <br /> In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /> <br /> <em>On Benefits: Lack of Data<br /> </em><br /> The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /> <br /> The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /> <br /> The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /> <br /> <em>Other Issues<br /> </em><br /> The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /> <br /> The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /> <br /> The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /> <br /> Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /> <br /> <em>In Conclusion<br /> </em><br /> I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /> <br /> <strong>Notes<br /> </strong><br /> 1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /> <br /> 2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /> <br /> 3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /> <br /> 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /> <br /> 5 Further, there are peaks and ebbs in material use for any work.<br /> <br /> <em>Reference<br /> </em><br /> Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford </div>', 'credit_writer' => 'Economic and Political Weekly, Vol-XLVIII, No. 10, March 09, 2013, http://www.epw.in/discussion/nipfp-response.html', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'on-the-nipfp-response-reetika-khera-19725', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 19725, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 19587 $metaTitle = 'LATEST NEWS UPDATES | On the NIPFP Response-Reetika Khera' $metaKeywords = 'aadhaar,uid' $metaDesc = ' -Economic and Political Weekly Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve...' $disp = '<div align="justify">-Economic and Political Weekly<br /><br />Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”.<br /><br />In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”.<br /><br /><em>On Benefits: Lack of Data<br /></em><br />The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2<br /><br />The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011).<br /><br />The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment.<br /><br /><em>Other Issues<br /></em><br />The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states).<br /><br />The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4<br /><br />The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5<br /><br />Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA.<br /><br /><em>In Conclusion<br /></em><br />I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages.<br /><br /><strong>Notes<br /></strong><br />1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work).<br /><br />2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available.<br /><br />3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.)<br /><br />4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website.<br /><br />5 Further, there are peaks and ebbs in material use for any work.<br /><br /><em>Reference<br /></em><br />Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford</div>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'
include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51
![]() |
On the NIPFP Response-Reetika Khera |
-Economic and Political Weekly
Before I take issue with some of the points made in the NIPFP response to this comment, it may be useful to recapitulate a few points on which there appears to be agreement: (1) Aadhaar-integration can resolve only certain types of leakages, for which reliable data is unavailable; this was not adequately accounted for in the cost-benefit exercise; (2) the NIPFP study has a fragile basis (in particular, the estimated “rate of return” on unique identification (UID) number builds on a whole series of ad hoc assumptions); (3) the study is conducted by a research group that receives funds from Unique Identification Authority of India (UIDAI), “without disclosure”. In spite of these limitation, the conclusions (“50% rate of return”) were handsomely played up in the media, including a newspaper in which one of the principal authors is a consulting editor (see “Large Returns Expected from Aadhaar”, Indian Express, 10 November 2012). The main purpose of the comment was to draw attention to the details of the NIPFP study which, unfortunately, were swept aside in the public discusssion. Instead, the ad hoc assumptions were repeatedly termed “conservative” or “modest”. On Benefits: Lack of Data The NIPFP study and the response use “overall leakages” (total corruption due to, say, leakage at the state food depot, at the ration shop, due to duplicates, in the case of the public distribution system (PDS)) and “Aadhaar-relevant leakages” (i e, leakages that Aadhaar-integration can resolve, e g, duplication) interchangably. Using estimates of overall leakages has the effect of exaggerating the benefits of Aadhaar-integration, so the assumptions are not “conservative”.1 When estimates of Aadhaar-relevant leakages exist, the study and response admit, they are outdated.2 The NIPFP response states “The study has steered away from relying exclusively on analyses of isolated and small sample sets”. I would like to draw attention to the evidence that the NIPFP study relied on. For ASHAs, Janani Suraksha Yojana and scholarships, no analysis,large or small has been used. For the Indira Awaas Yojana, the three analyses relied on exclusively are a Times of India news report, a press release based on a discussion in Parliament and a “Scheme Brief” by the Institute for Financial Management and Research (IFMR). Interestingly, the corruption estimate in the IFMR brief cross-refers to the Times of India article (apart from a CAG report)! Similar issues arise with the Mahatma Gandhi National Rural Employment Guarantee Act (MGNREGA) data which generally relies on small, often single-state, samples drawn from one to three districts. An all India average of “overall leakages” (not Aadhaar-relevant leakages) relies on these small sample estimates. Nationally representative estimates of overall leakages using National Sample Survey Office data were published in 2011 (see Imbert and Papp 2011). The fact remains that, at the moment, we do not have reliable estimates of “Aadhaar-relevant leakages” for most schemes. This is acknowledged in the NIPFP study and response.3 The lack of reliable information on these issues was the crux of the problem and the main point of my comment. Other Issues The NIPFP response claims that I am selective in citing PDS corruption data, even though they themselves extensively cite my estimates of PDS (overall) leakages published elsewhere. All of my estimation of corruption in several welfare schemes is in the public domain. Further, the low leakages in Chhattisgarh and Tamil Nadu were discussed in the context of the availability, and benefits, of alternate technologies (end-to-end computerisation, in this case, used in these two states). The NIPFP response brushes aside the question of alternate technologies. But as they ascribe benefits that accrue from other technologies (e g, real time monitoring of the number of labourers requires computerisation and is possible without Aadhaar) to Aadhaar-integration, they have to take alternatives into account. Further, the NIPFP response states that the government had to undertake a cost-benefit analysis after the National Identification Authority of India Bill (NIDAI Bill) was rejected in totality by the relevant Standing Committee (on Finance). Apart from the oversight regarding the disclaimer on the “affiliation” between UIDAI and the Macro/Finance group of NIPFP, a larger question on the process of policymaking also arises.4 The authors’ proposal on material corruption in NREGA is without merit. They suggest controlling material corruption in NREGA by linking material costs with number of labourers. The share of material in total costs depends, not on the number of labourers (as they suggest), but on the nature of the project. Material costs per labourer are very high for wells, but close to zero for land-levelling. If, as NIPFP proposes, there should be a fixed ratio between labourers and material costs, then in the case of wells, their proposal will lead to collapsed wells and for land-levelling, it would open the door to material corruption.5 Even on the cost side, which I completely ignored earlier, there are problems. The NIPFP study budgets Rs 1,200/year for connectivity (Table 2, NIPFP study) for payments of each Aadhaar-enabled scheme. As each authentication is likely to cost Re 1, only 1,200 beneficiaries per gram panchayat are envisioned to be paid each year. This translates to 100 transactions each month – which is certainly too few for the PDS and NREGA. In Conclusion I agree with the NIPFP authors that the way forward is “careful analysis that is mindful of difficulties in available research”. When available research is fraught with problems acknowledged throughout the NIPFP study and response, the “path to rational policymaking” lies in doing the hard work, i e, undertaking more and larger studies to estimate Aadhaar-relevant leakages. Notes 1 Here is an example: “Automating the maintenance of muster rolls, and carrying out authentication through Aadhaar, will help deal with corruption arising from embezzlement of funds on account of fake names and inflated days of work”. “Inflated days of work” is due to collusion which is not an Aadhaar-leakage. “Fake names” can either be non-existent persons with bank accounts operated by living persons (highly unlikely) or collusion (local officials collude with a worker to defraud the system without doing any work). 2 To apply a “discount” factor (to account for recent improvements), also requires some factual data which are not available. 3 For instance, in the NIPFP response they admit that “the study could not have relied on contemporary data for some of the assumptions, as leakage studies that are nationally representative do not exist”. (This also contradicts an earlier statement that they “steered away from relying exclusively on analyses of isolated and small sample sets”.) 4 I leave aside the minor issue of authorship (which the NIPFP response concedes) only by stating that every other publications of the group authorship has been clearly stated on their website. 5 Further, there are peaks and ebbs in material use for any work. Reference Imbert, Clement and John Papp (2011): “Estimating Leakages in India’s Employment Guarantee” in Reetika Khera (ed.), The Battle for Employment Guarantee (New Delhi: Oxford |