Skip to main content

CALPADS error brief · MEET

MEET0608

Invalid Academic Year based on Pending Meeting Date or Special Education Meeting 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

Academic Year ID must be the academic school Year associated with the Pending Meeting Date or Special Education Meeting Date

Focus fields

Fields validated

24.05 - Academic Year ID 24.13 - Special Education Meeting Date 24.14 - Pending As of Date

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.05 Academic Year ID
  • 24.13 Special Education Meeting Date
  • 24.14 Pending As Of Date

CALPADS academic years run July 1 through June 30. Derive 24.05 from the populated event date; do not default historical records to the current submission year.

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.

July 1 is the boundary

Event dateAcademic YearResult
202606302025-2026Valid: final day of the year.
202607012026-2027Valid: first day of the new year.
202606302026-2027Invalid: advanced one day too early.

Concrete checks

  • Confirm only one event date is populated.
  • Test the July 1 boundary in the extract.
  • Use CCYY-CCYY format.
  • Correct a bad event date before deriving Academic Year.

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

    When the event date is accurate, derive the matching July–June Academic Year. When the date is wrong, correct it first and regenerate 24.05. 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