What an RFP should say about admissions and enrollment

Describe the school and journey

A useful way to approach what an RFP should say about school admissions software is this: Make an admissions RFP comparable by requiring workflows, evidence, responsibility, controls, support, and complete commercial assumptions.

State campuses, grades, applicant volume, calendar, languages, current systems, family journeys, phase-one scope, desired outcome, decision timeline, and constraints. Ask for inquiry, application, documents, assessment, decision, offer, acceptance, waitlist, enrollment, and withdrawal responses.

Write requirements around actors, data, decision, permission, approval, exception, family message, handoff, and acceptance test.

Require evidence and boundaries

Require vendors to label native behavior, configuration, integration, manual work, roadmap, and unknowns. Use incomplete, duplicate, changed-guardian, rejected-document, waitlist, withdrawal, family-access, and enrollment-handoff 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 recommends minimum necessary data, access control, security, supplier accountability, incidents, and end-of-contract handling.

The U.S. Department of Education data governance checklist connects 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.

How what an RFP should say about school admissions software changes the decision

Use this guidance to improve one bounded part of what an RFP should say about school admissions software. Name the owner, affected record, evidence needed, and review date. Keep the test small enough for admissions staff to complete and specific enough for a later audit.

Check both an ordinary application and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the next step ready.

Record what changed, what remains manual, and who reviews the result before the next admissions cycle.

Choosing an admissions system for what an RFP should say about school admissions software

For a school evaluating what an RFP should say about school admissions software, the useful test is whether the workflow has a clear owner, a shared record, and a next step that can be measured. Move applicants from first enquiry to an owned next step without re-keying records.

The failure worth guarding against here is a strong pipeline that stops at the offer, leaving the registrar to retype every accepted applicant. Decide what the applicant record, which should become the student record is, and hold every candidate to it.

Start with one recent example of what an RFP should say about school admissions software. Write down who acted, which record they used, and where the work paused.

• Count how many times an applicant is typed in before they enrol.
• Identify who chases documents, and how they know what is missing.
• Note what a family can currently see about their own application.

A practical decision on what an RFP should say about school admissions software

Use the what an RFP should say about school admissions software decision as a workflow question, not a feature-count exercise.

The next action is not a demo. It is writing down where the current process actually breaks, because that is the only thing that will let you tell a good demo from a polished one.