RFP requirements for admissions and enrollment

Write the school context

State campuses, grades, applicant volume, intake calendar, applicant and family journeys, current systems, languages, documents, local constraints, phase-one boundary, desired outcome, and decision timeline.

Describe the workflow rather than listing modules. Ask vendors to respond to inquiry, application, document review, assessment, decision, offer, acceptance, waitlist, enrollment, and withdrawal.

Require observable workflow responses

For each journey, request actors, source, required data, permissions, approval, output, exception, family message, integration, audit history, and acceptance test. Include incomplete applications, duplicates, changed guardians, late documents, and rejected evidence.

Require labels for native behavior, configuration, integration, manual work, roadmap, and unknown. A yes without evidence should not receive the same treatment as an observed result.

Set data and control requirements

Ask about identity matching, guardian relationships, documents, decisions, offers, retention, correction, exports, support access, and contract-end return or deletion. Specify who can view, create, edit, approve, publish, export, correct, archive, and delete.

GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security, supplier accountability, incident notification, and end-of-contract handling. The U.S. Department of Education checklist provides governance prompts for quality and lifecycle.

Require an implementation response

Ask who owns discovery, cleanup, mapping, migration, validation, configuration, testing, training, communication, support, incidents, reconciliation, monitoring, exports, retention, and deletion. Include school capacity, peak admissions, leave, and campus variation.

Require a plan for temporary work and recovery. Shared accounts and uncontrolled exports should not be the default answer to a busy period or outage.

Make commercial answers comparable

Request subscription, setup, migration, integration, payment, training, support, growth, reporting, internal-capacity, export, retention, and contract-end costs. Require assumptions, exclusions, dependencies, variable charges, and renewal conditions.

Separate price from value. Ask how the school will measure completion, quality, family experience, support demand, and the defined outcome at 30, 60, and 90 days.

Publish scoring and gates

Publish the scoring method before responses arrive. Set hold criteria for identity, privacy, permissions, document handling, family visibility, recovery, support, and data return. Keep evidence and unresolved risk beside the score.

An RFP is strong when it produces comparable evidence and makes school responsibility visible. It is not strong merely because it contains many requirements.

Turn the guidance into an admissions decision

Apply this guidance to one bounded part of RFP requirements for school admissions software. Define the applicant or student journey, the people involved, the source of each value, the permission boundary, the evidence required, and the condition that pauses the next step.

Test a complete case and meaningful exceptions such as an incomplete application, changed guardian, duplicate student, withdrawn applicant, late document, waitlist movement, or transfer. Record what happened, who corrected it, and how the applicant received a clear status.

Keep vendor capability, school responsibility, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and the rollout rather than treating an assumption as a promise.

Review the decision at 30, 60, and 90 days. Look at completion, data quality, response time, access exceptions, family experience, support demand, and the original outcome. Decide whether to expand, repair, consolidate, or hold.

Before approval, ask an accountable reviewer to challenge the strongest claim. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Make the final record readable to an admissions operator and a reviewer who was not in the project. State what passed, what remains manual, what is deferred, who owns the unresolved item, and how a family receives help without creating an uncontrolled copy of applicant data.

Keep the approved record beside its acceptance tests, support guidance, and change history. A new campus, role, field, calendar, supplier, or family-facing output can change the risk even when the original workflow appears unchanged.