Process for Error Resolution
Aug 05, 2026
Process for Error Resolution
Use this process when onboarding a new student, resolving a CALPADS IVR, reviewing a certification error or CDD, or investigating a mismatch between SIRAS and CALPADS.
The goal is not simply to remove the message. The goal is to make the systems accurately represent what occurred.
Do not begin by changing data.
Capture the complete error, identify the applicable date and transaction, and confirm the field event before selecting a correction.
Capture the complete error, identify the applicable date and transaction, and confirm the field event before selecting a correction.
Which Article Do I Need?
| SIRAS Built-in Validation SystemSIRAS displayed the message before submission. | CALPADS IVR Errors Posted in SIRASCALPADS rejected a transaction and the error now appears in SIRAS. |
| CALPADS Error SummaryLook up the meaning and first checks for a CALPADS code or message. | Process for Error ResolutionUse the governing investigation and correction process. |
| CALPADS Submission Log HelpA transaction appears missing or rejected, but no error is posted in SIRAS. | Reporting Data to CALPADSReview the complete generate, send, import-error, and resend cycle. |
Contents
| Check Current Known Issues | Apply the Three Perspectives |
| Determine When the Error Is As Of | Review Related Errors |
| Identify the Correction Source | Complete the Correction Cycle |
| When to Stop and Ask for Help |
Check Current Known Issues
Before changing accurate data, check whether CALPADS has identified a current system issue affecting the error or report.
- When the message is a known issue, follow the current CALPADS or SIRAS notice.
- Do not alter accurate dates or values solely to work around an unresolved system defect.
- Remove or resend a posted error only when the issue is resolved or the documented workaround is complete.
Apply the Three Perspectives
There are three sides to the story:
- CALPADS: What enrollment and SEDS transactions are posted?
- SIRAS: What do the Current record, meeting, and archived transactions show?
- Field reality: What did the IEP team, enrollment staff, family records, and source documents establish actually occurred?
Give the greatest weight to verified field reality.
SIRAS and CALPADS may each contain incomplete information. Do not “fix” either system until the team understands the real event being represented.
SIRAS and CALPADS may each contain incomplete information. Do not “fix” either system until the team understands the real event being represented.
Determine When the Error Is As Of
- Is the message associated with new data entry or an older transaction?
- What Report Event Date or certification date controls the error?
- Does the correction belong in Current data, an existing archive, CALPADS enrollment, or a new transaction?
- Did the relevant enrollment, participation, meeting, plan, service, or exit occur before or after the reporting date?
A correction appropriate for Current data today may not correct a historical transaction representing an earlier date.
Identify the Correction Source
| Finding | Likely correction source |
|---|---|
| SIRAS Current data is wrong and future work also needs the corrected value. | Correct Current data, then determine whether the historical archive also requires correction. |
| Current data is correct, but the rejected archived transaction is wrong. | Correct the linked archive without changing what is currently true. |
| The reportable event occurred outside ordinary meeting finalization. | Use Archive for Reporting when its documented requirements apply. |
| CALPADS enrollment or SIS-controlled information is wrong or missing. | Coordinate the enrollment or SIS correction. Do not distort SIRAS dates to fit incorrect enrollment. |
| The event occurred, but the meeting remains open. | Use the applicable Meeting In Progress workflow. |
| A required event remained pending across the reporting date. | Use the applicable Pending As Of MEET workflow and accurate delay code and label. |
| CALPADS already contains the correct transaction and SIRAS is trying to send it again unnecessarily. | Review whether the archive should remain or return to Complete rather than resending a duplicate. |
Do not reactivate a finalized meeting merely because CALPADS reports an error.
Most reporting corrections belong in Current data, an archive, enrollment, a resubmission, or a specialized reporting workflow.
Most reporting corrections belong in Current data, an archive, enrollment, a resubmission, or a specialized reporting workflow.
Complete the Correction Cycle
- Correct the identified source while preserving the actual event dates.
- Revalidate the student or archive.
- Clear the imported IVR only after its cause is corrected.
- Set the applicable archive to Pending when the corrected transaction must be resent.
- Send the data again.
- Verify acceptance in the submission log or CALPADS history.
- Regenerate the applicable report or snapshot and confirm that the discrepancy is resolved.
- Review related records for the same student.
Use CALPADS IVR Errors Posted in SIRAS for the imported-error mechanics and CALPADS Submission Log Help when no new IVR appears.
When to Stop and Ask for Help
Contact SIRAS Support after the first or second informed attempt when:
- the field history cannot be established;
- multiple archives, duplicate records, transfers, or ownership histories conflict;
- the proposed correction would require changing an accurate finalized record;
- the error returns after the source was corrected and resent;
- a backdated, deletion, specialized CALPADS, or historical reconstruction workflow appears necessary; or
- you are not sure whether the correction belongs in SIRAS, the SIS, or CALPADS.
Include:
- SSID;
- complete error code and text;
- Report Event Date and applicable archive;
- the relevant CALPADS report, job, or screenshot;
- what actually occurred in the field; and
- the correction attempts already completed.
Email: [email protected]
