Make the right call
A compliance scenario where the learner handles three real situations at a logistics firm, decides what to do, and sees what that decision leads to. Open it and work through it now.
Built in Articulate Storyline and published to HTML5, so it runs on a desktop, a tablet or a phone with nothing to install. It is hosted here on our own site, so it opens in a new tab rather than inside this page.
The three situations
The Friday Request
Data protection. Your manager wants the full customer list sent to a personal Gmail tonight. Urgent, senior and entirely plausible, which is what makes it the hard one.
The Supplier Gift
Anti-bribery. A supplier bidding for your contract sends concert tickets worth $400. Refusing is easy to say in a policy and awkward to do in an inbox.
The Blocked Exit
Health and safety. A shift lead stacks pallets in front of a fire exit, just for tonight. Speaking up means contradicting someone more senior on their own floor.
Compliance training someone has to think about
Most compliance training asks a learner to agree that bribery is wrong. Nobody fails that. The difficulty in real life is never identifying the principle, it is applying it to a situation where the easy option is also the one your manager is asking for, at six on a Friday.
This module is built around that gap. Three situations, drawn from the three areas that generate the most awkward judgement calls: handling customer data, accepting things from suppliers, and safety shortcuts taken under time pressure. Each one is set at the same fictional company, Northwind Logistics, so the learner stays in one world rather than restarting in a new one every few screens.
How a situation is built
Each of the three opens with the setup in a sentence or two, then asks two questions, not one. The first is the obvious decision point. The second is what happens next, after the first choice has already narrowed the options, which is where most real compliance failures actually occur.
Every question offers three courses of action and a panel labelled What does the policy say?. That panel matters more than it looks. Letting someone check the rule at the moment they need it is how the rule gets remembered, and it mirrors what a sensible person does at their desk.
Why consequences beat correct answers
A choice here is confirmed, then played out. The learner sees what their decision led to rather than a green tick. That difference is the whole argument for scenario-based learning: a tick teaches that an answer was approved, a consequence teaches why.
The module also gates its own ending. All three situations have to be completed before the final screen unlocks, so a learner cannot sample one and claim the module. That is deliberate in compliance work, where the completion record is the thing an auditor eventually asks to see.
How it would be delivered
What you are playing is the published HTML5 build, hosted on this site. For a live rollout the same module is packaged as SCORM or xAPI and loaded into your LMS, where it reports completion and time. With xAPI it also reports which option a learner picked at each decision, so you can see which of the three situations is tripping people up and rewrite that one rather than the whole course.
This sits inside our custom e-learning development services. If you are weighing up tracking, our guide to SCORM and xAPI covers the decision, and instructional design models covers how a scenario like this gets scoped before anyone opens Storyline.
Frequently asked
What is a branching scenario in e-learning?
Why use a scenario instead of a quiz for compliance?
How long should a compliance scenario be?
Can a branching scenario be tracked in an LMS?
Can the situations be rewritten for our industry?
Need a compliance module people cannot click through?
Tell us the decisions your team actually get wrong. We come back within one business day with a scope and timeline.