Reply from a community member, 13 June 2025

Hey Ian, I thought I would fill you in on how I handle some of these things:

• How do you communicate to learners about updates or new versions of a course?

I utilize 'Teams' in Litmos. This allows for me to select the team and push out a course invite. We also give a heads up about the trianing so that the invite is expected. This is done to new courses and when revisions that need to have the course completed to match compliance.

• What do you do with learners who are partway through the current version?
  • Do you let them finish?
  • Transfer them to the new version?
  • Something else?

If it is a new course (replacing existing) then they all get a new invite. At the time a new course comes online, we remove the old one from the library and note it as 'inactive'. This way it no longer shows up in their library.

• Do you archive the old course or keep it live for a while?

We keep old courses. We note in the description if it has been replaced/retired and the date. We hold onto these courses for records purposes.

• Any tips for version control, naming conventions, or avoiding confusion?

If a course is revised, meaning a minor change, we note in the description course revised to v# and the date. If adding newer modules or attachments, these are then named the verion, i.e. v2. If the course has an annual requirement for compliance, the course receives the year on the end. This way we can track who was assigned for that year and the compliance completions. At the end of the year, it is inactive and removed from the library, but is still possible for future audits on completion.

Hope this helps - best of luck!

Amber