Most organisations budget carefully for the first version of a training library. Very few budget for the second. Two years on, an SOP has been rewritten, a regulator has published updated guidance, and the ERP system in your onboarding module now has a completely different interface. The library still plays, but half of it teaches behaviour your compliance team would fail on audit.
This is the quiet problem with training video. Production is a project; accuracy is a programme. The organisations that get years of value out of a training library are the ones that planned for change before they shot a single frame. The ones that treat every update as a fresh production tend to stop updating altogether, and the library dies of neglect somewhere in year three.
This article covers how to build and maintain a modular training library so that updating training videos when procedures change is a scheduled, contained piece of work rather than a crisis. It looks at shooting for modular replacement, deciding between a reshoot and a re-edit, retaining raw assets, and mapping version control to your LMS records so audit trails hold up.

Training video for Solas produced by One Productions
Why Training Libraries Age Faster Than Anyone Plans For
Ask an L&D manager how long they expect a compliance module to stay accurate and the usual answer is three to five years. Ask them to audit what they actually have and the picture is different. In regulated sectors, something in the content stack moves most quarters.
The four things that break a module
- Procedural change. An SOP is revised, a step is added, a sign-off moves to a different role. The module now demonstrates a sequence that no longer matches the controlled document.
- Regulatory change. Updated HSA guidance, a revised EU directive, new HPRA or HIQA expectations, GDPR interpretation shifting. Often the practice is unchanged but the framing, terminology, and stated obligations are not.
- System and UI change. The most common and most underestimated. Any module containing screen recordings of an LMS, HRIS, EHR, or ERP is on a clock set by someone else’s product roadmap.
- Organisational change. Rebrands, site closures, restructures, and the presenter who has since left. A module fronted by a departed operations director quietly loses authority.
Track those four vectors against a library of thirty modules and you will find that something needs attention roughly every eight to twelve weeks. That is your real training content refresh cycle, and enterprise L&D teams tend to discover it retrospectively.
The cost of not having a maintenance plan
When there is no version-control approach, three things happen in sequence. First, out-of-date modules stay live because pulling them leaves a gap in mandatory training completion. Second, trainers start prefacing sessions with verbal corrections, which never make it into the record. Third, the whole library loses credibility with learners, who begin to treat all of it as approximate.
None of that shows up in a production invoice. It shows up in audit findings and in retraining costs.
Shooting for Modular Replacement
The single highest-leverage decision in a training programme happens at pre-production, long before anyone thinks about maintenance. Structure the content so that individual pieces can be swapped without disturbing everything around them.

Training video for CPAS produced by One Productions
Design at the segment level, not the module level
A twenty-minute module built as one continuous flow is a single object. Change one procedural step and you re-open the entire edit, potentially the entire shoot. The same twenty minutes built as eight discrete segments, each with a clean in and out point, is eight objects. Change one step and you replace one segment.
In practice this means:
- Map segments to controlled documents. Where a module covers three SOPs, build three segments, each fully self-contained. When an SOP is revised, the affected segment is immediately identifiable.
- Avoid narrative carry-over across segments. A presenter saying “as we saw in the last section” locks two segments together permanently. Keep each segment able to stand alone.
- Use consistent framing, lighting, and locations. If a segment is reshot eighteen months later, a documented lighting and camera setup means the replacement cuts in without a visible seam.
- Build bookends separately. Titles, intros, learning objectives, and outros should be separate assets, not baked into the segment renders. Rebrands then cost hours, not weeks.
Isolate the volatile content
Some content ages predictably. Screen recordings, dates, named individuals, statistics, regulation numbers, and site-specific detail all have short half-lives. Fundamental safety principles, behavioural coaching, and demonstration of physical technique tend to last.
Separate the two in the edit structure so that volatile content lives in replaceable layers. Screen captures held as overlay sequences with generic voiceover can be re-recorded and dropped in. Regulation references delivered as lower-third graphics rather than spoken lines can be updated with a graphics render and no talent involvement at all.
This is the core discipline of modular training video production, and it is a briefing decision as much as a technical one. Tell your production partner at the outset that the library must survive change, and the whole structure of the shoot changes.
Scripting with maintenance in mind
Small scripting habits pay back for years. Avoid spoken dates where an on-screen graphic will do. Avoid naming specific software versions in voiceover. Refer to roles rather than individuals. Where a figure is likely to move, put it on screen rather than in the audio track, because updating a graphic is trivial and re-recording a voiceover line in a matching acoustic environment two years later is not.
Reshoot or Re-Edit: Making the Call
When a change lands, the first question is scope. Getting this wrong in either direction is expensive. Over-cautious teams reshoot when a graphics update would have done. Over-optimistic teams patch with text overlays until a module looks like a palimpsest.
When a re-edit is sufficient
- The change is terminology, a regulation reference, a date, or a statistic that appears as on-screen text or graphics.
- A step has been removed and the remaining sequence still reads logically.
- The change affects narration only and you can record a voiceover pick-up in a matching acoustic setup.
- The system UI has changed but the workflow has not, so a fresh screen capture drops into existing overlay slots.
- Branding, titles, or contact details need updating and those elements were built as separate assets.
When a reshoot is the right answer
- A physical procedure has genuinely changed and the footage shows the wrong action. No amount of editing fixes a demonstration of a superseded technique.
- New PPE, equipment, or environmental standards are visible in shot and now non-compliant.
- A new step has been inserted mid-sequence and there is no coverage to bridge it.
- The on-camera presenter has left and their continued presence undermines the content’s authority.
- Accumulated patches have degraded the module to the point where learners notice the joins.
The middle path: partial reshoot
Most real-world updates land here. One segment out of eight needs new footage; the rest is fine. A half-day shoot with a small crew, matched to the original setup, replaces the affected segment and the module is back in service within a fortnight.
This is only possible if two conditions were met at the original production: the segments were built as discrete assets, and the technical setup was documented. A camera and lighting continuity sheet from the original shoot is worth more to a maintenance programme than any other single deliverable. If you are commissioning training video now, ask for one explicitly.

