Skip to main content

CALPADS error brief · SENR

SENR0028

Multiple Primary Enrollments within CALPADS
Severity Warning
Error type Data Discrepancy
Record type SENR

Official CALPADS rule

What CALPADS is rejecting

Student primary enrollment submission overlaps an existing primary enrollment for the same student in another LEA. This submission will create a concurrent enrollment anomaly. Primary Enrollments are defined as: - Enrollment Status = “10” (Primary); - Enrollment Status = “30” (Short Term), and the enrollment period exceeds 30 days; Note: Enrollments with a N470 (NoShowOther) exit and a Enrollment Exit Date equal to or one day prior to the Enrollment Start Date are NOT considered Primary Enrollments.

Focus fields

Fields validated

1.22 - Enrollment Start Date 1.23 - Enrollment Status Code

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: A submitted primary enrollment overlaps an existing primary enrollment for the same student in another LEA, creating a concurrent-enrollment anomaly.

For this validation, primary enrollments include:

  • Enrollment Status 10 — Primary.
  • Enrollment Status 30 — Short Term, when the enrollment period exceeds 30 days.

An enrollment exited with N470 No Show is not treated as primary when its Exit Date equals its Start Date or is one day before it.

Severity: Warning   Type: Data Discrepancy

Fields validated:

  • 1.22 Enrollment Start Date
  • 1.23 Enrollment Status Code
Humorous illustration of two nearly identical students appearing at once, representing concurrent primary enrollments
Valid SENR records reduce ADA fraud.

SENR0028 versus SENR0027

The same date conflict crosses a different ownership boundary
QuestionSENR0027SENR0028
Where is the conflicting enrollment?Inside the same LEA.In another LEA.
Severity and typeFatal Input Validation.Warning Data Discrepancy.
What happens?The submitted record is rejected until the within-LEA conflict is corrected.The submission can create a concurrent-enrollment anomaly that must be reconciled.
Who controls the conflicting record?Your LEA generally controls both enrollment segments.The other LEA controls its own segment; your LEA cannot simply close it.
First identity questionUsually: which local school/date/status is wrong?First confirm the SSID belongs to the student; an incorrect SSID can make two different students appear to overlap.
Coordination requiredUsually internal coordination between schools and district staff.Inter-LEA coordination using student-specific, privacy-protected channels.
Corrective sequenceRepair the inaccurate local segment, then resubmit.Each LEA corrects only the record it owns; allow the prior LEA’s correction to post before verifying/resubmitting the new history as needed.

A warning is not permission to ignore the overlap. SENR0028 signals that CALPADS may now show two LEAs claiming primary enrollment for the same SSID on the same dates. That can distort concurrent-enrollment, attendance, funding, assessment, cohort, program, and accountability records.

Decide which of three problems you have

Identity, chronology, and status require different corrections
FindingWhat it meansCorrect response
Wrong SSID in your submitted rowYour enrollment was attached to another student’s CALPADS identity.Stop enrollment correction work on that SSID, identify/obtain the correct SSID, repair the SIS, and assess every record sent under the wrong identifier.
Right SSID; prior LEA failed to close enrollmentThe other LEA’s open or late Exit Date creates the overlap.Provide the supported transition information through an authorized channel and request that the prior LEA review and correct its own record.
Right SSID; your Start Date or Status is wrongYour LEA created or enlarged the overlap.Correct your authoritative SIS record and extract; do not ask the other LEA to change a valid enrollment.
Both enrollments actually occurred concurrentlyAt least one primary-status classification may be wrong, or the case requires formal review.Determine instructional responsibility and apply the precise definitions of Primary, Secondary, Short Term, and Non-ADA without recoding solely to clear the anomaly.
Transition date is disputedBoth LEAs may claim the same day based on different attendance/withdrawal evidence.Reconcile the student’s last expected attendance and first attendance; each LEA corrects its own supported dates.

Status codes still matter across LEAs

Confirm the instructional relationship before changing status
StatusRoleSENR0028 concern
10 PrimaryThe institution holds the primary enrollment/instructional responsibility described by CALPADS.Overlapping status-10 records in different LEAs trigger the cross-LEA anomaly.
20 SecondaryThe student concurrently attends while another institution remains primary.Use only for a genuinely secondary enrollment—not as a convenient escape from the warning.
30 Short TermAuthorized short-term placement intended to last fewer than 30 calendar days.If the period exceeds 30 days, this validation treats it as primary and it can conflict across LEAs.
40 Specialized Services OnlyHistorical non-ADA status that ended June 30, 2019.May explain an old record; it is not a current correction choice.
50 Non-ADACurrent status for qualifying non-ADA students only.Do not use it unless the enrollment meets the definition.

Read the cross-LEA chronology

The evidence determines which LEA record changes
Prior LEA recordNew LEA recordWhat to establish
Open status 10; student stopped attending September 20Status 10 begins September 23Prior LEA should review the supported Exit Date; the new LEA should verify its first attendance date.
Status 10 exits September 23Status 10 begins September 23Both claim September 23. Determine which LEA held primary enrollment that day.
Student still attends and remains legitimately primaryNew institution is a concurrent service/program placementThe new LEA must verify whether its record meets a non-primary status definition.
Extended status 30 exceeds 30 daysNew status 10 starts during the open periodThe short-term record is treated as primary for this rule; investigate actual dates and status.
N470 with the supported same-day/one-day-prior Exit DateNew status 10 beginsThe no-show record is excluded from the primary-overlap test.
Existing enrollment belongs to a different childYour row used that child’s SSIDThis is an identity/SSID problem, not an enrollment-date disagreement.

A disciplined inter-LEA handoff

