Author it once. Recognise it everywhere.
Some content belongs in every course: your GDPR module, your safety induction, the regulations unit your accreditation requires. Shared modules let you build that content once, attach it wherever it belongs, and stop making delegates sit through it twice.
The copy-paste curriculum problem.
Without shared modules, common content gets duplicated into every course that needs it, and every copy drifts out of date separately.
Duplicated content
- The same GDPR lesson pasted into fifty courses
- An update means editing every copy, and missing some
- Delegates repeat identical content in every course they take
- No answer to "which courses contain this material?"
- No record of why a delegate was marked complete
With Hotline
- One module, attached to every course that needs it
- Update the module once and every course carries the new version
- Complete it in one course and every other course credits it automatically
- A used-by view lists every course the module is attached to
- A recognition trail shows where and when each credit was earned
How shared modules work.
Build the module
Author it in the course builder or upload SCORM, exactly like any course. Modules live in their own library, hidden from the catalogue.
Attach it
Add the module to any number of courses, in the order you want, and mark it required where completion must be enforced.
Delegates get credit
A delegate who completes the module in one course is automatically credited in every other course that includes it, within the recency window you set.
Update on your terms
When the material changes, publish the update. Keep existing completions valid, or require everyone to complete the new version.
Recognition that respects time.
Recognition is not forever. Each module carries a recency window, so a completion from last month counts everywhere while one from five years ago is treated as expired knowledge and taken again. You decide what "recent enough" means, per module.
- Per-module recency windows: 6, 12, 24 months, or whatever the standard requires
- Required modules gate completion of the parent course
- Classroom and manual completions credit modules too
- Finishing the last outstanding module completes the parent course automatically
- Every credit is logged: where it was earned, when, and what it satisfied
Built to manage, not just attach.
Shared module questions
Shared modules are included from the Professional plan, alongside prerequisites and learning paths. See the plan comparison for the full breakdown.
Anything a course can. Modules are authored in the same course builder or uploaded as SCORM packages, and they play in the same players delegates already use. If you can build it as a course, you can share it as a module.
You choose. Publish the update and keep existing completions valid, or bump the version and require everyone to complete the new material. Before you decide, Hotline shows how many live recognitions the change would affect.
Yes. With training management, a module delivered in person can be credited on delivery, and blended courses can require shared modules as pre-work before the training day.
No. Delegates just see the module as part of their course, with their progress carried across. The sharing, recognition, and versioning machinery is admin-side only.
Stop maintaining fifty copies of the same lesson.
See shared modules and recognition running on a demo training business in a 30-minute walkthrough.