Skip to main content

CALPADS error brief · MEET

MEET0721

Invalid Pending As of Date in MEET record
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

Pending As of Date equal the Meeting Date of another MEET record in the same file or in CALPADS

Focus fields

Fields validated

24.05 - Academic Year ID 24.13 - Special Education Meeting Date 24.14 - Pending As of Date 24.16 - Meeting Activity - Evaluation Type Code 24.17 - Meeting Activity - Plan Review Indicator

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
  • 24.16 Evaluation Type Code
  • 24.17 Plan Review Indicator

This is the inverse of MEET0720. CALPADS already sees a completed meeting on the date now being described as pending.

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

  • Locate the accepted completed event in CALPADS.
  • Confirm whether the submitted pending row is older, duplicated, or misdated.
  • Compare evaluation type and plan-review indicator.
  • Do not overwrite a valid completed meeting with a later-generated pending snapshot.

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

    Remove or correct the unsupported pending representation, or correct the completed event only when authoritative evidence proves its date/type is wrong. 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