When BRC Returns Data — What Actually Happened

You submitted all your modules. Four days later, the school dashboard shows one or more modules back in "Returned" status. The Block MIS Coordinator sent data back. There may be a remarks note — "enrollment mismatch" or "APAAR pending" — or the remarks field may be completely blank.

BRC rejection is not a failure in the catastrophic sense. It is a standard part of the verification cycle. Every year, a significant percentage of schools in every block have at least one module returned before the block coordinator certifies it. What separates schools that resolve rejections in two days from schools that take three weeks is understanding exactly what triggered the return — and fixing only that, without introducing new errors elsewhere.

This page covers the 5 specific reasons BRCs return school data, what each means in practical terms, and the exact process for resubmitting correctly.

Rejection Reason 1: Enrollment Mismatch Between Modules

The most common rejection trigger. Your School Profile shows one total enrollment number and your SDMS shows a different individual student count. BRC's verification dashboard flags this automatically.

The mismatch can come from:

• The operator entered School Profile enrollment from memory or last year's register while SDMS has the actual current count
• The operator added students to SDMS after submitting the School Profile and did not update the aggregate total
• The operator updated dropouts and transfers in SDMS but did not reflect them in School Profile enrollment totals
• The operator entered class-wise counts incorrectly in School Profile — a common mistake is adding a class's boys and girls counts in the wrong row

Fix:

1. Go to SDMS and count students class-by-class, gender-by-gender
2. Note these numbers on paper
3. Request BRC unlock for School Profile
4. Update each class's enrollment row in School Profile to match SDMS
5. Check the total — it should now match
6. Save and resubmit School Profile

Rejection Reason 2: APAAR IDs Incomplete — The Certification Block

In 2026-27, APAAR ID is mandatory and BRCs cannot certify SDMS data if a significant number of students are missing APAAR IDs. "Significant number" varies by BRC — some require 100% APAAR completion, others allow a documented exception list for students with genuine Aadhaar issues.

What BRC sees in their dashboard: a count of students without APAAR IDs, and a percentage. If the percentage is above their threshold, they return the data.

Fix:

1. Pull the APAAR status report from SDMS — identify which specific students are missing APAAR
2. For each missing student, check whether they have an Aadhaar card
3. If Aadhaar exists: authenticate and generate APAAR — you can do this without BRC unlock as long as the portal retains the data in submitted (not certified) status
4. If no Aadhaar: prepare a documented list of students pending Aadhaar enrollment with reason and submit this list to BRC alongside your resubmission
5. Contact BRC and confirm whether they need 100% completion or will accept a documented exception list

Rejection Reason 3: Infrastructure Data Is Inconsistent

BRCs cross-check school infrastructure data against state records, previous year's data, and sometimes physical inspection reports. If something looks impossible — more computers than electricity connections, more classrooms than the school's total plinth area, or toilet count that tripled from last year — BRC will flag it for verification.

Common infrastructure flags:

• Toilet count significantly higher than last year with no new construction grant on record
• The operator entered computer count as 0 when the school received computers under a government scheme
• Functional vs. existing mismatch — more "functional" toilets than "existing" toilets (a mathematical impossibility)
• WASH data showing piped water when the village does not have a piped water supply according to Jal Jeevan Mission records

Fix: Go to the specific section the BRC flagged. Physically verify the infrastructure. Enter the correct figure. If the correction reduces toilets because some became non-functional compared to last year, add a note in the remarks field explaining why.

Rejection Reason 4: Teacher Count Discrepancy

The teacher count in your Teacher Module does not match what the state has on record from payroll or service book data. BRCs have access to state teacher deployment records and can see if your teacher count is significantly off.

Common causes:

• The operator did not add a teacher who joined in August 2026 to the Teacher Module before submission
• A teacher who transferred out is still showing as active in your module
• The operator did not update a retired teacher to inactive status
• The operator entered a guest or contract teacher with a qualification category they do not have, causing their record to fail validation silently

Fix: Open Teacher Module. Check every active teacher against your physical attendance register and service books. Add missing teachers. Mark inactive teachers. Update any incorrect qualification or status fields. Request BRC unlock if you already submitted the Teacher Module.

Rejection Reason 5: Blank Remarks — What to Do When BRC Doesn't Explain

The BRC returned the data. The remarks field says nothing — or just "Review required." You have no idea what to fix.

What to do:

1. Call the Block MIS Coordinator directly. Do not send a message or email — call. Ask specifically: "Which section did BRC return and what specific value triggered the return?"
2. If the BRC is unavailable, look at your dashboard for any color-coded flags or icons on specific module sections — some portals show section-level flags even without written remarks
3. Compare your submitted data against last year's certified data for the same modules — large unexplained differences between years are the most common cause of blank-remarks returns
4. Do not start editing everything. Fix nothing until you know what specifically triggered the return.

How to Resubmit After BRC Returns Data — The Correct Process

1. Contact BRC and confirm which specific sections or data points you need to correct
2. Request BRC unlock for the returned module (if they have not already unlocked it)
3. Fix only the flagged sections — do not edit anything else
4. Before resubmitting, review the fixed section once more to confirm the number is physically accurate
5. Click Submit on the module
6. Call BRC and inform them that you resubmitted the module — do not wait for them to notice passively
7. Ask the BRC for an estimated timeline for re-verification and make a note of that date

Written By

Ashish Sharma

Digital Marketer & Contributor 🎓 MBA (Marketing & Finance)

Ashish Sharma is an MBA graduate in Marketing and Finance, and a seasoned digital marketer. As a contributor to the UDISE Plus Guide, he combines his analytical expertise and digital strategy skills to simplify complex student data management, school profile updates, and portal registration guidelines for coordinators across India.

LinkedIn Facebook Instagram