What Pending Changes Do

During an open meeting, staff can propose changes to student, plan, service, and other data. Some of those proposed values are held as Pending Changes rather than immediately replacing Current data.

Accepting a pending change is a convenience that applies the approved change to Current so the same value does not need to be re-entered manually.

Parent Response and Pending Changes

See Parent Response - Impact Table for the full response matrix and Parent Response - Steps for Disagreements for disagreement/partial-consent procedures.

Partial Consent Requires Staff Review

When the parent gives partial consent, SIRAS cannot know from the response label alone which individual proposed data items were agreed to in the field. The IEP team and appropriate SIRAS/SEDS staff need to identify the agreed portions and use Pending Changes to complete the data flow back to Current.

1. Document which goals, services, placement, dates, or other plan components were agreed to and which were not.
2. Select the applicable partial-consent Parent Response.
3. Review every Pending Change before applying it.
4. Apply only the portions that were actually approved.
5. Preserve the last agreed-to Current information for anything that was not approved.
6. Verify Current/MIS, goals, services, and the meeting archive after finalization.

With Partial consent, review the Pending Changes tab and the pending service set before accepting anything into Current. The screen cannot determine which individual proposed items the parent agreed to without staff review.

Pending Services Need Whole-Set Review

Service changes need particular care because the pending service set can replace the previous Current service set when accepted.

Before accepting pending services:

• remove a proposed service that was not approved;
• edit an approved service when the agreed terms differ from the proposal;
• confirm the complete participating service set that should remain Current; and
• verify service dates and other service details that affect the plan/reporting history.

If Approved Changes Are Applied After Finalization

When the meeting has already been finalized and staff later determine that an approved value was not applied correctly, review both layers:

1. Correct Current/MIS so the student record reflects what is true now.
2. Review the existing archived transaction for that same meeting event.
3. If that archive also preserved the wrong value, correct the existing historical transaction as appropriate.
4. Do not create a brand-new archive merely to conceal or replace an error in the original meeting event.
5. Resubmit and verify only when the corrected historical transaction must be reported again.

See IEP Manager Meeting Archive vs. MIS Archived Transaction, Data Record - Archived Transaction, and Process for Error Resolution.

What Happens After Pending Changes Are Resolved?

Resolving Pending Changes determines what becomes Current/MIS. If the meeting/event creates an applicable historical reporting transaction, that archive then preserves the dated event state.

The archive may later have Report Status = Pending. That is a different use of the word Pending: it means SIRAS should attempt to submit the selected archived component or components.

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

Verification Checklist

• The Parent Response accurately represents what occurred.
• Pending Changes contain only changes still awaiting a decision or staff action.
• Only agreed-to plan/service changes became Current.
• Unaccepted portions of the prior agreed plan remain intact where required.
• Current services represent the participating service set.
• Goals advanced or remained in place according to the selected response.
• The meeting archive represents the same actual event and consent outcome.
• No new PLAN/SERV is being reported for an unaccepted plan.