CALPADS error brief · SENR
SENR0041F1
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
SENR DataRecommended correction path
Suggested resolution
Certification lens
This rule is evaluated from the Fall 1 snapshot and related ODS histories. A record can pass transactional validation and still fail when CALPADS compares the student, dates, school, program, language status, demographics, or special education relationships effective for certification.
Fields and records evaluated
- SENR enrollment histories
- Intra-LEA Concurrent Enrollment anomalies
Six questions that resolve this certification finding
| Question | Specific finding | Evidence |
|---|---|---|
| What passed? | Individual source transactions may have posted successfully. | Submission detail and ODS history |
| What did Fall 1 expect? | One coherent primary-enrollment history within the LEA for each student and date. | Census-day snapshot logic |
| What is inconsistent? | Two schools or records within the LEA assert incompatible enrollment ownership. | Student-level certification detail |
| Who owns correction? | Registrar or enrollment staff and the SIS/state-reporting owner; CALPADS staff resolve snapshot or anomaly state after the authoritative SENR history is corrected. | Authoritative local system and program records |
| What must change? | Correct the inaccurate SENR history first, then formally resolve the intra-LEA CCE. | Add, replace, delete, or sequence supported records |
| What proves resolution? | 1.0 Certification Errors; 12.1 Anomaly Status Report; CCE management detail | Refreshed aggregate and supporting reports |
Concrete checks
- Compare both schools, statuses, start dates, and exit dates.
- Determine whether one record is a true duplicate or whether dates/statuses are wrong.
- Do not delete a legitimate secondary enrollment.
- Check the next extract so the resolved record is not recreated.
Recommended correction path
- 1
Identify the exact snapshot row
Match the student, school, LEA, academic year, and census/snapshot revision implicated by SENR0041F1.
- 2
Compare the authoritative source
Use the owning SIS, program, language, enrollment, or special education record. Registrar or enrollment staff and the SIS/state-reporting owner; CALPADS staff resolve snapshot or anomaly state after the authoritative SENR history is corrected.
- 3
Test the complete rule
Compare both schools, statuses, start dates, and exit dates. Determine whether one record is a true duplicate or whether dates/statuses are wrong. Do not delete a legitimate secondary enrollment. Check the next extract so the resolved record is not recreated.
- 4
Choose the supported transaction
Correct the inaccurate SENR history first, then formally resolve the intra-LEA CCE.
- 5
Correct the source and resubmit
Repair the authoritative record or extract mapping so the next submission will not recreate the discrepancy. Allow all dependent transactions to post in chronological order.
- 6
Regenerate and reconcile
Refresh the Fall 1 snapshot, confirm the error clears, and reconcile 1.0 Certification Errors; 12.1 Anomaly Status Report; CCE management detail. Aggregate and student-level results must agree.
Official SENR0041F1 guidance · Current certification and real-time reports · SDLA CALPADS report directory







































































