Skip to main content

CALPADS error brief · MEET

MEET0352

Special Education Meeting Date is less than Initial Evaluation Parental Consent 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 greater than or equal to Initial Evaluation Parental Consent Date.

Focus fields

Fields validated

24.12 - Initial Evaluation Parental Consent Date 24.13 - Special Education Meeting Date

Recommended correction path

Suggested resolution

Official rule in plain language

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.12 Initial Evaluation Parental Consent Date
  • 24.13 Special Education Meeting Date

Same-day consent and meeting satisfy the CALPADS ≥ relationship, although local procedural requirements and documentation still govern whether the sequence is substantively appropriate.

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

  • Verify both dates belong to the same initial evaluation.
  • Compare all eight digits for transposition.
  • Distinguish consent for evaluation from consent for initial services.
  • Do not replace a valid meeting date with the upload 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

    Correct the unsupported consent or meeting date using the governing documents. Do not shift an accurate event merely to force the sequence. 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