Pending in SIRAS: Know Which "Pending" You Mean

Oct 15, 2026

“Pending” can mean several different things in SIRAS.
If your question is whether to send a Pending As Of MEET or a Meeting in Progress MEET, start with the first choice below. Most open or upcoming meetings require neither special reporting option.

When SIRAS says “Pending,” what do you mean?

Do I use Pending As Of, Meeting in Progress, or neither?Use this decision flow for overdue annual/triennial work around an upcoming reporting date and LEA Approve.

The Special Education student recordCurrent Active Status = Pending: referral, evaluation, or another unresolved SPED working state.

Changes from an IEP meetingIEP Manager Pending Changes: proposed MIS/Current changes still waiting for staff to resolve what was actually agreed to.

An archived transaction waiting to reportReport Status = Pending: SIRAS should attempt to submit the selected archived components.

An Initial Evaluation is pending after parental consentPending As Of parental consent MEET: a separate Initial Evaluation reporting scenario.

CALPADS 16.21 says “pending record”Interpret this in the context of a Pending As Of MEET record.

504 or SST uses the word Pending504 and SST have their own designation-specific workflows. Do not automatically apply Special Education rules.

Pending As Of, Meeting in Progress, or Neither?

Do not send either special MEET record just because a meeting is open.
An upcoming open meeting is not, by itself, a reason to send Pending As Of. A meeting taking longer than expected to finalize is not, by itself, a reason to send Meeting in Progress.

This decision flow is for an eligible student whose annual plan review or reevaluation/triennial work is overdue, or will be overdue as of the applicable reporting date.

For the normal annual reporting checkpoints described here, think of the applicable reporting date as:

Fall 1: Census Day, the first Wednesday in October; or
EOY: June 30.

Initial Evaluation?
Do not use the annual/triennial decision flow below for the parental-consent Pending As Of scenario. Go to Initial Evaluation Pending As Of.

Decision flow

1. Will the student be overdue as of the upcoming reporting date?

No → Neither. Do not create a Pending As Of or Meeting in Progress MEET merely because a meeting is open or coming up. Continue the normal meeting workflow.

Yes → Continue to Question 2.

2. Has the meeting already happened?

No → Continue to Question 3. This is the only branch where the normal annual/triennial Pending As Of scenario may apply.

Yes → Skip to Question 4. Once the meeting has happened, do not create a Pending As Of record for that meeting.

3. Was the meeting arranged in SIRAS on or before the reporting date, with the actual meeting date scheduled after the reporting date?

Yes → Pending As Of may be appropriate.

The student is overdue as of the reporting date.
The meeting event was created/arranged in SIRAS on or before that reporting date.
The planned meeting date is after the reporting date.
The applicable meeting delay reason is included.
The Pending As Of MEET is created/reported before the planned meeting occurs.
The Pending As Of MEET must be reported before the planned meeting occurs.

The Pending As Of date for an annual/triennial meeting is the date the meeting event was created in SIRAS, not the future meeting date.

Use Sending a Pending Meeting Record for the procedure.

No → Do not use Pending As Of under the normal reporting use described here. In particular, if the meeting is scheduled to occur on or before the upcoming reporting date, let the meeting happen. If the meeting later cannot be finalized before the LEA intends to LEA Approve, Question 4 determines whether Meeting in Progress is needed.

4. The meeting has happened. Will it probably be finalized before the LEA wants to LEA Approve/certify?

Yes → Neither. Close/finalize the meeting normally and allow the normal reporting workflow to create/report the MEET record.

No → Meeting in Progress may be appropriate. Use it when a meeting actually occurred, but finalizing the meeting will not happen soon enough for the LEA’s intended LEA Approve/certification timing.

The meeting date must already have occurred.
The Meeting in Progress archive reports the MEET for the meeting that happened.
Do not use it merely because finalization is taking longer than usual.
When the meeting is later finalized and the parent response supports implementation of the plan, the applicable PLAN and SERV reporting can follow through the normal workflow.

Use Send Meeting In Progress for the procedure.

Overdue as of reporting date? → Meeting not yet held and scheduled after reporting date? Pending As Of → Meeting already held but cannot be finalized before LEA Approve? Meeting in Progress → Otherwise Neither

Why Pending As Of exists

Pending As Of is a good-faith reporting notice.
For an overdue annual/triennial record, it tells CALPADS that the LEA is aware the meeting is due, has already arranged the meeting in SIRAS, and is actively working on it even though the actual meeting will occur after the applicable reporting date.

It is not a routine “meeting is planned” record. The normal district use is limited to the overdue-as-of-reporting-date scenario described above.

Why Meeting in Progress exists

Meeting in Progress reports a meeting that already happened.
It is useful when the LEA needs the MEET reported before certification but the meeting cannot be fully finalized in SIRAS soon enough. It is not a substitute for normal finalization when the meeting can reasonably be closed before LEA Approve.

