The training certificate is the record, not the course
Ask any registered manager what "mandatory training" means and you will get a list: moving and handling, safeguarding adults, medication, basic life support, infection prevention and control, fire safety, and the rest of the Skills for Care core and mandatory set. Ask what keeps them awake before an inspection and the answer is different. It is not whether the courses were done. It is whether every certificate is still in date, for every member of staff, today.
That gap is worth dwelling on, because most of the training admin that goes wrong in care agencies goes wrong inside it.
A completed course is a fact about the past
When a care worker finishes a course, the learning platform records a completion. That is a true and useful fact. It is also, for compliance purposes, almost the wrong fact.
Regulation 18 of the Health and Social Care Act regulations asks providers to make sure staff "receive such appropriate support, training, professional development, supervision and appraisal as is necessary". An inspector reading a training matrix is not checking that manual handling was ever completed. They are checking that the certificate on file has not lapsed, that the refresher was booked before it did, and that nobody was rostered onto a client who needs hoisting while their moving-and-handling was out of date.
There is no single statutory refresh period for most of these subjects. Skills for Care publishes recommended frequencies and each agency sets its own policy in its requirement library. That makes the expiry date something the agency decides, applied to something the learning platform reports. Two owners, one record.
Where the record breaks
In a typical agency the two halves live in two systems. The learning platform holds the completions. The care management system holds the staff compliance matrix: who is cleared to work, what each role requires, and which certificates are due.
The join between them is usually a person. A coordinator downloads a completion report on a Friday, opens the compliance matrix, and retypes dates. This works, in the sense that it produces a matrix. It fails in four predictable ways:
The report is a snapshot. Anyone who finished a course on Saturday is out of date until the next retype.
Retyping is where dates go wrong. A transposed month on one certificate is invisible until it matters.
The retype happens when there is time, which is never the week a new client with complex needs starts and three carers need cleared in a hurry.
A course with no expiry gets treated as permanent. If the report lists a completion but no expiry date, the temptation is to leave the cell green. That is exactly the certificate an inspector will ask about.
None of these is a training problem or a software problem on its own. They are what happens when two systems that each hold half the answer are joined by a spreadsheet.
What a proper integration should do (and not do)
Care Learner is being integrated with CareOS, a UK home care management software platform, and the design conversations behind that integration are a useful illustration of what "joined up" should actually mean. Two principles came out of them.
The expiry date is the payload. "Completed manual handling" on its own is close to worthless for compliance. What the compliance matrix needs is the date the certificate stops being valid, because every mandatory-training requirement is really a question about whether it is still in date. So the sync is being built to pull each learner's completed courses with their certificate expiry dates, with the soonest expiry driving the follow-up. A course that comes back without an expiry will be surfaced as such and counted, rather than quietly assumed to last forever.
The learning platform reports; the agency decides. The integration deliberately will not decide what "compliant" means. It returns what the learner has done and when it lapses. The agency's own requirement library decides which courses are mandatory for which role and how long each one is treated as valid. Baking a care-role policy into a vendor connection would bury a decision that belongs to the registered manager inside somebody else's software.
Get those two right and the coordinator's Friday job disappears. A carer finishes [a Care Learner course] on Saturday; the compliance matrix reflects it, with the right expiry, without anyone retyping a date. That is the bar the integration is being built to.
What this means for your training matrix
Whether or not you use either platform, the same test applies to any training set-up:
Can you answer "who is out of date today?" without building a report? If the answer needs a download and a spreadsheet, the record is a snapshot, not a record.
Does every completion carry an expiry? Check the ones that do not. Decide, in writing, how long they are valid for, and make the system enforce it.
Is the refresh policy in one place? Frequencies should live in the agency's requirement library, applied consistently, not scattered across course settings and individual memories.
Does the rota know? The point of a compliance matrix is to stop someone being scheduled onto work they are not currently cleared for. A matrix nobody's scheduling reads is a wall chart.
Who owns each half? Training completions belong to the learning platform. Validity rules belong to the agency. Clearance belongs to the care management system. When one of those is being done by a person in the middle, that is the join to fix first.
Want to check whether your training records would stand up to scrutiny?Book a free consultation with Manu Thomas to discuss your current training compliance, identify potential gaps in certificate expiry dates and records, and understand what you may need to strengthen.
The short version
Training compliance is not a record of what your staff have learned. It is a live statement, defensible on any given day, that every person delivering care holds an in-date certificate for everything their role requires. Completions are the input. Expiry dates are the record. The systems you use should be built around the second, not the first.
Comments