Which Admissions Tasks to Automate with AI: Full Inventory

What this inventory is for

This is a one-off strategic exercise, not a live escalation script. Before you configure a single chatbot flow, your admissions leadership team needs a written decision on which of the roughly dozen recurring tasks in your recruitment cycle are safe to hand to AI, which need AI drafting plus human sign-off, and which must never leave a human's desk.

Most institutions skip this step and default to instinct — "fees are fine to automate, interviews obviously aren't" — which fails badly at the edges: borderline ATAR-based offers, disability accommodation requests, hesitant offer-holders comparing you against a Group of Eight competitor. This article gives you a repeatable framework and a completed grid to adapt to your own institution.

It sits upstream of two related pieces from our AI Chatbot & Student Recruitment Guide: Automate Student Recruitment Without Losing the Human Touch covers the overall philosophy, and AI Chatbot vs Human Agent: When Should Schools Hand Off? covers real-time escalation triggers. This one is the audit you run once, before either matters.

The four-criteria framework for classifying any admissions task

A task belongs in one of three buckets — AI-safe, AI-plus-human-review, or human-only — depending on how it scores against four independent criteria. No single criterion decides the classification; a task can score high on volume but still land in human-only if the legal risk is severe enough.

1. Volume and repetitiveness. How often does this task recur, and how similar is each instance to the last? High-volume, low-variance tasks — the same tuition question asked five hundred times during change-of-preference week — are exactly what automation exists to absorb. Low-volume, highly variable tasks gain little from automation and often lose accuracy trying.

2. Rule-based vs judgment-based. Can the task be resolved by applying a fixed set of rules to known inputs, or does it require weighing competing, ambiguous factors? A HECS-HELP eligibility lookup is rule-based. Deciding whether a mediocre personal statement reflects genuine potential is judgment-based, and no amount of training data changes that.

3. Emotional or relational stakes. Does the task involve a moment the applicant will remember — good or bad — or is it purely transactional? Confirming a document was received is transactional. Telling someone their ATAR fell short, or that their scholarship application was declined, is relational, and it needs a human voice even when the underlying decision was rule-based.

4. Reversibility and legal risk if wrong. If AI gets this task wrong, can you catch and fix it before harm occurs, or is the damage done the moment the message sends? An FAQ answer that's slightly off gets corrected in the next message. A wrong offer/reject decision, a mishandled disability disclosure, or an appeal response that skips a statutory step carries reputational and TEQSA compliance exposure that a follow-up message cannot undo.

Score each task against all four, and the classification tends to fall out on its own: high volume, rule-based, low stakes, reversible leads to AI-safe. Anything with high emotional stakes or high legal risk pulls a task toward human-only regardless of how repetitive it looks on paper.

The full task-by-task decision grid

The table below applies the framework to twelve tasks that recur across almost every Australian higher education admissions cycle, from first enquiry through to enrolment.

Three tasks in that table need a short note, because they are where admissions directors most often get the classification wrong.

Following up incomplete applications looks purely mechanical — send a reminder, list what's missing — but the tone matters more than it seems. An applicant one transcript away from a complete file responds differently to a templated nudge than to a message that acknowledges where they are, particularly during UAC, VTAC or QTAC peak periods. AI can draft and send routine reminders; a human should step in once an applicant has missed two, which is the repeated-failure signal covered in our handoff triggers guide. Day-to-day slot booking and reminder flows are covered in our guide to chatbot scenarios that increase enrolment.

Negotiating with hesitant offer-holders is not a single task but a category of moments — an applicant comparing your offer against a Group of Eight university, a parent asking about HECS-HELP versus FEE-HELP repayment, a student who has gone quiet after an unconditional offer. AI can surface the signal (repeat page visits, a drop in email opens, a mention of a rival institution) and draft a first response, but the actual negotiation — extending a deadline, discussing a scholarship top-up, addressing an objection — belongs to a human who can adapt in real time.

Handoff to current-student ambassadors is rule-based in its trigger (a prospect asks "what's campus life actually like") but the value is entirely relational once the handoff happens. AI should identify the right moment and the right ambassador match; it should never attempt to simulate the peer conversation itself.

Why the 72-21-7 split matches this grid almost exactly

