Skip to main content

CALPADS error brief · MEET

MEET0426

Missing Meeting Delay Code for Part B or Part C Initial Evaluation
Severity
FATAL error - Must be corrected in order to post the record and/or certify the data.
Error type MEET - Special Education Meetings
Record type MEET

Official CALPADS rule

What CALPADS is rejecting

If Meeting Activity - Evaluation Type Code = 15 or 10 AND Special Education Meeting Date is greater than 60 days from the Initial Evaluation Parental Consent Date THEN the Meeting Delay Code must be populated.

Focus fields

Fields validated

24.12 - Initial Evaluation Parental Consent Date 24.13 - Special Education Meeting Date 24.16 - Meeting Activity - Evaluation Type Code 24.15 - Meeting Delay Code

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.12 Parental Consent Date
  • 24.13 Meeting Date
  • 24.15 Meeting Delay Code
  • 24.16 Evaluation Type Code

The code explains why the reported timeline was exceeded; it does not make the delay compliant. Part C and Part C-to-B scenarios also have additional timing rules beyond this CALPADS trigger.

Delay reporting follows the underlying activity

ActivityInitial evaluation, reevaluation, or plan review.
Timeline Compare required and actual dates.
Delay reasonUse a permitted, evidence-supported code.
DocumentationTechnical acceptance does not determine compliance.

Current Meeting Delay codes

CodeReasonImportant scope
10Delay in Parental ConsentActivity-specific consent or agreed reevaluation circumstances.
15Exceptional Family CircumstancesPart C Initial; effective beginning 2025–26.
20Parent/child unavailableRepeated documented unavailability.
25Late Referral to Part CPart C-to-B third-birthday scenario; effective beginning 2025–26.
30Parent contacted—did not attendPlan review, including reevaluation + plan review.
40School BreakInitial Part B 60-day context.
50TransferInitial Part B, reevaluation, or plan review as permitted.
60School emergency/closurePermitted activity combinations.
70Student/family emergencyPermitted activity combinations.
80Due process/settlementPermitted activity combinations.
85Hearing/vision screeningInitial Part B or reevaluation; not plan-review-only.
90Late Without CauseUse when no supported exception explains the delay.

Concrete checks

  • Calculate elapsed days from the correct consent and meeting dates.
  • Verify evaluation type 10 or 15.
  • Select a current delay code permitted for that activity/year.
  • Preserve documentation; never choose a more favorable reason than the evidence supports.

Recommended correction path

  1. 1

    Preserve the rejected row

    Capture submission ID, SSID, Reporting LEA/SELPA, Academic Year, all MEET dates, activity indicators, outcome, delay, and the ODS history.

  2. 2

    Identify the event state

    Determine whether the activity was pending or completed and whether it involved an initial evaluation, reevaluation, plan review, or combination permitted by Version 18.

  3. 3

    Build the chronology

    Place referral, consent, pending checkpoints, meeting, determination, delay, SWDS, and PLAN events in order.

  4. 4

    Verify governing evidence

    Use signed meeting/evaluation records, procedural documentation, the SEDS, and the current code/combination definitions. Do not infer an outcome or delay reason.

  5. 5

    Correct the source and mapping

    Correct erroneous dates/type, or populate the evidence-supported current delay code. A true late-without-cause event should be reported honestly as Code 90. Repair any recurring export rule.

  6. 6

    Resubmit and reconcile

    Confirm acceptance, inspect the complete MEET history, and review connected SWDS/PLAN records and affected reporting results.

Official references