12%
Paid customers lost to compliance issues
90+
Countries with unique regulatory frameworks
40+
Document types across the compliance chain
6
Months to build the compliance engine v1
The Problem We Could Not Ignore
In 2022, 12% of students who had paid their fees and received offer letters were not making it to enrolment. Not because they changed their minds — but because the compliance machinery around their applications was failing them. Across 90+ countries, each destination had its own regulatory ecosystem: UKVI rules, CAS issuance requirements, English proficiency mandates, financial thresholds — all of which changed without warning.
The Core Pain
A student would complete their application, receive a conditional offer, pay their deposit, and then fail at the compliance stage — often weeks later — because a document was outdated, a regulation had quietly changed, or a counsellor had used an old checklist. The student blamed Edvoy. The university questioned our process quality. And we had a paid customer who had not received value.
Why Compliance Is a Unique Product Challenge
Compliance is dynamic, multi-layered, and deeply consequential. Getting it wrong means visa refusals, wasted deposits, and institutional reputational damage — not just a bad UX score. We were dealing with four distinct layers:
The four layers of complexity
01
Regulatory dynamism — Government immigration rules change. The UK Home Office updates UKVI compliance requirements. Australia's Department of Home Affairs adjusts the Genuine Student (GS) assessment criteria. Canada's IRCC changes its Student Direct Stream (SDS) requirements. None of these bodies send product teams a changelog.
02
Institutional variance — Every university had its own interpretation of regulatory requirements. Two universities in the same city could have entirely different CAS issuance timelines, different English language cut-offs, and different expectations around gap year justification letters. 750+ institutional partners meant 750+ variations.
03
Document chain complexity — A typical UK student application involved 12–18 documents: passport, academic transcripts, language test scores, personal statement, reference letters, financial evidence, bank statements, property documents, sponsor letters, health certificates, and more. Each document had validity windows, format requirements, and attestation rules.
04
Counsellor knowledge gaps — Our counsellors were excellent relationship managers. But keeping up with regulatory changes across 10+ destination countries was genuinely unreasonable to expect from a human. When a counsellor used an outdated checklist, the student paid the price.
“The student does not know that the UK Home Office updated its financial sufficiency threshold six weeks ago. Neither does our counsellor. But the visa officer does. And that asymmetry is costing us 12% of paid customers.”
Mapping the Impact Beyond Churn
The 12% churn figure was the headline metric, but when we dug deeper, the compliance problem was creating secondary damage across the entire business:
| Impact Area |
The Problem |
Business Consequence |
| Student churn | Compliance failures at late stages of the funnel | 12% of paid customers not reaching enrolment |
| University relationships | CAS revocations and incomplete applications reflecting poorly on Edvoy-referred students | 4 partner universities had raised formal concerns; 2 threatened to delist us |
| Counsellor productivity | Counsellors spending 30-40% of time on compliance-related queries and rework | Capacity to serve new students was constrained |
| Support ticket volume | Students raising tickets post-rejection demanding explanations and refunds | CSAT scores dropping; refund disputes increasing |
| Regulatory exposure | Operating across markets with varying immigration liability | Legal team flagging potential exposure in 3 markets |
| Brand trust | Negative word-of-mouth from students who felt let down | Referral rates from affected cohort dropped to near zero |
How We Framed the Solution
Hiring more compliance people was not scalable. I reframed it: compliance is a knowledge problem, and knowledge problems can be systematised. We built the Compliance Intelligence Engine — five interconnected pillars:
Design Principle
We decided that compliance should be invisible to students and effortless for counsellors. The system should do the knowing, the checking, and the alerting — humans should only make judgment calls on edge cases.
The five pillars of the solution
01
Dynamic compliance knowledge graph — We built a structured knowledge base mapping every destination country, visa category, institution, and programme to its specific compliance requirements. Unlike a static document, this was a living graph with version history. Every requirement had a validity date, a source URL, and an owner responsible for reviewing it on a cadence.
02
Automated document validation pipeline — When a student uploaded documents, our system would validate them against the requirements for their specific application profile: destination country + institution + programme + nationality. Expired documents, wrong formats, missing fields, and attestation failures were caught at upload rather than at the visa stage.
03
Regulatory change monitoring — We built automated monitoring across key government websites (UK Home Office, IRCC, DHA, etc.) and set up alert workflows that notified our compliance team of relevant page changes. This reduced the time between a regulatory change and our system being updated from weeks to 48–72 hours.
04
Counsellor compliance assistant — Every counsellor now had a real-time compliance checklist generated specifically for each student application — not a generic document, but a personalised checklist derived from the student's profile, destination, institution, and visa category. Missing items were flagged in red with explanations and remediation steps.
05
Compliance risk scoring — We introduced a compliance risk score for every active application, visible to both the counsellor and the student. Applications with incomplete or expiring documents showed amber or red scores, triggering proactive outreach before the issue became a problem.
What We Learned
01
The hardest part was not the tech — it was the taxonomy. Before we could build anything, we needed to agree on how to structure compliance knowledge. What is a “requirement”? What is a “document type”? How do we represent conditional logic (“if nationality is X and programme is Y, then document Z is required”)? We spent three weeks just on the data model before writing a line of code.
02
Counsellors needed to trust the system before they would use it. Early versions of the counsellor assistant were ignored because counsellors felt the AI-generated checklists were missing nuance they carried in their heads. We had to build explicit feedback loops where counsellors could flag errors, and we acted on those flags visibly. Trust grew as the system learned.
03
Compliance is a retention problem dressed as a regulatory problem. Once we framed it in revenue terms — 12% churn = significant ARR — we got cross-functional buy-in immediately. Legal, ops, and engineering all moved faster once they saw the commercial case alongside the risk case.
04
Proactive beats reactive, always. Our biggest retention improvement came not from fixing failures faster, but from catching them before they happened. The risk score dashboard alone — which let counsellors see amber and red applications at a glance — changed the counsellor workflow fundamentally.
05
Universities became allies once we had data. When we could show partner universities a compliance dashboard — showing our students' document completion rates and average compliance scores — it changed the conversation. Two of the four universities who had raised concerns became reference partners for our compliance programme.
The Outcomes
Results After 12 Months
The compliance engine was not a silver bullet — it was a 12-month build that required sustained cross-functional effort. But the outcomes were measurable and meaningful.
✓ Compliance-related churn reduced from 12% to under 4%
✓ Counsellor compliance query time down by ~35%
✓ CAS failure rate reduced by 68%
✓ University concern cases resolved; 2 became reference partners
✓ Regulatory update-to-system lag reduced from weeks to 48–72 hours
✓ Document validation catch rate improved to 91% pre-submission
✓ Compliance became a sales differentiator in enterprise partnerships
The Bigger Lesson
Treat compliance as a knowledge and automation problem, not an ops headache. When you systematise it, you create a capability competitors cannot easily replicate, build trust with institutions, and recover revenue that was quietly leaking. At Edvoy, compliance went from the reason students left, to one of the reasons partners chose us.
Archisman Sarkar
Director of Product · Edvoy · Hyderabad, India
me@reacharchisman.com
← Back to Insights