Illustrated cover reading "Course Version Control" on a seafoam green background with a waves pattern

Course Version Control: How to Manage Updates When Regulations Change

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

Course version control is the practice of numbering, recording and releasing every change to a training course, so you can show which version each learner took and why it changed. This guide covers eLearning courses, not Git. When a regulation changes, it also tells you who must retake the course and who can keep their progress.

Below you get a version record, a three-tier rule for regulation changes and a comparison of how six tools treat learners in progress. None of it is legal advice. Retraining duties come from the regulation text and your client’s compliance team.

Key takeaways

  • Record every release with a version number, reason, source regulation, approver and learner action.
  • Classify each regulation change as Patch, Minor or Major. Only a Major change forces a restart and a new completion record.
  • Several tools keep in-progress learners on the old version by default, which is the wrong outcome when the rule changed.
  • Standard LMS reports may not show which package version a learner used, so keep your own release log.

Disclosure: SimpliAuthor is a SimpliTrain product, made by the company that publishes this site. It appears once, near the end.

What is course version control and why does it matter when regulations change?

Course version control is a set of rules for labeling each release of a course, recording what changed and why, and deciding how learners move to the new release. It matters when regulations change because clients and auditors ask which version a learner completed, and many LMS defaults cannot answer that.

As of October 2026, results for the bare phrase are mostly Git tutorials, and eLearning results are mostly short vendor help pages, such as Nimble’s guide to keeping versions of courses, which suggests a spreadsheet register for audits. Few connect versioning to a rule change.

Without a policy, old content stays live after a rule changes, learners in progress finish the outdated version, and nobody can prove who took what.

What should a course version control record contain?

A course version control record should hold the version number, release date, change summary, reason, source regulation, approver, learner action and a link to the archived package. Keep one row per release in a shared register. The register then doubles as audit evidence, as the Nimble guide above suggests. The table is our suggested template.

Field What to write
Version Major.Minor.Patch
Release date and effective date When it went live, and when the rule applies
Change summary One sentence a learner could read
Reason and source Regulation, section and link, or client request
Impact tier Patch, Minor or Major
Learner action Who restarts, who keeps progress, deadline
Approver Named person and date
Archive link Path to source files and published package

How should you number course versions?

Number course versions as Major.Minor.Patch. Major means the requirement or assessment changed, Minor means content changed under the same requirement, and Patch means a fix that does not change meaning. This scheme is our recommendation, not a SCORM or regulator standard.

A Docebo Community discussion (posted 2022) advises keeping version numbers out of learner-facing titles, so store the full number in an admin field and the register.

How do you assess a regulation change before you touch the course?

To assess a regulation change, capture the rule and its effective date, map it to the course modules and quiz items it touches, classify the impact, and decide who must retrain by when. Do this before anyone opens the authoring tool.

  1. Capture the change. Save the regulation text, section number, jurisdiction and effective date.
  2. Map it. List the modules, learning objectives, quiz questions and certificate wording it touches.
  3. Classify it. Assign Patch, Minor or Major using the tier table below.
  4. Decide the audience. Name who must retake, who keeps progress and the deadline.
  5. Edit and test. Update the source, publish a package and test it in a sandbox.
  6. Approve. Get the named approver’s sign-off before release.
  7. Release and record. Publish, apply the learner action and complete the register row.

Pro tip: Build a Regulation-to-Module Map Once. Keep a sheet listing each regulation section beside the modules and quiz items that teach it. Next time a rule changes, step 2 takes minutes.

Which regulation changes require a major version and a retake?

A regulation change requires a major version and a retake when it alters what a learner must know or do, such as a new duty, threshold, deadline or correct quiz answer. The regulation text and the client’s compliance team decide this, not the LMS default. Two U.S. rules show how regulations define their own triggers.

OSHA’s hazard communication standard, 29 CFR 1910.1200(h)(1), says employers must train employees on hazardous chemicals “at the time of their initial assignment, and whenever a new chemical hazard the employees have not previously been trained about is introduced into their work area,” according to the OSHA standard text.

The HIPAA privacy rule, 45 CFR 164.530(b)(2)(i)(C), requires training for workforce members “whose functions are affected by a material change,” “within a reasonable period of time after the material change becomes effective.” It also requires the covered entity to document the training, per the eCFR text. The word “reasonable” is a judgment for the client’s compliance officer.

The tier table turns those triggers into a working rule. It is our model, built from these sources and untested with a client.

Tier Typical trigger Version bump Learner action What to record
Patch Typo, broken link, caption fix. The requirement is unchanged. 3.1.0 to 3.1.1 None. In-progress learners keep progress. Completions stand. Release log line
Minor Clearer wording, new example or updated screenshot under the same requirement and pass criteria 3.1.1 to 3.2.0 No retake. Optionally let in-progress learners finish on the old version. Log line plus a note on why no retraining is needed
Major New duty, changed threshold or deadline, new hazard, changed quiz answer or pass mark 3.2.0 to 4.0.0 All affected learners take the new version by a set deadline. In-progress learners restart. Impact assessment, approver, effective date, list of learners retrained

Have the client’s compliance lead or counsel confirm the tier for any Major or borderline change.

What happens to learners in progress when you upload a new SCORM version?

What happens to learners in progress depends on the LMS and its setting. Some tools keep in-progress learners on the old version, some restart them, and some let you choose. Read your own LMS documentation and test with a dummy learner, because defaults differ and can contradict your tier decision.

The table summarizes each tool’s published documentation as of October 2026. Dates are page dates we saw, so re-check before relying on any row.