Situation	Use	Key timing
Student will be overdue as of the reporting date; meeting is arranged in SIRAS by that date; meeting will occur after the reporting date.	Pending As Of MEET	Create/report before the meeting occurs. Use the meeting-event creation date as the Pending As Of date and include the applicable delay reason.
Meeting already happened, but it probably will not be finalized before the LEA wants to LEA Approve/certify.	Meeting in Progress MEET	The actual meeting date has already occurred. Report the MEET now; complete the normal PLAN/SERV reporting later when the meeting is finalized as applicable.
Meeting is open/upcoming but the record will not be overdue as of the reporting date, or the meeting can be finalized before LEA Approve.	Neither	Continue the normal meeting/finalization/reporting workflow.

CDE monthly-monitoring exception:
If the LEA/district is currently being monitored monthly by CDE, reporting a planned Pending As Of MEET for a newly arranged meeting on a very overdue record may be warranted outside the normal Fall 1/EOY use above. Treat that as a monitoring-specific exception, not routine district practice, and follow the monitoring requirements applying to that LEA.

Initial Evaluation Pending As Of

Initial Evaluations have a separate Pending As Of scenario tied to parental consent for assessment.

The Pending As Of date is the parental consent date. This is used when the parental consent date is before the applicable reporting/census date but the anticipated Initial Evaluation meeting date will occur after that reporting date.

Timing matters.
The Pending As Of MEET must be created before the meeting date occurs and reported before the Initial Evaluation meeting is closed.

Use How to Send a Pending As Of Parental Consent MEET Record. For Initial Evaluation workflow and monitoring, also see Initial Evaluation Process and New Referral List.

Special Education Current Active Status = Pending

Here, the student’s Current Special Education record is Pending. This is a temporary working status used when a SPED referral, evaluation, participation decision, arrival, or other documented follow-up condition is unresolved.

This Current record status is not the same as a Pending As Of MEET, Meeting in Progress, or an archived transaction whose Report Status is Pending.

Use SIRAS Record Status for when a SPED record should be Active, Pending, or Inactive.

IEP Manager Pending Changes

Here, proposed changes to Current/MIS data are pending review. The changes originated in the Special Education IEP Manager meeting workflow.

This is especially important when full agreement has not been obtained—for example, partial consent where the IEP team knows that one service, eligibility item, goal set, or other proposal was agreed to while another proposal was not.

IEP Manager proposes MIS/Current changes → Parent Response does not fully resolve every proposed data item → IEP staff use what occurred in the field → accept, edit, or cancel the appropriate Pending Changes → Current/MIS represents what was actually agreed to

Use IEP Manager Pending Changes: Completing the Data Flow Back to Current.

Archived Transaction Report Status = Pending

Here, the archived transaction is pending submission. The event and its data already exist in the archive; the Pending report status tells SIRAS to attempt to send the selected reportable component or components through the CALPADS reporting workflow.

This happens later than resolving IEP Manager Pending Changes and is not the same as Pending As Of.

Resolve meeting data into Current/MIS → preserve the applicable dated event in an archive → archive Report Status = Pending → SIRAS attempts submission

See Data Record - Archived Transaction and Reporting Data to CALPADS.

“Pending Record” in CALPADS 16.21

When CALPADS 16.21 refers to a pending record, interpret it in the context of a MEET record with a Pending As Of date and no completed meeting date, not as IEP Manager Pending Changes or Current Active Status = Pending.

For annual/triennial work, use the Pending As Of / Meeting in Progress decision flow above before creating a special reporting archive.

Use CALPADS 16.21 Overdue Plan Review and Reevaluation List for report-specific interpretation.

Pending in 504 and SST Workflows

Designation matters. The Special Education meanings above should not be assumed to apply to 504 or SST simply because those modules share screen labels or Forms Manager concepts.

Designation/context	Meaning
504 record status = Pending	The student is under consideration/review for a 504 plan. Use the 504 workflow in 504/SST Summary Page Help, 504 Forms Help, and 504 Module Guide.
SST decision refers the student to 504	SIRAS can transfer the record to the 504 module and set the destination record Pending for the 504 referral.
SST decision refers the student to Special Education	SIRAS can transfer the record to the Special Education module and set the destination record Pending for the IEP referral.
Native SST record status	The SST workflow generally uses Active while the SST process/follow-up is underway and Inactive when the SST process is complete. See 10 Steps to Develop an SST Plan.

SIRAS Customer Documentation
This documentation is provided for SIRAS customers and authorized users for the purpose of using and supporting SIRAS. © SIRAS Systems. All rights reserved. Automated collection, bulk extraction, republication, creation of derivative datasets, or use of this content for artificial intelligence or machine-learning training, fine-tuning, grounding, retrieval, indexing, or similar automated processing is not authorized without prior written permission from SIRAS Systems. See SIRAS Documentation Terms of Use.