| Way to update training videos | What it changes | Use it when | Watch out for |
|---|---|---|---|
| Patch | On-screen text, captions or one scene | Only a name, label, value or single shot is wrong | Narration that still says the old name, and captions left behind |
| Re-voice | Narration and captions are replaced together while the pictures stay | The steps hold but a policy line, a term or the language changes | Longer scripts need scenes retimed; an on-camera presenter will not match new audio |
| Rebuild | The script is rewritten from the approved SOP and new visuals are made for changed steps | Step order, equipment, a safety-critical decision or the assessment has changed | Old footage showing the old method, because learners copy what they see |
| Scoping the change | The old and new step lists side by side, from the process owner | Before choosing any fix | Judging scope from a quick viewing of the old module |
| Publishing the update | A version number and date on the file and closing screen, a change log, and the old file archived | After any fix, with the LMS record effect decided first | Replacing a package can affect learner records, as Moodle support guidance warns |
To update training videos after a process change, match the fix to what changed. Patch when only text or a single shot is wrong, re-voice when the steps hold but the words or language change, and rebuild when the sequence, equipment or decision points have moved. Then retire the old version so nobody learns from it.
Last reviewed: November 2026
Patch, re-voice, rebuild: a patch edits on-screen text, captions or one scene. A re-voice replaces the narration and captions while the pictures stay. A rebuild rewrites the script and shoots or generates new visuals for the changed steps.
What changed in the process, and how much of the video does it touch?
Scoping an update to training videos starts with the change record, not the video. Ask the process owner for the old step list and the new one side by side, then mark every step that moved, was added or was removed. That list decides the scope far better than a quick viewing of the old module.
Three questions sort most changes:
- Does the learner now do something different with their hands, tools or screens? If yes, the pictures are wrong.
- Has only the wording, a value or a name changed? If yes, the pictures may still be right.
- Has the order of steps or a decision point changed? If yes, the structure is wrong, and small edits will leave gaps.
For regulated processes, timing matters too. In the US, OSHA's process safety rule says affected employees "shall be informed of, and trained in, the change prior to start-up" of the changed process (OSHA 1910.119). Indian sites should check their own obligations with the safety officer, but the principle is a useful default: the training update is part of the change, not a task for later.
When is a patch enough to edit a training video?
Patching a training video is enough when the change is cosmetic or local: a renamed menu, a new form number, an updated helpline, a corrected value on a label. You edit the on-screen text or replace one short scene, update the captions, and export again.
Patches go wrong in two ways. The first is a narration that no longer matches the screen, because the voice still says the old name. The second is captions left behind. The W3C's captions criterion expects captions to carry dialogue plus who's speaking and meaningful sounds (W3C WCAG), so every visual or spoken edit needs a caption check as well.
When should you re-voice a training video instead?
Re-voicing a training video is the right fix when the steps and visuals still hold but what is said must change: a new policy line, a different term, a corrected instruction that the screen doesn't show, or a new language version. Narration and captions are replaced together; the edit timeline is mostly kept.
Re-voicing has limits. If the new script runs longer, scenes need retiming. If a presenter appears on camera, new audio will not match their lips, so the scene needs a cutaway, a new take or a different format. For other languages, each version needs its own script review by someone who knows the process in that language; our guide to training video localisation for Indian teams covers that review.
When do you need to rebuild a training module and its assessments?
Rebuilding a training module is necessary when the order of steps, the equipment, a safety-critical decision or the assessment has changed. Patching such a module leaves old footage showing the old method, and learners copy what they see, not what the narrator says.
A rebuild doesn't mean starting from nothing. The approved SOP is the new source, so the script can be rewritten from it, as described in turning an SOP into a training video. Unchanged scenes can often be reused if the project files are available. Whether the new visuals are filmed or generated is a separate choice; our comparison of AI and traditional training video production covers that trade-off.
Patch, re-voice or rebuild: a decision table for L&D teams
| What changed | Patch | Re-voice | Rebuild |
|---|---|---|---|
| Name, number, label or contact | Yes | Only if spoken | No |
| Policy wording, spoken instruction | No | Yes | If visuals contradict it |
| New language version | No | Yes, with review | If on-screen text is heavy |
| Step order or decision point | No | No | Yes |
| Equipment, tool or screen layout | One scene only | No | Yes, if several steps |
| Assessment questions or pass rules | Quiz only | No | If the module structure changes |
If two columns both seem to fit, choose the larger one. A partial fix that leaves one wrong step on screen costs more later, in retraining and in doubt about which version is right.
How do you publish the update without breaking LMS records?
Publishing updated training videos to an LMS needs a plan, because replacing a package can affect learner records. Moodle's own support guidance lists several ways to update a SCORM package, including replacing it in place or hiding the old activity and creating a new one, and warns that unlocking completion settings "will result in Moodle clearing the previous activity completion reports" (Moodle). The same article notes that learners midway through an old package can meet a blank screen after a replacement.
Before release, decide whether the change is a new version that learners must retake or a correction that keeps their completion. Test the upload with a dummy learner on your real LMS, then announce it.
Version control keeps the library honest:
- Put a version number and date in the file name and on the closing screen.
- Keep one change log per module: what changed, why, who approved it.
- Archive the old file and remove it from every playlist, share link and intranet page.
Where Probbit fits
Probbit produces safety, EHS and SOP training videos and other training modules, with people writing, reviewing and signing off the script. For updates, we agree language versions, revision ownership and project-file handover in the scope, and confirm the LMS package and acceptance test on your platform. If a process change is coming, schedule a call to plan the update before it goes live.