Each LEA changes only the record it owns
Your LEA should provide or verifyAsk the other LEA to verifyDo not do
Correct student/SSID, school, first attendance, Start Date, and intended status.Whether the student remains enrolled; last expected attendance; Exit Date/reason; and status of the conflicting segment.Demand a specific Exit Date without supporting chronology.
The warning details and overlap dates through an authorized channel.Whether a prior exit failed to post or the ODS differs from its SIS.Send excessive personally identifiable information through unsecured communication.
Who will monitor CALPADS and when your record will be rechecked.When its supported correction has posted.Edit or fabricate your own dates to compensate for another LEA’s record.
Whether your local extract will preserve the correction.Whether its next extract could reopen the enrollment.Close the case merely because the current upload produced only a warning.

What commonly produces SENR0028

Symptoms, likely causes, and durable corrections
What you findLikely causeDurable correction
Other LEA enrollment remains openWithdrawal was not processed, rejected, or never transmitted.Prior LEA verifies and posts its supported closure; new LEA verifies its Start Date.
Same transition date appears in both recordsLEAs used different exit/start conventions or both counted the day.Reconcile actual attendance and assign each record its supported dates.
Student never attended the prior LEANo-show coding/date treatment is incomplete.Prior LEA evaluates N470 and the applicable Exit Date rule.
Both LEAs insist their dates are correctThe student may have concurrent activity, disputed attendance, or misclassified status.Escalate through authorized CALPADS/enrollment channels with evidence; do not make unsupported edits.
Identity details do not matchThe submitted SSID may belong to another student or local identity linkage is wrong.Resolve identity/SSID before changing enrollment history and review all connected submissions.
Short-term record remains openStatus 30 exceeded 30 days and became primary for the overlap test.Reconcile actual duration, authorized use, and the subsequent enrollment.
Correction reappears laterOne LEA made a CALPADS-only edit while its SIS/extract retained the old value.Both LEAs repair their authoritative systems and verify subsequent extracts.

Choose the diagnostic pathway

  • Verify student identity and SSID
    • Does the submitted SSID belong to this student?
    • Do authorized identity fields align with the local record?
    • Was an SSID mistyped, reused, merged, replaced, or attached to the wrong local student?
    • Do not change enrollment dates until identity is established.
  • Find the other LEA’s conflicting record
    • Which LEA, school, status, Start Date, and Exit Date create the conflict?
    • Is the record open or does it overlap by one or more days?
    • Is it status 10 or an extended status 30?
    • Does the record appear to be a no-show, duplicate, or legitimate enrollment?
  • Verify your LEA’s enrollment
    • When did the student first attend or become your LEA’s responsibility?
    • Is the Start Date accurate?
    • Is Primary the correct status?
    • Could a rollover, pre-enrollment, or extract default have started the segment early?
    • Will your next extract preserve the correction?
  • Coordinate with the other LEA
    • Use an authorized, privacy-protected contact method.
    • Ask the other LEA to verify its own attendance and enrollment history.
    • Agree on who owns each action and when CALPADS will be rechecked.
    • Each LEA corrects only its own unsupported values.
    • Escalate appropriately if the facts remain disputed.
  • Review downstream effects
    • Did the overlap create a concurrent-enrollment anomaly?
    • Could attendance or ADA reporting be duplicated?
    • Which SINF, SPRG, SELA, assessment, course, cohort, and special-education records depend on these dates?
    • Did the wrong SSID affect other file types?

Read the inter-LEA sequence

  1. IdentityConfirm the SSID.
  2. ConflictFind both segments.
  3. EvidenceReconstruct transition.
  4. CoordinationEach LEA corrects its record.
  5. VerificationConfirm one chronology.

Primary participants

  • CALPADS coordinators in both LEAs
  • Registrar/enrollment and attendance staff
  • Student records or SSID-resolution staff
  • School-site staff with transition evidence
  • District student-services staff when needed
  • SIS and integration support

Evidence to preserve

  • SENR0028 warning and submission details
  • Identity/SSID verification
  • Both CALPADS enrollment segments
  • Last and first attendance chronology
  • Authorized inter-LEA contact record
  • Accepted corrected history

Recommended correction path

  1. Preserve the warning

    Capture submission ID, SSID, both LEAs/schools, overlap dates, Start Date, Status, and untouched SENR row.

  2. Confirm the student and SSID

    Resolve identity before asking either LEA to alter enrollment history.

  3. Compare both enrollment segments

    Place both Start Dates, Exit Dates, statuses, and schools on one timeline.

  4. Verify your LEA’s evidence

    Confirm first attendance, instructional responsibility, Start Date, and Enrollment Status.

  5. Contact the other LEA securely

    Ask it to verify whether the student remained enrolled and to review its own dates, status, exit, or no-show record.

  6. Assign correction ownership

    Each LEA corrects only its unsupported record in its authoritative SIS and extract.

  7. Post in chronological order

    Allow the supported prior-LEA correction to reach the ODS, then verify/resubmit the new enrollment as necessary.

  8. Verify the anomaly is resolved

    Confirm CALPADS shows the intended identity, transition dates, statuses, and no unsupported concurrent primary enrollment.

  9. Review the broader impact

    Check related records and other students affected by the same SSID linkage, rollover, status default, or extract process.

Before closing the issue

  • Confirm the SSID belongs to the intended student.
  • Verify both LEAs’ accepted records reflect actual attendance and ownership dates.
  • Confirm each status code accurately describes the enrollment relationship.
  • Ensure no unsupported concurrent-enrollment anomaly remains.
  • Verify both SIS extracts will preserve the corrected chronology.
  • Review attendance, ADA, assessment, course, program, cohort, dropout, funding, and special-education effects.

Official SENR0028 troubleshooting page  |  SDLA CALPADS Code Sets V.18  |  CALPADS system documents and SSID/Enrollment Procedures