UDISE+ Guide for Schools: What It Is and How to Prepare (2026)

UDISE+ (Unified District Information System for Education Plus) is the Ministry of Education's online system for collecting data from every recognised school in India once a year. Each school logs in with its 11-digit UDISE code and fills the Data Capture Format (DCF): school profile, facilities, teacher details, and student-wise records. The government uses this data for planning, fund allocation, and the annual education statistics; the school gets a School Report Card out of it. This guide explains what is asked, who fills it, when, the mistakes that cause rejections and rework, and how to keep your records clean all year so the submission is a formality rather than a scramble.

#What is UDISE+?

UDISE+ is run by the Department of School Education and Literacy, Ministry of Education, at udiseplus.gov.in. It replaced the older UDISE system in 2018–19, moving data collection from paper forms compiled at block and district level to direct online entry by the school. It covers all recognised schools — government, aided, and private — from pre-primary to Class 12, across all boards.

Two things make it matter to a school head beyond compliance:

• Recognition and identity. The UDISE code is the school's identifier in most state and central systems. Board affiliation forms, scholarship portals, and scheme applications ask for it.
• Student identity. Since the student module became student-wise, each learner carries a Permanent Education Number (PEN) that follows them across schools, and the APAAR ID under NEP 2020 is generated through this data. Wrong entries here follow the child.

#The UDISE code

The UDISE code is an 11-digit number: the first two digits identify the state, the next two the district, then the block, the village/cluster, and finally a school serial number. It is issued once when the school is first registered on the system (usually through the district or block education office) and does not change with a change of management or name. Keep it, along with the school login, in a place that survives staff turnover — a surprising number of schools lose a season chasing a password reset because the only person who knew it left.

#What the Data Capture Format asks for

The DCF is the questionnaire behind the portal. Its exact fields are revised each year and vary slightly by state, so treat the list below as the shape of the form rather than a field-by-field checklist. In practice the data falls into four modules.

Government and aided schools also report receipts and expenditure under schemes; private unaided schools generally see fewer finance fields. Enrolment totals by class and gender are derived from the student-wise module rather than typed as separate counts, which is why student records must be right first.

#Student module, PEN and APAAR

The student module is where most of the effort goes and where most errors originate. Each student is one record with a PEN. At the start of a cycle, last year's students are “progressed” to the new class (or marked as passed out, repeated, or left), students who have left are released so their next school can import them, and new admissions are added — ideally by importing an existing PEN rather than creating a duplicate. Guides published for the 2025–26 cycle describe the sequence as: progression first, then new admissions, then identity linking (Aadhaar-based APAAR generation), then CWSN and other details, then verify and certify.

APAAR (Automated Permanent Academic Account Registry) is the “One Nation, One Student ID” under NEP 2020, a 12-digit ID generated when the student's UDISE+ demographic record matches Aadhaar. It requires parental consent. If the name or date of birth in your admission register differs from Aadhaar by even a spelling, the match fails and the school ends up correcting one or the other. See our NEP 2020 guide for school owners for how APAAR fits the wider policy picture.

#The annual cycle: who fills it and when

Who: The Head of Institution (principal or headmaster) owns the submission and certifies it. In most schools the actual data entry is delegated to a nodal teacher or an office assistant, with class teachers supplying student-level information. State and district education offices (block resource centres, district MIS coordinators) verify and consolidate what schools certify, and can reopen records for correction.

When: Data is reported as on a reference date in the academic session — 30 September has been the standard reference date — so the enrolment and staffing you report should reflect that date, not admission day or the end of the year. The portal typically opens for the new session's entry in the months around that date and states set their own freeze deadlines, which is where most of the pressure comes from. Because these dates are set annually and vary by state, treat any specific deadline you read online as something to confirm with your district office.

#Common errors and why they happen

Almost every UDISE+ problem traces back to a gap between the school's own records and what the portal expects. The recurring ones:

• Duplicate students. A transfer student is created as a new record instead of being imported by PEN, so the child now exists twice nationally. Later, the previous school cannot release them and your count is disputed.
• Name and DOB mismatches. Admission register says “Aryan Patel”, Aadhaar says “Aaryan Patel”; DOB entered from memory rather than the birth certificate. APAAR generation fails and every downstream form inherits the wrong value.
• Enrolment entered before progression. Adding this year's students before promoting last year's creates ghost repeaters and inflates class strength.
• Students who left never released. The child moved in April, but no one marked the exit; the next school is blocked and your dropout figures look wrong.
• Teacher records stale. A teacher who left in June still shows; the new appointee has no record; qualification or training fields are blank because the personal file was never updated.
• Facilities copied from last year. New classrooms, a repaired toilet, or new computers are not reflected because someone clicked through the profile without checking.
• Blank vs. zero. Leaving a numeric field empty when the honest answer is “0” triggers validation errors.
• Certifying without validation. Once certified, data locks; corrections need a request through the block or district office, which takes far longer than a five-minute check would have.

#Keeping master data clean all year

The schools that finish UDISE+ in a few sittings are not the ones with the fastest typist. They are the ones whose student and teacher master data is already correct on 1 April. That is a records discipline, and it comes down to a handful of habits.

#Student master data

