Finalized IEP Records and PDF Archival

Overview

SIRAS is designed to maintain the official electronic IEP record. Once an IEP has been finalized, the record is protected against ordinary modification and serves as the authoritative historical record for that meeting.

Occasionally, districts ask whether they should download the completed PDF and upload it back into SIRAS as a meeting attachment for safekeeping. While this may seem to provide additional security, it is not recommended and does not provide additional protection within SIRAS.

How SIRAS Maintains Finalized Records

Unlike a traditional file cabinet that stores a single PDF document, SIRAS maintains the finalized IEP as a protected electronic record. This record includes the finalized meeting data, the document templates used to generate the IEP, signature records, and the historical information associated with the finalized meeting.

Whenever a finalized IEP is viewed or printed, SIRAS reproduces the official document from this protected record.

This architecture provides several important benefits:

The official record remains searchable and reportable.
Historical information is preserved without maintaining multiple copies of the same document.
The official IEP can be reproduced whenever it is needed.
All users access the same authoritative record rather than separate stored copies.

Record Integrity

The Finalize process is specifically designed to preserve the integrity of the IEP.

After a meeting is finalized:

The finalized meeting information is no longer editable through normal SIRAS workflows.
Signature records remain permanently associated with the finalized meeting.
Any future changes to a student's program require a new meeting, amendment, or other documented process rather than modifying the finalized record itself.
Historical meetings remain available as part of the student's permanent record.

Because the finalized electronic record is protected, storing an additional copy of the generated PDF within SIRAS does not make the record more durable or more authoritative.

Why Complete IEP PDFs Should Not Be Uploaded as Attachments

Meeting attachments are intended for:

Single-page additions to a meeting packet.
Individual page replacements when specifically instructed.
Supporting documents that are not already part of the generated IEP.

Uploading the complete generated IEP PDF as an attachment creates an unnecessary duplicate of a document that SIRAS already maintains as its official electronic record.

This can lead to:

Multiple copies of the same IEP within the student record.
Confusion about which copy should be referenced.
Increased storage requirements.
More difficult records management over time.

For these reasons, SIRAS does not recommend uploading complete generated IEP PDFs as meeting attachments.

Independent District Archives

Some districts have local records-retention policies that require maintaining an independent archival copy of finalized IEP documents outside of their operational IEP system.

If your district requires an independent archival copy, the recommended practice is to:

Download the finalized IEP PDF from SIRAS.
Store that PDF in your district's approved records-management or document-management system.

Examples include SharePoint, an electronic records repository, or another district-approved archival solution.

Maintaining an independent archival copy outside of SIRAS allows the district to satisfy its own records-retention requirements without creating redundant copies within the student's SIRAS record.

Summary

For normal operation, no additional copy of the finalized IEP PDF is needed within SIRAS. The finalized electronic record maintained by SIRAS is the authoritative historical record and is designed to reproduce the official IEP whenever it is needed.

Districts that choose to maintain an independent archival copy may certainly do so, but that copy should be stored in the district's own records-management system rather than uploaded back into SIRAS as a meeting attachment.