Last updated: Oct 15, 2026
Why does Student History say “System” updated the record?
System means an automated background process made the update rather than a named user account. Depending on the district and time of year, that may be SIRAS pulling data from Aeries, an SIS file import, or a rollover process updating items such as grades or next-year data.
If your district uses Aeries and you want to know which fields may be updated, see Aeries to SIRAS API Reference: Fields, Defaults & Optional Mapping. If the update looks unexpected or you need to determine whether it came from an SIS integration, use SIS Integration Troubleshooting & Ongoing Monitoring.
System means an automated background process made the update rather than a named user account. Depending on the district and time of year, that may be SIRAS pulling data from Aeries, an SIS file import, or a rollover process updating items such as grades or next-year data.
If your district uses Aeries and you want to know which fields may be updated, see Aeries to SIRAS API Reference: Fields, Defaults & Optional Mapping. If the update looks unexpected or you need to determine whether it came from an SIS integration, use SIS Integration Troubleshooting & Ongoing Monitoring.
The Student History screen is divided into five sections: Archived Records; Archived Services; Transfer History; Meeting History; and the Change Log.
- SIRAS logs the who & date that the record was created, the who & date that the record was last modified, and who & date that the record was last validated.
- Archived Records - Logs all CALPADS archives

- Archive Services - historical logs all services that the student has had.
![]()
- Transfer History - logs history of transfer from school, districts, SELPAs and 504 or SST module

- Meeting History - logs meetings, event data and the forms used for that meeting

- Change Log - logs CALPADS, important fields and events