Tool Learners in progress To get the other outcome Source and date
SCORM Cloud Default “Never” keeps existing registrations on the old version. Choose when registrations move, such as “Always”. Moving loses progress on the old version. SCORM Cloud versioning article, updated June 2021
Content Controller (Rustici) You pick Restart or Maintain Progress when you publish. Rustici advises Maintain Progress for minor changes and Restart for compliance overhauls. Rustici support article, updated August 2024
Go1 In-progress learners stay on their original version. Completion records do not change. Deleting enrolments forces the new version, irreversibly erasing saved progress. Go1 help article, July 2026
SmarterU In-progress learners do not get the new version automatically. Unenroll and re-enroll them, which restarts the course. SmarterU support article, undated
Acorn A significantly updated SCORM file may not load for learners partway through. Select Delete Old Attempts when updating. Acorn help article, September 2026
Docebo Forum thread cites Docebo support: versioning restarts in-progress learners. The same thread prefers overwriting for minor edits. Docebo Community, 2022 to 2025

The sources disagree on defaults, so match the setting to your tier. Rustici’s guidance maps cleanly onto Patch and Major. Go1’s documentation shows the opposite default: keep learners on the old version. For a Major regulation change, an old-version default is a compliance gap, so plan to force the restart.

Should you overwrite the file, version it in place or publish a new course?

Overwrite the file only for Patch fixes, version it in place for Minor changes where you do not need version-level reports, and publish a new course for Major regulation changes. A new course keeps old completions attached to the old content, which is what auditors ask to see.

  • Overwrite the package. Choose it for typos and broken links. Do not choose it when quiz structure or completion rules change.
  • Upload as a new version in the same item. Choose it for Minor updates and easy rollback. Do not expect to filter completions by version, as one Docebo thread reports.
  • Import as a new item and hide the old one. Choose it for Major changes and compliance. Reporting is more complex, but you can tell which learners took which version.

Ideagen’s help article (updated November 2024) draws the same line: minor edits stay in the existing course but cannot be reported as V1 versus V2, while major changes get a new course.

Pro tip: Test the Restart With a Dummy Learner. Before release, enroll a test learner halfway through the old version, upload the new one and watch what happens. Vendor pages describe defaults, but only your LMS shows what your tier decision triggers.

How do you keep source files and packages under course version control?

Keep source files and published packages together in one folder per version, with the register row pointing to it. A practitioner reply on the Articulate Community forum (about 2022) uses one subfolder per version holding source files, LMS files such as the SCORM package, and supporting files such as design documents and reviews.

Git is the other option. An eLearning Industry article (October 2018, updated May 2021) describes repositories, branches and a core-plus-country model in which a central team owns the main course and local teams branch it. Our judgment, untested: use Git for text sources and client variants, and folder-per-version for authoring-tool project files on a small team.

If you only have the published package, see the guide to editing a SCORM file without the source files. For rescuing older client courses, use the update-old-SCORM-courses checklist.

How do you prove which version a learner completed?

Prove which version a learner completed by recording the course version beside each completion, either in the LMS or in your own release log. Do not assume the LMS does it. Go1’s documentation says its standard reports do not show which ZIP version a learner used, so it advises keeping your own release log.

AccessPlanit’s guide to training audit trails (undated, copyright 2026) lists course version among the course details an audit trail should include.

Before you publish a new version, run the checks in the guide to testing a SCORM package before it reaches a client’s LMS. If clients use different platforms, see SCORM compatibility across LMS platforms.

What should you do next?

Start with one course: add a version record row, classify your next change as Patch, Minor or Major, and test how your LMS treats an in-progress learner in a sandbox. That one exercise exposes most gaps before the next deadline arrives.

Then fold the seven steps into your review flow, which the course development process for small training teams describes from SME to publish.

Based on the vendor’s published documentation, SimpliAuthor’s free SCORM Converter turns PDF, PPT, Word and MP4 files into SCORM 1.2 or 2004 packages up to 95 MB, and the paid Visual SCORM Editor is described as editing compiled SCORM without the source files. We did not test either for versioning. To see versioning handled inside an LMS, you can request a SimpliTrain demo.

Frequently asked questions

What is course version control?

Course version control is a set of rules for numbering each release of a training course, recording what changed and why, and deciding how learners move to the new release. It lets you show which version each learner completed. It is separate from learning Git, though Git can be one tool for storing course source files.

Do learners have to retake a course when a regulation changes?

It depends on the regulation text. OSHA’s hazard communication standard requires training when a new chemical hazard is introduced, and HIPAA requires training for staff affected by a material change within a reasonable period. Ask the client’s compliance lead or counsel, because retraining duties are legal questions, not LMS settings.

What happens to a learner’s progress when you upload a new SCORM version?

It depends on the LMS. Go1 keeps in-progress learners on their original version, SCORM Cloud keeps them there by default, and Rustici’s Content Controller lets you choose Restart or Maintain Progress. Moving learners can erase progress on the old version, so check your platform’s documentation and test first.

How do you track which version of a course a learner completed?

Record the version number next to each completion, in the LMS if it supports version reports or in your own release log if not. Go1 says its standard reports do not show the ZIP version used. Archive each version’s package so you can reproduce what the learner saw.

How often should compliance courses be reviewed?

The regulation and client contract set the real schedule. As starting points, Absorb’s compliance article (September 2025) suggests every 12 to 18 months and after major regulatory updates, and a Docebo Community thread suggests a review date about one year after first publishing. Both are vendor or practitioner guidance, not rules.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.