Admissions

Why an admissions team deserves better than a generic tool

The choice looks reasonable: the institution may already own a CRM, it is solid, it can be configured for almost anything. The gap does not show on the day you buy it. It shows in the middle of the campaign.

28 August 20266 min readBy the GEERD team

An admissions team looking for a tool usually ends up in front of a sales CRM. But “configurable for anything” is not the same as “built for admissions”. The gap does not show at purchase, nor during the demonstration. It shows around mid-campaign, on the day the tool cannot name what the team is doing.

Two different shapes of work

A sales CRM is built around a deal: one contact, an amount, a forecast close date, an owner, and an ending with two outcomes, won or lost. The salesperson moves the deal, and moves the stage. The model is good, and coherent from end to end.

An admission is built around a file: required documents, a deadline shared by every applicant, several people giving an opinion, and an ending with five outcomes. Above all, the team is not the one moving the file: the applicant is. The team checks, follows up and decides. And it happens for two hundred people at once, across a few weeks, then stops dead until the next intake.

So the useful question is not “which tool has the most features” but “which tool can name what we do”. A piece of software’s vocabulary is its data model; whatever it does not name, somebody will have to hold by hand.

Two vocabularies

Neither column is wrong. They describe two trades, and the second is the one your team practises.

What has to be named	In a sales CRM	In an admissions team
The person	A lead, then a contact attached to a company.	An applicant, and usually a family behind them, writing on their behalf.
The object of the work	An opportunity: an amount and a probability.	A file: required documents, checked one by one, and a reasoned decision.
Time	A pipeline, running all year.	A campaign and an intake: an opening date, a closing date, and a peak in the middle.
Progress	A stage the deal owner moves.	A stage the applicant clears: document uploaded, fee paid, interview attended.
Documents	An attachment on an activity, for the record.	The substance of the file itself: an expected list, a state per document, an approval.
The ending	Won or lost.	Admitted, admitted with conditions, waiting list, rejected, and admitted but never enrolled.
What comes next	Renewal, in the same pipeline.	The registry: the same record, taken over by another office, for several years.

What the team ends up doing instead of the tool

Each workaround is reasonable on its own. Together they are the tool’s real cost, the one that is not on the licence.

Custom fields multiply

Someone creates a box for “transcript received”, another for “fee paid”, another for “interview done”. After one campaign each contact carries a pile of them, ticked by hand. The box records what somebody remembered to tick, not what happened.

The documents live elsewhere

Transcripts go to a drive, personal statements stay in the inbox, copies of ID circulate as attachments. The CRM becomes a log of what was done, not the place the file exists.

The applicant has nowhere to look

With no space of their own, they write to ask where they stand, at the worst point of the campaign, when the team is already under water.

The rules become a job

Someone writes rules so the tool tells the applicant when a stage changes. They hold for a season, then break when a new programme opens or when an applicant has to redo a stage. Someone becomes responsible for maintaining them, and that someone works in admissions.

Payment stays outside

The application fee is not a stage: you link out to an external page, or you wait for a transfer and its proof. Between the family’s decision and the proof arriving, the file does not move, and nobody knows it is waiting.

When a generic tool is enough

None of the above is a failing of the CRM. It does very well what it was designed for, and a corporate-relations team is probably right to use it. The complaint is not about the tool, but about asking it to model a trade it does not know.

There are cases where it is more than enough: one programme, one person holding the whole campaign in their head, a volume that fits in a morning. We say so when we think so. The tipping point comes with the second programme, the second person, and the intake that overlaps the previous one, where the process stops fitting inside one memory.

Four checks, in the tool you already have

No demonstration, no quote. If all four bother you, the gap is no longer a matter of configuration.

Count the custom fields created since the last campaign, and how many of them are ticked by hand.
Open one file at random: how many tools does it take to see its documents, its payment and its interview?
Ask how many “where does my application stand?” messages your team handled last week.
Ask who maintains the sending rules, and what happens while they are on leave.

What to take away

A sales CRM is not a bad tool. It is a tool whose vocabulary does not cover yours. While the gap is small, configuration fills it; when it grows, people fill it, and they fill it every day of the campaign.

An admissions tool starts from the other end: the applicant, the file, the campaign and the intake are objects in it, not fields to create. That is what BrightStep does, and what any seriously chosen dedicated tool does. The point is not the brand: it is that your vocabulary is already in there.

So before changing anything, list the words your team uses and check which ones your tool can write. If it writes them all, keep it: you have just saved yourself a project.