A production manager at a 70-person factory gets a call at 9 a.m. on Tuesday: the labour inspector arrives at 10. By then HR needs a list of who holds a valid forklift license, a height-work certificate, and a hazardous-materials permit. HR opens a shared drive with 40 PDFs, three of them undated. Two hours later the list is assembled — but for three employees it is unclear whether the certificates are still valid.
This scenario is the best test for an LMS. Certificates are not courses — they are dated evidence with an expiry, an audit trail, and a consequence if missing. This guide breaks down what an LMS must do and shows two SMB examples.
Why certificates fall through the cracks
Three mistakes repeat in teams under 100 people:
- Certificates live in a shared drive. Two folders, each department head with their own logic. After a year nobody knows which one is authoritative.
- No expiry alerts. When a certificate lapses, nobody notices. The gap surfaces at an inspection, or when applying for a new client project.
- No link to role. The LMS shows who took a course. It does not show who, by role, should hold it and does not.
An LMS typically solves the first two problems. The third is the main reason it is worth the money.
Six features that separate an LMS from a folder
An LMS for certificate management needs six concrete features. Each one solves a specific problem:
- Role-based requirements. The role "Line B operator" automatically requires four certificates. When you move someone in, the system shows what is missing.
- Expiry alerts, in advance. Alerts fire at 60, 30, and 7 days before expiry — not on the day. The manager has time to book a refresher.
- Audit trail. Every change to a certificate (upload, renewal, removal) stores who did it and when. Supervisory authorities often ask for this.
- Evidence storage. The PDF attaches to the employee record, with issue and expiry dates. A folder in a shared drive is not proof.
- Dashboard by role and department. The production head sees in 20 seconds how many operators are current and how many certificates expire in the next 30 days.
- Audit-ready export. CSV with name, role, certificate, issue date, and expiry — exported in two clicks. Without it, HR retypes manually during an inspection.
The audit trail is the one most often missing. EU workplace safety law expects proof that training is job-specific and periodically refreshed. A document without upload history is weak — the inspector can ask who uploaded it and when.
What GDPR expects from certificate data
A certificate is personal data. GDPR Article 5(1)(e), the storage limitation principle, means an LMS must not hold certificates indefinitely. Two practical rules:
- Set a retention period per certificate type. Safety certificates stay longer (typically employment duration plus a defined period to prove compliance). Commercial certificates stay shorter.
- Retention past termination. Supervisory authorities expect you to prove compliance retroactively. Deleting everything on the day someone leaves is a risk.
The GDPR itself states no number — only the principle. Specific durations are a decision for your DPO and your safety advisor, grounded in national labour and safety law. The LMS must support different schedules by certificate type, not one global timer.
Example 1: Manufacturing company, 70 people
The quality manager had 40 line operators, 12 maintenance staff, and 8 shift leads. Four different certificates per role. Before the LMS: an Excel sheet HR updated manually each month.
The problem surfaced at the last inspection. Three maintenance staff held an electrical-work certificate that had expired four months earlier. Nobody had noticed. The inspector issued no fine, but the quality manager had 30 days to overhaul the system.
LMS rollout in six weeks:
- Week 1. HR imports all existing certificates and links them to roles. 142 entries.
- Week 2. Alerts (60/30/7 days) and a department dashboard go live.
- Weeks 3 to 4. Each team lead trains on reading the dashboard. 15-minute briefing per person.
- Weeks 5 to 6. The first automatic alert fires. Two certificates expire in 30 days, both booked.
Six months in: zero expiries without renewal, audit export in 30 seconds. HR time on certificates dropped from 8 hours a month to 1 hour a month.
Example 2: IT services, 40 people
The managing director had 25 consultants, 18 of whom needed assorted technical certificates (AWS, Azure, security). Clients occasionally asked for proof before starting a project.
Before the LMS: certificates sat in email threads between the consultant and the director. The typical reply to a client: "Give me 24 hours to check." In three cases, a project kickoff slipped because of that delay.
Rollout in four weeks:
- Week 1. Each consultant uploads their own certificates to their profile. 72 entries.
- Week 2. The director defines a "Senior AWS consultant" role with required certificates. The system shows that 4 of 7 do not meet the bar.
- Week 3. Expiry alerts turn on. 11 certificates are due in the next 90 days.
- Week 4. First export for a client. Time: 90 seconds, instead of 24 hours.
Four months later: they won two new projects partly on the back of fast qualification proof. One client wrote in an email: "The speed of the qualification reply was decisive."
For a related topic on cadence, see the compliance training frequency guide.
Common mistakes
- Alerts only to HR. If only HR receives the alert, the line manager never hears that their person's certificate is lapsing. The alert must reach both the manager and HR.
- One global retention period. Ten years for everything is too long for marketing certificates and often too short for safety. Set per type.
- Treating a certificate like a course. A course is an event; a certificate is a state. If the system fuses the two, you cannot renew a certificate without a new course — which is not always required.
- No evidence uploaded. "Completed a course" without a PDF is not proof. The inspector or the client wants to see the actual document.
The last mistake is the most expensive. A certificate in the LMS with no attached document fails the first audit.
What to do this week
Pull the five riskiest certificate types in your company. For each, write down who must hold it by role, where it currently lives, and when the next one expires. The exercise surfaces the scope of the gap — and often the first certificate that will expire in 30 days with nobody tracking it.
An LMS like Mentor covers the other half: storage, alerts, audit trail, and export. Once certificates sit in one system wired to roles, a 9 a.m. inspection call is no longer a crisis — it is a 15-minute export.