DINC 1 Previously Overdue Meetings: Reconcile SIRAS with CALPADS 16.21
Aug 17, 2026
DINC 1 — Reconcile Previously Overdue MeetingsUse SIRAS Previously Overdue lists to confirm that Annual/Triennial meetings held late are represented in CALPADS 16.21 with the expected MEET history and supported delay information.
You are here: Reconcile & Repeat → Previously Overdue meetings.
DINC 1 includes both current and historical late Annual/Triennial compliance work. Use Meeting Compliance Quick Actions for current/preventive queues and this page for the historical reconciliation after the meeting has occurred.
What Do You Need to Check?
| DINC 1 — Find Annuals/Triennials that were held lateRun the SIRAS Previously Overdue Annual and/or Triennial lists. | Does CALPADS 16.21 show the same meeting history?Compare the verified event, late/overdue category, and MEET history. |
| The historical delay reason is missingCorrect the applicable archived MEET history only after the delay is verified/documented. | Confirm reconciliation is completeRerun SIRAS and CALPADS after correction, then return to the monitoring workspace. |
Do not add a delay reason simply because 16.21 says the meeting was late. First establish what actually happened. A missing MEET record, wrong date, or enrollment/participation history can create a misleading result.
Run the SIRAS Previously Overdue Lists
Go to:
Reporting → Student Lists → Predefined Lists → Compliance Concerns → Overdues
Run one or both:
- DINC1: Previously Overdue Annual
- DINC1: Previously Overdue Triennial
To reconcile all meetings held late:
Run the list with Find only records with delay reason missing not checked. A delay reason may have been correctly reported in an archived MEET transaction even though Current no longer needs to display that historical value.
Run the list with Find only records with delay reason missing not checked. A delay reason may have been correctly reported in an archived MEET transaction even though Current no longer needs to display that historical value.
Compare the SIRAS Result with CALPADS 16.21
For each meeting that was held late:
Need to interpret the MEET fields themselves? Use this page to reconcile a previously overdue event; use the MEET reference when you need to read the archived Meeting Date, Evaluation Type, Plan Review Indicator, or Delay Code. See MEET Component: Evaluation and Review Events.
- Open or obtain the applicable CALPADS 16.21 report.
- Confirm the meeting appears in the expected CALPADS history.
- Check whether the meeting was categorized as held late or overdue as expected.
- Check whether the applicable Meeting Delay Reason was reported when required.
- If the SIRAS and CALPADS histories do not agree, move the record into Data Monitoring Investigation Guide.
If the Historical Meeting Delay Reason Is Missing
Once a late meeting has been reported, the historical delay reason belongs with the applicable archived MEET/reporting history. Current data does not need to carry the historical delay value indefinitely.
If the investigation confirms that the meeting was late, the documentation supports a delay reason, and CALPADS is missing that delay reason:
- Open the applicable meeting archive.
- Use the archived-record editing workflow to add/correct the historical Meeting Delay Reason.
- Set the report status needed to resend the MEET information without unnecessarily resending unrelated components.
- Submit through Reporting data to CALPADS.
- Verify through CALPADS Submission Log Help when needed.
- Rerun the CALPADS 16.21 report.
Do not add a delay reason merely because 16.21 shows a record as late.
First verify what actually happened. If the report is wrong because a meeting record is missing, a date is incorrect, or enrollment/participation history is wrong, correct that source instead.
First verify what actually happened. If the report is wrong because a meeting record is missing, a date is incorrect, or enrollment/participation history is wrong, correct that source instead.
Reconciliation Complete
Complete when:
The SIRAS previously-overdue history and CALPADS 16.21 represent the same verified meeting event, including the appropriate late/overdue status and historical delay information.
The SIRAS previously-overdue history and CALPADS 16.21 represent the same verified meeting event, including the appropriate late/overdue status and historical delay information.
Then return to Data Monitoring Tasks and continue the recurring monitoring loop.
