The email that announces an audit
An audit or inspection is announced, or a sample of learner files is requested. Your compliance lead sends a message to all coaches: please check your learner files by Friday. Everyone stops what they are doing. Some files are in the e-portfolio, some in a shared drive, some in the MIS as attached documents. Coaches find unsigned reviews, a missing training plan revision, an employer agreement stored under the wrong learner.
By Friday most files are presentable, but the week of normal delivery was lost, and everyone knows that the next announcement will start the same scramble.
Why files are never quite complete
- Nobody has written down, per stage, what a complete file should contain, so each coach has their own idea.
- Documents live in several systems, so checking one file means opening three.
- Missing items are found by opening files, which only happens under pressure.
- When staff leave, their learners' files are inherited with gaps nobody knew about.
- Changes such as breaks, extensions or new employers add documents that are easy to forget.
The cost of keeping files by panic
The obvious cost is the lost week of delivery every time files are checked. The less obvious cost is that problems found late often cannot be fixed properly. A review signed months later is not the same as one signed at the time.
Your compliance lead also spends their time chasing rather than improving practice. What your files must hold is for your own quality team, funding rules and auditors to set; we make sure you know, every day, where each file stands against that list.
Continuous file checks
- With your compliance lead, we write the list of what a learner file should contain at each stage: at start, during learning, at breaks and changes, at gateway, at completion or withdrawal.
- We connect to where documents and data live: your document store, MIS and e-portfolio.
- Each learner's file is checked against the list every night, and missing or out-of-date items are recorded.
- Coaches see a short to-do list of missing items for their learners, most urgent first.
- Managers see completeness by coach, standard and stage, and the items that go missing most often.
- When an audit sample is requested, the chosen files can be exported as a tidy pack with an index.
| Stage | Typical items your list may include | Checked against |
|---|---|---|
| Start | Agreement, training plan, eligibility evidence, initial assessment | Document store and MIS |
| During learning | Signed progress reviews, off-the-job record | E-portfolio |
| Changes | Revised plan, break or change of employer records | Document store |
| Gateway | Gateway evidence and employer confirmation | E-portfolio and tracker |
| Exit | Completion or withdrawal records | MIS and document store |
Files that stay ready
Each coach spends a few minutes a week clearing their to-do list while the information is fresh. A missing signature is chased the week the review happened, not months later.
New coaches benefit as well. When someone joins and inherits a caseload, the to-do list tells them on day one which files have gaps, instead of leaving them to discover it one file at a time. And because the list is written down and checked the same way for everyone, the argument about what a complete file looks like happens once, with your compliance lead, rather than in every audit.
When the next audit is announced, your compliance lead checks the completeness view, sees a handful of open items, and exports the sampled files. The rest of the team carries on delivering.
Recognise the scramble?
- File checks happen only when an audit is announced.
- Coaches have different ideas of what a complete file is.
- Checking one file means opening several systems.
- Inherited caseloads come with gaps nobody knew about.
- Compliance time goes on chasing rather than improving.