Skip to main content

CALPADS error brief · MEET

MEET0398

Missing Parental Involvement Facilitation Code
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

Parental Involvement Facilitation must be populated for Initial Part B and Plan Review Meetings

Focus fields

Fields validated

24.16 - Meeting Activity - Evaluation Type Code 24.17 - Meeting Activity - Plan Review Indicator 24.19 - Parental Involvement Facilitation Code 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 Meeting Date
  • 24.16 Evaluation Type Code
  • 24.17 Plan Review Indicator
  • 24.19 Parental Involvement Facilitation Code

This code reports the parent’s response to whether the district facilitated involvement—not whether the parent attended the meeting and not staff’s opinion of the parent.

Delay reporting follows the underlying activity

ActivityInitial evaluation, reevaluation, or plan review.
TimelineCompare required and actual dates.
Delay reasonUse a permitted, evidence-supported code.
DocumentationTechnical acceptance does not determine compliance.

Parental Involvement response codes

CodeResponseMeaning
10YesParent responded that the district facilitated involvement.
20NoParent responded that the district did not facilitate involvement.
30No Response GivenNo response was provided, or no response was expected under the code definition.

Concrete checks

  • Use 10 Yes, 20 No, or 30 No Response Given.
  • Do not infer Yes from attendance or signature.
  • Use 30 when no response was provided or no response was expected under the code definition.
  • Confirm the collection method and source documentation.

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

    Populate the parent’s documented response for the qualifying completed meeting, or correct the activity fields if the record was not Initial Part B or a plan review. 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