Show Me: Fix a Plan Adoption Archive After It Was Created

Aug 19, 2026

Use this worked example when:
The Plan Adoption archive already exists, but staff have verified that one of its CALPADS reporting properties needs correction.

Data Monitoring Journey: Learn · Plan · Monitor → Investigate → Correct → Submit → Verify → Reconcile & Repeat
This worked example supports incoming-student onboarding and Plan Adoption.

Do not use archived-record editing to force a desired result.
First confirm what actually happened and whether the error is in Current, the archived transaction, CALPADS history, or a later event. See Archived Transactions and Archive for Reporting for the correction boundary.

What Needs Fixing?

The Plan Adoption already exists, but I need to report SWDS 1This is a follow-up correction after the Plan Adoption baseline was already created and the verified participation-status change still needs to be sent.

I selected the wrong Reason for PLANCorrect Same Plan Type vs. Different Plan Type after verifying which arrival scenario actually occurred.

Fix 1: Send the Missing SWDS 1 From the Existing Archive

Use the creation-time option when you still can.
If the Plan Adoption has not yet been created, use the normal SWDS 2/3 → SWDS 1 Plan Adoption workflow instead. This section is for the source scenario where Plan Adoption was already created and the SWDS participation transaction still needs to be reported.

1. Open the Plan Adoption archive

Select the Plan Adoption from the archived-record menu on the MIS Summary.

MIS Summary archived records menu showing the Plan Adoption transaction to correct

Select the existing Plan Adoption transaction.

2. Open the archived record for editing

Archived Plan Adoption showing the Open archived record for editing button

Enter archived-record edit mode.

3. Open Edit CALPADS Reporting

Archived Plan Adoption in edit mode with Edit CALPADS Reporting button

Open the reporting-property editor for the archive.

4. Open the Report Status menu

Edit CALPADS Reporting dialog with Report Status menu highlighted

Use the Report Status control only after verifying the correction is actually needed.

5. Select SWDS Only

In this source example, the PLAN/SERV Plan Adoption baseline had already been created and the remaining correction was the participation-status transaction, so the archive was changed to SWDS Only.

Report Status dropdown showing SWDS Only selected

SWDS Only is used here to send the verified participation-status correction after the Plan Adoption baseline already exists.

6. Validate / Save

Edit CALPADS Reporting dialog with Validate Save button highlighted after choosing SWDS Only

Validate and save the corrected reporting property.

7. Return to Current

Finish archived-record editing and return to Current. Verify the archive/reporting status and continue through the normal submission/verification cycle.

SIRAS archived record view with Go To Current Record highlighted

Return to Current after the archived reporting correction is saved.

Fix 2: Correct the Reason for PLAN

Use this when staff originally flagged the Plan Adoption as a different-plan-type adoption but the verified scenario is same plan type, or when the opposite correction is required. The source example changes 4 — Adoption Different Plan Type to 3 — Adoption Same Plan Type.

1. Select the Plan Adoption archive

MIS Summary archived records menu showing the Plan Adoption selected for Reason for PLAN correction

Open the Plan Adoption transaction that contains the wrong Reason for PLAN.

2. Open the archived record for editing

Archived Plan Adoption showing Reason for PLAN 4 and Open archived record for editing

Enter edit mode for the existing archive.

3. Open Edit CALPADS Reporting

Archived Plan Adoption edit mode with Edit CALPADS Reporting highlighted

Open the archive's CALPADS reporting properties.

4. Choose the verified Reason for PLAN

Select the option that matches the actual arrival:

Set adopt same plan type when the receiving LEA adopted the same plan type; or
Set adopt different plan type when the incoming plan was adopted and the plan type is changing in the follow-up meeting.

Edit CALPADS Reporting dialog showing Reason for PLAN options including same plan type and different plan type

Choose the Reason for PLAN that matches the verified Plan Adoption scenario.

Edit CALPADS Reporting dialog showing Reason for PLAN changed to 3 Adoption Same Plan Type

Source example after changing the archive to Adoption Same Plan Type.

5. Validate / Save and return to Current

SIRAS archived-record editing view showing the saved Reason for PLAN and Go To Current Record

Save the correction, finish editing, and verify the result before resubmission.

After either correction:
Verify the archive, submit the applicable pending transaction, and confirm the CALPADS result. Use Reporting Data to CALPADS and CALPADS Submission Log for the submit/verify stages.