Compliance training has a different success condition from other training. You're not primarily trying to change behaviour — you're establishing that a specific person was told a specific thing on a specific date, and can prove it later.
That makes the record the product.
What Poplearn does and doesn't supply
Being clear about the split, because it decides whether this is the right tool.
It converts what you give it. /courses new takes a policy document — one your legal or security team has already written — splits it into modules, and writes the questions. If the policy exists, this is the shortest path from document to tracked training.
It doesn't supply regulated content. If you need correct HIPAA, GDPR, or PCI training written by someone who knows the regulation, that's a different purchase. Haekka is the notable Slack-first option that ships maintained compliance content through pre-built subscription Streams.
It can't ingest SCORM. Purchased compliance libraries almost always ship in that format. If you've already bought one, you need an LMS that reads it.
For the very common case — legal has written the policy, and the problem is getting it read, tested, and recorded — the conversion path is the right one.
The record
/progress returns live completion by team, exportable on demand, as a per-person timestamped record.
That distinction is the whole point. A dashboard showing 94% is a management metric. When an auditor asks whether a named individual completed a named policy and when, you need a record you can hand over, not a percentage.
Because modules are completed inside Slack, completion is written as it happens. There's no separate system to reconcile against, which is where manual tracking normally drifts and where the parallel spreadsheet usually comes from.
Run the test before someone else does
Pick a person and a policy at random. Time how long it takes to produce a record showing they completed it, and when.
If it takes more than a minute or involves asking someone, you have a reporting layer rather than an evidence layer. Much better to discover that on a Tuesday.
Setting it up
Split by policy, not by year. One course per policy is easier to update and easier to evidence than an annual omnibus. When the code of conduct changes, you regenerate one thing.
Assign to everyone joining from a date forward. This is where compliance gaps actually hide. If enrolment is manual, someone who joined between annual sweeps was never in the population — so completion reads 100% while a genuine gap exists. That's the most dangerous reporting error available, because nothing looks wrong.
Set a real deadline tied to something external — a certification date, an audit window — rather than an arbitrary one that gets renegotiated.
Keep completion visible by team, so managers close gaps themselves instead of compliance chasing individuals across the company.
Questions as evidence
A quiz turns "was sent" into "engaged with", which is a meaningfully stronger position in an audit.
Keep questions about the substance of the obligation rather than the wording of the module — the record you want is that someone understood what's required, not that they could match a sentence. Four questions after a six-minute module is enough.
Review the generated questions before assigning. If one option is obviously the responsible-sounding answer, the question isn't establishing anything.
Retention
Where training recurs annually, keep the historical records rather than overwriting them. An auditor asking about a specific past period needs the record for that period.
Add Poplearn to Slack — free under 20 seats, installs in about a minute. Then run the test above.
