SchoolDeck Databus SchoolDeck
Databus
SchoolDeck
Features Solutions Use cases Tools Compare Guides Pricing
All products
Education
Finance & Operations
FinDeckAccounting & analytics Soon StockWiseInventory & stores Soon TaskDeckTasks & workflows Soon PeopleDeckHRMS & payroll
Sales & Support
LeadDeckSales & admissions CRM Soon TicketDeckSupport service desk Soon ConnectlyCommunity & messaging LiveLoopVideo meetings
Property & Mobility
AI
AskWiseAI assistant Soon
Blog

The census every school files, explained

Every recognised school in India files into UDISE+, and most also feed a state EMIS — Tamil Nadu's EMIS, Telangana's ISMS and their siblings. Administrators searching for these portals want the official sites, which are government domains: UDISE+ at udiseplus.gov.in, and each state's EMIS on its own official portal. This page is the independent explainer: what these systems are, how they relate, and how to make the returns painless.

Explainer, written August 2026. We are not affiliated with CBSE, any state board or any government portal. Portal versions, URLs and procedures change by official circular — the circular is always the authority.

UDISE+, the national census

UDISE+ — the Unified District Information System for Education — is the Ministry of Education's annual census of every recognised school. It assigns each school its UDISE code, the eleven-digit identity that follows the school through every other system, and collects the yearly Data Capture Format: enrolment by class and category, teachers and their details, infrastructure, facilities and outcomes. Student-level records carry PENs — permanent education numbers — designed to follow a child across schools and years. UDISE+ data drives planning, grants and policy, which is why the census is mandatory, dated and increasingly validated: casual figures that once slid through now bounce as inconsistencies.

State EMIS systems, and how the two relate

States run their own education MIS portals for operational administration — Tamil Nadu's EMIS with its student and staff IDs, Telangana's ISMS, Bihar's systems around BSEB and welfare schemes, and their counterparts elsewhere. The state system is the daily-work portal: admissions, transfers, staff, schemes. UDISE+ is the annual national photograph. They overlap heavily in content, and schools must file both — with figures that agree, because mismatches surface in verification. The emerging pattern in several states is integration, with state systems feeding UDISE+ — but the school remains responsible for its data being right in both places, which keeps the underlying discipline unchanged: one true internal record, exported everywhere.

The Data Capture Format, without fear

The DCF looks intimidating and is mostly a mirror: it asks for what a functioning school already knows about itself. Enrolment tables want what the admission register holds. Teacher tables want what the staff file holds. Infrastructure wants what the office can see from the window plus its papers. The scramble happens when those internal records are scattered or stale, so the census becomes an investigation into one's own school. The preparation that works is boring: a September-through-August habit of keeping admissions, transfers, staff changes and facility changes recorded as they happen, so the DCF is an afternoon of reading numbers off the school's own system — and the same numbers serve the state EMIS, the board and every scholarship scheme that comes asking.

Scholarships, schemes and the same identifiers

The census identifiers do double duty: UDISE codes and student identities are increasingly the keys that scholarship portals, scheme databases and welfare transfers verify against. A student whose record is inconsistent — name spelt differently across systems, a date of birth that disagrees with the admission register, a missing or duplicated identity — is a student whose scholarship application bounces in verification, and the school office inherits the untangling. This raises the stakes of ordinary record hygiene: the admission register entry made carefully on day one, with documents checked and names transcribed exactly, saves a family a bounced benefit two years later. It also argues for the school keeping identifier fields — UDISE-linked identity, state EMIS number, board registration — on the student's master record from the start, so that any scheme's form is answered by reading one screen. The schools that parents thank at scholarship season are rarely doing anything heroic in that season; they did the work at admission time.

Who should own the returns

Give the returns a named owner — often the head clerk or a senior administrator — with the head's oversight and a deputy who can act in absence. The owner keeps the credentials register, reads the circulars, runs the pre-cycle reconciliation and files. What the owner should not have to do is generate the data: that is the whole school's daily record-keeping, systematised. Schools that assign an owner without fixing the records give one person an annual crisis; schools that fix the records make the owner's job an administrative rhythm.

How SchoolDeck applies this

SchoolDeck keeps the school's single record — students with their identifiers, staff, infrastructure, documents — current through the year, so UDISE+, the state EMIS and board filings are exports from one truth instead of three reconstructions.

Go deeper: Student records · State board software

Written by Databus Technology Solutions, the makers of SchoolDeck. These guides explain government school portals for the administrators who file on them. We are not affiliated with CBSE, any state board or any government portal; portal versions, URLs and procedures change by official circular, which is always the authority.

Frequently asked questions

Is this page UDISE+ or a state EMIS portal?

No — those are government systems on official domains (UDISE+ at udiseplus.gov.in; each state EMIS on its own government portal), and logins, codes and filings happen there. This is an independent explainer; official instructions always take precedence.

How does a school get or recover its UDISE code?

Codes are issued and managed through the district education machinery — new schools apply through their district office, and corrections or recovery route the same way. The code is the school's permanent identity across systems, so record it institutionally, not in one person's memory.

What is a student PEN and why does it matter?

The permanent education number is the student-level identity UDISE+ assigns, meant to follow the child across schools and years. It matters at transfers: a student arriving with a PEN should be continued, not duplicated — duplicate identities are the census's classic pollution and generate reconciliation work downstream.

What is the EMIS number parents keep being asked for?

In EMIS states, each student carries a state EMIS identity — Tamil Nadu's per-student EMIS ID is the familiar example — used for schemes, exams and transfers. Schools issue and look these up on the state portal; parents asking for the number should be pointed to the school office, which reads it off the student record.

When is UDISE+ due each year?

The census runs on an annual cycle with reference dates and windows announced by the ministry and state authorities. Rather than memorising a date that shifts, the school's data owner should track the official notification each cycle — and keep the underlying records ready year-round so the window's length never matters.

What happens if our UDISE+ and state-portal numbers disagree?

Verification catches it: block and district officers reconcile, queries land, and grants or approvals can hang on corrections. Agreement is not achieved at filing time — it is achieved during the year, by maintaining one internal record both filings are drawn from.

One record, every return.

Applied on every payslip, files generated for upload — per employee, per month.

Start free