Five Portals, No Flowchart

UDISE+ is not one portal. It is five portals, each at a different URL, each handling a different part of your school's data. The School Profile goes to udiseplus.gov.in/moe_udise/. Students go to sdms.udiseplus.gov.in. Teachers go to udiseplus.gov.in/udiseteacher/. Reports come from udiseplus.gov.in/udisereport/. And there is a User Directory module at udiseplus.gov.in/ud/ that Block and District officers use for school management.

What nobody tells you is that these five portals are not independent. What you enter in School Profile affects what SDMS validation checks. The Teacher Module and School Profile must reflect the same teacher count. If you submit these in the wrong order — or if the numbers between them do not match — the BRC will return one or more for correction, and you will not immediately understand why.

This guide explains the module order that prevents most inter-module problems, and the specific conflicts that happen when you fill modules independently without coordination.

The Correct Module Order — And What Happens If You Get It Wrong

The recommended order for UDISE+ data entry is:

1. School Profile Module first — Enter infrastructure, facilities, and enrollment totals (aggregate counts by class and gender). This establishes the baseline numbers everything else is validated against.
2. Teacher Module second — Enter all active teachers' profiles and generate PENs. Teacher count here is compared against the School Profile.
3. Student Module (SDMS) last — Complete promotions, add new students, generate APAAR IDs. The portal verifies the individual student count here against School Profile enrollment totals.

What happens if you fill SDMS before School Profile:

• You enter 180 students in SDMS, then put 175 in the School Profile enrollment count — making a small mistake by estimating from memory. When BRC checks, you have submitted both numbers, and the mismatch triggers a rejection on both modules.
• If you fill School Profile after SDMS, the natural tendency is to estimate enrollment from memory rather than counting actual students in SDMS. This creates mismatches that are hard to trace.

Problem: A Module Is Blocked or Year Not Accessible

You log in to SDMS. The 2025-26 data is visible but the 2026-27 year does not appear in the dropdown. Or a module shows "Data entry not open for current year."

Problem: Enrollment Count Mismatch Between School Profile and SDMS

Your School Profile shows 268 total students across all classes. Your SDMS student count shows 271. The BRC is asking why these numbers differ by 3. You do not know which is right.

This mismatch is one of the most common reasons BRCs partially return school data. How to identify and fix it:

1. Go to SDMS and count enrolled students class-by-class. Note the count for each class and gender separately.
2. Go to School Profile and compare the class-wise enrollment table with your SDMS count.
3. SDMS count is built from actual individual records — it is more reliable. Correct School Profile to match SDMS, not the other way around.
4. The most common discrepancy source: you promoted students in SDMS but did not reflect them in the School Profile, or you marked students as dropout in SDMS but still counted them in School Profile enrollment totals.

Problem: Same UDISE Code — Different Password for Different Modules

You use your UDISE code to log in everywhere. But the School Profile password and SDMS password may have diverged — especially if someone changed one password and not the other.

How this happens:

• A previous headmaster or data entry operator changed the SDMS password but not the School Profile password
• A state portal migration reset some modules' passwords and not others
• BRC reset one module's password to help with a login issue, and the other password stayed the same

What to do:

1. Try logging into each module separately and note which ones work with which password
2. Contact your Block MIS Coordinator with the modules you cannot access
3. They will tell you the current active password for each module, or reset the ones that the system blocked
4. Once you have both passwords, write them in the school register alongside the UDISE code — never only memorize module passwords

Problem: BRC Returned One Module But Certified Another

The BRC certifies each module independently — BRCs can certify School Profile infrastructure data while sending back SDMS student data if they find an APAAR ID issue. This is normal and means you only need to fix and resubmit the returned module, not all of them.

One important exception: if BRC returns your School Profile after certifying it, it means the district found an inconsistency — usually an enrollment count that contradicts the SDMS data that you certified later. In this case, contact your BRC to understand what specifically triggered the re-open before you make any changes.

When resubmitting a returned module:

• Fix only what the BRC flagged — do not edit other sections that they did not mention in their rejection note
• Resubmit and notify the BRC directly so they can verify and re-certify without delay
• Do not assume the other certified modules are affected — check each module's status independently after resubmission

Module Quick Reference — URL, Status Meaning, Who to Contact

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.