An audit is coming
You need evidence that every employee was trained, on a date, with a score. We build to SCORM so your LMS holds the record.
Fire safety, phishing, AML, manual handling. Built to hold attention and to stand up in an audit.
You need evidence that every employee was trained, on a date, with a score. We build to SCORM so your LMS holds the record.
The module is a slide pack with a voiceover and people click away. More slides will not fix it.
The same rule has to land in six languages without six reshoots. We build the master for re-versioning from the start.
Beat by beat, and roughly how much of the runtime each one takes.
We open on the thing the rule exists to prevent, played out, before anyone names a regulation.
The clause itself, in plain language, tied back to what the viewer just watched happen.
The same situation handled correctly, so the correct behaviour has a picture and not just a sentence.
The two or three grey areas your team argues about, answered on camera so nobody has to guess.
Scored questions that report back to your LMS, so completion is evidence rather than a tick.
15 in the library, 7 shown.
The techniques this kind of film is actually shot in. Each one links to a project that used it.
You send the policy, the regulation reference and the old module. We mark what is mandatory wording, what can be paraphrased, and what is missing.
A script in plain language with the mandatory clauses quoted verbatim, sent to whoever owns the risk before a frame is made.
Every scene drawn, including the incident sequence. This is where a compliance team catches a scenario that would not pass review.
Animation, voice over, sound, and the knowledge check authored against your LMS spec rather than bolted on afterwards.
We upload the SCORM package to a test LMS, confirm completion and score report correctly, then hand over masters and source.
Sectors we have already shipped this kind of film into, newest library first.
No two of these are priced the same. These are the four things that actually change the number.
A single eight-minute module costs more than one three-minute module, but a series of six brings the per-module cost down sharply.
Animation is quoted flat. A filmed incident needs a crew, a location and a day, so it moves the number most.
Re-versioning from a master built for it is a fraction of the original. Localising a module that was not built for it is close to a rebuild.
A five-question check is included. Branching scenarios where a wrong answer routes somewhere different are quoted separately.
Five things we see on this kind of film, and what we do in their place.
CommonThe module opens with the regulation number and the date it came into force.
InsteadIt opens on the incident, and names the regulation once the viewer already cares.
CommonA narrator reads the policy over slides of the policy.
InsteadThe policy is dramatised, then stated. Reading and watching do different jobs.
CommonCompletion is the only thing the LMS records.
InsteadScore, time spent and the questions people got wrong all report back, so you can see what is not landing.
CommonGrey areas are left out because they are hard to script.
InsteadThe grey areas are the reason people ask their manager. Those are the scenes worth the most.
CommonLocalisation is quoted as a second production.
InsteadVoice over, on-screen text and graphics are separated in the master, so a language is a re-version.
We deliver SCORM 1.2 or 2004 packages that report completion and score back to your LMS, so the record sits where an auditor already looks. Completion, time spent and assessment result are all tracked.
Yes, and it is the usual starting point. You send the policy, the SOP or the old deck, and we return a script and a storyboard for sign-off before any animation begins.
Scenario first, rule second. We open on the situation the rule exists to prevent, then name the rule. A narrated slide pack asks for compliance; a scenario earns attention first.
We keep the project files. A clause change is usually a voice over pickup and a few frames rather than a rebuild, which is far cheaper than starting again.
Yes. We separate voice over, on-screen text and graphics in the master so a new language is a re-version, not a new production. Ten or more languages with native casting.
You do, at script stage, before anything is animated. We mark which lines are quoted verbatim from the regulation and which are paraphrased, so your legal or risk owner reviews a short list rather than a whole script.
Yes, and for site safety it often works better because the hazard is specific to your floor. It needs a shoot day and a location, so it changes the quote more than any other choice.
That is your policy, not ours, but annual is the common cycle. Because we keep the project files, the refresh is usually a pickup on the clauses that changed rather than a new production.
Tell us what you need. We reply within 24 hours with a tailored recommendation, no fluff, just what works for your goals.
Looking for a job? See open roles →