The enrolment inbox in September
Your enrolment team sends every new learner the same email: please send proof of identity, evidence of your right to live and study here, your previous qualification certificates and anything else on the attached list. The replies come in all week. A passport photographed on a kitchen table with the corner cut off. A certificate as a Word document. A screenshot of a screenshot. One learner replies with nothing but a question.
Someone downloads each attachment, renames it, saves it to the learner's folder and ticks a spreadsheet. The unreadable ones mean another email. Learners who do not reply are chased by phone. By the start date some files are still incomplete, and your compliance team will not let those learners start.
Why the document chase never gets shorter
- Every learner gets the full list, including items that do not apply to them, so they are unsure what to send.
- Email attachments have no quality check, so bad scans are found only when someone opens them.
- Documents are saved by hand, and file names and folders vary.
- The spreadsheet tick is manual, so it is sometimes wrong.
- Reminders depend on someone having time to send them.
Eligibility rules themselves are set outside your organisation and your team applies them. The trouble is the collection, not the rules.
What the chase costs
Starts get delayed, which hurts the employer relationship and delays income. Enrolment staff spend their busiest weeks moving files around. Personal documents sit in inboxes, which is not where you want copies of passports kept.
There is also the risk of a document that was never checked properly because it came in during a rush. Your team decides what is acceptable evidence, and we do not give advice on eligibility; we make sure every document is collected, readable, stored in the right place and looked at by a person.
The guided upload we build
- The learner answers a few questions first, set by your team, which decide which documents they need, so they see a short personal list instead of the full one.
- Each document has its own upload step with an example of what a good photo looks like.
- Uploads are checked for blur, cropping and file type as they arrive, and the learner is asked to retake a bad one straight away.
- Reminders go by text and email until the list is complete, and the learner can see what is left.
- Your enrolment team sees a verification queue, with each document beside the learner's details and a place to accept or reject it with a reason.
- Accepted documents are stored in your document system against the learner, with consistent names, and removed from any temporary storage.
| Step | Learner sees | Your team sees |
|---|---|---|
| Questions | Short set of plain questions | Answers stored with the record |
| Upload | Personal document list with examples | Nothing yet |
| Quality check | Prompt to retake a poor photo | Only readable files |
| Reminders | What is still missing | Who has not finished |
| Verification | Confirmation or a clear reason to resend | Accept or reject queue |
Access to the stored documents is limited to the roles you choose, and every view is logged.
Enrolment week, done differently
The learner gets a link the day their start is agreed. Most finish the uploads that evening on their phone. Your enrolment officer works through a queue of documents that are already readable and already labelled. Rejections go back with a reason, and the learner fixes them in minutes.
Compliance sees which learners are fully verified and which are not, without asking. Nobody has to open an email attachment to find out whether it is a passport or a cat.
Is enrolment slowing your starts?
- Learners are sent one long list of documents by email.
- Poor quality scans are found days after they arrive.
- Staff rename and file attachments by hand.
- Starts are held because documents are missing.
- Copies of ID sit in shared inboxes.