How many staff-hours does admissions admin really take?

The short answer

Admissions admin is a volume problem disguised as a series of small tasks. No single step takes long: acknowledging an application is a few minutes, booking an interview a few more. Multiplied by thousands of applicants and five or six steps each, it becomes one of the larger administrative workloads in a college — and it arrives in a spike rather than evenly.

This article works through an illustrative college step by step, so you can replace each input with your own. It is written with further education colleges in England in mind; schools, sixth forms and training providers follow a similar shape with different volumes.

The steps every application goes through

1. Received and acknowledged. Logged, and the applicant told it has arrived.
2. Checked. Course suitability, predicted or achieved grades, entry requirements, any additional needs flagged.
3. Interview or advice session booked, then held, and the outcome recorded.
4. Offer issued, usually conditional on results.
5. Conditions and results chased, and offers confirmed, changed or withdrawn.
6. Enrolled, with the learner's details entered into the MIS and whatever else needs them — timetabling, the VLE, ID cards, the funding return.

Not every applicant reaches every step. Some withdraw, some are redirected to another course, some never reply. That drop-off matters for the arithmetic, so it is built into the example below.

A worked example with illustrative inputs

Take an illustrative college receiving 3,000 applications a year, where 2,400 are interviewed, 2,100 receive an offer and 1,500 enrol. The minutes per step are assumptions to replace with your own:

• Acknowledge (3 min) and check (8 min): 3,000 × 11 min = 550 hours
• Book (6 min) and record (5 min) the interview: 2,400 × 11 min = 440 hours
• Offer letter (4 min) and conditions follow-up (6 min): 2,100 × 10 min = 350 hours
• Enrolment data entry across systems: 1,500 × 10 min = 250 hours

Total: 1,590 hours a year — about 30 hours a week on average, or roughly 0.8 of a full-time contract.

To get that figure, divide by 52 for a weekly average, multiply by 4.33 for a month (about 132 hours), and divide by 162.5, the hours in one UK full-time month (37.5 × 52 ÷ 12). That uses contracted hours. Allowing for statutory leave, a full-timer works about 1,740 hours a year, which puts the workload nearer 0.9 of a person.

None of those minutes includes the interview itself, the advice conversation, or anything that needs a tutor's judgement. This is the administration around them.

The peak is the real problem

An annual average of 30 hours a week sounds manageable. The trouble is that admissions work does not arrive evenly. Applications build through the year, but enrolment concentrates around GCSE results in August and the start of term.

In the example, enrolment is 250 hours of data entry. If 70% of it lands in three weeks, that is 175 hours across those weeks:

175 ÷ 3 ≈ 58 hours a week — more than one and a half full-time people doing nothing but enrolment data entry, at the busiest moment of the year.

That is when learners are queuing, when details are typed fastest, and when two systems are most likely to end up disagreeing about a learner's course or date of birth. Errors made in those three weeks resurface months later, often when the funding return is being reconciled.

Where the hours can come back

• Acknowledgements and reminders. Sent automatically the moment an application arrives or an interview approaches — see notifications.
• Interview booking. Applicants choose from real availability instead of a staff member finding a slot by email — see scheduling.
• Offer letters. Generated from the record rather than typed, with conditions tracked in the same place.
• Enrolment. Details the applicant has already given flow into the MIS once, instead of being re-keyed during the peak. This is usually the largest single gain, and the one we describe in why most colleges have a seam problem rather than an MIS problem.
• An applicant view. Applicants see where they stand without phoning to ask — see portals.

What should not be automated: judging borderline applicants, advice and guidance conversations, anything involving additional needs, and safeguarding concerns. The point of removing the admin is to give staff more time for exactly those.

Measuring your own college

Pick two ordinary weeks outside the peak and one week inside it. For each step above, count how many times it happened and time a sample of ten. Then:

1. Multiply count × minutes for each step, and add them up.
2. Scale to a year using your real application and enrolment numbers.
3. Work out how much lands in the peak weeks, separately.
4. Count how many systems a single learner's details are typed into.

If the result is small, change nothing — that is a legitimate finding. If most of it is re-keying, connect admissions to the MIS before you consider buying anything. The same method underpins how we estimate automation savings generally, and treating applicants like enquiries gives the same answer as how much time a CRM saves.