Managed marketplace and workflow
Students receive human support while repeatable work moves through a governed case workflow.
Business and platform architecture
A team-ready view of the business, the platform and every hand-off from first enquiry to verified enrolment.
The business in one view
People remain accountable for guidance and quality. Technology coordinates evidence, decisions, deadlines and hand-offs.
Students receive human support while repeatable work moves through a governed case workflow.
Material restrictions, cost and missing evidence appear before a student commits money.
Students, staff and partners work from the same versioned facts, tasks and decisions.
Verified suitable enrolments with consent, lawful permission, cost fit and evidenced commencement.
Why this opportunity exists
Search, selection, applications, funding, immigration support and enrolment are often split across people, portals and spreadsheets.
UNESCO mobility contextThe end-to-end service
Each stage has an owner, required evidence and a decision before the next stage unlocks.
Confirm the service scope, lawful data use and the basic route facts.
Classify the route as open, conditional, restricted or manual review.
Link student-approved facts to source evidence and unresolved gaps.
Compare eligibility, academic fit, real cost and commercial disclosure.
Create programme-specific tasks, documents, owners and deadlines.
Review the exact package independently before the student approves it.
Record confirmation, requests, corrections and evidence-backed status.
Verify the original decision, every condition, owner and deadline.
Show full cost, funding gaps and assumptions before commitment.
Use current official guidance and authorised professional referrals.
Protect payment routing, fee visibility, travel and arrival planning.
Confirm safe arrival, registration and evidenced commencement.
Capture support, quality signals and consented alumni participation.
Two sides of one case
The same evidence and case state appear differently for each authorised role.
One prioritised next action, visible reasons, real cost, consent controls and ownership of every submission.
Open the student journey
Queues ordered by risk, deadlines and evidence, with independent QA and controlled permissions.
Open the staff journey
The platform and cloud
Start with one region and low fixed cost, then add infrastructure only when scale, recovery or contracts require it.
GitHub Actions uses temporary AWS roles. Production and non-production remain separate.
Least privilege, encrypted documents, malware scans, retention and incident readiness come first.
Roadmap and economics
The recommended build remains a planning envelope. A concierge pilot should prove demand, quality and operating capacity first.
Review the detailed briefingBring the team into the journey
Use the briefing for alignment and the prototype for a live student and staff walkthrough.