CALPADS error brief · SINF
SINF0555
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
2.39 - Guardian 1 First Name 2.41 - Guardian 2 First NameRecommended correction path
Suggested resolution
Complete validation
Current rule: If field 2.41 is populated, field 2.39 must be populated.
Severity: Fatal Type: Data Discrepancy
- 2.39 Guardian 1 First Name
- 2.41 Guardian 2 First Name
The April 2025 update narrowed this validation to these two first-name fields.
Guardian 1 does not mean “more important,” custodial, biological, or primary contact. It is simply the first CALPADS storage position. Reorder complete people as needed; never split one person across Guardian 1 and Guardian 2.
Family-information framework
Correction choices
| What you find | Correction | Caution |
|---|---|---|
| Only one person is reported in Guardian 2 | Move that complete person’s supported fields into Guardian 1. | Move the whole information group, not only the first name. |
| Two people exist; Guardian 1 First Name was omitted | Restore the supported Guardian 1 First Name. | Verify all values remain attached to the correct person. |
| Guardian 2 was populated accidentally | Remove the unsupported Guardian 2 group. | Do not fabricate Guardian 1 to preserve bad data. |
Recommended correction path
- 1
Inspect both complete groups
Review fields 2.38–2.42 and 2.50, not just first names.
- 2
Verify authorized source information
Confirm which values belong to each person and any privacy restrictions.
- 3
Fill Guardian 1 first
Move or restore the first complete supported person before Guardian 2.
- 4
Correct mappings
Repair contact-priority filters, imports, or Guardian 1/2 slot assignment.
- 5
Resubmit and verify
Confirm SINF0555 clears without crossing people or education values.