Kitab Vitran · NIPUN Bharat
Target vs. officer-reported receipt of foundational learning material across 75 districts of Uttar Pradesh.
State-wide received as a share of target, per book title.
How the 75 districts split across delivery stages.
Sorted lowest first — the districts needing follow-up sit at the top.
Every figure on this screen is summed from the UDISE-level work order dated 27 Jul 2026. A block is identified by district + block code + block name, and its target is the sum of the schools sitting inside it — 71,877 UDISE codes rolled into 881 blocks. That roll-up is built bottom-up, so it is independent of the district figures on the district screen and may not sum to them. Connect a block-scan sheet to layer received against target; rows match on Block_Code, falling back to district + block name.
One row per UDISE code — 71,877 schools, straight from the work order with no aggregation. This is the base every other level is built from, so if a block or district figure looks wrong, check it here first. Pick a district to list its schools; connect a school-scan sheet to layer received against target, matched on UDISE code.
Two coverage summaries built from the same figures as the Block and School screens. A unit’s percentage is books received ÷ books targeted across all nine titles. Never scanned means no scan record was matched at all — blocks are matched on block code (falling back to name), schools on UDISE code. A unit that did scan but reported zero books counts as 0% and sits in the lowest band, not in “never scanned”. Bands are exclusive, so the buckets always add up to the total.
Targets. District targets are embedded from the district work order and are left exactly as issued.
Block and school targets are built bottom-up from the school work order dated 27 July 2026: one row per
UDISE code, 71,877 schools, summed into 881 blocks. Because the district and school files are compiled
separately, a district roll-up of the school file will not always match the district work-order figure — both are
shown as issued rather than forced to agree. The Data checks panel on the Block screen reports what the
roll-up found in the file.
Received. Received figures come from your connected Google Sheet (read live, refreshed automatically) or an
uploaded CSV. District names and the nine title headers are matched by normalisation plus fuzzy matching, so
spelling differences (e.g. Allahabad/Prayagraj, Nipun Talika/Taalika) are reconciled
automatically. Block scans match on block code, schools on UDISE code. Any district not present in the data is
counted as 0 received (not reached).
Reading the cells. Colour follows received share of target: green above 80%, yellow 50–80%,
red below 50%. A dot means no scan was reported; a dash means there is no target to report against.
Click any district for its full title-by-title breakdown. The sheet is read directly in your browser; nothing is
stored or sent anywhere else.