Archived Transaction Components: SWDS, MEET, PLAN, and SERV
Aug 06, 2026
Archived Transaction Components: SWDS, MEET, PLAN, and SERV
This article explains how the four CALPADS components fit together inside a SIRAS archived transaction.
Contents
An Archived Transaction Is the Container
An archived transaction is a dated SIRAS record created for a finalized meeting or another reportable event. The archive preserves the applicable information for that event and identifies which CALPADS components SIRAS will submit.
The archive and its components are not the same thing.
The archive is the dated container. SWDS, MEET, PLAN, and SERV are the reporting components that may be generated from the information stored in that archive.
The archive is the dated container. SWDS, MEET, PLAN, and SERV are the reporting components that may be generated from the information stored in that archive.
Not every archive contains all four components. The event, outcome, dates, report status, and information available in the archive determine which components belong.
The Four Transaction Components
| Component | What it represents | Detailed article |
|---|---|---|
| SWDS | Eligibility and participation status over time, including the status effective date and applicable non-participation reason. | SWDS Component |
| MEET | A reportable Initial Evaluation, Annual Plan Review, or Triennial Reevaluation event and its applicable dates and outcomes. | MEET Component |
| PLAN | The plan effective for the student, including plan type, program setting, participation, placement, and related plan information. | PLAN Component |
| SERV | The reportable regular services associated with a PLAN component. | SERV Component |
Common Component Combinations
| Event or outcome | Possible component pattern | Why |
|---|---|---|
| Initial Evaluation completed; student is not eligible | MEET + SWDS | The evaluation is reported and the eligibility status changes, but there is no eligible plan or service set. |
| Initial Evaluation completed; student is eligible and participating | SWDS + MEET + PLAN + SERV | The event establishes eligibility/participation, the evaluation, the approved plan, and its reportable services. |
| Annual Plan Review with no status change | MEET + PLAN + SERV | The review and new plan baseline are reported without duplicating an unchanged SWDS status. |
| Plan Adoption at a new LEA when SWDS [1] already exists | PLAN + SERV | The receiving LEA establishes its plan and service baseline without submitting another unchanged SWDS [1]. |
| Status change outside a meeting | SWDS only | The event changes eligibility, participation, or enrollment status without creating a new plan or evaluation. |
| Evaluation or review reported without a new plan | MEET only or MEET + SWDS | The evaluation/review is reportable, while PLAN and SERV depend on the actual eligible-plan outcome. |
These are orientation examples, not substitutes for the governing workflow.
Always review the actual event, outcome, Current record, archive dates, and existing CALPADS history before changing the components or report status.
Always review the actual event, outcome, Current record, archive dates, and existing CALPADS history before changing the components or report status.
Offboarding: When an Inactive Record Does or Does Not Need SWDS
- Review the CALPADS SENR exit reason, exit date, and completion status.
- Use Appropriate SWDS Status and Non-Participation Reason for Student Exit Categories and Completion Statuses — May 2026.
- If SWDS [1] remains, make the local Current record Inactive using a non-reportable reason and do not create a SWDS archive.
- If the status changes to SWDS [2], [3], or [4], update Current and create a new SWDS archive dated for the actual event.
Local Inactive status does not always mean statewide SWDS status changed.
A district may close its Current record because the student transferred while CALPADS correctly continues to show SWDS [1].
A district may close its Current record because the student transferred while CALPADS correctly continues to show SWDS [1].
Dates That Organize the Transaction
| Date | Purpose |
|---|---|
| Report Event Date | Identifies the dated event represented by the archive. For a meeting-created archive, it should align with the associated meeting or reporting event. |
| Plan Effective Date | Identifies when the PLAN becomes effective and connects the associated SERV records to that PLAN. |
| SWDS Status Effective Start Date | Identifies when the new eligibility or participation status became effective. |
| Meeting and evaluation dates | Supply the applicable MEET history and timeline information. |
How Current Data Supplies the Components
The Current MIS Summary is SIRAS's best known information now. When a manual archive is created, SIRAS copies the applicable Current information into the dated archive. When a meeting is finalized, approved meeting information updates Current and creates the associated archive.
| Current MIS area | Reporting relationship |
|---|---|
| Active Status, eligibility, inactive date and reason | Supplies SWDS status context. |
| Last Annual, Last Evaluation, referral, consent and evaluation information | Supplies MEET context. |
| Special Education information, plan type, program setting and plan dates | Supplies PLAN context. |
| Regular services at the bottom of the MIS Summary | Supplies SERV context for the applicable PLAN. |
SWDS status must be interpreted with the applicable enrollment and event history.
MEET history supplies the reportable evaluation and review context.
PLAN information comes from the applicable plan data stored in the transaction.
SERV records are associated with the applicable PLAN.
Inspect a Transaction in SIRAS
- Open the student’s MIS Summary.
- Choose the dated archive from the Archived Records menu.
- Review the Associated Meeting, Report Event Date, Plan Effective Date, CALPADS Record Types, and Report Status.
- Compare the archived MIS information with the Current record and the source event.
- Use Archived Transactions: Current Data, Archived Data, and Reporting Status for the screen-level review and editing procedure.
New Events and Corrections Are Different
| Situation | Historical action |
|---|---|
| A later real event or new reportable value occurred. | Create a new archive dated for that event. Preserve the prior valid transaction. |
| The earlier transaction reported bad data. | Correct the existing archive that sent the bad data. Correct Current when needed, remove the incorrect CALPADS entry, set the corrected archive to Pending, and resend it. |
| Only Current is wrong. | Correct Current. Do not alter or resend a correct archived transaction. |
Do not use a new archive to conceal an error in an older transaction.
A new archive says a new event happened. Correcting the existing archive says the original event was reported incorrectly.
A new archive says a new event happened. Correcting the existing archive says the original event was reported incorrectly.
