When the rule changes, the training changes — included
LessonSlate builds compliance modules that import into your LMS as a SCORM package, report a completion and a score to your gradebook, and get rebuilt and redelivered whenever the regulation, the policy or the role definition underneath them moves. No change order. No new production cycle.
Your current vendor cannot match this, and it is not because they don't want to
Established compliance-video vendors bill against production hours — scriptwriters, voice talent, animators, an editor. Those hours are their revenue. An offer of "unlimited re-renders whenever the rule changes, included in your renewal" would delete the per-module income that pays for the studio.
LessonSlate has no studio. A module is assembled by the same pipeline that produced it in the first place, so rebuilding one when a control gets reworded is a re-run rather than a project. That is why the re-renders are included rather than quoted.
The practical commitment: an affected module is re-cut and redelivered within two weeks of you confirming the change.
- The regulation moves — a control is reworded, a standard is revised
- Your policy moves — a threshold changes, a step is added to an escalation path
- Your org moves — a role is renamed, a system is retired, a team is merged
- The module is rebuilt — new render, new captions, new quiz, same SCORM identifier
- You re-import it — and the version your staff are assigned is current again
What arrives when you buy a module
Not a video file with an invoice attached. A package your administrator imports the same way they import anything else.
A SCORM 1.2 package
The format nearly every Learning Management System accepts. It reports a completion and a score back to your gradebook, so the record of who passed lives in your system rather than in ours. It also plays on its own, outside any platform, so you can watch a module before importing it.
Captions that match the words
A WebVTT caption file, written from the script the lesson was built from rather than guessed by speech recognition. The captions and the video are timed off one shared clock, so they do not drift apart over a twelve-minute module the way auto-captions do.
A scored knowledge check
Three to five questions per module, marked and reported through SCORM. The pass mark is set so a learner is allowed exactly one mistake — an 80% mark on a four-question quiz silently demands a perfect score, which fails people who understood the material.
A source map
One page listing which control or guidance clause each segment of the module teaches. Compliance buyers get audited, and being able to hand over the mapping is worth more than production polish.
Your brand, not ours
Colours and wordmark are theme variables rather than baked-in artwork, so a module carries your identity without a re-render being an art project. Demo modules use a clearly fictional company, named as fictional on screen.
Nothing that phones home
The package makes no outbound network calls during playback. There is no account, no login, and no learner data of any kind reaches us — completion and score stay between the module and your LMS.
It has been run through the conformance service your LMS vendor tests against
A LessonSlate module was imported into SCORM Cloud — the service ADL's own ecosystem points at for SCORM conformance — and taken end to end by a learner. It imported without errors, played, recorded a completion, and reported a score matching the answers given.
That is the same package your platform receives. Platforms still differ at the edges, so if you are planning a rollout, tell us which LMS you use and we will confirm against it before you commit to anything.
| Registration report | |
|---|---|
| Learning standard | SCORM 1.2 |
| Completion | complete |
| Success | passed |
| Score | 75.00% |
| Run | 30 August 2026 |
The quiz tests what staff actually get wrong
A multiple-choice question is only as good as its wrong answers. Ours are not invented to fill three slots — each one is a specific mistake somebody actually makes, recorded before the module was written.
"Disabled means gone"
Someone leaves, their account is disabled, and the offboarding checklist is ticked. A disabled account still exists, still holds its group memberships, and can be re-enabled by anyone who could disable it.
"Holding the door is just manners"
A stranger with a lanyard and full hands follows you through a badge reader. Letting them in reads as politeness and is the single most common way a controlled door gets defeated.
"No harm, no report"
A near miss with nobody hurt feels like nothing happened, so it never reaches the incident log — and the pattern that would have predicted the real incident is never visible.
There are 18 of these recorded across the two topics in the catalogue today, written against the full NIST control text rather than a summary of it. They are what the quiz distractors are built from, and they are also what the on-screen dialogue is steered toward — the module walks into the wrong turn deliberately and then corrects it, because a mistake a learner watches being fixed is one they are less likely to make.
Two topics, deliberately
The compliance catalogue currently covers two subjects end to end:
- Access control — what happens to someone's access when they leave, built against NIST AC-2 (account management)
- Physical security — challenging an unbadged person in a controlled space, built against FEMA IS-906
That is a small catalogue and we would rather say so than imply a shelf of finished courses. The engine behind it is not small — it produces a library of chemistry, algebra, geometry and nursing lessons on a daily schedule — but compliance is the newest subject on it.
Which is exactly why the design-partner slots exist, and why there are only two of them.
A design partner's own compliance calendar decides what gets built next, and their policy documents are what the third and fourth topics are modelled on. That is worth a genuinely lower price to us, and it is a real constraint rather than a scarcity tactic: past two, the roadmap stops being coherent.
If your topic is not in the list above, that is not a problem — it is the conversation.
Prices, published
Custom compliance modules from an established vendor run roughly $5,000–15,000 each on a six-to-eight-week cycle. These are not the cheap option — they are the same order of price with a delivery time you cannot buy elsewhere, and a renewal that keeps the library current.
- Three modules from your own policy or SOP documents
- Input on which compliance topics get built next
- Early delivery, ahead of the general queue
- Brand-themed, captioned, SCORM packaged
- In exchange: a named reference and a short case study
- Three custom modules from your own documents
- Brand-themed to your identity
- Captions and a scored knowledge check per module
- SCORM package plus source map
- Sized to sign on a manager's discretionary budget
- Twelve modules across the year
- Delivered on a schedule you set
- SCORM and xAPI packaging for your LMS
- Your material held as structured content, not just finished files
- Everything in the pilot, at volume
- Unlimited re-renders when a rule or policy changes
- Affected modules redelivered within two weeks
- No change orders, no per-revision quotes
- Role, system and threshold updates included
- Your library stops being a stack of files that ages
These prices are published rather than quoted. There is no discovery call before you can find out what something costs, and no proposal to wait on — if a package fits, the next step is a scoping conversation and a payment link.
The questions procurement asks
Will it import into our LMS?
If your platform accepts SCORM 1.2, which nearly all of them do, yes. A module has been imported into SCORM Cloud — the conformance service LMS vendors test their own products against — and run end to end: it played, it scored, and it reported a completion, with no errors. That is the same package you receive. Platforms differ at the edges, so tell us which one you use and we will confirm against it before you commit.
Is any of this AI-generated, and do we have to disclose it?
Yes, and we disclose it for you rather than waiting to be asked. The AI is in the authoring — it drafts the dialogue and speaks the voices. Nothing runs while a learner is watching: by the time a module reaches them it is a video file, a caption file and a scored quiz, with no prompt box and no model to interact with. A person reviews every module before it ships, after an automatic checker recomputes the numbers and refuses to publish anything that does not add up. The full statement is here, and there is a one-page version written to be forwarded.
What about accessibility?
Every module ships with a WebVTT caption file generated from the script rather than from speech recognition, so the captions carry the exact words spoken, including technical terms that auto-captioning mangles. Captions and video are timed from one shared clock, so they stay in sync to the end of a long module.
Plainly: we have not yet had a formal third-party accessibility audit and there is no VPAT to send you. If your procurement requires one, say so early — it is a scheduling question rather than a rebuild, and knowing it is needed changes the order things get done in.
Where does our data go?
Nowhere. The package makes no outbound network calls during playback. There is no account and no login. Completion and score are reported to your LMS through the standard SCORM interface and stay in your system. We never see who took a module or how they did.
How fast is delivery, really?
A pilot of three modules is two weeks. A re-render triggered by a rule change is delivered within two weeks of you confirming the change. We write those as "within two weeks" rather than naming a day, because production runs on a schedule we control and we would rather commit to something we can hold than to something that sounds better.
Who writes the compliance content?
The subject matter comes from the published source — the NIST control text, the FEMA guidance — read in full rather than summarised, and from your own policy documents for anything specific to you. What we add on top is the catalogue of mistakes staff actually make on each topic, which is what the quiz and the on-screen correction are built from. Every module is reviewed by a person before it is delivered; the compliance path is never run unattended.
What if we need a topic you don't cover?
That is the normal case right now — the catalogue is two topics. Adding one means building its shape and its list of common mistakes, which is the work a design-partner slot is priced around. If your topic is on your compliance calendar for this year, that is the conversation to have.
Can we see one before we buy?
Yes, and that is the preferred first step. We would rather send you a module to import and run in your own LMS than book a demo call — you see it in the system it will actually live in, and your team sees it without a sales call in the way.
Run one in your own LMS this week
Tell us which platform you use and which topic is next on your compliance calendar. We will send a module you can import, run, and judge on its own terms.
Request a module