Admissions CRM RFP questions: the buyer's checklist

Choosing an admissions CRM is a decision your team will live with for years. It shapes how counselors spend their day, how applicants experience your institution and how leadership understands enrollment. Yet many selection processes focus on feature lists and polished demos, and discover the important questions only after the contract is signed.

This checklist is designed to help you ask better questions of any vendor, including us, and our own answers are published. Use it to structure demos, reference calls and your internal discussions. If you're new to the category, start with what is an admissions CRM?

Before you speak to vendors

The most useful preparation happens internally. Agree what problem you are solving before you see any product, or every demo will redefine it for you.

• Write down where inquiries arrive today and where they get lost.
• Map your stages from inquiry to enrollment, including the post-offer period.
• List the systems that must connect, especially your student information system.
• Identify who will use the CRM daily, weekly and monthly, and what each needs to see.
• Agree three to five outcomes that would make the project a success in its first cycle.
• Decide who owns the system internally after go-live.

Fit with your admissions process

• Can we configure our own stages, programs, entry terms and campuses without custom development?
• How does the system handle applicants interested in several programs or entry terms?
• Can different schools, departments or teams run different processes within one system?
• How are inquiries routed and assigned, and how easy is it to change the rules mid-cycle?
• What does a counselor see when they start their day?
• How are online applications, document checklists and decisions handled?

Ask to see your own process in the demo. A good vendor will want to understand it before showing you anything.

Communication and engagement

• Which channels are supported for outbound and two-way messaging: email, SMS, WhatsApp, others?
• Can journeys branch on behavior, stage and deadlines, and pause when someone replies?
• How are consent and channel preferences recorded and respected?
• Can counselors see every conversation with an applicant on one record?

Data, integrations and reporting

• How does the CRM exchange data with our student information system, and in which direction?
• Is there a documented API and webhooks, and are there extra charges for using them?
• How are duplicates detected and merged across channels?
• How is lead source attributed from first touch to enrollment?
• Can we build our own reports, and how do leadership summaries work?
• If AI features are included, what data do they use, and can users see why a recommendation was made?

Security, privacy and responsible AI

• How is data encrypted in transit and at rest?
• How granular are access controls?
• Are changes and data access recorded in audit logs we can review?
• Is a data processing agreement available, and what does it say about sub-processors?
• Where is our data hosted, and what options exist for data location?
• How are data subject requests, retention and deletion handled?
• Is our applicants' data ever used to train models, and on what terms?
• How will you tell us if something goes wrong, and how quickly?

Ask for evidence rather than adjectives. Documentation, a security questionnaire response and a clear incident process are worth more than a slide that says "enterprise-grade".

Implementation and support

• What does implementation involve, who does the work, and how long does it usually take?
• Will you migrate our existing prospect data, and in what formats?
• How are different user groups trained?
• What support is available after go-live, and does it continue through our first full admissions cycle?
• Who will be our named contact, and what happens if they leave?
• How are product updates communicated, and how do customer requests reach the product team?

Pricing and commercial terms

• What is the pricing basis?
• What is included and what costs extra: implementation, messaging, integrations, storage, support?
• How does pricing change if our volume grows or falls?
• What are the contract length, renewal terms and notice periods?

The exit questions

Every good relationship should be easy to end. It is much easier to agree exit terms at the start than at the end.

• Can we export all of our data, including communication history and documents, at any time?
• In what format, and at what cost?
• What happens to our data after termination, and how is deletion confirmed?

Running a fair evaluation

1. Shortlist a small number of vendors against your written requirements.
2. Send each the same brief and ask them to demonstrate your scenarios.
3. Involve counselors in demos. They will spot friction that managers miss.
4. Ask for a sandbox or trial with your own sample data where possible.
5. Score each vendor against the outcomes you agreed at the start.
6. Bring in your IT and data protection colleagues early, before contract stage.

For colleges and universities, the right admissions CRM is the one your team will use every day, that connects cleanly to the systems you already have, and that is sold by people who listen to how you work before telling you how to change it.