Why the UDISE+ Student Module Confuses First-Time Operators

The UDISE+ Student Module looks like a single data entry form. It is not. Every student in your school has three completely separate sections — General Profile (GP), Enrollment Profile (EP), and Student Facilities (SF) — that you must fill in a specific sequence. Skip the order, miss a mandatory field in GP, or try to generate APAAR before you tick the consent checkbox—and the Student Module either silently refuses to save or locks you out of the next section with no clear error message.

First-time operators spend their first two days confused by this. They fill EP correctly but it does not save — because you left GP incomplete. They click the Authenticate Aadhaar button and nothing happens — because you left the consent checkbox below the Aadhaar field unticked. They finish all entry and submit — only to have BRC return the data because you half-filled SF for 40 students.

This guide explains how the UDISE+ Student Module actually works: the three-section structure, which fields in each section block progress if wrong, where APAAR ID generation fits, and the exact entry order that prevents BRC rejection.

GP → EP → SF — The Three-Section Structure Every Entry Depends On

In the UDISE+ Student Module, the system divides each student's data into three sections that build on each other:

The system enforces this sequence. You cannot access EP until you fill and save at least the mandatory fields in GP. You cannot access SF until you save EP. You generate the APAAR ID within GP after the Aadhaar field and consent checkbox are complete.

This is not just a UI choice — it reflects data logic. GP establishes who the student is (identity). EP establishes where they are academically (class, marks). SF establishes what entitlements they receive. Each section depends on the accuracy of the previous one.

General Profile (GP) — Fields That Block APAAR If Entered Wrong

GP is the foundation of a student's record in the UDISE+ Student Module. A mistake here creates problems that compound through EP, SF, and APAAR. The fields that most commonly cause problems:

Name — must exactly match Aadhaar card

• You must enter the name exactly as UIDAI prints it on the Aadhaar card — including middle name if present
• Do not use abbreviations: "Rajesh K. Sharma" will fail Aadhaar verification; enter "Rajesh Kumar Sharma"
• Do not add titles (Ku., Smt., etc.) — Aadhaar has only the name

Date of Birth — day/month/year must match Aadhaar

• A single digit difference causes Aadhaar authentication failure — the OTP is received but verification fails
• If the school register shows a different DOB than Aadhaar, use the Aadhaar DOB in SDMS

Social Category — cannot be "Select"

• You must choose SC, ST, OBC, or General. If you leave the default "Select..." placeholder, the system will not unlock EP even after you save GP.

Disability Status — opens sub-fields

• If a student has any disability, marking "Yes" opens CWSN-specific sub-fields (type of disability, nature of impairment). These sub-fields become mandatory. If you select "Yes" and leave the sub-fields blank, the system will not save GP.

Consent Checkbox — the most missed mandatory step

• You can locate this small, easy-to-miss checkbox below the Aadhaar number field in GP.
• If you do not tick this checkbox, the system will not activate the Authenticate Aadhaar button for APAAR generation.
• Tick it even if you plan to generate the APAAR ID later—you must tick it before you freeze GP.

Enrollment Profile (EP) — Class, Category and Marks Entry

EP records the student's academic position at your school. The fields that matter:

• Admission Number: Must be unique per student in your school. This is your school's own admission register number — not a UDISE-assigned number. Duplicate admission numbers or "0" will prevent the system from saving EP.
• Roll Number: Unique within the class. Two students in Class 3 cannot have the same roll number.
• Enrollment Type: This determines how BRC reads the student's status:
  • Fresh Admission — new to government schooling (Class 1 first-time enrollment)
  • Promoted — moved up from previous class (most students)
  • Transfer In — came from another school
  • Detained — repeating the same class
• Previous Year Marks: The system requires previous year marks for Classes 2 and above. For Class 1 fresh admissions, this field is either absent or shows "N/A". If you leave it blank for Classes 2+, the system will block the EP save.
• Medium of Instruction: Ensure the medium of instruction matches the language your school actually teaches in. If your school teaches in Hindi and you enter English, BRC flags this against last year's record.

Student Facilities (SF) — The Section Most Schools Rush and Regret

SF is the last section per student and it shows. It is also the section BRC most commonly flags during rejection. Schools that rush SF because "it is just checkboxes" find out at submission time that blank SF is a rejection trigger.

What SF actually records:

The common mistake: marking MDM as "No" for all students because it feels like less work than confirming each one. This removes your school from MDM beneficiary counts and can affect mid-day meal budget allocation. Enter actual Yes/No per student based on attendance and meal receipt records.

Where APAAR ID Generation Fits in the Student Module Workflow

You do not generate the APAAR ID through a separate process outside the UDISE+ Student Module—it occurs within GP after you authenticate the Aadhaar number. Understanding exactly where it sits:

1. Fill GP completely — name, DOB, Aadhaar number, category, all mandatory fields
2. Tick the consent checkbox in GP (near Aadhaar field)
3. Save GP
4. Now the system activates the "Authenticate Aadhaar" button
5. Click it—the system sends the OTP to the mobile number registered on the student's Aadhaar card (the parent's phone)
6. Enter OTP within 10 minutes
7. On successful authentication, the system generates the APAAR ID immediately and displays it in the student's GP
8. Proceed to EP, then SF

Two things that block APAAR generation that are not obvious:

• Parent's Aadhaar entered instead of student's: Operators sometimes enter the parent's Aadhaar because they find it easier to get. The OTP arrives, and authentication appears to succeed, but the system links the APAAR ID to the wrong Aadhaar—or fails if the parent's Aadhaar already links to another student record somewhere.
• Student's Aadhaar not linked to any mobile number: If parents enrolled the student's Aadhaar without a mobile number (common for children enrolled as infants), the system cannot deliver the OTP. Resolution: visit a UIDAI enrollment center to link a mobile number to the Aadhaar first.

The Entry Sequence That Prevents BRC Rejection

The most common reason schools face BRC rejection in the UDISE+ Student Module is not wrong data—it is entering correct data in the wrong order, which creates inconsistencies that the BRC system flags automatically.

Follow this sequence for the entire school:

1. Class promotions first — promote all existing students to their new class before you touch new admissions. If you promote after adding new Class 1 students, you will cause enrollment count confusion in both the old and new classes.
2. Mark Class 8 passouts as "Passed Out" — do this before you run promotions so you do not accidentally include them in a bulk promotion.
3. Mark dropouts and transfers out — you must correctly categorize students who left before September 30 before you finalize your enrollment count.
4. Add new Class 1 admissions — only after you complete all promotions. Enter GP → EP → SF for each new student. Generate the APAAR ID for each student before you move to the next.
5. Add transfer-in students — search by Aadhaar first to find their existing record. Link them to your school. Do not create duplicate entries.
6. Complete SF for all students — including students who already exist in the system from last year. You must update SF for the current year.
7. Cross-check total enrollment count against your school register before freezing. Count class-wise: total in register vs total in SDMS per class.
8. Freeze only after the cross-check — unfreezing requires BRC intervention. Spend 30 minutes on verification before you freeze to avoid this hassle.

Written By

Pooja Sharma

Teacher & Contributor 🎓 BSc. (Physics), MSc. (Physics) and BEd.

Pooja Sharma is a qualified physics graduate (BSc, MSc) and certified teacher (BEd). As an active educator and contributor, she simplifies complex school portal processes, student registrations, and educational data entry tasks for academic administrators.