{"id":17812,"date":"2026-04-11T03:14:42","date_gmt":"2026-04-11T03:14:42","guid":{"rendered":"https:\/\/www.educli.com\/resources\/?p=17812"},"modified":"2026-04-11T03:14:44","modified_gmt":"2026-04-11T03:14:44","slug":"built-to-run-newsletter-issue-3","status":"publish","type":"post","link":"https:\/\/www.educli.com\/resources\/built-to-run-newsletter-issue-3\/","title":{"rendered":"Built to RUN newsletter – Issue 3"},"content":{"rendered":"\n
\n\n \n
\n
\n Migration Agents<\/span>\n Built to RUN \u00b7 Issue 3<\/span>\n April 2026<\/span>\n <\/div>\n

Two Weeks of Signals. Here’s What They Add Up To.<\/h1>\n

Student visa grants at an eight-year low. Commission flows reversing. AI entering the practice. And a framework for reading all of it the same way.<\/p>\n <\/div>\n\n \n

\n

Jan Karel Bejcek<\/p>\n

Founder, Educli  \u00b7  Published in Built to RUN<\/p>\n <\/div>\n\n \n

Welcome back to Built to RUN.<\/p>\n

The past two weeks have produced more material for migration agents to absorb than most quarters. New data. Commission changes. Regulatory shifts. AI tools landing in practice management conversations. Each topic generates its own noise. This issue pulls the threads together \u2014 what the signals mean, why they connect, and where to look next.<\/p>\n\n \n

\n

The Data Picture Is Clarifying \u2014 and It Isn’t Good<\/h2>\n <\/div>\n\n \n
\n
\n

67.6%<\/p>\n

Higher Ed offshore
grant rate \u2014 8-yr low<\/p>\n <\/div>\n

\n

60%<\/p>\n

India
grant rate<\/p>\n <\/div>\n

\n

35%<\/p>\n

Nepal
grant rate<\/p>\n <\/div>\n

\n

62%<\/p>\n

Sri Lanka
(was 98% \u2014 12 months prior)<\/p>\n <\/div>\n <\/div>\n\n

The February 2026 student visa grant data landed with some of the clearest numbers we’ve seen in several years. Overall offshore grant rate for higher education: 67.6%. An eight-year low. Not a dip \u2014 a structural shift that has been building since the Genuine Student requirement replaced GTE in 2024 and the Evidence Level changes took effect in January 2026.<\/p>\n\n

Sri Lanka’s 36-point collapse in a single year is the data point that stops most agents mid-sentence. India at 60%. Nepal at 35%. Bangladesh at 49%. These aren’t marginal movements.<\/p>\n\n

The headline grant rate improvement (83.1% across all visa types in FY2024\u201325) is real \u2014 but it sits on a contracting application base. Applications fell 14% in FY2024\u201325, after falling 21% the year before. A rising rate on shrinking volume still means fewer grants in absolute terms. For agents whose practice includes student visa work from South Asian or Sri Lankan markets \u2014 this is the operating environment now, not an aberration.<\/p>\n\n

Full February 2026 grant rate analysis \u2192<\/a><\/p>\n\n \n

\n

The Commission Flow Is Reversing<\/h2>\n <\/div>\n\n
\n

The liability gap:<\/strong> When a student visa is refused, a refund is owed. Under TPS, the obligation sits with the registered provider \u2014 not the agent. But when offshore agents collected the fees and didn’t pay refunds, providers carried a debt they never held the money for.<\/p>\n <\/div>\n\n

Colleges are sending emails. The message: fees must now be paid directly to the provider in full. Agents who previously collected student fees \u2014 taking commission off the top, remitting the balance \u2014 are being cut out of that flow.<\/p>\n\n

The providers sending those emails have almost certainly already been burned. The structural change is a direct response to a liability problem that was predictable but not widely acknowledged until refunds went unpaid.<\/p>\n\n

The ESOS Act’s commission reporting provisions are moving in the same direction \u2014 toward providers having visibility and control over fee flows and agent arrangements. For migration agents involved in student recruitment: if your agent agreements and fee arrangements were built around the old model, they need reviewing.<\/p>\n\n

Commission reversal and TPS liability analysis \u2192<\/a>   ESOS commission reporting framework \u2192<\/a><\/p>\n\n \n

\n

Processing Times: A Reminder That Matters More Than It Looks<\/h2>\n <\/div>\n\n

The Department of Home Affairs updated its processing time guidance. The headline reminder: processing times are not guarantees. This is technically routine. In practice it’s a prompt for a conversation most agents are having with clients too late.<\/p>\n\n

\n

The median processing time is not a promise. It’s a midpoint in a distribution. Clients who see “75 days” and call on day 76 are operating on a misunderstanding the agent was positioned to address from the start.<\/p>\n <\/blockquote>\n\n

In a tighter scrutiny environment where requests for information are more frequent and processing is slower across high-scrutiny markets, client expectation management has become a practice management discipline in its own right.<\/p>\n\n

Processing times and expectation management \u2192<\/a><\/p>\n\n \n

\n

AI in Practice: Where the Conversation Has Landed<\/h2>\n <\/div>\n\n

Two things happened in the past two weeks worth naming together.<\/p>\n\n

The EU AI Act’s first major enforcement action landed \u2014 a \u20ac35 million fine for a provider that built fast and governed late. The compliance gap between “we deployed an AI tool” and “we can demonstrate how it performs and what it decides” is where regulators are heading.<\/p>\n\n

At the same time, migration agents are increasingly being pitched AI tools for inquiry handling, document drafting, and client communication. Some are genuinely useful. Some aren’t.<\/p>\n\n

\n

The distinction that matters for MARA agents<\/p>\n

Any AI tool you deploy in your practice interacts with clients and influences advice. Your Code of Conduct obligations \u2014 including advice traceability and the requirement to give accurate, complete advice \u2014 don’t stop at the point where the AI starts. The agents most exposed won’t be those using AI badly. They’ll be those who couldn’t demonstrate oversight when something went wrong.<\/p>\n <\/div>\n\n

AI in migration practice \u2014 where it helps and where it doesn’t \u2192<\/a><\/p>\n\n \n

\n

The RUN Framework: Why These Signals Connect<\/h2>\n <\/div>\n\n

Grant rate shifts. Commission reversals. Processing time dynamics. AI compliance exposure. These look like separate topics. They aren’t.<\/p>\n\n

Each one is a variation of the same underlying question: is your practice built to absorb change, or does each change require you to scramble?<\/p>\n\n

\n
\n

Regulatory<\/p>\n

Compliance obligations are documented and triggered automatically \u2014 not recalled from memory when something changes.<\/p>\n <\/div>\n

\n

Unified<\/p>\n

Every client record, communication, and decision sits in one place. One system change updates every case it touches.<\/p>\n <\/div>\n

\n

Navigable<\/p>\n

Active cases, deadlines, risk concentration \u2014 visible at any moment without reconstructing it.<\/p>\n <\/div>\n <\/div>\n\n

A practice with those three properties handles a grant rate collapse, a commission flow reversal, and a new AI compliance question by updating its processes. A practice without them handles each one as a crisis.<\/p>\n\n \n

\n

A note on where Educli is<\/p>\n

A few of you have asked how the platform is developing. The core case management and workflow modules are live. The compliance architecture \u2014 file notes, evidence trails, deadline tracking \u2014 is the foundation everything else is built on.<\/p>\n

What’s coming: a practice diagnostic tool that places every agent on the RUN\u2122 maturity scale across five dimensions, produces a personalised gap report, and tracks progression over time. The working name is the Practice Maturity Index (PMI)<\/strong>. I’ll cover it properly in the next issue once it’s live \u2014 it’s the most direct translation of the RUN framework into something you can act on immediately.<\/p>\n See the platform \u2192<\/a>\n <\/div>\n\n \n

\n

Further reading<\/p>\n