Education
Education document management for student records
Education document management spans records with very different sensitivities: enrolment files, safeguarding referrals, staff records and accreditation evidence. Each needs its own permission set and retention period, and FERPA in the US or UK GDPR elsewhere gives students a right of access that has to be answerable.
Why documents are difficult in education
Education document management has to accommodate record types whose sensitivities differ by an order of magnitude, held by one institution and often in one system. An enrolment form, a safeguarding referral, a staff disciplinary file and an accreditation evidence pack all need different permissions, different retention periods and different disclosure treatment. Applying one policy across them either over-restricts the routine records or under-protects the sensitive ones.
The second characteristic is that students have access rights over their own records, and those rights outlast their enrolment. A graduate can request their file years after leaving, which means records must remain findable and produceable long after the department that created them has reorganised — and long after the staff who filed them have gone.
Regulatory pressure
Three pressures that shape the configuration
Student record access rights — FERPA (US) and UK GDPR / GDPR
What it requires. Students and, for minors, parents have a right to inspect and review education records, and to request correction. Under the GDPR the response period is one month, extendable; FERPA requires access within 45 days.
What it means for a document system. Retrieval has to work across the whole record, not just the student information system — including scanned correspondence and documents filed by individual departments. The one-month clock also means a search that requires asking several teams where they keep things will miss it.
Safeguarding and child protection record duties
What it requires. Safeguarding concerns and referrals must be recorded contemporaneously, retained for extended periods, and disclosed only to those with a legitimate need — with retention typically extending well past the age of majority.
What it means for a document system. These are the most restricted records the institution holds and the longest retained. They need permissions narrower than any other branch, recorded access, and a retention trigger keyed to the subject reaching the age of majority rather than to the record date.
Accreditation and inspection evidence
What it requires. Accrediting and inspecting bodies require evidence of policies, procedures, staff qualifications, curriculum design and student outcomes, in force during the review period rather than at the date of inspection.
What it means for a document system. Superseded versions matter: the question is what was in effect during the period reviewed. That makes version retention and acknowledgement records the substance of an accreditation submission, not a byproduct of it.
Capability mapping
Five capabilities mapped to education requirements
Branch separation by school or faculty
Branch and department separation under central administration suits multi-school trusts, federated colleges and universities with devolved faculties — administered centrally while keeping each unit’s records separate.
Narrow permissions for safeguarding records
Per-module permission levels finer than read/write, with preview-only for staff who need to confirm a fact without retaining a copy, and per-document overrides visible in the shared-access overview rather than hidden.
Subject access response from one search
OCR over scanned correspondence plus enforced metadata means a request for a student’s records is a query across the whole repository rather than a canvass of departments — which is what makes the statutory deadline achievable.
Policy versions as accreditation evidence
Superseded versions are retained and dated, and acknowledgement is recorded per named staff member against a specific version. An inspection asking what was in force during the review period is answered from the record.
Retention keyed to age of majority
Retention rules take explicit triggers, including the subject reaching the age of majority — the trigger that safeguarding and pupil records need and that a creation-date schedule gets wrong by years.
Taxonomy
A starting folder taxonomy
Student records
- Applications and enrolment
- Assessment and progression records
- Correspondence with students and parents
- Support plans and adjustments
- Awards and transcripts
Safeguarding (restricted)
- Concerns and referrals
- Multi-agency correspondence
- Case notes and reviews
- Allegations against staff
Staff records
- Contracts and variations
- Qualifications and registrations
- Pre-employment checks
- Training and appraisal
- Disciplinary and grievance files
Governance and quality
- Policies and procedures (controlled)
- Governing body minutes
- Accreditation and inspection evidence
- Curriculum documentation
Estates and operations
- Premises and health and safety records
- Statutory inspections
- Contracts and procurement
- Insurance
Safeguarding is a separate top-level branch rather than a folder inside student records, deliberately. It carries the narrowest permissions and the longest retention in the institution, and nesting it under a branch with broader access is how inappropriate access happens by inheritance rather than by intent.
Worked example
A worked workflow: a subject access request from a former student
Step 1: Log and start the clock
The request is recorded with its receipt date and identity verification. The statutory response date is calculated rather than estimated, and the case is assigned to a named owner.
Step 2: Search across the repository
A saved search across document contents and metadata identifies records associated with the individual, including scanned correspondence filed by departments. The query is retained as evidence the search was adequate.
Step 3: Review and apply exemptions
Third-party information, references given in confidence and material subject to other exemptions are redacted on the released copy, with the reasoning recorded and the unredacted original retained.
Step 4: Respond and retain the response
The response is issued and filed with the request, the search record and the exemption decisions — which together become a record with its own retention period.
Retention
Retention expectations
| Record class | Commonly applied period | What starts the clock | Source |
|---|---|---|---|
| Pupil / student records | Commonly retained until the subject’s 25th birthday, or longer | Subject reaching the age of majority | National records management guidance for schools and colleges |
| Safeguarding and child protection records | Very long — commonly decades, sometimes until the subject’s 100th birthday | Date of birth of the subject | Statutory guidance and inquiry recommendations; verify locally |
| Staff pre-employment checks | Duration of employment plus a defined period | End of employment | Safer recruitment guidance |
| Accreditation and inspection evidence | At least until the next review cycle completes, commonly longer | Completion of the review | Accrediting body requirements |
| Governing body minutes | Often permanent | Not applicable | Institutional archive policy |
| Subject access request files | Commonly 1–3 years, longer where challenged | Closure of the request or final appeal | Institutional policy informed by regulator guidance |
These periods are indicative and should be replaced with the retention schedule applicable to your jurisdiction and institution type before you rely on them. Safeguarding retention in particular is long, contested and repeatedly reshaped by public inquiries, so treat any published figure as a starting point rather than an answer. Nothing here is legal advice.
FAQ
Education document management: common questions
Does DocumentMS replace our student information system?
No. The SIS holds structured student data — enrolment, assessment, progression. DocumentMS holds the documents around it: scanned correspondence, support plans, safeguarding files, staff records, accreditation evidence. That distinction matters at subject access time, because the documents are usually the part nobody can find.
How do we keep safeguarding records restricted?
By making safeguarding a separate top-level branch with its own narrow permissions, rather than a folder inside student records where it would inherit broader access. Access is recorded as well as restricted, so inappropriate access is detectable and not merely prevented.
Can retention be triggered by a student’s date of birth?
Yes — retention rules take explicit triggers, including the subject reaching the age of majority. This is the trigger that pupil and safeguarding records require, and a schedule that starts every clock at document creation will dispose of them years early.
How does this help with an inspection?
Inspections ask what was in force during the review period, not what is in force today. Because superseded policy versions are retained and dated, and acknowledgement is recorded per staff member against a specific version, the evidence pack is assembled from the record rather than reconstructed.
Can each school or faculty administer its own records?
Yes. Branch and department separation lets each unit manage its own documents under central administration, which suits multi-school trusts and federated institutions where commingling records between units would itself be a problem.
最終レビュー: 2026-09-01. Compare all ten industry configurations.