The record that answers for you
The email arrives on a Tuesday. It is polite, it is short, and it is from the partnerships officer at a university you have worked with for four years. They are carrying out their annual agent review, and they would like to see how you supervise your counsellors and your sub-agents. They have attached a form. They would like it back within ten working days.
Nothing in that email is hostile. The officer is not accusing you of anything. They are doing a job that their own compliance team has handed them, and they will send the same email to every agent on their list. The difference between the agents is not who behaves well. It is who can produce the evidence inside ten working days, and who spends those ten days reconstructing it from memory, from four phones, and from a Drive folder nobody has opened since March.
This post is about what that evidence actually is, why the usual setup cannot produce it, and what a system has to do to produce it on demand. It is about Casly, specifically, because the answer is not a tidier spreadsheet.
What changed, and when
Since April 2026, UK Home Office sponsor guidance requires sponsors to retain evidence of how they oversee their education agents. That obligation sits on the sponsor, but it does not stay there. A sponsor who must evidence oversight has only one way to do it, which is to ask the agent for records. The agent who cannot produce records becomes the agent who is quietly dropped at the next review.
The framework behind this is the Agent Quality Framework and the National Code of Ethical Practice for UK Education Agents. Universities now assess agents against National Code standards as part of annual review. And the pressure behind all of it is numerical: sponsors must hold student visa refusal rates below five per cent, down from ten.
For a consultancy recruiting from Pakistan, those numbers are not abstract. Refusal rates for Pakistani applicants ran at roughly 18 to 19 per cent for the year to June 2026, but at around 39 per cent across the first two quarters of 2026, and more than 40 per cent of applications were withdrawn in the first half of the year against about 3 per cent a year earlier. Around fifteen UK universities suspended Pakistani recruitment outright.
The consultancy's risk is no longer disorganisation. It is being unable to answer a question that arrives by email, with a deadline, from the partner who pays you.
These figures move, and they vary by how each body counts. Check them against the primary source before you quote them to anybody. The direction, however, is not in dispute, and it has one practical consequence: the record you keep has stopped being an internal convenience and become the thing your partnerships depend on.
What "evidence of oversight" actually means
The phrase sounds vague until you break it into the questions a reviewer will actually ask. They are not sophisticated questions. That is what makes them dangerous.
Who advised this student, and what were they told?
Not a summary written afterwards. The advice itself. Which course was recommended and on what basis, what the student was told about their chances, what was said about tuition, living costs and the funds they would need to show. When a student complains eight months later that they were promised something, this is the only record that settles it, and a counsellor's recollection is not a record.
Which documents were checked, by whom, and when?
A folder containing a passport scan proves that a passport scan exists. It does not prove that somebody looked at it, noticed the expiry date, compared the name spelling against the transcript, or flagged that the bank statement was eleven days outside the required window. The reviewer is asking about the checking, not the storing.
What did you promise, and what were you paid?
The fee agreement the student signed, the version of it that was in force when they signed, what was invoiced, what was received, and what commission you expected from the institution. Conflicts of interest sit here: a reviewer wants to see that the student was told how you are paid.
How do you supervise your sub-agents?
This is the question that catches most firms. A Freedom of Information response from UEA sets the position plainly: oversight of sub-agents is left to the contracted agent. The university is not supervising the small office in another city that sends you students. You are. And you are expected to show how.
What happened to the cases that went wrong?
Refusals, withdrawals, complaints. Not just the count, but what was done about each one. A firm that can show it reviewed its refusals and changed something is a firm a partner can defend internally. A firm that cannot show its refusals at all is a line item in somebody's risk report.
Why the usual setup cannot answer
Almost every consultancy under fifty staff runs on the same four things: WhatsApp on counsellors' personal phones, a shared spreadsheet, a Drive or Dropbox folder per student, and email. Each of those is good at something. None of them is a record.
WhatsApp on a personal phone is not your record, it is your counsellor's. It leaves when they leave. It cannot be searched by you. It cannot be exported by you. It contains, somewhere, the only evidence of what was promised to a student who is now unhappy, and you cannot reach it.
A spreadsheet is a photograph of now. It holds the current value of every cell and no memory of the previous one. Ask it what the fee was in March, or who changed the stage from "documents pending" to "submitted", and it has nothing to say. Disputes are always about then, and a spreadsheet only knows about now.
A Drive folder has no state. A file is either there or not there. It cannot tell you that the police certificate expires in six weeks, that the English test result was never verified, or that three of the eleven documents this country requires were never requested in the first place.
Email is a filing cabinet with no index. The information exists. Finding all of it for one student, across four counsellors' mailboxes, inside ten working days, is the work you were hoping to avoid.
None of this is carelessness. Every one of those tools was chosen because it was the fastest way to do the thing in front of you. The cost only appears when somebody asks a question that spans all four.
What Casly does about it
Casly was built for this shape of business, which is why the audit trail is not a feature bolted on the side. It is a consequence of how the record is put together. Here is each piece, and the question it answers.
One timeline per client, not per channel
Every message, from every channel, lands on the client's file. WhatsApp, Instagram DMs, Facebook, website forms, email and Meta lead ads all arrive in the same inbox and attach to the same person. The conversation is not a copy of what happened on somebody's phone. It is the original, held by the firm.
That single decision answers the first reviewer question on its own. "What was this student told" stops being an act of archaeology and becomes a page you scroll.
It also means the record survives staffing. When a counsellor leaves, their cases stay, tagged to them and reassignable one at a time. The history does not walk out of the building.
The activity log
Separate from the conversation is the log of what was done: who opened the case, who changed the stage and when, who edited the fee, who uploaded or replaced a document, who sent the contract, who exported a report. Every write path in the system records an action.
This is the difference between a system that stores your work and a system that can account for it. "Who changed this, and when" is a question a spreadsheet can never answer and an audit will always ask.
Documents as a checklist with state
A document in Casly is not a file in a folder. It is an item on a country-specific checklist with a status: requested, received, verified, expired, rejected. The checklist fills itself as attachments arrive, so the gap between "eleven documents required" and "seven documents present" is visible at a glance rather than discovered by counting.
Expiry is tracked as a date that can arrive, not a fact buried in a scan. A passport that expires inside the course duration, a police certificate that will be out of date by the submission window, an English test result approaching its validity limit: each surfaces before it becomes a refusal rather than after.
For the sub-five-per-cent problem, this is the practical lever. Most refusals in this market are not sophisticated. They are incomplete financial evidence, documents outside their valid window, or inconsistencies between documents that nobody compared. A checklist that will not call a case ready while items are missing does not guarantee an approval, but it stops you submitting the cases that were never going to succeed.
Contracts and e-signature
The fee agreement is generated from the client's record, sent, signed electronically and stored against the case with the signature, the timestamp and the version that was signed. When the student says they were quoted differently, the document that settles it is one click away and carries its own proof of when it was agreed.
This is one of the three capabilities that competitors in this niche generally do not have. AgentCIS, LeadSquared and Relently all leave e-signature to a separate tool, which means the signed contract lives outside the record of the case it belongs to.
The sub-agent portal
Sub-agents do not get your password and they do not get a WhatsApp group. They get their own portal, where they submit students, see the stage of the cases they referred, upload documents, and see their commission position. You see every case they submit, every document they upload, and every action they take, in the same activity log as your own staff.
That is what "we supervise our sub-agents" looks like as evidence rather than as a sentence in a form. You can show a reviewer which sub-agent submitted which case, what they were told about fees, what documents they provided and when, and what they were paid.
Commission, including the part nobody models
Commission is tracked per case against the institution and the agreed rate, with clawbacks. Clawbacks matter here because they are where the money and the compliance story meet: a student who withdraws after enrolment reverses a commission, and a firm whose books do not model that is carrying revenue it will have to give back. With withdrawals running above forty per cent in some cohorts, that is not an edge case.
Reports you can hand over
The questions a reviewer asks map to reports: cases by stage, cases by sub-agent, refusals and withdrawals by period and by country, document completion rates, commission by institution. Exports are gated and logged, so you also know who produced which report and when.
Company-wide money is visible only to the CEO. Per-client balances are visible only to the counsellor the case is assigned to. Client-facing pages carry no money at all, by design, so a student opening their portal link sees their application and never an invoice. These are not settings somebody can quietly change: the restrictions are enforced in the database as well as the interface.
The dry run
The useful way to test any of this is to behave as though the email has already arrived. Pick one student from last year, one who was refused, and try to answer these without asking a colleague:
- Who advised them, and what did that person tell them about their chances?
- What fee were they quoted, in writing, and on what date?
- Which documents did you check, and which did you merely receive?
- Was any part of this case handled by a sub-agent, and what did that sub-agent tell the student?
- What was invoiced, what was received, and what is still owed?
- Why was the case refused, and what did you change afterwards?
- If the counsellor who handled it has left, how much of the above is still reachable?
If three of those take more than a few minutes, the gap is not in your diligence. It is in where your work is stored. Ten working days sounds generous until you are reassembling four years of it.
What a defensible file looks like, line by line
It helps to stop talking about systems and look at one case. Here is what sits on a single student's record in Casly by the time their visa decision arrives, and what each part is for.
The person, not the enquiry. One record for the student across their whole journey, including the parts that earn nothing. The enquiry they made two years ago and did not act on. The refusal and the reapplication, which are the same person with history, not two leads. The sibling who comes to you later, on the same family record. A reviewer asking about a repeat applicant wants to see that you knew they were a repeat applicant.
The source. Which channel the enquiry arrived on, which campaign or referrer sent them, and whether a sub-agent was involved. This is the field most firms skip and the one that answers both the marketing question and the oversight question.
The advice, as it was given. The conversation itself, in the client's timeline, with dates. Not a counsellor's summary. The messages.
The stage, and whose desk it is on. Waiting on the student is a different problem from waiting on a university, which is different again from waiting on an embassy. The first you chase, the second you escalate, the third you prepare for. A stage that cannot tell you which of the three you are in is a progress bar, not a record.
The document set, with status and dates. Required, requested, received, verified, expiring on a date. Country-specific, because the set changes by destination.
The deadlines, each with a name against it. Intake close, offer acceptance window, deposit date, visa application window. Separate the deadlines you set from the deadlines set for you: missing your own follow-up costs a conversation, missing a university's acceptance window costs the student a year.
The agreement. The signed fee contract, the version signed, the date, and the signature.
The money, at the stage it was earned. What was invoiced, what was received, what the student still owes, and what the institution still owes you. The last of those is the column most firms cannot produce on demand, and it is usually the largest.
The actions. Every change, with a person and a timestamp.
Nothing in that list is exotic. The point is that all of it sits on one record rather than across four tools, which is the only reason it can be produced as an answer rather than assembled as a project.
Moving what you already have
The honest objection to all of this is not "we disagree". It is "we have four years of history in a spreadsheet and three thousand WhatsApp threads, and we are in the middle of an intake".
Two mistakes make that objection true. The first is trying to move everything. The second is trying to move it all at once.
Move active cases only. Whatever is live right now goes into the system. Everything closed stays in the spreadsheet, which becomes a read-only archive you keep. You are not deleting history; you are deciding that history does not have to be migrated for the new record to start being complete.
Start where it hurts. For most firms that is either lead capture, because enquiries are visibly leaking, or document checklists, because a refusal just landed. Pick one. The rest of the system does not have to be switched on the same week.
Draw the line on a date. From Monday, every new enquiry arrives in the system and every conversation happens there. Counsellors keep answering on WhatsApp, because the business WhatsApp number connects to the shared inbox, so what changes for them is where they type, not how they work.
Accept that old cases have thin records. A case you migrated will have less history than one that started in the system, and that is fine. A reviewer looking at a four-year-old file expects less than they expect of last month's. What matters is that the line is drawn and that everything after it is complete.
The firms that stall are the ones who treat this as a data project with a go-live date. The firms that succeed treat it as a change of address: new post goes to the new place from today, and the old filing cabinet stays in the corner.
What software cannot do
It is worth being plain about the limits, because the market around this is not.
No system changes a visa decision. A refusal is made by an officer applying rules to a case, and the best record in the world does not alter the facts of that case. What a record does is stop you submitting cases that were never ready, and let you learn from the ones that failed.
No system makes you compliant. Compliance is a set of obligations that sit with your firm, and a tool is evidence, not absolution. Casly can show what was done. It cannot decide what should have been done.
No system replaces judgement about who to take on. The firm that accepts every applicant with a weak financial profile will have a refusal rate that reflects that, whatever software it runs.
And the regulatory detail in this post should be checked against the Home Office guidance, the Agent Quality Framework and the National Code themselves before you rely on it. They are updated, and a blog post is not a primary source.
Why this is the argument that matters now
For years the pitch for software in this sector was efficiency: do the same work with fewer hours. That argument is true and it has never been very persuasive, because the owner comparing a spreadsheet to a subscription can always decide to work a bit harder.
The argument has changed. The record is now the thing that keeps your university partnerships, and partnerships are the business. A firm that loses two partners because it could not evidence oversight has not become less efficient. It has lost the product.
That is the whole case for building the file properly: not so the office feels tidier, but so that when the polite email arrives on a Tuesday, the answer takes an afternoon instead of ten days, and the answer is the truth.
Common questions
What evidence of agent oversight do UK universities actually ask for?
In practice: who advised the student and what they were told, which documents were checked and when, the signed fee agreement and what was invoiced, how any sub-agents were supervised, and what happened to the cases that were refused or withdrawn. Check the Agent Quality Framework and the National Code for the authoritative list.
Am I responsible for my sub-agents?
Yes. A Freedom of Information response from UEA sets out that oversight of sub-agents is left to the contracted agent. The university is not supervising the office that sends you students; you are, and you are expected to show how.
Can software keep my refusal rate under five per cent?
No system changes a visa decision. What it changes is which cases you submit. Most refusals in this market come from incomplete financial evidence, documents outside their valid window, or inconsistencies nobody compared, and a checklist that will not call a case ready while items are missing catches those before submission.
We keep everything in WhatsApp and Drive. Is that not a record?
Not one you control. WhatsApp on a personal phone leaves when the counsellor does, a spreadsheet holds only the current value of every cell with no memory of the previous one, and a Drive folder can tell you a file exists but not that anybody checked it.
How long does it take to move to a system like this?
Move active cases only and keep the old spreadsheet as a read-only archive. Draw a line on a date, start with whichever part hurts most, and accept that migrated cases will have thinner records than ones that began in the system.
Build the file once, answer any time
One timeline, a document checklist with dates, and an activity log behind every case.
Start free