You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Using 16.21 in CALPADS
print icon

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.

 

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.

 

Feedback
0 out of 0 found this helpful

scroll to top icon