Plan Effective Date, Service Start Date & CALPADS SERV Reporting

Several SIRAS and CALPADS dates describe when a plan or service is considered effective. They are related, but they are not interchangeable.

This article distinguishes the Plan Effective Date, the SIRAS Service Start Date, and the effective date reported in the CALPADS SERV file.

The key distinction:
The SIRAS Service Start Date is a local IEP service field. The effective date reported in the CALPADS SERV file always comes from the Plan Effective Date—not from the SIRAS Service Start Date.

In This Guide

Compare the three date concepts
Understand the Plan Effective Date
Understand the SIRAS Service Start Date
Understand the CALPADS SERV effective date
Apply the dates during an Initial Evaluation
Confirm CALPADS enrollment alignment
Correct a Plan Effective Date

1. Compare the Three Date Concepts

Date	What it means	Where it is used
Plan Effective Date	The date the approved IEP, IFSP, or ISP plan becomes effective.	SIRAS plan records and CALPADS PLAN reporting. It also supplies the effective date used in CALPADS SERV reporting.
SIRAS Service Start Date	The date the IEP team considers an individual service ready to begin or effective as of in the field.	SIRAS service records, implementation tracking, service logs, exports, and local reports. It is not used as the CALPADS SERV effective date.
CALPADS SERV Effective Date	The effective date reported with each service in the CALPADS SERV file.	Always derived from the Plan Effective Date. It is not taken from the SIRAS Service Start Date.

2. Plan Effective Date

The Plan Effective Date establishes when the approved plan becomes effective. It is the date used for CALPADS PLAN reporting and for the effective date attached to the associated CALPADS SERV records.

There must be parental agreement to the plan before the plan can take effect.
The Plan Effective Date must be on or after the applicable parental approval date.
The Plan Effective Date must align with an applicable CALPADS enrollment at the reporting district.
For a Part C-to-B Initial Evaluation, the Plan Effective Date can be no earlier than the child's third birthday, even when the parent signs before that birthday.

A meeting date is not automatically the Plan Effective Date.
The meeting may occur before the plan can legally or operationally take effect. Enter the date that represents when the approved plan actually becomes effective.

3. SIRAS Service Start Date

What the field means

The field labeled Service Start Date in SIRAS is best understood as the date the IEP team considers an individual service effective as of in the field.

Depending on district or SELPA practice, the date may represent:

the date the team proposes the service and considers itself ready to begin providing it;
the anticipated implementation date for the service; or
the literal date service delivery is expected to begin.

A proposed effective date is not proof that service delivery actually began on that date.
The team may identify a Service Start Date showing when the service is ready to begin, but actual service delivery cannot begin until the parent has approved the plan.

Relationship to the Plan Effective Date

The SIRAS Service Start Date may be before, the same as, or after the Plan Effective Date, depending on the meeting context and local policy. Do not change the Service Start Date solely to make it match the Plan Effective Date unless district or SELPA policy requires that alignment.

For a Part C-to-B transition, the SIRAS Service Start Date can be no earlier than the child's third birthday. See Transition IFSP to IEP Meeting Procedure – Part C to Part B.

How SIRAS uses the field locally

The SIRAS Service Start Date is used by service records, implementation tracking, service logs, exports, and local reports that determine whether a service is considered active during a selected period.

Do not confuse this field with the effective date sent in the CALPADS SERV file.
The local SIRAS Service Start Date is not the date SIRAS reports as the CALPADS SERV effective date.

4. CALPADS SERV Effective Date

When SIRAS creates CALPADS SERV records, the effective date reported for every service associated with that plan is the Plan Effective Date.

SIRAS does not send the local Service Start Date as the CALPADS SERV effective date.
The PLAN and SERV records created from the same plan transaction therefore use the same Plan Effective Date.
A local Service Start Date may differ without changing the effective date reported in the CALPADS SERV file.

CALPADS rule in SIRAS:
CALPADS SERV Effective Date = Plan Effective Date.

Do not change a SIRAS Service Start Date merely to force the CALPADS SERV effective date to match. The CALPADS value is already derived from the Plan Effective Date. Adjust the local Service Start Date only when the IEP team or local policy requires a different effective-as-of or implementation date.

5. Initial Evaluation & Future Participation

When an Initial Evaluation establishes eligibility and participation, the Plan Effective Date indicates when the approved plan becomes active.

The District Enrollment Date used for SIRAS special education participation should align with the date the student begins participating under the plan.
An Initial Evaluation may produce a Plan Effective Date immediately after the meeting or at a future date.
When participation will begin later, verify the District Enrollment Date, Plan Effective Date, and anticipated local Service Start Dates together.
For Part C-to-B transitions, see Transition IFSP to IEP Meeting Procedure – Part C to Part B.
For the broader Initial Evaluation workflow, see Initial Evaluation Process.

6. CALPADS Enrollment Alignment

A CALPADS PLAN effective date must overlap or otherwise align with an applicable CALPADS enrollment at the reporting district. A district cannot report that a student is participating on its active plan during a period when the student is not enrolled with that district.

Confirm the District Enrollment Date in SIRAS.
Confirm the applicable CALPADS SENR enrollment.
Confirm that the Plan Effective Date belongs to the reporting district's enrollment period.
Coordinate with district SIS staff when the enrollment record must be corrected before special education data can post.

Plan Effective Date and enrollment alignment example

7. Correct a Plan Effective Date

Meeting is still open

Change the Plan Effective Date in the open IEP Manager meeting and verify the updated meeting-document preview before finalizing.

Meeting has already been finalized

Open the archived transaction from the MIS Summary.
Select Open Archived Record for Editing.
Select Edit CALPADS Reporting.
Correct the Plan Effective Date.
Set the report status to the appropriate Pending or plan-reporting status.
Validate and save.
Return to the Current record and remove any obsolete error associated with the earlier date after the corrected transaction posts.

Correcting the Plan Effective Date also changes the effective date SIRAS reports in the associated CALPADS SERV records.