Mojo the Registrar

reads your programme pages · A university's team

Arrives when your team is set up

The challenge

Everything downstream of your entry requirements depends on them being right — who applies, who is rejected, what a student is told about their chances. And most institutions do not have one version of them. They have a PDF, a website, a prospectus and one administrator's memory, updated at different times by different people. As more of this gets read by machines rather than humans, the cost of that drift stops being cosmetic. Every student who applies against the wrong version is a rejection that wasted both of you.

What it does about it

Now imagine your requirements existing correctly in one place, and every student encountering that version. The Registrar reads what you have already published, writes them out cleanly, and hands them to your team to check. One confirmation, not a data project.

How it works

It reads the requirements you have already published — subjects, grades, English levels, deadlines — and writes them out in a form the rest of the system can read, for your team to check. Nothing goes live until a person on your side says so, and once confirmed it becomes the version every student is answered against.

What you get

One correct version of your requirements, confirmed by your own team, in every place a student encounters them. What your team confirms becomes the rules a student's own Admissions Analyst applies, which is how a correct requirement reaches every student at once.