Foundation year programmes face a specific enrollment challenge: the student journey is longer than a standard admission, entry requirements vary more, and a single intake can include students from very different academic backgrounds. Managing that in a spreadsheet quickly becomes unworkable. A CRM built for education teams gives foundation year coordinators a single place to track every enquiry, manage multiple pathways, and follow up at the right time without leads slipping through.
This guide covers how foundation year and pre-university programme teams can structure a CRM to handle their specific enrollment process.
Most foundation year programmes have multiple entry routes: a direct academic pathway, an English language pathway, a conditional offer route, and sometimes a deferred entry option. Each of these should be a stage in your CRM pipeline, not a tag or a note. This lets your team filter by pathway and see at a glance how many students are in each track at any time.
Foundation year enquiries come from varied sources: school counsellors, education agents, parents, direct website enquiries, and open days. Tag the source at contact creation, not just the campaign. This tells you which relationships and channels produce the most enrolled students, not just the most initial enquiries.
A student who enquired via an agent needs different follow-up than one who came direct. Build separate email sequences for each: a shorter one for agent-referred students (since the agent handles much of the communication) and a longer educational one for direct enquiries. Trigger the right sequence automatically based on how the lead was tagged at entry.
Foundation year applications typically require transcripts, English test scores, and sometimes a personal statement or reference. Create a custom property to track which documents have been received for each applicant. Filter your pipeline by document status to see which applicants are stalled on paperwork, and trigger a reminder automatically when a deadline is approaching.
Deferred students are common in foundation year programmes. Add a “Deferred to [intake]” status to your pipeline and create a re-engagement sequence that fires six weeks before their deferred intake opens. Students who deferred and then went quiet are often still intending to enrol — a timely check-in recovers a portion of them that would otherwise not respond until too late.
What makes foundation year enrollment different from standard admissions?
The main differences are a longer decision cycle, a higher proportion of international students, more parental involvement, and more variance in the student’s academic background. A student applying for a foundation year programme is often still deciding whether they want to study abroad, which pathway to take, and what subject area to pursue — none of which is resolved at the enquiry stage. Your CRM process needs to reflect that the journey from first contact to enrolled student involves more touch points and a longer timeline than a standard undergraduate admission.
How should you handle parent and student contacts separately?
In many foundation year enquiries, particularly from Southeast Asia and the Middle East, the parent is the primary decision-maker and the student is a secondary contact. A well-configured CRM creates the student as the primary contact (since they are the applicant) but associates a parent contact to the same deal record. This lets your team track communication with both and ensure neither is missed in follow-up sequences.
In HubSpot, you can link multiple contacts to a single deal using associations — this lets your team view the full household communication in one place. See the parent communication guide for how to structure this effectively.
How do you track agent-referred students without double-handling?
Education agents are a significant source of foundation year students, and their involvement adds complexity: the agent communicates with the student, your team communicates with the agent, and sometimes both communicate with the student in parallel. To avoid confusion, create an “Agent” company record in your CRM and associate it with every student who comes through that agent. This gives you a relationship view — you can see all of an agent’s referred students in one place and report on which agents generate the most enrolled students by programme.
For a more detailed approach to this, see the guide on managing agent referrals in your admissions CRM.
What reports are most useful for a foundation year admissions team?
Three reports give a foundation year coordinator the clearest picture of their pipeline:
- Enquiries by pathway: How many students are on each entry route. Useful for planning staff time and identifying which pathways have the most drop-off between enquiry and offer acceptance.
- Conversion rate by source: Which enquiry sources (direct, agent, school counsellor, open day) convert to enrolled students at the highest rate. This is more useful than enquiry volume alone for understanding where to invest relationship time.
- Document submission status: How many applicants are complete versus waiting on a transcript or test score. This drives the weekly follow-up priority list for your admissions coordinators.
If you are building your reporting setup from scratch, see the CRM reporting guide for admissions teams.
Can the same CRM setup work for a pathway programme within a university?
Yes, with minor adjustments. If your foundation year runs as a pathway programme within a larger university, the main change is linking your admissions pipeline to the university’s intake schedule and destination programmes. Create a custom property for the destination degree the student intends to progress to, and use it in pipeline filtering and reporting. This lets the wider institution see how many students are in the foundation pipeline heading toward each faculty — useful for capacity planning and curriculum coordination.
For multi-programme providers, building a separate pipeline per programme (Foundation Year, Pre-Sessional, Diploma) keeps each funnel clean and measurable independently. See the guide on setting up an admissions pipeline for the structural approach.
FAQ
- Which CRM works well for foundation year admissions teams?
- HubSpot works well because it supports multiple pipelines, custom properties, automated sequences, and contact-deal associations out of the box. It also has a reasonable starting price for smaller teams. For a starting comparison, see enrollment CRM vs spreadsheet.
- How do we handle students who apply to multiple programmes at once?
- Create one deal per programme application. A student applying to both the science foundation and business foundation tracks should have two deal records, one in each pipeline, linked to the same contact. This keeps each application’s progress separate while giving your team a full view of the student’s activity.
- Can we use automation to re-engage students who have gone quiet?
- Yes. Set up an automated sequence triggered when a deal has been in the same pipeline stage for more than a set number of days — for example, 14 days with no logged activity. The sequence sends a check-in message, and if there is no response, a second message a week later. This recovers a portion of students who are still interested but have been slow to reply.
- We work with university partners who need updates on enrolled student numbers. How do we handle that without giving them full CRM access?
- Build a filtered report showing enrolled students by destination programme and export it as a CSV or share a read-only dashboard link. Avoid giving external partners direct CRM access unless you have configured appropriate permission levels. For most partner reporting needs, a scheduled export covers what they actually require.
If you want help setting up a CRM for your foundation year programme, talk to our team about what a setup looks like for your intake size and team structure.
Want to improve your admissions and enrollment process?
Talk to us