How to Update an Online Course Without Rebuilding It

Every course starts decaying on the day it ships. A system changes, a policy is revised, a regulation moves, someone points out that the screenshots are from two versions ago. The question is not whether it needs updating but how expensive updating is, and that is decided long before the first update.

What makes a course expensive to update?

Three things, all of them design decisions:

• Volatile content scattered throughout. If names, system screenshots and figures appear in eleven places, every update is a hunt.
• One large course instead of several small ones. A change to one topic means redeploying everything, and in an LMS that often means reassigning it too.
• Content locked in a format you cannot edit. Text baked into an image or a video is a rebuild, not an edit.

The corresponding habits are worth adopting before you need them: concentrate the perishable material, split by topic, and keep words as words.

What is the actual update process?

Edit the course, then export and redeploy. The important thing to understand is that these are two separate acts, and the second one is the one people forget.

A SCORM package is a file. Once uploaded to an LMS it is a copy that has no connection to the original. Editing the course here does not change the file sitting in Moodle, Canvas or anywhere else. It has to be exported again and uploaded again, and depending on the platform, that may create a new activity rather than updating the existing one.

Should I replace the SCORM package or add a new one?

It depends on whether completion history matters.

• Replacing in place keeps the existing completion records attached, which is what you usually want for a minor correction. Most platforms support this, though the exact mechanism varies.
• Adding a new activity resets everyone to incomplete, which is what you want when the content has changed enough that a previous completion no longer means anything.

That second case is a judgement about substance, not convenience. If the update changed what someone is expected to do, their old completion is evidence of nothing.

How do I keep track of what changed?

Keep the exported package for every version you deploy, filed by date. This sounds like bureaucracy and it is the single most useful habit in compliance-adjacent training.

The question you will eventually be asked is not "what does the course say" but "what did this person see when they completed it in March". Only the March file answers that. The current course cannot, and neither can your memory.

Do I need to tell people about updates?

For anything that changes what they should do, yes — and not through the LMS. Reassigning a course notifies people that they have a task, which is not the same as telling them something has changed.

A short note saying what changed and why, sent by a person, does more than a reassignment. It also makes the reassignment feel purposeful rather than administrative, which measurably affects whether people engage with it rather than clicking through.

What about small corrections?

Batch them. A typo, a rephrased sentence and a corrected date do not each justify a redeployment cycle, and a stream of updates trains people to ignore update notices.

Keep a running list and ship them together on a schedule — quarterly suits most courses. The exception is anything factually wrong in a way that could lead someone to act incorrectly, which goes out immediately regardless of the calendar.

How does this work if I edit in Word?

If you maintain the source document and re-import, be clear that re-importing creates a new course rather than merging into the existing one. That is fine when the document is genuinely the master and you have made no edits in the course editor, and it quietly discards work when you have.

Word export is the other direction and often the better fit for a substantial revision: export the course to Word, edit it with track changes so a reviewer can see what moved, then bring it back. That keeps the review in the tool your reviewers actually use.

The habit that pays for itself

Put a review date in the course description when you publish it. Not a promise to anyone — a note to yourself. Courses do not announce that they have gone stale, and a date is the only mechanism most teams have for finding out before a learner does.