The Dashboard Problem — When Measurement Replaces Delivery
India has more real-time government dashboards than any comparable state. Pendency, learning outcomes and delivery gaps have not moved with them. Visibility is not accountability.
India solved the measurement problem and assumed it had solved the management problem. It had not. A number that nobody is required to act on is decoration.
Over the last decade India has built genuinely world-class public monitoring infrastructure. The National Judicial Data Grid publishes case pendency down to the individual court, updated daily. PM Gati Shakti maps infrastructure projects across ministries. PRAGATI reviews stalled projects at the highest level of government. Scheme dashboards report beneficiary counts, disbursement and physical progress in near real time. State chief ministers' offices run their own command centres.
This is a real achievement and other developing states study it. It has also, in a specific and important way, failed to convert.
Four findings anchor this analysis:
- Visibility rose and the underlying indicators did not follow. Judicial pendency is more precisely known than at any point in Indian history and has continued to rise past five crore cases. Learning outcomes are measured in detail by PARAKH and ASER and remain far below grade level. Scheme dashboards report high disbursement while independent audits report weak outcomes. Measurement improved; the measured thing did not.
- The metrics that get published are the ones that are easy to count. Funds released, beneficiaries enrolled, certificates issued, structures sanctioned. Each is an input or an output. The outcome — did the household's income rise, did the child learn to read, did the case get decided — is harder to count and is largely absent from the dashboard layer.
- Self-reported data has no independent check. Almost all dashboard data is entered by the implementing agency being assessed. The CAG's finding that a skilling programme's beneficiary survey returned 171 usable responses, padded with duplicates and identical photographs, is the extreme case of a general condition: nobody verifies the number against the ground.
- Where verification is independent, the picture changes. The CAG's finding of 61 per cent fund utilisation by urban local bodies, and of 56 per cent property tax collection efficiency, come from audit rather than self-report. Independent measurement consistently produces harsher and more useful numbers than dashboards do.
Why dashboards drift toward theatre
Three mechanisms, each rational at the level of the individual official.
What is displayed is what is optimised. If a district's standing depends on the percentage of funds disbursed, funds get disbursed — on time, in full, and not necessarily well. The dashboard does not cause bad delivery; it redirects effort toward whichever proxy it has chosen to display.
Entry is a task, not a consequence. The officer entering the data is usually the officer being judged by it, and entry competes for time with the delivery itself. A field officer spending a fifth of the week on reporting is spending a fifth less on the work being reported.
There is no consequence loop. This is the decisive failure. A dashboard is a control instrument only if a red cell triggers something — a review, a resource shift, a defined escalation with a deadline. Most Indian dashboards display without triggering. They are windows, not thermostats.
The counter-case
The strongest defence of the dashboard decade is that transparency has value independent of immediate effect. The NJDG made judicial delay a public fact rather than an anecdote, and it is now impossible to argue about pendency without data. Direct benefit transfer dashboards made leakage visible and correctable in a way paper never allowed. Aadhaar-authenticated portability of food entitlements works precisely because the transaction is recorded centrally in real time.
That is true, and it establishes what dashboards are good for: they are superb at exposing a problem and poor at resolving one. The error is not building them. It is treating construction of the instrument as completion of the reform.
What we would do
- Attach a consequence to every published indicator. For each metric, state in advance what happens when it breaches a threshold, who owns the response, and within how many days. An indicator with no defined trigger should be removed from the dashboard, not celebrated on it.
- Verify a sample independently. Field verification of a small random sample — one or two per cent — by an agency that does not report to the implementer. This is inexpensive and it changes reporting behaviour immediately, because the possibility of being checked is what makes self-report honest.
- Publish one outcome per scheme, even if it is late and imperfect. Employment retained at twelve months. Learning level at end of year. Case disposal rate rather than pendency count. One honest outcome measure is worth twenty input measures.
- Reduce reporting burden at the field level in proportion to what you add centrally. Every new field a state adds to a reporting format is time taken from delivery. Publish the total reporting load on a field officer and treat reducing it as an objective.
- Protect the officer who reports a bad number. A system that punishes accurate reporting will receive inaccurate reports and then govern from them. This is the cheapest reform on this list and the hardest to sustain.
India can now see its own government in more detail than almost any comparable state. Seeing is not governing. The distance between the dashboard and the household is the same distance this Review keeps measuring — and no amount of resolution on the screen shortens it.