The Training Admin Audit: Where Your Team's Hours Go, from Enquiry to Certificate
Follow real bookings from enquiry to certificate, count every manual touch, price the hours and fix them in order. A method for providers with a team.
On this page
A training provider’s admin rarely goes on one big job. It goes on dozens of small hand-offs between tools: an enquiry copied into a spreadsheet, the same names typed into an invoice, a register and a certificate, a payment matched by hand. An admin audit follows real bookings from the first enquiry to the certificate, counts every time a person has to touch them, and prices the hours. It takes about a week, needs nothing but your inbox and a worksheet, and tells you which hand-offs to fix first and whether you need another person or a different setup.
Key takeaways
- Admin time hides in the hand-offs between tasks. Follow bookings end to end, and you see them; ask people how long each job takes, and you miss them.
- Sort every touch into five kinds: re-keying, copying, chasing, checking and deciding. Only deciding needs a person every time.
- Price the hours with a published pay figure. Median hourly pay for administrative work was £15.17 in the UK (April 2025), $23.23 in the US (May 2025) and A$41.40 in Australia (August 2025), before employer costs.
- Fix the hand-offs that touch money and compliance first, then the ones with the most volume.
- The usual root cause is the same record living in several places. The fix that lasts is a single record that every step reads from.
Why audit the admin at all
In a provider with a team, nobody sees a booking from start to finish. The person who answers the enquiry is rarely the one who raises the invoice, takes the register or sends the certificate. Each of them sees a small, reasonable task. Nobody sees that the learner’s name was typed six times, or that the purchase order number went through three inboxes before it reached the invoice.
An audit puts the hand-offs on one page, which helps in several places.
- Hiring. When the team feels stretched, the obvious answer is another administrator. An audit tells you how much of the load is work that only exists because data is moved by hand.
- Errors. A certificate with a misspelt name, an invoice without the PO and a learner who never got the joining details each start at a hand-off.
- Buying software. A list of the touches you want gone is a sharper test of training software than any feature list. What is a training management system? covers what such a system does.
The stages of one booking
Every booking passes through the same stages, whatever you sell. The audit follows a booking through each of them and asks, at every step, who touched it and why.
| Stage | What happens | Where hand-offs usually sit |
|---|---|---|
| Enquiry | A question by email, phone or a form | Details copied into a spreadsheet or CRM before anyone replies |
| Booking | Places are taken, by a learner or by an employer for several people | Names arriving later by email; the booking added to a course sheet |
| Invoice and payment | An invoice is raised or a card payment taken | Company details and PO typed into the accounting package; payments matched by hand |
| Before the course | Confirmation, joining details, reminders, trainer briefing | The same message written per learner; the trainer sent a list |
| On the day | The register is taken | A printed list, marked by hand, typed back afterwards |
| Certificate | Proof of completion, with an expiry date where it has one | Names copied into a template; each PDF emailed; the expiry date noted somewhere else |
| After the course | Feedback, CPD records, follow-up | Forms sent by hand; results collated in a sheet |
| Changes | Transfers, cancellations, refunds, waitlists | Every record above updated again |
| Renewal | The certificate expires and the learner is due again | Someone has to remember, or search old files |
Changes deserve a line of their own in the audit. A transfer to another date undoes several earlier steps, and in a setup held together by hand each one is redone.
Five kinds of touch
Each time a person handles a booking, the touch falls into one of five kinds. Sorting them is what turns a log of tasks into a list of fixes.
| Kind | What it is | Example | Does it need a person? |
|---|---|---|---|
| Re-key | Typing something a system already holds | Copying a learner’s name from the booking email into the invoice | No: the data exists |
| Copy | Sending or moving the same content by hand | Emailing joining instructions to each learner | No: it follows a rule |
| Chase | Asking someone for something you need | Emailing the client for names or the PO number | Sometimes: a reminder can ask |
| Check | Comparing two records to see if they agree | Matching a bank payment to a booking | Rarely: when the records are linked, there is nothing to compare |
| Decide | A judgement only a person can make | Approving an invoice order, moving a learner, answering a question | Yes |
The audit’s aim is not zero touches. It is a business where the touches left are decisions.
Running the audit
Plan for a week, most of it spent tracing.
- Pick five recent bookings of different shapes. A public seat paid by card, a group booked by an employer and paid by invoice, a private date for one client, a booking that was transferred or cancelled, and one with an online element. Different shapes take different routes, and the expensive routes are rarely the common ones.
- Trace each one through every tool. Search the inbox, the sent folder, the spreadsheets, the accounting package and any shared drive for the booking’s name or reference. Write down every time someone did something, in order.
- Log each touch on one line. Use the worksheet below. Note the stage, what was done, who did it, the tool it came from and went to, and the kind of touch.
- Time a sample. For a day or two, ask the team to note minutes against the touches they do. Exact figures matter less than the order of size.
- Count and multiply. Total the touches and minutes per booking shape, then multiply by how many bookings of each shape you take a year.
| Stage | Touch | Who | From | To | Kind | Minutes | What goes wrong if it is missed |
|---|---|---|---|---|---|---|---|
| Invoice | Typed company, PO and places into the accounting package | Office manager | Booking email | Accounting | Re-key | Invoice returned unpaid without the PO | |
| Before | Sent joining details to each learner | Coordinator | Course sheet | Copy | Learner turns up without the link or the address |
The last column is the one people skip and the one that ranks the fixes. A touch that costs a minute but sends an invoice back unpaid is worth more attention than a five-minute one with no consequence.
An example trace
Here is the trace for one booking shape: an employer books four places on a public course and pays by invoice, in a provider that runs on email, a booking spreadsheet, an accounting package and a certificate template. It shows how a trace reads; your own will differ in the detail.
| # | Stage | Touch | Kind |
|---|---|---|---|
| 1 | Enquiry | Reply with dates and the price for four | Decide |
| 2 | Enquiry | Add the client and contact to the spreadsheet | Re-key |
| 3 | Booking | Add four places to the course sheet | Re-key |
| 4 | Booking | Ask for the learners’ names | Chase |
| 5 | Booking | Type the names into the course sheet when they arrive | Re-key |
| 6 | Invoice | Raise the invoice with company details, PO and places | Re-key |
| 7 | Invoice | Ask for the PO number, which was not in the first email | Chase |
| 8 | Payment | Find the payment in the bank feed and mark the booking paid | Check |
| 9 | Before | Send joining details to each of the four | Copy |
| 10 | Before | Send a reminder a few days before | Copy |
| 11 | Before | Send the trainer the list of learners | Copy |
| 12 | On the day | Print the register from the course sheet | Copy |
| 13 | After | Type attendance back into the sheet | Re-key |
| 14 | Certificate | Fill four certificates from the template | Re-key |
| 15 | Certificate | Email each learner, and the employer, their certificates | Copy |
| 16 | Certificate | Note the expiry dates for renewal | Re-key |
| 17 | After | Send the feedback form and collate the answers | Copy |
| 18 | After | Note the course on the client’s record | Re-key |
That is eighteen touches for one booking, and one of them is a decision. Eight are re-keying, seven are copying or checking, and two are chasing. Every re-keyed line is also a place where a name, a date or a number can go wrong, and the certificate inherits any mistake made upstream.
Price the hours
Once the trace is timed, the cost is one line of arithmetic: bookings a year, times minutes of admin per booking, divided by sixty, times an hourly cost. Use your own pay rates if you know them. If not, the national statistics give a fair starting point for administrative work.
| Where | Median hourly pay | Group | Period |
|---|---|---|---|
| UK | £15.17 | Administrative and secretarial occupations, all employee jobs, excluding overtime | April 2025 (provisional) |
| US | $23.23 | Secretaries and administrative assistants | May 2025 |
| Australia | A$41.40 | Clerical and administrative workers, main job | August 2025 |
These are pay only. Employer taxes, pension contributions, holiday and overheads all make an hour of a team member’s time cost more than its pay.
The calculator uses the same arithmetic. The starting figures are an example, so put in your own.
As a guide to scale, here are the hours for a range of booking volumes and measured minutes.
| Minutes of admin per booking | 1,000 bookings a year | 3,000 bookings a year | 5,000 bookings a year |
|---|---|---|---|
| 10 | 167 hours | 500 hours | 833 hours |
| 20 | 333 hours | 1,000 hours | 1,667 hours |
| 40 | 667 hours | 2,000 hours | 3,333 hours |
Every 1,000 hours is about 27 working weeks of 37.5 hours. At the median pay figures above, 1,000 hours is £15,170 in the UK, $23,230 in the US and A$41,400 in Australia, before employer costs. The table is arithmetic on the inputs, not a benchmark: the minutes are whatever your trace measures.
What to fix first
A long list of touches can be fixed in any order. A sensible order saves the most hours and removes the most risk first.
Which hand-offs to fix first
Errors here delay cash or send invoices back. The PO typed into the invoice and the payment matched by hand are the usual candidates.
A wrong name or a missing expiry date is found by an auditor or a client, usually much later.
Multiply the minutes by the bookings a year. Confirmations, reminders and joining details usually come out on top.
Approving an order or moving a learner needs a person. Make sure that person sees the booking, the client and the history when they decide.
Then choose how to fix each one. Some touches go with a better habit: a template for joining details, or asking for the PO at the point of booking. How to sell training to corporate L&D buyers covers why the PO belongs at checkout. Some go with an integration between two tools. Most re-keying, though, comes from one cause: the same booking lives in several places, so every step has to copy it to the next. That is solved by putting the booking in one record that every later step reads from, which is the job of a training management system.
What the audit asks of your system
Read your worksheet back and the requirements write themselves. They make a test for the setup you have, or any system you are considering.
| Touch in the trace | What the system should do |
|---|---|
| Client and contact typed into a spreadsheet | Create the contact and link them to their organisation when they book |
| Names chased and typed in | Let the person who booked add the names themselves |
| Company, PO and places typed into an invoice | Raise the invoice from the booking, with the PO taken at checkout, and pass it to your accounting package |
| Payment matched by hand | Mark the invoice paid when the payment is recorded, in either system |
| Confirmations, joining details and reminders written per learner | Send them per learner, from templates, on a schedule |
| Trainer sent a list | Notify the trainer when they are assigned and before the course |
| Register printed and typed back | Take attendance once, on the record |
| Certificates filled and emailed | Issue them from the attendance, with the expiry date, and send them |
| Feedback forms sent and collated | Ask for feedback when the course is completed and keep the answers on the record |
| Every record updated after a transfer | Move the booking once and let everything follow |
From spreadsheets to a training management system covers how to move the data across once you have chosen.
The same booking, run in Cademy
Cademy is built around that one record. A booking creates the contact, links them to their organisation by email domain, and puts each learner on a registration on the course date. The order, the invoice, the attendance and the certificate are all attached to it, so each step reads from the one before instead of copying it.
Here is the employer’s booking of four places from the trace, and what happens at each stage without anyone typing it in again.
Posted to Xero
In the calendar
Paid, from Xero Set against the eighteen touches in the trace, this is what changes.
| Touches in the trace | In Cademy |
|---|---|
| 2, 3: client, contact and places typed in | Created by the booking, with the contact linked to the organisation by email domain |
| 4, 5: names chased and typed | The person who booked adds or invites the learners from their own account |
| 6, 7: invoice typed, PO chased | The PO number is taken at checkout and printed on the invoice; on Teams the invoice is posted to Xero |
| 8: payment matched | A payment recorded in Xero marks the invoice paid in Cademy; overdue reminders are one setting |
| 9, 10, 11: joining details, reminders, trainer list | Booking confirmations and reminders a week, a day and an hour before go to each learner; trainers get an email when they are assigned and before the course |
| 12, 13: register printed and typed back | Attendance is marked once, on the date’s registrations and in bulk if you like; a printed register with the fields you choose is there for the room |
| 14, 15, 16: certificates and expiry dates | Once switched on, certificates issue when attendance is marked, with the expiry date set, and go to each learner by email |
| 17: feedback | A feedback request goes out when the course is completed, and the answers stay on the record |
| 18: client record | The organisation’s record shows every order, learner and certificate as they happen |
What is left is the first line of the trace: a person answering the enquiry and deciding what to offer. Conversations sit in Cademy’s inbox, and every email sent from Cademy is on the contact’s record with its delivery status, so whoever picks up the conversation sees what was said before. Where a step still needs people, task sets give the team the same checklist for every course.
The changes that undo work in a hand-built setup are single actions here. A registration moves to another date or course with its history and certificates. When a place frees up, the people on the waitlist are emailed in the order they joined. Imports bring the spreadsheet, the courses and the past bookings across on every plan, so the audit’s worksheet can become the plan for the move.
To see your own trace run this way, book a call and bring the booking that took the most touches, or start for free and run one course end to end. The training management system page shows the rest of the record behind each booking.
Frequently asked questions
What is a training admin audit? A training admin audit follows real bookings from the first enquiry to the certificate and records every time someone on the team has to handle them. Each touch is sorted by kind, timed and multiplied by the number of bookings a year, which shows where the admin hours go and which hand-offs to fix first.
How long does an admin audit take? Plan for about a week in a provider with a small team. Most of the time goes into tracing five recent bookings through the inbox, spreadsheets and accounting package. Timing a sample of the touches takes a day or two of the team noting minutes.
What should I measure in a training admin audit? For each touch: the stage, what was done, who did it, which tool it came from and went to, its kind (re-key, copy, chase, check or decide), the minutes it took and what goes wrong if it is missed. Then total the touches and minutes per booking shape and multiply by bookings a year.
How do I put a cost on admin time? Multiply bookings a year by minutes of admin per booking, divide by sixty and multiply by an hourly cost. Use your own pay rates, or a published median for administrative work: £15.17 an hour in the UK (ONS, April 2025), $23.23 in the US (BLS, May 2025) and A$41.40 in Australia (ABS, August 2025), with employer costs on top.
Which admin tasks should a training provider automate first? Start with the ones that move money, such as raising invoices with the PO and matching payments, then the ones that create evidence, such as registers, certificates and expiry dates. After that, go by volume: confirmations, joining details and reminders sent per learner on every booking.
Do I need another administrator or better software? Run the audit first. If most of the touches are decisions, the team needs more people. If most are re-keying, copying and checking, the work exists because the same booking lives in several places, and a system that keeps one record removes it.
Sources
Figures checked 13 October 2026 on the publishers’ own pages.
- Office for National Statistics, Earnings and hours worked, occupation by two-digit SOC: ASHE Table 2 (Table 2.6a, hourly pay excluding overtime, all employee jobs, 2025 provisional)
- US Bureau of Labor Statistics, Occupational Outlook Handbook: Secretaries and Administrative Assistants (2025 median pay)
- Australian Bureau of Statistics, Employee earnings, August 2025
- Cademy: training management system, B2B training and pricing