Aug 05, 2026
SERV Component: Services Associated with a Plan
Use this article to understand the SERV component stored in a SIRAS archived transaction.
Contents
| What SERV Represents | Which Services Are Reported |
| How SERV Connects to PLAN | Service Information |
| When SERV Is Omitted | Existing Examples |
| Review and Correct | Related Help |
What the SERV Component Represents
SERV preserves the reportable services associated with a PLAN component. Service information is maintained near the bottom of the MIS Summary and is stored in the applicable archived transaction.

Which SIRAS Services Are Reported
| SIRAS service category | CALPADS SERV treatment |
|---|---|
| Regular services | Reported when associated with the applicable PLAN. |
| ESY services | Not submitted as CALPADS SERV records through this component. |
| Supplemental services | Not submitted as CALPADS SERV records through this component. |
Keep ESY and Supplemental information accurate in SIRAS for local program and document purposes even though those categories are not submitted as CALPADS SERV through this workflow.
How SERV Connects to PLAN
SERV records are tied to a PLAN by the Plan Effective Date. The PLAN and its reportable services should therefore be reviewed together.
- A new participating PLAN normally has at least one associated regular service.
- The CALPADS SERV effective date is derived from the Plan Effective Date.
- Changing only a local Service Start Date does not replace the need for the correct Plan Effective Date.
- When a PLAN is not reportable, its SERV records should not be reported as the student’s participating service set.
The PLAN and SERV records should share the governing Plan Effective Date.
Service Information to Review
Review the applicable:
- service code and description;
- provider;
- service location;
- frequency;
- duration;
- local Service Start and End Dates;
- Regular, ESY, or Supplemental category; and
- Plan Effective Date governing CALPADS reporting.
When SERV Is Omitted
SERV is not included when:
- the event does not create a reportable PLAN;
- the student was found not eligible;
- the offered plan was not accepted and is not the participating plan;
- the archive is intentionally MEET-only or SWDS-only; or
- the service belongs only to an ESY or Supplemental category not reported as CALPADS SERV.
Examples Retained from the Prior Article

Review and Correct SERV Information
- Verify the accepted plan and Plan Effective Date.
- Review the Regular services associated with that plan.
- Open the archived transaction and confirm that PLAN and SERV are both included when appropriate.
- Resolve missing, duplicate, or inconsistent services in the correct source.
- Correct the archive when the historical service set is wrong.
- Return the applicable transaction to Pending and verify CALPADS acceptance.
See Plan Effective Date, Service Start Date, and CALPADS SERV Reporting for date behavior.

