CALPADS error brief · SDEM
SDEM0200
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
7.04 Effective Start Date 7.06 Reporting LEARecommended correction path
Suggested resolution
What this error actually means
CALPADS compares the organization’s official open/closed dates with the effective-dated SDEM interval. A successor LEA, obsolete code, or historically incorrect interval can cause the mismatch.
Valid versus invalid
| Example | Submitted value or condition | Interpretation |
|---|---|---|
| Valid | LEA open dates overlap the SDEM effective period | Organization and record history agree. |
| Invalid | SDEM begins after the LEA closed | Use the accountable open successor only if it owns the record. |
| Invalid | SDEM ends before the LEA opened | Correct the organization or historical dates. |
| Unsafe shortcut | Replace the code because the LEA is closed today | Preserve the LEA that was valid historically. |
Fields validated
- 7.06 Reporting LEA with 7.04/7.05 Effective Start and End Dates
Recommended correction path
- 1
Open the rejected submission detail
Locate the exact physical row, field number, submitted value, Reporting LEA, SEID, Academic Year, and effective dates.
- 2
Read the raw exported value
Do not rely only on the formatted HR or SIS screen. Inspect spaces, delimiters, zero padding, dates, and local code translations.
- 3
Test this rule
- Resolve the seven-digit Reporting LEA to its official organization.
- Compare official open/closed dates with 7.04 and 7.05.
- Identify reorganizations, mergers, and successor LEAs.
- Verify which LEA actually employed/reported the staff member for that period.
- 4
Confirm correction authority
HR/personnel staff own authoritative employment and demographic facts; technical staff own mappings and export behavior; the CALPADS operator verifies the submitted representation. Protect confidential personnel data throughout the review.
- 5
Correct the responsible source
Correct the evidence-supported Reporting LEA or effective interval. Do not rewrite a historically valid LEA merely because it later closed.
- 6
Resubmit and reconcile downstream records
Confirm the row posts under the intended SEID and Reporting LEA. Review Staff Profile Report 4.4 and relevant Reports 4.1–4.5; then check whether the same mapping affected other staff, SASS assignments, or CRSE sections.
Official SDEM0200 guidance · CALPADS Staff Demographics guidance · Fall 2 Reporting Roadmap · Report 4.4 Staff Profile List · Current CALPADS specifications and code sets







































































