Skip to main content

CALPADS error brief · IVR

IVR0612

Duplicate Plan Effective Start Date
Severity
FATAL error — Must be corrected to post the record or certify the data.
Error type SERV — Student Services
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

Student has an existing record with the same Special Education Plan Effective Start Date

Focus fields

Fields validated

25.04 - Reporting LEA 25.07 - SSID 25.08 - Reporting SELPA 25.16 - Plan Effective Start Date

Recommended correction path

Suggested resolution

Current fields validated

  • 25.04 Reporting LEA
  • 25.07 SSID
  • 25.09 Reporting SELPA
  • 25.17 Plan Effective Start Date

The official page currently displays older SERV field numbers. The Version 18 numbers above identify the same four concepts.

One plan event can support many services

Records sharing one plan dateResultReason
Speech and occupational therapy; same LEA and SELPAPotentially validDifferent service/provider keys may attach to the same PLAN event.
Several services; same student, LEA, SELPA, and plan datePotentially validIVR0612 is not a one-service-per-plan rule.
Same student and plan date; different Reporting LEAsConflictOne plan event cannot be owned by two Reporting LEAs.
Same student and plan date; different Reporting SELPAsConflictOne plan event cannot carry two SELPA associations.

How this conflict usually develops

  • A student transferred, but services were exported under both the former and new organizational relationship.
  • A PLAN or SERV record already exists in the ODS with different ownership.
  • Two source systems assign different LEA or SELPA values to the same plan event.
  • A new plan was given the prior plan’s effective date.
  • A historical correction changed only PLAN or only SERV, leaving the other record behind.
  • The submitted Plan Effective Start Date belongs to another plan entirely.

Do not change the date merely to make the row unique. Plan Effective Start Date is the link between PLAN and SERV. An invented date can clear IVR0612 while creating an orphaned or historically false service.

Read the ownership history

Existing ODSFind every PLAN and SERV record on the disputed date
Authoritative planEstablish the real effective date and responsible organizations
Enrollment historyConfirm which LEA had the qualifying relationship
Coordinated correctionAlign PLAN and all associated services

Recommended correction path

  1. 1

    Inventory every record on that date

    Review submitted rows and existing CALPADS PLAN and SERV history for the SSID.

  2. 2

    Separate multiple services from conflicting ownership

    Different service/provider combinations can be legitimate; different LEA/SELPA ownership for one plan date is the problem.

  3. 3

    Verify documentary authority

    Use the operative IEP, IFSP, or ISP; transfer records; enrollment history; and responsible LEA/SELPA determination.

  4. 4

    Find the first inaccurate record

    Determine whether the existing ODS record, submitted PLAN, submitted SERV, plan date, LEA, or SELPA is wrong.

  5. 5

    Coordinate the correction

    Correct PLAN and every associated SERV record together. Coordinate with the other LEA/SELPA when it owns the record that requires correction.

  6. 6

    Verify one organizational relationship

    Confirm the plan date now has one supported Reporting LEA/SELPA combination while retaining all legitimate services.

Official SERV IVR0612 page · Current SERV details