The proportions in this grid are not arbitrary — they mirror what actually happens in prospect conversations at scale. Automated classification of 12,000 Skolbot conversations found that 72% of prospective student questions are simple FAQs answerable with no school-specific context, 21% need some institutional context, and only 7% genuinely require a human (Skolbot, automatic classification of 12,000 conversations, 2025). The AI-safe row in the grid — fees, programs, logistics, slot scheduling — sits squarely inside that 72%. The AI + human review row corresponds closely to the 21% that needs context but not necessarily judgment. The human-only row is a subset of the 7%, but a consequential one: it's where volume is lowest and stakes are highest.

That distribution is echoed in broader sector commentary. Analysts at McKinsey Education and Gartner covering AI adoption in education draw the same line: automation gains are largest in high-volume, low-judgment interactions, while decisions with material consequence for an individual applicant remain a governance concern, not just an efficiency one. Forrester research on customer-facing AI reaches a similar conclusion outside education — AI performs best where errors are cheap to detect and correct, and worst where a wrong output is a one-shot, high-stakes event. EDUCAUSE research on generative AI in higher education adds a caution relevant here: institutions that automate without a documented classification process drift toward over-automating exactly the tasks where students need a human response.

Why running this inventory changes what your team actually does

Running this exercise once, in writing, changes how your team spends its week — not by removing tasks from human hands, but by making the remaining human tasks the ones that actually need a person. Institutions that hand the AI-safe row to a chatbot see prospects return to explore further: 34% of prospects return to the institution's website within 7 days of a chatbot interaction, compared with 12% without one — a 2.8x difference (Skolbot, cohort analysis of 8,000 sessions over 90 days, 2025). That reengagement comes from removing friction in the transactional 72%, not from pushing AI into the human-only rows.

The grid is also a governance artefact, not just an efficiency plan. Written classifications matter if TEQSA, an internal audit, or a prospective student ever asks how your institution decided which applicant-facing decisions involve automated processing. The Office of the Australian Information Commissioner (OAIC) is explicit under the Privacy Act 1988 and the Australian Privacy Principles that automated handling of personal information needs a documented purpose and human oversight where the outcome affects an individual materially — an offer, a reject, or an accommodation decision plausibly qualifies. TEQSA's Higher Education Standards Framework points the same direction, and the Disability Discrimination Act sets a statutory floor for accommodation requests. Keeping a dated copy of your grid, reviewed annually, is the simplest way to show AI-safe classifications were deliberate, not an accident of convenience.

For families comparing institutions on outcomes and reputation — the audience the Good Universities Guide serves — how an institution handles the human-only rows is part of what eventually shows up in satisfaction data. Automation that frees your team's time for those conversations, rather than replacing them, is the difference that compounds.

FAQ

Should every institution use the same classification grid?

No — the framework transfers but the classifications should be checked against your own process, especially for HECS-HELP/FEE-HELP eligibility and appeals, where policy varies between providers. Use the four criteria to re-score any task where your process differs, particularly around who signs off on borderline ATAR decisions.

What happens to the "AI + human review" row in practice?

AI drafts, scores, or flags the task, and a named human reviews before anything reaches the applicant. For incomplete-application follow-ups, that might mean AI sends the first two reminders automatically and a human reviews before a third, more personal message goes out. The review step is not optional — it's what keeps the task out of the human-only bucket while still capturing most of the efficiency gain.

Does automating the AI-safe tasks reduce the quality of applicant experience?

The evidence points the other way for the tasks that genuinely belong in that row. Removing a multi-day email wait for a fees question, or an unanswered call for a slot booking, improves the applicant's experience of speed and reliability, which frees your team's time for the judgment-based tasks that actually need them.

How often should we redo this inventory?

Revisit it at least once a year, and after any change to admissions policy, HECS-HELP/FEE-HELP arrangements, or TEQSA obligations — a new scholarship scheme or an appeals procedure change can shift a task's risk score enough to move it between buckets. Treat the grid as a living document your admissions leadership team owns jointly, not a one-off memo.

Can AI ever be involved in human-only tasks like admit/reject decisions?

AI can support the process — summarising an application file, flagging missing evidence, surfacing ATAR and academic data points — without making or drafting the decision itself. The line is between AI as an input to human judgment and AI as the source of the decision; the human-only row is where that line must be enforced strictly. International applicants add a further layer under the ESOS Act and National Code, one more reason those decisions stay with a person.