Modules
A module is one thing your team needs to retain: an SOP, a regulation, a product line, a playbook. The container you build training around.
What you publish
A module is the thing you, as a team admin or a module admin, hand to your team. One SOP. One regulation. One product line. One clinical protocol. One customer-service playbook. Build it once, publish it, and HeyLoopy keeps it warm in your people’s heads from then on.
Inside the module live the lessons that break the subject down. From those lessons, HeyLoopy generates the drills your team sees in their Daily Loops .
How you build one
You start a new module, give it a clear subject, and point HeyLoopy at the source documents that already define it. Loopy reads them and drafts a first pass of lessons and drills for you to review.
The review step is the whole job. You edit what Loopy drafted, kill the ones that miss the point, add the ones the source did not say but your team needs to know. Loopy proposes; you publish. Nothing reaches a member until you say it does.
What happens after you publish
When you enroll a team member in a module, two things change for them:
- The module’s drills start showing up in their Daily Loop on the spacing schedule.
- Their mastery on each lesson begins tracking, so you can see which parts of the material the team has actually internalised.
A member can be in several modules at once. The daily-loop time budget is per-member, not per-module, so studying three procedures at once still takes a minute a day. The schedule handles the balancing.
How to scope a module
Module scope is a real design choice and HeyLoopy supports either direction. Pick the shape that matches how your team actually thinks about the material.
A few broad modules. One module per role, one per program, one per certification. Easier to administer when you have a small team or when the body of knowledge naturally hangs together. The trade-off: mastery rolls up to a coarser bucket, so “78% mastered on Field Service Safety” tells you less than you might want about which specific procedure is shaky.
Many narrow modules. One module per SOP, one per regulation, one per protocol. Easier to keep current when a single source document changes, and you get sharper mastery signal: you can see, line-item, which procedure your team has cold and which still needs work. The trade-off: more modules to manage and more enrollment decisions.
Most teams end up somewhere in the middle. A common pattern: broad modules for the always-on baseline (“Workplace Conduct,” “Customer Service Standards”), narrow modules for the high-stakes specifics (“Lockout-Tagout for Distribution Panels,” “Refund Authorization Limits”).
Either way, the structure is not permanent. You can split a broad module into narrower ones later, or roll narrow modules into a single program. Enrollment is also fluid: you can add or remove people from any module as roles change, as new hires arrive, or as a procedure becomes relevant to a different team. See How to manage module members .
When the source changes
When the underlying SOP or regulation gets updated, you update the module. HeyLoopy tracks the change and re-exposes affected drills so the team picks up the new version before it slips into old muscle memory. You do not have to re-train everyone from scratch.