Special Education IEP Manager Meeting History vs. MIS Archived Transaction -->

Aug 15, 2026

This article is Special Education/SEDS-specific. SIRAS preserves the completed IEP meeting in IEP Manager and separately preserves the dated reporting state on the Special Education MIS Summary.

These records are related, but they serve different purposes and should not be treated as interchangeable.

504 and SST use different meeting/data lifecycles.
Use 504 Forms Help or 10 Steps to Develop an SST Plan instead of applying this SPED archive model to those designations.

Two histories are involved:
The IEP Manager meeting history preserves the meeting event and forms. The MIS archived transaction preserves the dated data/reporting state and the applicable SWDS, MEET, PLAN, or SERV components.

Quick Links

How the Two Histories RelateUnderstand the meeting-to-transaction relationship.

Meeting-Created TransactionsMost finalized reportable meetings create an associated MIS archive.

Manual TransactionsSome reportable events create an MIS archive without an IEP Manager meeting.

What Can Be ReportedThe archive components—not the meeting label alone—control the reporting content.

Use Both Histories for InvestigationCompare meeting, Current, archive, and CALPADS when something does not match.

New Event vs. CorrectionDo not create a new archive just to hide an error in an older event.

How the Two Histories Relate

IEP Manager meeting event → meeting is completed/finalized according to the Parent Response → meeting history is preserved → applicable approved data updates Current → a dated MIS archived transaction preserves the reportable event state

A finalized meeting can therefore be represented in two places for different purposes:

Record	Primary purpose
IEP Manager meeting history/archive	Preserves the meeting event, forms, meeting type, documentation, and finalization history.
MIS archived transaction	Preserves the dated reporting state and identifies the SWDS, MEET, PLAN, and/or SERV components SIRAS can submit for that event.

SIRAS comparison showing dated MIS archived records on the left aligned with IEP Manager meeting events on the right, including an archive with no matching meeting event

The histories often line up by date and event, but an MIS archived transaction can also exist without an associated IEP Manager meeting.

Meeting-Created Archived Transactions

When a meeting is finalized, SIRAS can preserve the applicable dated Current/meeting information in an associated archived transaction.

The actual components depend on the event and outcome. Examples can include:

Initial Evaluation outcomes involving SWDS, MEET, and—when an accepted participating plan is established—PLAN and SERV;
Annual Plan Review events involving MEET and an accepted PLAN/SERV baseline;
Triennial Reevaluation events involving MEET and the applicable status/plan/service outcome; and
amendments or other meeting events when the actual accepted change is reportable.

The meeting name by itself does not determine the CALPADS transaction.
Review the actual event, Parent Response, dates, Current data, and archived component selection. An amendment can document a change without necessarily producing the same component pattern as an Annual or Initial Evaluation.

See Archived Transaction Components: SWDS, MEET, PLAN, and SERV.

Archived Transactions Without an IEP Manager Meeting

Some reportable events occur outside the ordinary meeting-finalization workflow. In those cases, a dated MIS archived transaction can be created without a corresponding IEP Manager meeting event.

Examples include documented workflows such as:

Plan Adoption for an incoming student;
a reportable status change outside a meeting;
certain Pending As Of or specialized reporting events; and
other cases where Archive for Reporting is the documented procedure.

A manual archive is still a real dated reporting event.
Its Report Event Date, component selection, and data must represent something that actually occurred. Do not create a manual archive simply because CALPADS is missing data without first determining what event should be represented.

What the Archived Transaction Can Report

The MIS archived transaction is the reporting container. Depending on the event, it can include one or more of:

SWDS — eligibility/participation status;
MEET — evaluation/review event;
PLAN — participating plan/program information; and
SERV — reportable services associated with PLAN.

For a meeting-created archive, the associated meeting helps explain the source event. For a manually created archive, the archive itself may have no associated meeting and must be interpreted through the documented reporting reason and field event.

When the Archived Transaction Says Pending

If an archived transaction has Report Status = Pending, the event is already represented in the archive and the pending item is its submission. This is different from IEP Manager Pending Changes, which occur earlier while determining what proposed meeting data should become Current.

See Pending in SIRAS and Data Record - Archived Transaction.

Use Both Histories When Investigating a Discrepancy

When a CALPADS record, monitoring list, or archive does not make sense, compare:

what actually happened in the field;
the IEP Manager meeting event and final response/outcome;
Current MIS data;
the dated MIS archived transaction and component selection; and
the resulting CALPADS history.

Use Data Monitoring Investigation Guide when the histories do not tell the same story.

A New Event and a Correction Are Different

Situation	Action
A later real event occurred.	Preserve the earlier valid history and create/use the later archive appropriate to the new event.
The older archived transaction reported the original event incorrectly.	Correct that historical transaction using the appropriate correction workflow.
Only Current data is wrong now.	Correct Current without rewriting a valid historical event.

See Data Record - Archived Transaction and Process for Error Resolution.