Skip to main content

CALPADS error brief · PLAN

PLAN0667

Special Education Plan Effective Start Date for PLAN Record is greater than Current Date plus six months
Severity
FATAL error - Must be corrected in order to post the record and/or certify the data.
Error type PLAN - Special Education Plan
Record type PLAN

Official CALPADS rule

What CALPADS is rejecting

Special Education Plan Effective Start Date for PLAN Record is greater than Current Date plus six months

Focus fields

Fields validated

23.12 - Special Education Plan Effective Start Date

Recommended correction path

Suggested resolution

PLAN validation

Severity: Fatal   Type: Input Validation

Fields validated

  • 23.12 Special Education Plan Effective Start Date

This is not a blanket prohibition on future plans. It prevents excessively early submission and catches year, century, rollover, and scheduled-date errors.

The effective-date chain

Authoritative plan eventMeeting, amendment, signatures, and governing documentation.
23.12 Plan Effective Start DateThe date this version becomes effective.
23.05 Academic Year IDThe July–June year containing that date.
Dependent historySERV and later PLAN segments reconcile to the effective plan.

Three future-date scenarios

ScenarioInterpretationResponse
Documented future effective date within six monthsPotentially acceptable under PLAN0667 Verify PLAN0610, ownership, plan facts, and connected record timing.
Documented future effective date beyond six monthsAccurate locally but too early for CALPADSDo not falsify the date; wait until it enters the permitted window.
Future date caused by typo or rolloverThe submitted date is not the plan’s true effective dateCorrect the source date and repair the process that generated it.
Meeting and decisionThe team documents what was decided and when.
Plan becomes effectiveField 23.12 reports the supported implementation date.
PLAN and SERV historyDependent records align to the effective plan—not merely the upload date.

Concrete checks

  • Confirm the plan or amendment has an evidence-supported future effective date.
  • Distinguish Meeting Date, signature date, implementation date, and upload date.
  • Check whether the SIS or special education system rolled into a future school year too early.
  • Inspect transposed month/day or incorrect year digits.
  • Confirm the effective date is no more than six months beyond the submission date.

Recommended correction path

  1. 1

    Preserve the rejected record

    Capture submission ID, SSID, Reporting LEA and SELPA, Academic Year ID, Plan Effective Start Date, and the current CALPADS PLAN history.

  2. 2

    Locate governing documentation

    Identify the plan, amendment, meeting record, implementation decision, and local source record that support the effective date.

  3. 3

    Identify each date’s purpose

    Separate meeting, signature, effective, upload, and service dates. Do not substitute one date merely because it is available.

  4. 4

    Test the two boundaries

    Place the effective date in the correct July–June academic year and, when prospective, confirm it is within the six-month submission boundary.

  5. 5

    Correct the source or submission timing

    Correct an inaccurate date in the authoritative special education system. If the future effective date is accurate but still beyond the permitted window, retain it locally and submit when it falls within six months. Repair any rollover, default-year, or mapping defect.

  6. 6

    Resubmit and reconcile the lifecycle

    Confirm acceptance and review neighboring MEET, PLAN, SWDS, and SERV dates for gaps, overlaps, or disconnected records.

Official references