Training video for The UN produced by One Productions
Retaining Raw Assets: The Insurance Policy Nobody Reads
Two years after delivery, the difference between a two-hour re-edit and a full reshoot is usually whether anyone kept the rushes. You’d be surprised how often the answer is no, or “probably, somewhere”.
What to keep, and for how long
- Camera original footage. All of it, including unused takes and alternate angles. Alternate coverage is what makes a mid-sequence insert possible without a reshoot.
- Project files. Editing timelines, motion graphics projects, and colour grade settings, with fonts and asset dependencies collected.
- Separated audio stems. Voiceover, sync sound, music, and effects held as separate tracks so one narration line can be replaced without rebuilding the mix.
- Text-free master renders. A clean version with no burned-in graphics, which makes localisation and text updates straightforward.
- Setup documentation. Lens choices, camera height and distance, lighting diagrams, location details, wardrobe notes.
Agree the retention terms in the contract
Archive is a cost, and production companies do not hold multi-terabyte projects indefinitely by default. Settle three points before the project starts: how long raw assets are retained, who holds the archive, and whether project files transfer to you on delivery or remain with the producer.
For regulated training libraries, a five-year minimum retention is a sensible baseline, aligned to how long the training records themselves must be kept. Some clients take a full copy of everything on delivery and hold it in their own storage. That works, provided someone in the organisation knows the archive exists when the SOP changes.
Version Control That Maps to Your LMS and Audit Trail
Production-side versioning and LMS-side versioning are frequently disconnected, which is where audits get uncomfortable. The question an auditor asks is not “is the training current?” It is “can you demonstrate which version of this module a named employee completed on a given date, and what that version said?”
A workable versioning convention
Keep it simple enough that non-production staff can use it. A three-part scheme covers most enterprise needs:
- Major version (v2.0, v3.0) for changes that alter learning outcomes or procedural content. These normally trigger retraining for anyone who completed a prior version.
- Minor version (v2.1, v2.2) for corrections that do not change what the learner must do. Updated branding, a corrected regulation reference, a re-recorded screen capture of an unchanged workflow.
- Effective date and source document reference in the metadata, tying the video version to the SOP or regulation revision it reflects.
Carry that identifier everywhere: the file name, the LMS course record, the on-screen end card, and the production archive. When the auditor asks, you produce a single mapping table rather than an archaeology project.
Handling superseded versions in the LMS
Resist deleting old versions. Archive them as inactive but retrievable. The completion record of an employee who trained on v1.3 in 2024 is only meaningful if v1.3 still exists somewhere and can be produced on request. Training video version control in an LMS is fundamentally a records-management exercise, and deletion destroys evidence.
Deciding who needs retraining
Tie the retraining trigger to version type rather than to a calendar. A major version release means everyone in scope repeats the module. A minor version means the content is silently updated and no completion records reset. Documenting that rule once, and applying it consistently, removes an argument that otherwise recurs with every update.
Build a refresh calendar, not a reactive queue
The most stable programmes review the whole library on a fixed cycle, typically annually, and treat urgent regulatory change as an exception that interrupts it. A scheduled review with a standing budget line is a fraction of the cost of periodic emergency remediation. It also means production capacity can be planned, so multiple segment updates are batched into a single shoot day instead of three separate mobilisations.
If you are at the earlier stage of building a library rather than maintaining one, our wider work across corporate training and internal communications video covers the production side of getting a programme off the ground.
Frequently Asked Questions
How often should we review our training video library?
An annual full-library review works for most organisations, with an exception process for regulatory changes that cannot wait. If your library contains significant software screen capture, move to a six-monthly review for those modules specifically, because UI changes arrive on the vendor’s schedule, not yours.
Is it cheaper to reshoot a whole module or update segments?
Segment updates are substantially less expensive, provided the original production was built modularly and the raw assets were retained. Where those conditions were not met, a full reshoot is often the more economical route, because reverse-engineering a monolithic module usually costs more in edit time than it saves.
What should we keep from the original production?
Camera original footage including unused takes, editing and graphics project files, separated audio stems, a text-free master, and technical setup documentation. Agree retention periods and ownership in the production contract rather than assuming they are covered.
How do we handle version control across a multi-site or multilingual library?
Version the source language master and treat localised versions as dependent children of it. When the master moves to v3.0, every localisation inherits a pending update flag. Text-free masters and separated audio stems make that process practical; without them, each language becomes an independent maintenance burden.
Does a minor content change require retraining employees who already completed the module?
That depends on whether the change alters what the learner must do. Corrections to branding, terminology, or a regulation reference generally do not warrant retraining. Any change to a procedural step, a safety instruction, or a stated obligation normally does. Define the rule in your training governance documentation and apply it consistently, so the decision is not relitigated each time.
Building a Library That Survives Its Own Success
A training library becomes an asset rather than an operational burden when it is produced once and maintained well for years. That outcome is decided at pre-production, in decisions about segment structure, asset retention, and how volatile content is isolated from stable content. Retrofit it later and you are paying twice.
For L&D and compliance owners, the practical takeaway is to brief maintenance into the original scope. Ask your production partner how the library will be updated in year three, and judge the answer as carefully as you judge the showreel.
If you are planning a new training programme, or looking at an existing library that has drifted out of step with your procedures, we are happy to talk through the options. Get in touch with One Productions for a straightforward conversation about scope and approach.
Written by Freddie, One Productions.