CALPADS documentation of 16.21 Report

 

We can use the 16.21 weekly to identify students that need plan adoptions.

These are the records where your district is not listed as the Plan LEA Name, these will require plan adoptions.

 

When using 16.21 report for Fall 1 or End of Year, be sure to run the report with the 'as of date' = to your current census date.

• Fall 1, first Wed. in Oct.  This year it is 10/2/2024
• EOY 4, 6/30.      This next year it will be 6/30/2025

 

Each listing should be checked for accuracy:

If not accurate, use Siras to fix the data in CALPADS that got it on this list.

If it is accurate, verify meeting delay reason is valid and documented.

• Here is CALPADS documentation on using 16.21 (CALPADS documentation)
• Here is a Siras helpsheet on using 16.21 (Padlet link)

 

Finding incoming SWDS needing Plan Adoption

When a student record appears in the 16.21 report and the SELPA and/or district does not match your district, they most likely need a plan adoption.

Have staff verify they will begin participating. If they will not, see new or returning student with disability status.

 

Monitoring Categories

• Plan review Held late
• Reevaluation Held late
• Overdue Plan Review, No Pending Record
• Overdue Plan Review, Pending Record
• Overdue Revevaluation, No Pending Record
• Overdue Revevaluation, Pending Record
• Initials that are overdue - Yet to be incorporated.

 

Plan review Held late

The most recent plan review date (prior to census date) is more than a year prior to previous plan review in CALPADS.

• (Was the most recent plan review or Initial IEP that we know was held not showing as a MEET record in CALPADS?)
• (Was this meeting continued and the meeting date changed to the continuation date when it didn't have to?)
• (Was meeting held after 2/28/2024 and previous plan review was literally one year to the day prior? Leap year exception.)

 

Reevaluation Held late

The most recent reevaluation date (prior to census date) is more than three years prior to previous plan review in CALPADS.

• (Was the most recent initial IEP or reevaluation meeting that we know happened not showing as a MEET record in CALPADS?)
• (Was meeting held after 2/28/2024 and previous reevaluation was literally three years to the day prior? Leap year exception.)

 

 

Overdue Plan Review, No Pending Record

The most recent plan review date (prior to census date) is more than a year prior to previous plan review in CALPADS.

MEET record with Pending As Of Date in CALPADS. Pending as of date reflects date of when meeting was planned.

• Is your district under some level of CDE monitoring where FMTA are requesting this type of record be sent?
• If so you would consider sending a pending (meeting planned as of) MEET record if it's really overdue
• Be sure to add meeting delay reason before archiving the Pending As Of transaction.
• If meeting happened, the new meeting date will either remove SSID from this list or switch monitoring category to Plan Review Held Late.

 

Overdue Plan Review, Pending Record

The most recent plan review date (prior to census date) is more than a year prior to previous plan review in CALPADS.

MEET record with Pending As Of Date in CALPADS. Pending as of date reflects date of when meeting was planned.

• This type of MEET record can send reason meeting is delayed in meeting delay reason.
• There is no meeting date only a pending as of date.
• The pending as of date should be the date the meeting event was created in SIRAS
• This record is archived on MIS before creating meeting event in IEP Manger.
• If meeting happened, there is no more need to send this type of record.

 

Overdue Revevaluation, No Pending Record

The most recent reevaluation date (prior to census date) is more than three years prior to previous plan review in CALPADS.

MEET record with Pending As Of Date in CALPADS. Pending as of date reflects date of when meeting was planned.

• Is your district under some level of CDE monitoring where FMTA are requesting this type of record be sent?
• If so you would consider sending a pending (meeting planned as of) MEET record.
• This type of MEET record can also send reason meeting is delayed in meeting delay reason.
• If meeting happened, we don't send this record.
• If meeting happened, the new meeting date will either remove SSID from this list or switch monitoring category to Reevaluation Held Late.

 

Overdue Revevaluation, Pending Record

The most recent reevaluation date (prior to census date) is more than three years prior to previous plan review in CALPADS.

MEET record with Pending As Of Date in CALPADS. Pending as of date reflects date of when meeting was planned.

• This type of MEET record can send reason meeting is delayed in meeting delay reason.
• There is no meeting date only a pending as of date.
• The pending as of date should be the date the meeting event was created in SIRAS
• We do this before creating meeting event in IEP Manger.
• If meeting happened, there is no more need to send this type of record.

 

 

 

How to run the 16.21 report:

• Log in to CALPADS.
• Click the Reports section on the left-hand side.
• Click Accountability/Monitoring Reports.
• Click 16.21 Monitoring link.

 

In the report builder, you can choose any ‘As Of Day’ from the Academic Year that you like.  In this example, we have chosen as of January 21^st. You will want to run it as of today or a future date like the upcoming Census Date.

Click the View Report button

When the report is ready, click on the disc icon.

Select the Excel option.

Locate the filter option from the Home area, look on the far right hand side of the toolbar up top for the sort/filter icon.

Or, click on the Data tab and select the Filter.

Make sure you don’t have one column selected prior or you will only filter that one column and we want the filter to apply to all columns.

How to filter the 16.21 report if you downloaded CSV file.

• Click on Row 1
• Select the Data Tab
• Click the Filter Icon

We suggest deleting the columns with Student Name, Birthdate, Gender and Ethnicity first so if this list is emailed later it will not contain sensitive PII that can be compromised by plain text email.

Use the notes column for yourself to document your research and follow-up with IEP teams.

 

Tips to address all areas of Non-Compliance:

• Finalize open meetings that are currently awaiting consent. If parent has since consented, change the parent response to accepts the plan.
• Finalize open meetings that are currently awaiting consent, as parent contacted, no response if contact attempts for written consent have been unsuccessful.  Follow the steps on the Finalizing IEPs Awaiting Consent and Parent Response & IEP Disagreements Help Sheets for properly following up with meetings finalized as parent contacted, no response.
• Send SPED data from SIRAS to CALPADS often. This should be done weekly. Do not let the worry that this process will create errors during the amendment window, by closely monitoring/addressing errors/warnings after each submission.
• Monitor Upcoming IEPs on the homepage of SIRAS to make sure IEP teams are scheduling upcoming meetings so that they will be held in a timely fashion.
• Monitor Overdue IEPs on the homepage of SIRAS or use the Meeting Report called Emergency Conditions-Open Meetings (Reporting/Meeting Reports/Predefined) to make sure the IEP teams are working to finish them up/finalize; they are probably meetings that are/need to be continued.
• Attend SIRAS webinars for support. Zoominar schedule posted under this link. 
• If needed, contact SIRAS Support or schedule a 1:1 support meeting with Brian.