The training happened. You're almost sure of it. You ran the harassment-prevention session, or pushed out the safety refresher, or made everyone read the new data-handling policy — and if someone asked you to prove it, you'd reach for a spreadsheet. A tab with names down the side and checkmarks you typed in by hand as people told you they'd done it. It feels like a record. It is not a record. It's a note you wrote to yourself, and the moment it has to stand up to an auditor, an insurer, an OSHA inspector, or a plaintiff's attorney, it dissolves — because a self-typed checkmark proves that you typed a checkmark, and nothing about whether a specific person completed a specific training on a specific day.
This is the quiet bind of mandatory training at a small company. The obligation is real and rising — safety, harassment, privacy, industry rules — and so is the standard of proof. But the machinery built for it, the LMS with its completion certificates and audit logs, assumes you have an administrator, a rollout budget, and a reason to maintain a platform that does one thing four times a year. You have none of those. So you fall back to the spreadsheet and hope nobody asks you to prove it, which is a plan right up until the day someone does.
The instinct is to buy the enterprise LMS and inherit the admin burden, or to keep hoping. Both are bad. The LMS is overkill you'll half-configure and abandon; the hoping is a liability you're carrying without pricing it. There's a narrower thing you actually need, and naming it precisely is most of the solution: not a learning platform, but defensible evidence of completion — assign the training, track who's done it, and produce a record that holds up. That's a smaller problem than "run an LMS," and it's the one worth solving.
What "defensible" actually means
Before you fix anything, get clear on what you're being asked to prove, because "we did the training" is not it. When completion records are tested — in an audit, a claim, an investigation — they're tested against a few specific properties. A record is defensible when it can answer, without you reconstructing anything from memory:
- Who, specifically. A named individual, not "the team" or "everyone in the June session." Compliance is personal; the obligation attaches to a person.
- What, specifically. Which training — the exact course or policy, and ideally which version. "Harassment training" is weak when the content was updated and the question is whether they got the current one.
- When, and by when. The date completed, measured against the date it was due. Overdue-but-eventually-done and on-time are different facts, and sometimes the difference is the whole case.
- Generated by the system, not by you. The record's credibility comes from it being a byproduct of the person actually completing the thing — a timestamp the system wrote — rather than a status you entered on their behalf. Self-attested checkmarks are exactly what auditors discount.
Your spreadsheet fails on the fourth property, which quietly poisons the first three: because you typed the checkmarks, none of the who/what/when is independently trustworthy. Fixing this isn't about a fancier spreadsheet. It's about moving from records you assert to records the system captures.
Assign, track, evidence — the three moves that hold up
Strip away the platform question and defensible completion is three plain steps. You can reason about them independent of any tool, and they're the frame for evaluating whatever you do use.
Assign it to named people with a deadline
Not "make it available" — assign. There's a difference between posting a training and giving a specific person a specific obligation with a due date. The assignment is what creates the record that this person was required to do this thing by this time. Everything downstream references it.
Track completion as it happens, not after
The record you want is generated at the moment of completion, by the act of completing — not backfilled later from memory or from people telling you they're done. Tracking should be a live picture: who's complete, who's outstanding, who's overdue, right now. If you only know the state by asking around, you don't have tracking; you have a survey.
Evidence it in a form you can hand over
The end product is a report you can produce on demand: these named people completed this training, by these dates, against this deadline. It should exist whether or not you've thought about it lately, because the request always comes at a bad time. Evidence you have to assemble under pressure is evidence that has gaps.
Notice what's not on this list: fancy content authoring, learning paths, gamification, an admin console. Those are LMS features. Defensible completion needs assign, track, evidence — and almost nothing else. Buying more than that is how you end up with a platform you don't maintain.
Design the assignment so it survives scrutiny
Two disciplines make the difference between a completion record that holds and one that technically exists but crumbles under a question.
The first is version discipline. When mandatory content changes — the policy is revised, the law updates, the procedure changes — an old completion doesn't cover the new content. The defensible move is to re-assign on material change and keep the record tied to what was actually completed, so "they did the training" always means "they did this version." Without it, you can be simultaneously honest and wrong: everyone completed the training, none of them completed the current one.
The second is overdue as a first-class fact, not an afterthought. The most common failure isn't people refusing training; it's the long tail who never get around to it while your attention is elsewhere. A defensible system makes "overdue" visible continuously and nudges before the deadline becomes a finding — because the gap you can see this week is a reminder, and the gap you discover during an audit is a problem. Track the outstanding as attentively as the complete; the outstanding is where the risk lives.
Get those two right — versioning and a live view of who's not done — and your completion records stop being a hopeful spreadsheet and start being something you'd willingly put in front of an auditor.
Where the tool fits
The three moves and the two disciplines are yours to run with judgment, but they do need something to capture system-generated records — that's the one thing a spreadsheet structurally can't give you, because you're the one typing in it.
LearningByDesign covers exactly this narrow need without the LMS overhead. You assign training to your people, and its compliance analytics show you completion as a live picture — who's done, who's overdue — rather than a status you maintain by hand. The record is generated by people actually completing the assigned training, which is precisely the system-captured evidence that a self-typed checkmark can never be. So when the request comes — the audit, the insurer, the investigation — you're reading a report, not rebuilding one.
That's the whole role of the software here: assign, track, and surface who's complete and who's overdue, so your proof of completion is a byproduct of the training happening rather than a note you wrote and hoped no one would test. Deciding what's mandatory, and re-assigning when the content materially changes, stays your call.
The bottom line
Mandatory training carries a standard of proof, and a spreadsheet of hand-typed checkmarks doesn't meet it — not because you did the training wrong, but because a record you assert isn't a record the way an auditor means it. You don't need to inherit an enterprise LMS and an admin job to fix that. You need the narrow thing underneath compliance: assign the training to named people with deadlines, track completion as a live picture rather than a survey, and hold evidence you can hand over on demand — with version discipline and a real view of who's overdue. Solve that, and "prove the training happened" stops being the question you dread and becomes one you can answer with a report.
Build the mandatory course first — free
The free Course Outliner takes a topic and an audience and gives you modules, measurable objectives, and an assessment — the training you then assign and track. No signup.
Try the free Course Outliner →