• Capture at admission, verify against a document. Name (as on Aadhaar or birth certificate, in the same spelling), date of birth from the certificate, gender, category, parent names, and the previous school's name and the child's existing PEN if they have one. Ask for it on the admission form.
• Record exits the day they happen. A transfer certificate issued should mean the student is marked as left in your system on the same day, with the date and reason. This is exactly the release you will need to do on the portal.
• Promote once, in one place. Decide promotions and repeats as a single, dated exercise at the end of the session, so the class-wise list you take into UDISE+ progression is the one your registers agree with.
• Keep class and section stable. Mid-year section shuffles happen; make sure they are reflected in the master, not just in a teacher's notebook.
• Store PEN and APAAR as fields. Once generated, they belong in the student record next to the admission number, not in a separate spreadsheet.

#Teacher and staff master data

• Maintain one staff register with date of joining, date of leaving, appointment type, highest academic and professional qualification, subjects and classes taught, and any in-service training attended.
• Update it on the joining or relieving day. Payroll is a good forcing function: if a person is being paid, they should be in the master with complete details; if they have been relieved, payroll and the master should agree on the date.
• Class-teacher and subject allocations from your timetable should match what you report as “classes taught”.

#Facilities and profile

• Keep a one-page infrastructure sheet — classrooms, toilets by gender, drinking water source, electricity, ramps, computers, internet — and update it whenever a purchase or repair happens.
• Photographs of the building and facilities are increasingly asked for; take fresh, dated ones at the start of each session.

#How school software makes UDISE+ easier

UDISE+ is not integrated with private school ERPs — there is no API a vendor can push your data into — so the value of software is not automation of the portal but having export-ready, already-correct records so that entry becomes copy and check rather than research. Concretely, a well-run system gives you:

• A single student master with the fields UDISE+ asks for stored once at admission, and a class-wise export you can sort and read alongside the portal.
• Exits and promotions as dated events, so the list of students to release and progress is a filter, not a memory exercise.
• Attendance history that tells you who has actually been present around the reference date, useful for identifying silent dropouts before they become a discrepancy. Our guide to student attendance rules in India covers the record-keeping side.
• Staff and payroll records that agree on who is employed and since when, with qualifications and subject allocations attached.
• Timetable-derived subject allocations for the “classes taught” fields.

If you are choosing or replacing software, ask specifically whether the student profile can hold PEN, APAAR, category, and previous-school fields, and whether class-wise lists export cleanly. Our school ERP implementation checklist and the overview of what school ERP software is cover the broader evaluation.

#UDISE+ preparation checklist

Run through this two to three weeks before your state's window.

• UDISE code, portal login, and registered mobile/email confirmed and known to at least two people.
• Class-wise student list as on the reference date, with admission number, name as per document, DOB, gender, category, PEN (or “new”), and previous school for new admissions.
• List of students who left since the last submission, with date and reason, ready for release.
• Promotion/repeat decisions for every student from last session.
• Parental consent for Aadhaar-based APAAR generation on file for students who need it.
• Staff list with joining/leaving dates, qualifications, training, appointment type, and subject-class allocation; new joiners' documents in hand.
• Updated infrastructure sheet and fresh photographs.
• Recognition and affiliation details unchanged, or the new certificate available if changed.
• Time blocked for the nodal teacher — ideally early morning, when the portal is less loaded — and a final validation pass before the HM certifies.

#FAQ

#Is UDISE+ mandatory for private schools?

Yes. Every recognised school — government, aided, or private unaided — is expected to report annually. Recognition, board affiliation processes, and many state portals rely on the UDISE code and current data.

#How do I find my school's UDISE code?

It is on your previous UDISE+ School Report Card and in your recognition or affiliation correspondence. The public UDISE+ portal also has a school search by state, district, and name. If the school is genuinely new and has never had a code, apply through your district or block education office.

#What is the difference between PEN and APAAR?

PEN is the Permanent Education Number that UDISE+ assigns to a student record so it can move between schools. APAAR is the NEP 2020 academic ID generated when that record is verified against Aadhaar with parental consent, and it links to the student's DigiLocker/Academic Bank of Credits. A student can have a PEN without yet having an APAAR.

#A student joined us from another school. Do I create a new record?

No. Ask for the PEN and import the existing record; the previous school should have marked the student as left. Creating a fresh record produces a duplicate that is difficult to undo later.

#Can we correct data after certification?

Not directly. Once the Head of Institution certifies, the data locks for the year, and corrections go through a request to the block or district education office. This is why running the validation report and a second-person review before certifying is worth the hour.

#Can school software submit UDISE+ for us?

No private software integrates with the UDISE+ portal; entry is done by the school on the government system. Software helps by keeping the student, teacher, and facility records clean and exportable so the entry is quick and error-free.

#Where Edacify fits

Edacify is a student-success platform, not a UDISE+ tool — but the records that make UDISE+ easy are the ones it keeps every day: a single student master per class and division, attendance history, exam and marks records, staff and payroll details, and timetable allocations. If your admission register, class lists, and staff files currently live in three places, start a 21-day free trial, import one standard, and see whether a class-wise export answers the student module in one sitting. Or talk to us about how your school keeps its records today.