Updating Compliance Training Every Year Without Rebuilding It
Compliance training has a rhythm: every year the policy date changes, a regulation gets a new clause, a logo is refreshed, or one statistic is updated. The content is 95% the same as last year. Yet teams routinely treat the annual refresh as a rebuild — reopen the source file (if they still have it), re-export, re-upload — and inherit a fresh round of QA, new identifiers, and the risk of wiping the records they are legally obligated to keep. There is a leaner way.
The annual update is usually a small edit, not a rebuild
Be honest about what actually changed. Most annual compliance updates are some combination of:
- A date — "valid for 2026," a "last reviewed" stamp, a copyright year.
- A few sentences — a revised policy line, an updated definition, a new regulatory reference.
- A statistic or figure that gets refreshed each cycle.
- Branding — an updated logo or color after a rebrand.
- A single new or replaced slide for a new requirement.
Every one of these is editable directly in the published package. On-slide text, images, and titles live in the course data, separate from the player engine. You do not need to regenerate the course to change a date or a paragraph — and not regenerating it is exactly what protects your records.
Why rebuilding endangers your records
Learner records — who completed the training, when, with what score — are stored by the LMS and keyed to the course identity. When you replace a package, many LMSes treat the new upload as a different course or reset the activity, detaching learners from their prior completions. For a marketing course that is annoying; for compliance training it is a problem, because those completion records are the evidence that your organization trained its people. Lose them and you may be unable to demonstrate compliance for a period you actually covered.
Decide deliberately: refresh records or preserve them
There is a real fork here, and it should be a conscious choice, not an accident of how you happened to upload the file.
- Cosmetic or minor change (date stamp, typo, logo refresh): preserve records. Everyone who completed last year is still compliant; making them retake adds cost and annoyance for no benefit.
- Material change (new regulation, substantively new policy, new required content): you may want everyone to retake it, so resetting completion is correct. The danger is resetting by accident for a trivial fix.
The principle: let the substance of the change decide whether learners retake, and never let the mechanics of your tooling make that decision for you.
The audit trail matters as much as the content
Compliance is not just about having current content — it is about being able to prove what changed, when, and by whom. When an auditor asks why the 2026 version differs from the 2025 version, "we edited the policy date and one definition on March 14" is a far stronger answer than "we rebuilt it." Keeping a record of exactly what was edited turns the annual refresh into documented evidence rather than an untracked change.
A safe annual-update checklist
- Export current completion and score data first, as insurance.
- List exactly what changed this cycle, and decide per change whether it warrants a retake.
- Make the smallest edit that solves it — change the text and images in the published package rather than re-exporting.
- Keep the manifest and item identifiers stable so the LMS recognizes the same course.
- Use the LMS in-place "update content" action, not delete-and-re-add.
- Test on a copy: confirm a prior completion still shows and the new content appears.
- Keep a record of what was changed for the audit trail.
The cheapest, safest annual refresh changes as little as possible: same course identity, same records, only the words and images that genuinely had to change this year.
Making the yearly edit in the browser
ScormEdit is built for the annual refresh: edit the dates, text, statistics, and logos in your published SCORM package without re-exporting, keeping the manifest and identifiers intact so your LMS treats it as the same course and your completion records survive. It works from the .zip you already have, needs no source file, and produces a record of precisely what changed — useful evidence, year over year, that the update was a content tweak rather than a brand-new course.