Certificates, CPD and Compliance Training: Platform Requirements
What an LMS has to do for mandatory training and CPD: completion records that stand up, expiring certificates, recertification cycles, attestations, an audit trail and the reports an auditor asks for.

A course site succeeds when people learn something. A compliance training platform is judged later and more coldly: can you show that a named person completed a specific version of a specific course on a specific date, and that somebody noticed when their certificate ran out? Many learning sites that work well for teaching cannot answer that.
This article lists what the software has to be able to do. It is not legal advice. Which training is mandatory, how often it must be renewed and how long records are kept are questions for your regulator, your accrediting body or your counsel. Once you have their answers, the requirements below are how you check that a platform can carry them out.
What a compliance training platform has to prove
Begin with the questions you expect from an auditor, an inspector or a client's procurement team, and write them down with whoever owns compliance in your organization. They tend to be these:
- Who is required to hold this training, and which of them are current today?
- What had this person completed on a given date last year?
- What content did they see, and which version of it?
- When did they acknowledge this policy, and what did the text say at the time?
- Who changed this record, and when?
Every requirement that follows exists to answer one of those. A feature that helps with none of them is not a compliance feature.
Completion records that survive change
A completion record needs more than a tick. At minimum it should hold a stable identifier for the person (an employee or member number, since names and emails change), the course and its version, the date and time, how the completion was earned (score, pass mark, number of attempts), and whether the system recorded it or a person entered it by hand.
Then test what happens to the record when things change around it:
- The person leaves. Their account should be deactivated, not deleted, until the retention period ends.
- The course is edited or retired. Old completions must still say which version was taken.
- The person moves department. History moves with them, and the new manager can see it.
- An administrator marks someone complete. The record shows who did it and why.
Retention cuts both ways. Some rules require you to keep training records for years, and privacy law may require you to delete personal data you no longer need. The platform has to support both: keeping records past a user's departure, and removing them on a schedule you set with counsel.
Certificates that expire and can be verified
A certificate used as evidence needs a unique number, an issue date, an expiry date and the course version behind it. Two ways of calculating expiry are common, and you should know which your scheme uses: a fixed period after completion, or a fixed calendar date such as the end of the year for everyone.
Third parties should be able to check a certificate without phoning you. That means a public verification page, reached by a link or a code printed on the certificate, which confirms the holder, the course, the dates and whether it is still valid. You also need a way to revoke a certificate issued in error, and the revocation should show on that page.
Recertification without spreadsheets
Renewal is where most home-grown setups fall back on a spreadsheet and a calendar reminder. A platform that handles it properly does five things:
- Opens a renewal window a set time before expiry and enrolls the person in the refresher.
- Sends reminders to the learner at intervals you choose.
- Escalates to the manager when the learner does not act.
- Changes the status to expired on the day, in every report, without anyone pressing a button.
- Stores the new completion as a new record and leaves the earlier ones untouched.
The fifth point is the one to test hardest. On many LMS setups, the easy way to make someone retake a course is to reset their progress, and the reset erases the proof that they were certified last year. Each cycle has to be its own record.
CPD credits and policy sign-off
CPD hours and credits
Continuing professional development adds arithmetic. Each activity carries a number of hours or credits, often in categories, and a professional has to reach a target within a period. What counts is defined by the professional body. The platform's part is to hold:
- a credit value and category on every course or event;
- the period for each person, since cycles do not always follow the calendar year;
- running totals against the target, visible to the learner;
- external activities, such as a conference, entered by the learner with evidence attached and approved by a reviewer;
- a transcript the learner can download and submit.
Attestations
"I have read and understood this policy" is a different kind of record from a course completion, and it is often handled badly. Opening a PDF is not an attestation. A usable one stores the identity of the logged-in user, the exact version of the document, the wording they agreed to, and a timestamp, in a form that cannot be edited afterwards. When the policy changes, the platform should ask for a fresh attestation and keep the old one.
Audit trail and the reports people ask for
An audit trail records who changed what: enrollments, completions, grades, certificates, role assignments. Each entry needs the actor, the time, and the old and new values. Ask to see it for a manual completion and for a deleted enrollment, the two changes that matter most.
Reports should be organized around status, not activity. For each required course, every person is current, due soon, overdue or expired. Managers need that view for their own teams only. Compliance staff need it across the organization, filtered by department, location and role, as it stands today and as it stood on a past date. Scheduled delivery by email and a CSV export cover most of what remains.
One dependency is easy to miss. A report can only say who is missing training if the platform knows who should have it, and that comes from your HR or membership system. Keeping roles, departments and leavers in step is an integration job, which we cover in LMS integrations that matter.
What the common platforms give you, and what gets built
No general-purpose LMS does all of this out of the box, and the gaps differ.
Moodle is strong on evidence. It tracks activity and course completion, its standard log records events against user and time, and the built-in custom reports can be scheduled and shared with defined audiences. Certificates come from a plugin. Recertification cycles are part of Moodle Workplace, the commercial edition, and on standard Moodle they are met with plugins or custom development.
WordPress LMS plugins such as LearnDash are strong on delivery and selling. LearnDash records course completion, issues certificates, lets group leaders report on their own people and can end course access after a set number of days. Certificate expiry, renewal cycles, attestation records and a change log are usually added with add-ons or a custom plugin.
Specialist SaaS products ship many of these features ready to use, in exchange for less freedom to adapt them. Our article on building, buying or extending an LMS weighs that trade.
Whichever you use, the software enforces and records a process. It does not make the process meet a regulation.
Turn each requirement into a test
Vague requirements produce vague platforms. Rewrite every line as something you can run before launch:
A learner's certificate expires in 30 days. They receive a reminder today and another in two weeks. Their manager's report shows them as "due soon". On the expiry date the status becomes "expired" and the manager is emailed. After the learner passes the refresher, a new certificate is issued and the old one still appears in their history.
Run tests like this with dummy users and backdated records on a staging site, and have your compliance owner sign off the results. Simple cases, with one course, annual renewal and one report, can be configured by a capable administrator. Multiple schemes, CPD categories, HR integration and point-in-time reporting are development work, and that is what our eLearning platform team builds on Moodle and WordPress.
Frequently asked questions
Can an LMS make our training compliant?
No. An LMS delivers training and keeps records according to rules you configure. Whether those rules satisfy a law, a standard or a contract is a judgment for your regulator, auditor or legal adviser. Choose the platform after you know what they expect.
What is the difference between completion and certification?
Completion is an event: this person finished this course on this date. Certification is a status with a validity period that can lapse, be renewed or be revoked. A platform that only stores completions cannot tell you who is current today.
Should expired learners be removed from the course?
No. Removing an enrollment often removes or hides the history with it. Keep the old record, mark the certification as expired, and enroll the person in a new cycle so the renewal is stored separately.
How long should training records be kept?
That depends on your sector's rules and on privacy law where you operate, so ask counsel for a retention period for each type of record. From the platform, require two things: records outlive a user's account, and they can be deleted on schedule when the period ends.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
