Solution · Education & training providers
Admissions, enrolment changes and student cases by the procedure
An admissions decision waits on a document nobody asked for. An enrolment change is processed outside the deadline rule. A student complaint skips a stage. Ovenbird gives administrators the documented next step on each case, with the deadline.
Reads the documents you already have. Writes to no customer. One afternoon to set up.
Sounds familiar?
- Cases bounce between officesAdmissions, finance and the programme each do their part when it reaches them.
- Deadlines applied inconsistentlyExceptions granted by whoever is asked.
- Term-start staff start coldTemporary administrators learn the procedure during the peak.
The procedures you already have
- Admissions and enrolmentWhat an application needs, who decides, when the applicant is told what.
- Enrolment changes and withdrawalsDeadlines, refunds, who approves, what the student must be told.
- Student support casesWhen a concern escalates, to whom, with what record.
- Course and programme approvalsThe steps a new course passes, in order, with the evidence each committee needs.
What changes
- AdmissionsTodayApplicants are told different things by different officers.With OvenbirdWhat an application needs, who decides, when the applicant is told what.
- Withdrawals and changesTodayRefund rules are applied inconsistently around deadlines.With OvenbirdThe rule for day 20 of term, the approver, the confirmation content — quoted from the policy.
- Student supportTodayConcerns reach the wrong office.With OvenbirdWhen a concern escalates, to whom, with what record.
- Course approvalsTodayProposals circle committees for missing evidence.With OvenbirdThe steps in order and the evidence each committee needs.
- Across all fourOfficers trained on policies before term starts, refreshed when policies change; registry sees who holds which procedure; policy pages corrected from real cases.
How it works
- 1
Point it at the documents you have
Confluence, Google Docs, Notion or a web page. No rewriting; Ovenbird reads the live version and shows which one it followed.
- 2
People ask on the work in front of them
In Slack, on the web or from the record: the one next step, the fact it depends on asked first, the paragraph quoted.
- 3
Corrections and training come from the same page
Every "this is wrong" becomes a proposed edit. Every procedure becomes a short course with refreshers and records.
Built for
- Registrar or head of student servicesCases decided by procedure, measurable.
- Admissions managerDecisions made with complete files, first time.
- Programme administratorsClear next steps on every case, no chasing.
What a pilot measures
- Cases escalated incorrectlyConcerns sent to the wrong office.
- Deadline exceptionsChanges processed outside the published rules.
- Time to first unaided termWeeks before a new officer handles cases alone.
Agreed before the pilot. Reported after 90 days, before and after.
Questions buyers ask
Does it make decisions?
No. It tells the administrator what the procedure requires next and who decides. Decisions stay with people.
Our procedures differ per programme.
If the document branches by programme, it follows that branch and asks which applies.
Can it help train term-start staff?
Yes. Each procedure becomes a short course with scenarios from the document, and a record of who is trained.
See it on one of your own documents
Paste a link to a procedure. The next step and the course exist the same minute.