There are times when as of today we have to create an archive to fix a CALPADS error resulting from missing data that should have been archived earlier.

 

But the problem is that an annual or plan review has been held after the census date to creating an archive today reflects a whole new plan.

 

Ex. PLAN0619

Student turned 5 in August just before first day of school on 8/21 and needed the updated 400 program setting sent at the time but it was missed.

Today is October 15 and there was a plan review that happened on October 8, after the first Wed. Census date.

 

Ex. SENR0606

Student transferred to your district. Somehow an annual plan review or triennial reevaluation happened before a plan adoption archive was created.

Student enrolled in your district on 9/1. Meeting updated last IEP date to be 10/20.

Plan adoption should have been done as of 9/1

Today is 11/1, so we archive amendment as of 11/1.

Then open the archive created today with the 11/1 date, but we need to back date it to look like what it 'would have' looked like on 9/1 the date the student enrolled at your district.

 

If we try to 'archive' the updated plan today, it will reflect the plan of the meeting held after Census on October 8th.

If we try to archive as of the older date, SIRAS gives you an error that report event date can't be before the annual date.

 

This is where the 'Back In Time' solution will allow us to create the missing archive 'today' as if it was from the 'past'.

How to create back in time archive:

1. Click the Archive for reporting button.
2. Select Addendum/Amendment
3. Leave the Report Event as of 'today'
4. Make note of an earlier archive with a screenshot
5. Open the archive with today's data
6. Click open archive for editing
7. Put back the old last Annual date
8. Put back any other older data
9. Ensure the correct program setting is place
10. Change the report event date to be the 'back in time date' of when we want the amendment plan to be in effect.
11. In this example the first date the student was 5 and enrolled so we roll it back to the example date of 8/21
12. Save the new date
13. Now we have created an archive that for all intents and purposes 'could have' been created 2 months earlier
14. Send data