CALPADS error brief · SINF
SINF0068
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
2.11 - Student Legal First Name 2.13 - Student Legal Last Name 2.18 - Student Birth Date 2.19 - Student Gender CodeRecommended correction path
Suggested resolution
Read the complete validation
CALPADS comparison: At least one of two pathways must match the latest SINF record:
- Pathway A: Student Gender Code and Student Birth Date year match; OR
- Pathway B: Student Legal First Name and Student Legal Last Name match.
Severity: Warning Type: Data Discrepancy
- 2.11 Student Legal First Name
- 2.13 Student Legal Last Name
- 2.18 Student Birth Date
- 2.19 Student Gender Code
A warning is not permission to ignore identity risk. The SINF row may still post because the submitted information is correct. But if the SSID belongs to someone else, posting can place one student’s legal identity and history onto another student’s statewide record.
Understand the two matching pathways
| Names match? | Gender + birth year match? | Validation outcome | Interpretation |
|---|---|---|---|
| Yes: First and Last | Yes | No SINF0068 | Both pathways support the identity match. |
| Yes: First and Last | No | No SINF0068 through Pathway B | A supported birth/gender correction may be occurring; verify it. |
| No | Yes: Gender and birth year | No SINF0068 through Pathway A | A supported legal-name change may be occurring; verify it. |
| No | No | SINF0068 warning | Neither pathway sufficiently anchors the row to the latest SINF identity. |
Precision matters: Pathway A compares Gender and the year of Birth Date—not necessarily the complete month/day. Pathway B requires both Legal First and Legal Last Name.
Decision tree: do not cross the identities
- 1
Does the submitted SSID belong to this student?
No or uncertain: Stop. Do not update SINF. Compare local ID, enrollment history, prior names, complete birth date, gender history, and other authorized identifiers. Resolve the SSID/duplicate issue first.
Yes: Continue. - 2
Are the submitted demographics supported?
No: Correct the local student record and SINF extract.
Yes: Continue; the latest CALPADS demographics may be stale. - 3
Is this a legitimate legal-name change?
Yes: Preserve the same confirmed SSID and submit the supported legal identity with the correct effective date. Gender plus birth year may provide Pathway A continuity.
No: Investigate spelling, truncation, transposition, nickname/alias mapping, or the wrong person. - 4
Is Birth Date or Gender being corrected?
Yes: Verify authoritative evidence and effective-date handling. Matching legal first and last names may provide Pathway B continuity.
No: Investigate incorrect mappings, defaults, or identity crossover. - 5
Do neither pathway’s pairs match?
Require deliberate identity review before accepting the change. Multiple simultaneous differences create the greatest risk of posting one student’s information to another SSID.
Common scenarios and the safe response
| What you find | Likely explanation | Safe response |
|---|---|---|
| Last name changed; gender and birth year match | Possible supported legal-name change. | Confirm the same person and legal source; update the same SSID with the proper effective date. |
| Birth date corrected; legal first/last names match | Possible prior DOB error. | Verify the complete DOB from authoritative records; correct the SIS and submit supported SINF. |
| Nickname submitted as Legal First Name | Preferred/alias field mapped into field 2.11. | Restore Legal First Name and use the appropriate preferred/alias fields. |
| All four demographics resemble another student | Wrong SSID, sibling/twin selection, merge, or local crosswalk defect. | Stop the update and perform formal identity/SSID reconciliation. |
| Names differ only because of punctuation, spacing, order, or truncation | Normalization or field-mapping defect. | Compare the raw SINF row with authoritative legal-name fields; repair the extract. |
| ODS is stale; submitted identity is fully supported | Legitimate update after documentation change or earlier error. | Because SINF0068 is a warning, retain the correct supported data, post as appropriate, and verify resulting history. |
Compare enough information to identify the person
- SSID and Local Student ID
- Legal first, middle, and last names
- Prior legal names and supported aliases
- Complete birth date—not merely year
- Gender history
- School and enrollment history
- Parent/guardian information when authorized
- Authoritative cumulative-file/source documentation
No single field should decide a high-risk identity reconciliation. Twins, siblings, shared names, changed names, and prior data-entry errors require the full record context.
Recommended correction path
- 1
Preserve both versions
Capture the rejected/warning row and the latest CALPADS SINF record before posting further changes.
- 2
Verify SENR and SSID
Confirm the submitted SSID, local student, school, and enrollment history describe the same person.
- 3
Test both matching pathways
Compare Gender plus birth year, then Legal First plus Legal Last Name. Record which pair changed.
- 4
Return to authoritative evidence
Establish the correct legal name, full DOB, and gender information using authorized records and procedures.
- 5
Choose the correct identity action
Correct erroneous submitted demographics; retain a supported legitimate change; or stop and initiate SSID/duplicate reconciliation when the SSID is wrong or uncertain.
- 6
Correct SIS and mappings
Repair legal/preferred/alias selection, local-to-SSID crosswalks, DOB transformations, defaults, or record merges.
- 7
Post deliberately and verify
Confirm the correct student’s effective-dated SINF and SENR histories remain attached to the correct SSID.
- 8
Audit related records
Review siblings, twins, merged records, and students processed by the same identity crosswalk or extract defect.
Before closing the issue
- Confirm the SSID belongs to the intended student.
- Document whether Pathway A, Pathway B, or neither matched.
- Verify every changed demographic from authoritative information.
- Ensure a preferred name or alias did not overwrite a legal-name field.
- Review both SINF demographic history and SENR enrollment history after posting.
- Confirm the SIS and next extract reproduce the correct identity.
Official SINF0068 page | CALPADS Student Information guidance