Purpose: Determine whether a missing historical census-effective CALPADS PLAN can be reported through an existing open or closed meeting or ordinary archiving, and, only when it cannot, reconstruct the verified historical record using the Back In Time workflow. This is an exception procedure, not a way to invent or alter the actual meeting history.
Useful for: Updating Program Setting after Census.
Useful for: Creating Plan Adoptions for some return to participation scenarios.
Navigation: Open the appropriate student record in SIRAS → Archive for Reporting → select Addendum/Amendment → create the archive using today's Report Event Date. Then open that archive for editing to reconstruct the verified historical record. The original article does not provide a fuller menu-by-menu path; follow your district's authorized record-access workflow.
Contents
1. Do I need Back In Time? Check whether the meeting can report the census-effective PLAN
Can this meeting produce the required reportable PLAN with a Plan Effective Start Date on or before Census Day? The meeting's date or open/closed status by itself does not answer the question.
Practical decision rule: Back In Time is needed only when a historical census-effective PLAN is missing, the open or already closed meeting cannot produce that required PLAN, and an appropriate historical archive cannot be obtained through the normal process.
| Question | If YES | If NO |
|---|---|---|
| 1. Is the required PLAN, effective on or before census, already correctly represented by a reportable archive? | Stop: Back In Time is not needed for this PLAN. | Continue to question 2. |
| 2. Can the open or already closed meeting produce the required reportable PLAN with an effective date on or before census? | Use the normal meeting/reporting workflow. Back In Time is not needed. | Continue to question 3. |
| 3. Can an appropriate earlier historical PLAN archive still be created by the ordinary archive workflow? | Use normal archiving. Back In Time is not needed. | Back In Time is needed to reconstruct the missing verified historical PLAN, subject to the authorization and evidence checks below. |
Quick examples
| Meeting / reporting situation | Result |
|---|---|
| Open meeting before census; agreed plan can be finalized and reported with the required effective date on/before census. | No Back In Time — use normal reporting. |
| Already closed meeting produced the required PLAN effective on/before census. | No Back In Time — use that reportable PLAN. |
| Meeting after census; its PLAN is effective after census and the earlier required PLAN is missing. | Back In Time if normal archiving cannot create the missing earlier PLAN. |
| Meeting before census but plan not agreed to; open stay-put meeting cannot report the proposed PLAN needed for the earlier timeline. | Back In Time if a separate historical reportable PLAN is required and normal archiving cannot supply it. |
| Already closed meeting produced no PLAN, or only a PLAN effective after census, and the necessary prior PLAN is missing. | Back In Time if ordinary archiving cannot supply the prior PLAN. |
Why the error appears: A newer Annual Plan Review or Triennial Reevaluation can update Last Annual or Last Evaluation. Attempting to archive an earlier event may then show “Report Event Date cannot be before Last Annual.” This message indicates a workflow obstacle; it does not establish which PLAN should be reported.
Open meeting blocks creating any archive? Normally complete the applicable meeting workflow first. If that cannot occur and a reporting deadline is approaching, contact SIRAS Support for assistance; do not bypass the restriction without authorization.
2. Verify historical information
Before creating or changing an archive, collect and confirm:
- The actual historical effective date (for example, the student’s enrollment date or the date a program-setting change took effect).
- The prior Last Annual and, when relevant, Last Evaluation dates.
- Any other plan fields that differed at that time, including the correct program setting.
- The relevant earlier archive or another reliable record of the earlier plan; take the screenshot of that archive recommended in the original workflow as a comparison reference.
- The specific CALPADS issue being corrected and the reporting window.
3. Create and correct the archive
Stage A — Create an archive with today's date
- In the relevant student record, click Archive for Reporting.
- Select Addendum/Amendment.
- Leave Report Event Date at its default date of today; create the archive. This initial creation is necessary before editing the archived values.
Stage B — Reconstruct the verified historical values
- Open the archive just created with today's date.
- Choose Open Archive for Editing.
- Using your verified earlier records, restore the historical Last Annual date and any other old values that were different on the intended effective date. Where applicable, also verify Last Evaluation.
- Confirm that the program setting matches what should have been reported for that historical event.
- Change Report Event Date to the documented historical date of the missing event.
- Save the edited archive.
4. Worked CALPADS examples
PLAN0619 — Historical program setting not archived
A student turned five in August, before the first day of school on August 21. A change to program setting 400 should have been reported at that time, but was missed. By October 15, a plan review held October 8 had already updated the plan after the Fall census date. Reconstruct the missing archive using the verified program setting and historical effective date, rather than simply archiving the later plan as if it were the August plan.
SENR0606 — Missing plan adoption before a later meeting
A student enrolled in the district on September 1, when a plan adoption should have been documented. A later meeting changed the Last IEP date to October 20. On November 1, the missing September transaction is discovered. Create the amendment archive using November 1 first, then edit it to reflect the verified September 1 historical plan and event date.
Note: These are illustrative timelines from the source article, not current calendar dates or universal CALPADS instructions. The type and historical fields of any correction must match the actual situation.
Also consider unresolved/stay-put meetings: Even if a meeting occurred before census, a plan that was not agreed to may not produce a reportable PLAN. In that case, determine the historical plan actually in effect. If its required archive is missing and cannot be created normally, the Back In Time workflow may be necessary. Do not represent the unagreed proposed plan as the historical plan.
5. Verify and send
- Reopen or review the saved archive and confirm the Report Event Date, Last Annual/Last Evaluation dates where applicable, program setting, and other relevant values reflect the verified historical event.
- Compare the reconstructed archive with the earlier documentation and ensure it does not inadvertently include changes introduced by the later meeting.
- Check that the archive is eligible for the intended CALPADS reporting workflow and obtain any required district approval.
- Send data through the authorized SIRAS reporting workflow, then review the reporting results and any remaining CALPADS errors.
6. When to request help
If an open meeting blocks the new archive, the historical data is unclear, or the reporting deadline is too close to complete the usual finalization process, contact [email protected]. Explain the CALPADS error, the event you need to report, whether a meeting is open, and the verified dates. Do not send confidential student information in unsecured email.
