339
When PLAN records are reported by SIRAS, they are also sent with SERV service records.
As any plan will need to have at least one service as part of the plan or offer of FAPE that it represents.
The first new PLAN record for a student newly arriving or returning, who probably participate is the plan adoption archive.
We say 'probably' because for expediency of due dilligence, Districts should create a plan adoption archive and report it upon enrollment to signal the acceptance of child responsibility for this SWDS.
Participation may or may not start immediately but that should not hold up the plan adoption archive from being sent.
If we for a fact know upon enrollment the student will not participate, as in the family informs the district, then we can report a new non participation SWDS reason for cessation of services or even a new not eligible SWDS if the student is withdrawn from SPED.
To reiterate, those are two separate scenarios for newly arriving or returning students.
- Eligible student will participate at some point.
- Eligible student will for sure not participate. This scenario will involve a PWN being documented and uploaded to SIRAS.
A new PLAN record for a student already enrolled is typically represents the most recent offer of FAPE as represented by data elements of the MIS Summary page.
Plan records should always have at least one SERV record with same plan effective date.
The Plan Information of a CALPADS record is what populates the Special Ed. Information area of SIRAS (see screenshot at bottom.)
If the parent response to the meeting event is 'does not accept the plan' then the archive created from that meeting will not be allowed to send PLAN or SERV records.
Those archives must be made DNR.
If a students SWDS is not 1, there should not be any PLAN or SERV records with a plan effective date after the status effective date of SWDS 2 or 3.
SIRAS sends PLAN as A add record to CALPADS keyed around the plan effective date.
This will add a new PLAN record with the a plan effective date.
Services are associated to the plan by the plan effective date.
Example Plan Submission Progression
- Initial Evaluation on 8/14/2023 with Plan Effective Date of 8/21/2023
- to Annual Plan Review dated 6/25/2024 with Plan Effective Date of 6/26/2024
Initial Evaluation on 8/14/2023 with Plan Effective Date of 8/21/2023
Note the SERV records are linked thru plan effective date to the plan.
to Annual Plan Review dated 6/25/2024 with Plan Effective Date of 6/26/2024
Note the SERV records are linked thru plan effective date to the plan.
