UDISE+ Data Entry Guide for Schools

UDISE+ is the Unified District Information System for Education Plus, run by the Ministry of Education. It collects yearly information about schools across the country, from pre-primary to Class 12: school profile, infrastructure and facilities, teachers, and enrolment. In recent years the system has moved towards student-level data as well, with reporting tied to individual children rather than only totals. The data feeds planning, grants, reports and, increasingly, student identifiers.

Schools, whether government, aided or private, are generally expected to submit through their own login. Formats, fields, deadlines and verification steps change from year to year and differ by state, so always follow the instructions issued by your state education department and the latest circular. This guide describes the preparation, not the exact screens.

Keep the previous year’s submitted data open as a reference. Many fields repeat, and a sudden change in a number, such as enrolment dropping by half, invites questions from verifiers.

Teacher and infrastructure data change slowly. Student data changes constantly, and it is the part most likely to be wrong. Build a clean student master list at the start of the session and update it whenever a student joins, leaves or changes class.

• Names and dates of birth: match the birth certificate or the record used at admission. Differences between school records and identity documents cause problems later when linking identifiers.
• Class and section: make sure promotions are done before the data window, not after.
• Category and gender fields: use the exact categories the portal expects.
• Parent names and contacts: keep one primary mobile number per family and check sibling records agree.
• Transfers and dropouts: record the date and reason, and do not leave names on the rolls that have gone.
• Children with special needs: record accurately and sensitively, with documentation as required.

If your student information system exports the fields in a sheet that mirrors the portal’s layout, data entry or upload becomes copying rather than creating. Takshiva’s student information system holds these profile fields in one record and can produce a UDISE+ data-capture export from them for your own checking. The submission itself is always made by the school on the official portal.

1. Read the current instructions. Download the circular, the data capture format and any guidance from your state.
2. Confirm your login and role. Check that the school’s credentials work well before the window opens, and that the person who holds them is still on staff.
3. Freeze the reference date. Data is usually reported as of a given date set in the instructions; take a snapshot of strength on that date.
4. Fill school profile and facilities. The principal or administrator should check these personally.
5. Fill or update teacher records. Match them with payroll and appointment files.
6. Prepare student data. Clean, deduplicate and map the fields.
7. Enter or upload, in batches. Save often and keep a record of what was submitted.
8. Run validations on the portal, correct errors and warnings.
9. Submit and keep proof. Download the acknowledgment and any summary reports.
10. Respond to verification queries from block or district officers promptly.

• Enrolment totals that do not match the sum of class-wise or category-wise numbers.
• Duplicate student entries because a child moved from one section to another and was added again.
• Students in the wrong class band after late promotions.
• Teachers counted twice when they teach two sections or are listed under different spellings.
• Missing date of birth or an impossible age for the class.
• Facilities reported inconsistently with last year without explanation.

Most can be spotted with a simple pre-check in a spreadsheet: sort by name and date of birth to find duplicates, filter by class and age to find outliers, and compare totals against your own fee and attendance records. The point of connected records is that a student counted for fees and a student counted for UDISE+ are the same person.

Keep a one-page UDISE+ calendar on the office wall with the data window, internal deadlines and who owns each section. Have the accountant reconcile enrolment with the fee ledger every quarter. Record transfers on the day the transfer certificate is issued. Fill in infrastructure changes, such as a new lab or ramp, as soon as they happen, with a photograph and date.

Schools are also being asked to link students to the APAAR ID, and the student data you maintain for UDISE+ supports that work; see APAAR ID for students. Finally, avoid handing the login to a vendor or a clerk you cannot track; it gives access to sensitive student data. Rotate the password when staff change.

UDISE+ goes wrong when everything rests on one clerk. Spread the work in a way that reflects who actually knows the information, and have the principal sign off before submission.

A one-hour meeting at the start of the data window to walk through this table prevents most last-minute scrambles. Put internal deadlines two or three days before the official ones, so that errors found in validation can be corrected without panic.

Keep a folder, physical or digital, with the submitted acknowledgment, the date of submission and a copy of the data you uploaded. When a block or district officer raises a query months later, you can answer from the file instead of reconstructing what happened.