Skip to main content

CALPADS error brief · MEET

MEET0518

Special Education Meeting Date is greater than Current Date
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

Special Education Meeting Date must be less than or equal to current date.

Focus fields

Fields validated

24.13 - Special Education Meeting Date

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.13 Special Education Meeting Date

A scheduled meeting belongs in local workflow, not in 24.13. If the event remains pending, use the supported Pending As Of reporting structure rather than future-dating completion.

Completed and pending are different event states

Prerequisite historyReferral and consent when applicable.
Pending24.14 means the event had not occurred as of that date.
Completed24.13 is the date the meeting/determination occurred.
Academic Year24.05 follows the populated event date.

Concrete checks

  • Confirm the meeting actually occurred.
  • Check century, year, month, and day.
  • Determine whether a scheduled date was exported as completed.
  • If pending, verify 24.14 and all activity fields rather than simply moving the date.

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

    Use the actual completed meeting date. If the meeting has not occurred, do not submit a future 24.13; report a supported pending event when applicable. 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