That's usually not what administrators want to hear, because a single simple number would make life easier. But a single student file often contains transcripts, attendance logs, discipline records, special-education documentation, health records, consent forms, and email threads. Each of these can carry a different legal shelf life.
This article breaks down what FERPA actually requires, how to classify records correctly, where retention periods really come from, and how to build a destruction process that won't come back to bite you.
Key Takeaways
- FERPA governs privacy, access, amendment, and disclosure, not a nationwide retention timeline
- Districts must consult state and local records schedules to set actual destruction dates
- Special-education, health, financial, and legal-hold records often carry separate rules
- Retention systems need audit trails, access controls, and documented destruction approval
- Confirm your state’s schedule (e.g., Texas TSLAC Local Schedule SD); do not assume a generic period
What FERPA Requires—and What It Does Not
FERPA is a federal privacy law under 34 CFR Part 99. It applies to any educational agency or institution that receives funding through a program administered by the U.S. Department of Education. Receipt of that funding is the trigger, not the nature of any single benefit a student receives. Current FERPA regulations apply to the district as a whole once it's a covered recipient.
For K-12 purposes, FERPA gives parents (and eligible students at 18) four core rights:
- Inspect and review education records
- Request amendment of records believed to be inaccurate or misleading
- Consent before disclosure of personally identifiable information, with limited exceptions
- Receive annual notification of these rights, including how to exercise them
The 45-Day Access Window
Districts must provide access "within a reasonable period of time," but no later than 45 days after receiving a request. This is an access deadline, not a retention period—and that distinction drives destruction planning.
Here's the practical trap: a district cannot destroy a record while an access request for it is outstanding, even if the scheduled retention period has technically expired. Any destruction workflow needs a hold-check for pending requests built in before anything gets shredded or purged.
Disclosure Logging Runs Alongside the Record
FERPA also requires districts to keep a record of each request for access and each disclosure of personally identifiable information. That log must stay with the education record for as long as the record is maintained.
Narrow exceptions do not need to be logged:
- Parent or eligible-student requests
- School-official access
- Written-consent disclosures
- Directory-information requests
The key distinction: FERPA does not tell you when to destroy a record. It tells you how to handle privacy, access, and disclosure while you keep it.
A district can retain a record for the legally correct period and still violate FERPA. Wrong staff access, or a disclosure without consent or a valid exception, is enough.
Which Records Are Covered by FERPA?
An "education record" has two elements under 34 CFR 99.3:
- Information directly related to a student
- Maintained by the school or by someone acting for the school
In a typical K-12 context, that covers:
- Enrollment forms and registration paperwork
- Grades, transcripts, and academic progress notes
- Attendance records
- Discipline files, including suspension and expulsion documentation
- Special-education evaluations and IEPs
- Parent communications tied to a specific student
- Consent forms
- School-maintained health and immunization records
The Exclusions Are Narrower Than People Think
Four categories fall outside the education-record definition, but each has specific conditions:
- Sole-possession notes — only if used solely as a personal memory aid and never shared except with a temporary substitute
- Law-enforcement-unit records — subject to separate conditions under 34 CFR 99.8
- Employee records — only if made in the normal course of business, tied only to employment, and unrelated to student status
- Treatment records — only for students 18+ or in postsecondary education; created by a specified health professional, used only for treatment, and shared only with treatment providers
That last one trips up a lot of districts. A school nurse's note about a student's asthma action plan is not automatically excluded just because it's health-related. Unless it meets every condition of the treatment-record exclusion, it's an education record subject to FERPA.
Don't Treat Cumulative Files as One Retention Unit
A student's cumulative folder often gets treated as a single block with one retention date. That's a mistake. Transcripts might be permanent records while attendance logs inside the same folder expire in two years. Build your classification around individual record types, not the folder as a whole.
A workable classification method tracks:
| Field | Purpose |
|---|---|
| Record type | What the document actually is |
| System/location | Where it physically or digitally lives |
| Owner | Who's responsible for it |
| Retention authority | Which schedule or law governs it |
| Retention trigger | What event starts the clock |
| Access level | Who can view or edit it |
| Destruction approval | Who signs off before disposal |
How Long K-12 Districts Should Keep Student Records
Let's settle the seven-year question first. FERPA itself does not impose a universal seven-year retention rule. If you've seen a seven-year figure somewhere, it's almost certainly coming from a specific state schedule for a specific record type, or from a district policy — not from federal FERPA regulation.
The U.S. Department of Education's own guidance confirms schools generally aren't required to maintain particular education records; FERPA protects the privacy of whatever records the school chooses or is otherwise required to keep. That "otherwise required" part is where state law and local policy take over.
The Retention Hierarchy Districts Should Follow
When setting an actual destruction date, work through this order:
- Applicable state education or public-records schedule — usually the controlling authority
- District policy — can be more restrictive but not shorter than the state minimum
- Federal program requirements — grant-funded records often carry their own rules
- Court orders or litigation holds — override scheduled destruction entirely
- Contractual or accreditation obligations — relevant for specialized programs
A Record-Type Framework
Different record categories tend to fall into recognizable retention patterns, though the exact periods vary by state:
- Permanent or long-term academic records — transcripts and core academic history often never expire
- Attendance and enrollment records — frequently shorter windows, sometimes 2-5 years
- Discipline records — often tied to a fixed period after the incident, not graduation
- Special-education records — commonly retained for a period after services stop
- Health records — often keyed to withdrawal date plus a set number of years, or a specific age
- Consent documentation and disclosure logs — tied to the life of the associated record, not a standalone timeline
Texas: A Case Study in Why This Gets Complicated
Texas is a good example of how record-specific retention actually works. Under TSLAC Local Schedule SD, districts face genuinely different rules depending on the record:
- High school transcripts (grades 9-12): permanent
- Special-education records: cessation of services plus 5 years, with a requirement to notify the parent or eligible student before destruction
- DAEP, suspension, or expulsion records: 5 years
- Attendance reports submitted to TEA: 5 years
- Cumulative health cards: withdrawal plus 7 years, or until age 21, whichever is later
Notice that even within one state, the triggers differ: withdrawal, cessation of services, submission date, and age all appear as separate starting points. The Texas Education Agency also requires certain student records to be kept permanently — proof that retention rules are set record by record, not district-wide.
If your district is in Texas, don't extrapolate from a neighboring state's schedule or a generic online list. Check TSLAC's current schedule and TEA guidance directly, then apply it record by record.
Document Your Triggers
Retention periods only work if the trigger event is documented and tracked. Common triggers include:
- Graduation
- Withdrawal or transfer
- Last date of attendance
- Record creation date
- Audit completion
- End of a legal hold
A retention period without a clearly logged trigger date is unenforceable in practice. If nobody recorded when a student withdrew, you can't calculate when that record's clock started.
How to Build a FERPA-Aligned Retention Program
Build retention management as a working system with four parts: a complete inventory, a retention matrix, named owners, and recurring reviews.
Start With a Complete Inventory
Map every place student records live, not just the obvious ones:
- Student information systems
- Paper files in school offices
- Shared drives and email
- Nurse offices and health platforms
- Special-education case management systems
- Transportation records
- Archived media (old backups, microfilm, etc.)
- Third-party vendor platforms
The U.S. Department of Education's Privacy Technical Assistance Center recommends this kind of complete inventory as the foundation for data governance, paired with documented data-collection purposes and sensitivity classifications.
Build the Retention Matrix
Turn the classification fields from earlier into a living matrix that captures:
- Record series
- Controlling authority
- Trigger event
- Minimum retention period
- Owner
- Access roles
- Destruction approver
Keep this matrix as the district’s authoritative reference so staff are not left relying on institutional memory.
Assign Governance Roles
Retention programs fail when nobody owns them. Define these roles explicitly:
- Records owner — oversees the overall program
- Privacy/FERPA lead — handles rights requests and disclosure decisions
- IT administrator — manages system-level access and technical destruction
- Legal contact — advises on holds and exceptions
- School-level records coordinator — handles day-to-day building requests
Operational Controls That Keep the System Honest
Put these controls in place so day-to-day practice stays aligned with the matrix:
- Log every access request and disclosure per FERPA requirements
- Send the annual FERPA notice to parents of currently enrolled students
- Review vendor contracts for data-handling and retention terms
- Track legal holds so scheduled destruction doesn't override them
- Build an exception process for records that need to survive past their normal period
Schedule Recurring Reviews
Set a recurring cadence (annual is typical) to identify expired records, confirm holds are still being honored, spot-check access permissions, and reconcile disclosure logs against actual maintained records. Document what you find and what you fixed. This audit trail is often what protects a district if a retention decision is ever challenged.
Secure Storage, Digitization, and Destruction
Paper, digital, and hybrid storage each trade off access control, disaster recovery, and record-specific rules.
- Paper is simple but hard to search, easy to misplace, and vulnerable to physical damage
- Digital systems support access logging and faster retrieval, but need backup management and version control
- Hybrid setups are common in practice but require clear rules about which format is authoritative
Digitization Doesn't Erase the Retention Clock
Scanning a paper file doesn't automatically end your retention obligation. Before disposing of originals, confirm:
- Whether your state schedule requires the original to be preserved regardless of digitization
- That scan quality and indexing are accurate and complete
- That the source files are protected from unauthorized edits
- That disposition of the paper record is documented, not just assumed
Texas's own schedule, for example, only allows disposal of the paper original before its minimum period ends if it's been properly microfilmed or electronically stored under specific state rules.
Digitization is a storage decision, not a retention shortcut.
A Defensible Destruction Process
Whether you're purging paper or wiping electronic files, follow the same sequence:
- Confirm the retention period has ended for that specific record type
- Check for legal holds or pending access requests tied to the record
- Obtain authorization from the designated records officer
- Use secure destruction or media sanitization appropriate to the format
- Preserve a destruction record or certificate documenting what was destroyed and when
For electronic media, NIST media-sanitization guidance is the standard reference for verifying that data is genuinely unrecoverable, not just deleted from a visible folder.
Where a School Health Platform Fits In
School health records add another layer: they combine FERPA-covered education records with sensitive medical information such as medication logs and immunization history. A platform built for school health workflows, such as MyCabinet School Health, supports:
- Role-based access so only authorized staff see specific record types
- Structured documentation with audit trails for clinic visits and medication administration
- Digital health forms that parents submit directly, reducing paper handling
- Controlled, one-way parent notifications for clinic visits and medication expirations
The school retains ownership and control of student records stored in the system. MyCabinet follows district direction on retention and deletion rather than setting its own timeline.
That distinction matters. A well-designed platform can support your retention matrix with structured access and audit logging, but retention decisions still come from your state schedule and district policy—not the software vendor.
Frequently Asked Questions
What is the 7-year FERPA student records retention policy?
There isn't one. FERPA doesn't establish a universal seven-year retention period. Any seven-year figure you've encountered comes from a specific state schedule or district policy for a particular record type, not from FERPA itself.
How long do schools keep student records in Texas?
It varies by record category and trigger event. Districts should consult the current TSLAC Local Schedule SD, TEA guidance, and their own district policy rather than assume one period applies to every record.
What is not considered an educational record under FERPA?
Common exclusions include qualifying sole-possession notes, law-enforcement-unit records, certain employment records, and treatment records meeting specific eligibility conditions. Confirm the exact regulatory conditions before assuming something is excluded.
Does FERPA require schools to keep student records for a specific amount of time?
No. FERPA mainly governs privacy, access, amendment, and disclosure. Retention periods generally come from state records schedules, district policy, and other applicable program requirements.
How should school districts securely destroy old student records?
Confirm the retention period has ended and that no legal holds or pending access requests apply. Then get authorization, use secure destruction or media sanitization methods, and document exactly what was destroyed and when.
