Operations
What an RFP should say about student records and enrollment data
What an RFP should say about student information systems: records, workflows, evidence, implementation, access, privacy, security, support, and total cost.
Describe the school and journey
State campuses, grades, student population, users, calendar, current systems, record types, phase-one scope, desired outcome, decision timeline, and constraints.
Ask for inquiry, enrollment, class placement, transfer, correction, reporting, family access, archive, and support responses.
Require evidence and limits
Require vendors to label native behavior, configuration, integration, manual work, roadmap, and unknowns. Use duplicate, changed name, transfer, withdrawal, missing value, correction, report, family-access, and outage scenarios.
Record observed result, school responsibility, vendor responsibility, support route, limitation, and unresolved risk.
Include governance and delivery
Ask about identity, documents, roles, exports, retention, suppliers, subprocessors, incidents, recovery, migration, validation, training, support, monitoring, and contract end.
GOV.UK guidance emphasises accountable and secure handling. The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring.
Make commercial answers comparable
Request subscription, setup, migration, integration, payment, training, support, growth, reporting, internal capacity, export, retention, and contract-end costs. Publish scoring and hold criteria before responses arrive.
Make the next improvement testable
Use this guidance to improve one bounded part of what an RFP should say about student information system. Name the owner, record, evidence, correction route, and review date so staff can apply it consistently.
Check an ordinary record and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, training note, or support route.
Record what changed, what remains manual, and who reviews the result before the next reporting or enrollment cycle.
Keep the decision beside its evidence so the next operator can understand the rule without relying on informal memory.
Use the review to decide whether the change should be expanded, repaired, narrowed, or held.
