What procurement teams ask about admissions and enrollment

Ask what work the proposal covers

Require the supplier to respond to inquiry, application, documents, assessment, decision, offer, acceptance, waitlist, enrollment, withdrawal, family communication, and reporting. Ask for school-specific scenarios rather than module names.

Require labels for native behavior, configuration, integration, manual work, roadmap, and unknown. Record assumptions, exclusions, dependencies, and school obligations.

Ask how data is governed

What is the source of truth for applicants, guardians, documents, decisions, offers, and enrollment? Who can view, create, edit, approve, publish, export, correct, archive, and delete? How are duplicates, changed guardians, retention, and contract-end exports handled?

GOV.UK procurement guidance recommends minimum necessary data, access control, security, supplier and subprocessor accountability, incident notification, and end-of-contract handling. The U.S. Department of Education checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring.

Ask what implementation requires

Request school and vendor responsibilities for discovery, cleanup, mapping, migration, validation, configuration, testing, training, communication, support, incidents, monitoring, and reconciliation. Include peak admissions and staff absence.

Ask who handles a duplicate applicant, wrong offer, missing document, family access issue, failed notification, or student handoff problem. A named route is better evidence than a general promise of support.

Ask for complete commercial evidence

Compare subscription, setup, migration, integration, payments, training, support, growth, reporting, internal capacity, export, retention, and contract-end costs. Define the outcome and the evidence that will be reviewed at 30, 60, and 90 days.

Make the next action clear

Use this guidance to improve one bounded part of what procurement teams ask 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.