Skip to main content

CALPADS error brief · SERV

SERV0666

Plan Effective Start Date for SERV Record is greater than Current Date plus six months
Severity
FATAL error — Must be corrected to post the record or certify the data.
Error type SERV — Student Services
Record type SERV

Official CALPADS rule

What CALPADS is rejecting

Plan Effective Start Date for SERV Record is greater than Current Date plus six months

Focus fields

Fields validated

25.17 - Plan Effective Start Date

Recommended correction path

Suggested resolution

Read the rolling window

Plan date relative to submissionRule resultOperational question
Past or current dateNot blocked by SERV0666Does it match the operative PLAN and enrollment history?
Future date within six monthsPermitted by this ruleIs the future plan established and supported, rather than merely anticipated?
Future date beyond six monthsFatal SERV0666Is the date wrong, premature, or simply not yet eligible for submission?

Example: If submitted on January 15, a July 15 plan date is at the six-month boundary; a later date falls outside the allowed window. Because month lengths and system calculations matter, verify the actual CALPADS processing date rather than relying on a rough 180-day estimate.

Common causes

  • The year was mistyped—for example, 2027 instead of 2026.
  • Month and day were transposed during conversion to CCYYMMDD.
  • A projected meeting or renewal date was exported as an approved Plan Effective Start Date.
  • The SEDS generated next year’s services too early.
  • A copy-forward process advanced the plan year without corresponding authoritative action.
  • PLAN and SERV were updated on different schedules.

Do not backdate the plan to force acceptance. If the future date is correct but outside the window, retain it in the authoritative system and submit when eligible. If the date is tentative rather than operative, the SERV record should not yet be posted as an established service.

Distinguish three correction paths

EvidenceCorrectionDo not do
The date is a typoCorrect the authoritative PLAN/SEDS date and every associated SERV row.Correct only the upload file and leave the source wrong.
The plan is valid but more than six months awayHold the record until it enters the permitted window.Invent an earlier effective date.
The date is only projectedFollow the local plan-development workflow and submit once the event is established and reportable.Treat a scheduling placeholder as an operative plan.

Recommended correction path

  1. 1

    Record the processing date

    Use the date CALPADS evaluated the submission, then determine the exact six-month boundary.

  2. 2

    Inspect all eight date digits

    Check century, year, month, day, conversion logic, and whether the value belongs to the intended plan.

  3. 3

    Verify plan authority

    Confirm that the IEP, IFSP, or ISP supports the effective date and services; distinguish an established future plan from a projected event.

  4. 4

    Choose correction or timing

    Correct an inaccurate source date, or hold an accurate record until it is within the allowed window.

  5. 5

    Keep PLAN and SERV synchronized

    Ensure all services use the same supported Plan Effective Start Date and Academic Year ID as the corresponding PLAN.

  6. 6

    Resubmit and verify history

    Confirm acceptance and review for SERV0610, IVR0612, GERR0005, or a missing corresponding PLAN.

Official SERV0666 page · Current SERV details