Also see Plan Adoption PPT on SIRAS Padlet

Align SIRAS District Enrollment date with when student starts participating.

If student won't start participating yet, don't fill out district enrollment date yet.

 

For almost all cases of students new (even returning) to your district, SIRAS protocol is to capture an arrival transaction. (Reported or not, this transaction is useful in error resolution later, if needed.)

• If student arrives eligible and started participating immediately, this is a standard plan adoption as of district enrollment date.
• If student arrives eligible and participating, but then immediately stops services or revokes eligibility, this becomes our arrival transaction.
• If student arrives eligible and not participating, contact IEP team to find out:
  • If there is intent to participate immediately, if so archive a plan adoption type arrival transaction. This archive can be used to se
  • If there is intent to participate after an assessment or meeting, archive an arrival transaction to allow meeting to be created, don't report arrival transaction yet.
  • If after the meeting the student will not participate, don't report anything, close meetings and make record inactive.
  • If after the meeting the student will participate, the meeting archive can be used to send the SWDS 1, align SIRAS district enrollment date with plan effective date before closing meeting.
  • If the student will not participate and IEP team does not need to hold an assessment, transferring record to your district is optional.
• If the student arrives eligible for IEP but will start on ISP immediately, we keep the plan type IEP in SIRAS but use the 'plan type is changing' option when archiving the plan adoption. Then staff change the plan type during the meeting to address the new plan and the plan from that meeting reports the new plan on that new plan type.
• If the student arrives eligible for ISP but will start on IEP immediately, we keep the plan type ISP in SIRAS but use the 'plan type is changing' option when archiving the plan adoption. Then staff change the plan type during the meeting to address the new plan and the plan from that meeting reports the new plan on that new plan type.

For students in private school, here is the CALPADS data for students with disabilities CDE PPT for reference.

 

Per EDC 49068 the previous school needs to transfer to the current school (in your district) at least a copy of their records, including IEP documentation.

If the student's IEP is based in CA, then the most recent IEP plan that the student has in theory should already posted in CALPADS so if they are not coming from a SIRAS district, you can complete the MIS Summary page from SWDS, MEET, PLAN & SERV records posted by the previous district.

If the student's IEP was not based in CA, (and CALPADS has no data at all) then this is when we use SELPA_FROM = Out of State.  That indicator tells SIRAS to send more information than would normally be reported in plan adoption archive.

 

If your district has more than 40 incoming students from previous SIRAS districts that all need plan adoptions, SIRAS can batch archive them for you.

Email [email protected]

 

Requirements for batch archive of incoming students:

• Leave the incoming record active status as Pending, SIRAS will set it to Active.
• Fill in the district enrollment date, aka first day of school when they start to participate
• Fill in the school type and school attending
• All records to be batch archived must have the same district enrollment date
• (Filling in providers, optional but useful)
• If developmental delay is the disability, see this page.

 

Procedure for individually archiving a plan adoption of incoming student:

• Confirm student is eligible and will start participating
• Leave the incoming record active status as Pending, SIRAS will set it to Active.
• Fill in the district enrollment date, aka first day of school when they start to participate (this will be the report event date)
• Fill in the school type, school attending, grade & providers
• Update MIS Summary page to have the latest 'plan' information. EX, new last IEP date? new last EVAL date?  new services?
• Click the archive for reporting button

 

 

 

 

 

 

 

Before we archive:

Update district enrollment date to the date they start participating, typically the same as the enrollment start date in CALPADS.
Without overlapping enrollment in CALPADS, GERR0005

 

How to archive:

Click on the Archive for reporting button

 

 

 

 

 

 

Once the archived transaction is created, it is automatically set to send to CALPADS

This type of archive will send PLAN and SERV records with a plan effective date equal to the district enrollment date which set the report event date of the archived transaction.

 

If this student was 'eligible not participating' or 'eligible not enrolled' in CALPADS upon arrival and they now are starting to participate again.

After this plan adoption archive is reported to CALPADS, we can open it back up and set the report status to SWDS Only and this same archive will send a SWDS = 1 record with the SWDS effective as of date equal to the district enrollment date.