Show Me: Plan Adoption When IEP/ISP Plan Type Will Change

Aug 19, 2026

Use this worked example when:
The student arrives with an existing plan that must first be adopted by the receiving LEA, but the receiving team expects the plan type to change (for example, IEP ↔ ISP) in the follow-up meeting.

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

Adopt the plan the student arrived with.
Do not change Current to the future plan type before creating the Plan Adoption. The Plan Adoption should preserve the incoming plan. Use the Plan Type (IEP/ISP) will be changing at the next meeting option so the later meeting can document the actual change.

Use the current meeting-purpose guidance for the follow-up event that establishes the new plan type. See Plan Adoption, Selecting Meeting Purpose Issues, and Forms Manager Meeting Purposes.

Expected Result

At Plan Adoption	Special option	Verify in archive
Current still represents the incoming plan type.	Plan Type (IEP/ISP) will be changing at the next meeting.	PLAN + SERV Reason for PLAN: 4 — Adoption Different Plan Type.

Show Me the Steps

1. Validate the incoming plan as it actually exists now

Fully update the MIS Summary from the incoming plan/history, but keep the incoming plan type. Validate and resolve errors before archiving.

MIS Summary showing Validate with errors and warnings before a plan-type-changing Plan Adoption

Validate the incoming Current record before creating the archive.

2. Choose Archive for Reporting after validation

MIS Summary showing Archive for Reporting after validation

Archive only after the incoming plan and District Enrollment Date are correct.

3. Correct a missing District Enrollment Date before continuing

If the preview reveals the date is missing, cancel the Plan Adoption and correct Current first.

Plan Adoption preview and MIS Summary demonstrating a missing District Enrollment Date

Stop and correct the source date rather than archiving an incomplete arrival.

4. Enter the verified District Enrollment Date

MIS Summary showing the verified District Enrollment Date

Use the actual receiving-district enrollment date.

5. Select Plan Adoption and the plan-type-change option

Select Plan Adoption at new LEA, then check Plan Type (IEP/ISP) will be changing at the next meeting. Confirm the Report Event Date equals the District Enrollment Date.

Archive for CALPADS Reporting with Plan Adoption selected and Plan Type will be changing at the next meeting checked

The special flag tells SIRAS this adoption preserves the incoming plan while a later meeting changes plan type.

6. Confirm the archive was created

Read the confirmation message and verify the resulting Current status for this student.

SIRAS confirmation message after creating a plan-type-changing Plan Adoption archive

Confirm that the archive was created successfully.

7. Open the Plan Adoption archive

Archived records menu showing the new IEP Plan Adoption transaction

Open the new transaction to verify its reporting properties.

8. Verify Reason for PLAN = 4

Confirm PLAN + SERV and Reason for PLAN = 4 — Adoption Different Plan Type. The follow-up meeting—not the adoption archive—documents the receiving team's actual new plan type.

Archived Plan Adoption showing PLAN and SERV with Reason for PLAN 4 Adoption Different Plan Type

Expected archive when the incoming plan type will change at the next meeting.

Next: Return to Plan Adoption and create the appropriate follow-up meeting only after the incoming baseline has been established.