[This is a live document intended to be a resource that can be returned to for help and guidance on these subjects.]

 

Upcoming Census Date for Fall 1 2024 is 10/2/2024

 

The data monitoring procedures are ongoing maintenance preparing for certification.

Do we know who our data reviewers are?

Are they staying in contact and meeting

 

• Attend Fall 1 2024 CDE Roadshow Trainings
• Review Fall 1 2025 Roadshow Slide Deck
• Each LEA confirm Fall 1 plan overall
• Also review CALPADS Statewide Leadership Training Presentation for Fall 2024 (good 'Preparing for Fall 1' model information.)
• Each LEA confirm SPED Fall 1 tasks who they are assigned to.
• Each LEA confirm local SPED Fall 1 deadlines with SELPA.
• Each LEA confirm scheduled check in with SELPA.
• Make sure the CALPADS SIS Coordinator knows when SEDS coordinator is done sending data from SIRAS.
• Make sure each LEA is planning on doing the Census day reports on or as close to the literal census date this year of 10/2/2024
• Review CALPADS Statewide Leadership Training Presentation for Fall 2024 (good 'Preparing for Fall 1' model information.)

 

 

Important resources for local planning:

• CALPADS FALL1 Roadmap
• Fall 1 Preparation Checklist from CDE - Each district should have a LEA approve planning meeting and go over this list.

Planning to get to LEA Approve

• Keep up with data monitoring as it reduces errors.
• SIRAS Fall 1 suggested due dates
• Pick a goal date to LEA approve by, SIRAS suggests Nov. 22nd.
• Plan to have all IVR errors cleared in SIRAS by Nov. 4th
• Plan to run data monitoring queries on data before it is sent and even after it is sent.
• Once all IVR errors are cleared and no more data needs to be sent, resolve any final SPED related CDDs in CALPADS
• Once all CDDs are resolved in CALPADS, we can look for a snapshot to certify.
• Who is the team to make this happen? Have a meeting to plan how the teams check in with each other.
• CALPADS enrollment, SIRAS SEDS coordinator sending data, key  IEP Team contacts like program specialists who generate that can help explain context of what happened in the field.
• Plan to get all meetings either finalized, independently reported, or a pending as of record sent by an agreed upon date.
• CALPADS SIS coordinator keeps in contact with SEDS coordinator to know when all data needing to be sent to CALPADS for Fall 1 has been sent. This is all events with report event date 10/2/2024 or earlier.
• Meetings that happened on or before 10/2/2024 that can't be finalized before LEA approve need to have MEET record archived to report the meeting.

 

Before Fall 1 10/2/2024

• Keep doing these SPED Fall 1 Tasks until complete.
• Monitor students needing updated program setting
• Look for program setting and % in gen. ed. anomalies
• Look for HS students turning 16 prior to Fall 1 to ensure the 8 transition reg. questions have set of Y/N answers in a plan effective prior or to 10/2/2024,
• Run 16.21 to monitor for missing plan adoptions
• Run 16.21 to compare to meetings held late in SIRAS

 

On Fall 1 10/2/2024

• Do the:  Census Day Data Pull Report Tasks
• Print and save 16.12 statistical report from SIRAS.
• Print and save 16.13 statistical report from SIRAS.
• Print and save 16.15 statistical report from SIRAS.
• Print the Age by Disability matrix report from SIRAS.
• Run any other statistical grouped lists, matrix or table reports and securely store the .xlsx  and .pdf files together in a Fall 1 2024 secured folder.
• Run FTE reports in SIRAS (to compare to FTE from 16.14 from Fall 1 2024)
• Run Out of Home Care Search (Padlet Link)
• Run Credentialing Audit Search (Padlet Link)
• Run Low Incidence Search (Padlet Link)
• Do Personnel report research

 

After Fall 1 10/2/2024

• Harder to fix problems as any archives made have dates after Fall 1.
• Use reporting period block to filter only sending event dates directly related to completing Fall 1.
• Don't Disable reporting period block until after Fall 1 amendment window ends.
• Meetings done on or prior to 10/2/2024 that can't be finalized need to have their meetings sent so these records don't look overdue.
• Records that are already overdue as of 10/2/2024 minimally need a 'pending' record record sent designating when the meeting event was created in SIRAS. This tells your FMTA your district is aware of the record being overdue. Include meeting delay reason if at all possible.