When prospective students contact dBs Institute of Music, they aren't thinking about franchise partnerships, governance structures, or regulatory oversight. 

They're thinking about their future. 

They're wondering whether they've chosen the right course, whether they'll fit in, and what happens next in the application process. They want answers, reassurance, and confidence that they're making the right decision. 

As Head of Admissions at dBs Institute of Music, I've always felt that if an applicant is confused about who to contact, receives conflicting information, or feels passed between organisations, we've already created unnecessary friction in their journey. 

That belief has shaped much of the work we've done over the past few years as we've continued to develop our partnership with Falmouth University. 

Like many higher education partnerships, the reality behind the scenes is complex. There are multiple systems, shared responsibilities, quality assurance requirements, and governance processes that ensure students receive a high-quality experience and outcome. 

But applicants shouldn't have to navigate any of that complexity. 

One phrase has become something of a guiding principle for us: 

One journey, two systems, one applicant. 

It sounds simple but achieving it requires constant focus. 

A few years ago, we took a step back and looked critically at the applicant journey. Operationally, our processes worked, but we asked ourselves an important question: what does this actually feel like for the applicant? 

The answer wasn't always as positive as we wanted it to be. 

Like many partnership models, there were points where responsibilities overlapped, communications could feel disconnected, and applicants weren't always certain who they should contact. Nothing was fundamentally broken, but we recognised opportunities to create a more joined-up and intuitive experience. 

What I've learned through this process is that applicant experience and operational design are inseparable. Every internal handoff, every unclear ownership point, and every process designed around organisational convenience rather than student needs eventually becomes visible to the applicant. 

That's why one of the most important changes we made was establishing clearer ownership of the applicant relationship. 

The introduction of a dedicated UCAS provider code for dBs was a significant milestone. While it delivered obvious operational benefits through greater visibility of applicant data and more direct control of admissions activity, its real value was what it enabled us to do for applicants. 

It allowed us to communicate more effectively, respond more quickly, and build stronger relationships throughout the admissions journey. 

Today, applicants engage directly with the dBs admissions team from enquiry through to enrolment. Behind the scenes, we continue to work closely with colleagues at Falmouth University, whose support, expertise, and oversight remain fundamental to the partnership. However, from the applicant's perspective, the experience feels far more consistent and personal. 

At a time when higher education partnerships are receiving increased attention from regulators and policymakers, there is naturally a strong focus on compliance, governance, and accountability. Those things matter, and they should. 

But alongside those discussions, I believe we need to keep talking about applicant experience. 

Because successful partnerships aren't defined by how responsibilities are divided. They're defined by how effectively organisations come together around a shared purpose. 

For us, that purpose is simple: helping applicants feel informed, supported, and confident throughout their journey. 

Looking back, that's probably the biggest lesson I've learned. Applicants don't see governance frameworks, systems integrations, or organisational structures. 

They simply experience the journey. 

And if we've done our job well, that's exactly how it should be.