MEET0669

Completed and pending are different event states

Concrete checks

• Confirm the event was unresolved on 24.14.
• Check for a scheduled meeting date mapped into the pending field.
• Review whether the meeting has since occurred and requires a completed event.
• Check date transposition and extract run-date logic.

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

   Use the actual historical pending checkpoint. Do not report an anticipated future checkpoint; submit after the date exists and the pending state is supported. 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

• Official CALPADS MEET0669 troubleshooting page
• CALPADS MEET record guidance
• Current CALPADS specifications, code sets, and valid combinations