Staff training software that keeps every certificate in date

The price turns on one question: how much of your training model our own platform already covers. Setting up software that exists costs far less than writing rules that do not, so most of the first call goes on separating the two. After the call you get one document with the work, the date and the price on it, agreed before anybody builds anything. The monthly fee for running it afterwards is quoted at the same time, not sprung on you later, so you can budget for the whole year.

Not always. If your current platform delivers courses well and the pain sits elsewhere, in renewals, attendance, reporting and chasing, we build around it and leave it where it is. If it is the reason your records cannot be trusted, our own learning platform is usually the shorter route: courses, groups, enrollments, question banks, tests and certificates are already in it, so you are setting it up rather than building it. We tell you which of the two you are in on the call, including when the honest answer is that nothing needs replacing.

Each certificate is stored with its issue date and its expiry date, against the person rather than the course. Reminders follow a schedule you set: a first notice weeks ahead, then a nudge to the line manager, then a flag on every report until it is renewed. Where a certificate is a condition of doing a task or entering a site, the platform shows that person as not cleared rather than letting it slide. Renewal cycles vary, so the schedule is set per certificate type, not one rule for all of them.

Yes, and that is usually the harder half of the job. Our attendance software already runs across a manufacturer's plants, so shift patterns, several sites and people with no company email are the normal case for us. Classroom sessions are registered on the day, on a device already on site, instead of typed up from paper later. People can be identified by employee number where there is no email address, and course material can be cut into short pieces that work on a phone between shifts.

The record behind each completion: who did it, on what date, how long it took, what they scored if there was a test, and which version of the material they saw. Version matters. If a policy changed in March, you need to prove who saw the old one, who saw the new one and that everybody was moved across. Certificate records show issue and expiry dates with the renewal history behind them. All of it comes out as a file you can hand over, not a dashboard somebody has to be walked through.

We keep running it, and that is half of what we do. The monthly fee covers watching the software, fixing faults inside agreed times, security updates, changes as your obligations shift, and a written report on uptime and the work done. The team does not change hands, so nobody needs your escalation rules explained a second time. Agencies that build and leave are the reason a renewal reminder quietly stops sending in month fourteen and nobody notices until the audit.