Skip to main content

CALPADS error brief · MEET

MEET0604

Invalid Special Education Meeting Date and Pending As Of Date combination
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 or Pending As of Date must be populated; however they cannot both be populated.

Focus fields

Fields validated

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.13 Special Education Meeting Date
  • 24.14 Pending As Of Date

These dates describe mutually exclusive event states. Meeting Date says the event occurred; Pending As Of Date says it had not occurred as of that date.

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

  • If completed, retain 24.13 and clear 24.14 for that record.
  • If still pending, retain 24.14 and leave 24.13 blank.
  • Do not use both dates to describe a scheduled versus actual date.
  • Compare the same evaluation/plan-review type across ODS history.

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

    Report the evidence-supported event state. Correct the source workflow so completion replaces or resolves the pending state rather than producing a row with both dates. 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