Mandated compliance content — such as harassment prevention training — requires learners to complete a course on a recurring basis, typically annually. Managing versions of this content requires a different approach to standard Go1 content updates.
The key question: Should you update your existing course, or publish a new version alongside it?
For mandated compliance content only, the answer is: publish a new version alongside it.
What Is Mandated Compliance Content?
Mandated compliance content covers topics where learners are legally or organizationally required to complete a course on a recurring basis — typically once per year. Common examples include harassment prevention, workplace safety, and data privacy training.
Go1's Versioning Policy for Compliance Content
For mandated compliance courses only, Go1's policy is to keep up to two versions live side-by-side in the library, rather than updating or overwriting the original course.
Note: This is an exception to Go1's standard content update practice. For non-compliance content, refer to Updating or Retiring Content: Best Practice.
Why Side-by-Side Versions — Not Updates?
Updating a course (overwriting the original learning object) causes problems for customers and learners:
Learners within the same cohort can end up taking different versions of a compliance course mid-rollout
Customers and channel partners receive no advance warning that content is changing
Compliance tracking becomes inconsistent and difficult to manage
What Counts as a New Version?
A new version must be materially different content — the same compliance topic covered with:
Fresh role-based scenarios
A different instructional approach or feel
New examples or updated context
Both versions must be fully compliant. Think of it like a reboot of a well-known film: the same core material, told anew.
Important: A minor content refresh or wording update does not constitute a new version. Use the standard update process for those changes.
Naming Convention
Distinguish versions clearly in the course title using version notation:
Harassment Prevention
Harassment Prevention v2
Include the following description in the course metadata:
"We offer different versions of this course to provide a fresh learning experience each year. All versions are fully compliant and up to date. Versions offer variety so learners do not take the same course twice."
What To Do (and What To Avoid)
✅ Do: Upload the new version as a separate learning object with a version-denoted title
✅ Do: Keep the previous version live in the library
✅ Do: Use version notation in the course title (v2, etc.)
🛑 Don’t: Update or overwrite the existing course — this disrupts learners mid-rollout
🛑 Don’t: Add more than one new version at a time
🛑 Don’t: Use vague or inconsistent naming that makes versions difficult to distinguish
FAQs
Can I publish more than two versions at once?
No. A maximum of two live versions should be available in the library at any time. If you are considering publishing a third version, work with your Content Partner Success Manager (CPSM) to retire the oldest version first.
Does this policy apply to all compliance content?
This policy applies to mandated compliance content only — topics where learners are required to complete training on a recurring basis. For all other content types, follow the standard Updating or Retiring Content: Best Practice guide.
What if my compliance content has minor wording updates rather than new scenarios?
Minor updates should be applied directly to the existing learning object, not published as a new version. A new version should represent materially different content.
Do I need to notify Go1 when publishing a new compliance version?
Let your Content Partner Success Manager know so they can help promote the updated content to relevant customers.
Need Help?
Contact your Content Partner Success Manager or the Go1 Support Team at [email protected] if you have questions about versioning your compliance content.