Secure Compliance Training
With the spread of more powerful web browsers and fewer restrictions around devices and access, it has become easy to skip compliance training but still report full completion to the LMS. Firms that need reliable records for boards, regulators, and law enforcement eliminate this security loophole by using courses that run on the Salt Compliance Platform but still work with their LMS.
Unlike traditional courses that generate LMS reports that are both inconclusive in nature and limited in scope, Salt Compliance LearnerLogs provide records that are both more detailed and fully reliable, i.e. resilient against such hacks.
If you are responsible for training that carries legal implications, such as in compliance, safety, or medical training, Salt Compliance courses with LearnerLogs can help you capture reliable training evidence and eliminate this risk.
Comparing The Methods
Typical LMS Reports
After a compliance training roll-out, an LMS will typically provide the following information for each learner: start time, end time, total time, score, completion.
The problem with this model is that anyone can easily feed fake information into the LMS, thus invalidating the value of such reports. This exposes companies to various risks.
Salt Compliance LearnerLogs
LearnerLogs help companies raise the quality and quantity of evidence they collect and retain to prove that staff have taken the relevant trainings and passed the appropriate exams. In particular, LearnerLogs deliver two unique benefits:
- Reliability. Instead of using client-side reported learning data (SCORM or Tin Can) which can be easily faked, LearnerLogs relies on Salt Compliance server-side architecture to collect, assess, and store learner actions and responses.
- Completeness. Instead of relying on binary yes/no completion data, LearnerLogs provide the full, timestamped history of learner actions (moving to the next slide, answering a question, etc.) during taking a course.
This means that during regulatory audits or legal investigations, instead of saying “John Smith (probably) completed the training on 5 May 2014″, the compliance team can pick any employee, any course and just “replay” that particular person’s training to the regulators, second by second, based on data that is actually reliable.
The following screenshot shows what a typical LearnerLog looks like — it is effectively a feed that describes how someone completed the course, from switching between slides to answering each question and reviewing hints.
To see an expanded view of the LearnerLog as a web page in a new window, please click the image itself.