Every team that touches it field guide to safety training videos: Fixing safety training that is forgotten by the time it matters

The overlap between Learning and Development and IT and Cybersecurity here reflects a broader pattern: safety and compliance increasingly sit at the intersection of workforce training and formal governance, and treating them as fully separate functions tends to leave gaps neither team catches alone. Forgotten safety training touches Learning and Development, who own the training program, and IT and Cybersecurity, who often own related compliance and incident response procedures, particularly for anything touching regulated or security-adjacent processes.

What Every Team Should Evaluate First

• Does it generate from existing safety SOPs? Saves real time and ensures the video accurately reflects officially approved procedure rather than a separately-drifted script.
• Can content be revisited quickly outside of formal training sessions? The core requirement for addressing retention specifically, distinct from simply delivering training content once during onboarding.
• Does it track completion and support informal retention checks? Completion tracking alone doesn’t confirm the content will actually hold up when genuinely needed.
• Is update turnaround fast enough to match how often relevant procedures actually change? A slow update process means content chronically risks falling behind current, approved practice.

The Learning and Development Checklist

• Does it generate from existing safety SOPs? Saves real time and keeps content aligned with what’s officially documented and approved, rather than introducing a parallel, potentially inconsistent source.
• Can content be revisited quickly outside of formal training sessions? Essential for addressing the actual retention gap, since content locked into a once-a-year session doesn’t provide the ongoing reinforcement that durable retention requires.
• Does it track completion and support informal retention checks? Completion alone doesn’t confirm genuine, lasting understanding of a safety-critical procedure months after the original session.

How Learning and Development Teams Use Safety Training Video

Safety procedures get converted into short, specific videos that stay accessible well beyond the initial training session, giving workers something precise to revisit rather than relying on memory alone. Teams that get the most value from this build it into a broader safety culture initiative, treating accessible, revisitable video content as one part of an ongoing reinforcement strategy rather than a one-time replacement for the classroom session, combining both formats to cover both the initial learning and the long-term retention challenge separately.

The IT and Cybersecurity Checklist

• Does it handle safety and compliance-adjacent content precisely? Particularly important for any procedure touching regulated activity, where imprecise narration could create genuine compliance exposure.
• Is there a review step before publishing high-stakes content? Worth building in given the consequences of an inaccurate or outdated safety-compliance video reaching the workforce.
• Does update speed match how quickly relevant regulations or internal policy actually change? A slow update cycle for compliance-adjacent safety content creates accumulating exposure the longer it goes unaddressed.

How IT and Cybersecurity Teams Use Safety Training Video

Compliance-adjacent safety procedures get precise, reviewed video treatment, kept current as regulations or internal policy change, with particular attention to the accuracy of technical or regulatory detail that a general-purpose safety video might handle more loosely. Teams managing this well tend to build a specific review checkpoint into their compliance calendar, confirming safety-adjacent video content stays synchronized with whatever regulatory or policy updates have occurred since the last review, rather than assuming synchronization happens automatically without deliberate checking.

When These Two Teams Should Bring in a Third Stakeholder

For organizations with a dedicated safety or environmental health and safety function separate from both Learning and Development and IT and Cybersecurity, that team’s involvement matters as much as, and often more than, either of the two teams discussed here. Where a dedicated safety function exists, they typically hold the deepest expertise on which procedures genuinely carry the highest risk and what precise accuracy standards content needs to meet, making them a natural third stakeholder in prioritization and review even if they’re not directly responsible for producing or maintaining the video content itself. Organizations without a dedicated safety function, often smaller companies where safety responsibility is distributed across operational leadership, should identify whoever holds the closest equivalent expertise and involve them similarly, rather than defaulting entirely to Learning and Development and IT and Cybersecurity’s judgment on matters of genuine safety risk assessment.

Building a Shared Prioritization Process Across Teams

Rather than each team independently deciding which procedures matter most from their own perspective, Learning and Development focused on training gaps, IT and Cybersecurity focused on compliance exposure, a joint prioritization exercise tends to produce a more complete and defensible priority list. Bringing both perspectives together, along with a dedicated safety function where one exists, surfaces procedures that might be underweighted by either team working alone: a process with real compliance implications that Learning and Development wouldn’t naturally flag as a training priority, or a training gap with genuine safety consequence that IT and Cybersecurity wouldn’t independently identify as a compliance concern. This joint exercise doesn’t need to be elaborate, even a single working session reviewing the full list of safety-critical procedures together tends to surface a more balanced and complete prioritization than either team’s independent list.

Sustaining Cross-Team Collaboration Over Time

Cross-functional initiatives like this one often work well initially, when both teams are actively engaged in launching a new program, and then quietly lose momentum as each team’s attention returns to its own primary responsibilities and competing priorities. Building in a recurring, lightweight touchpoint, even a brief quarterly check-in between the relevant stakeholders from each team, specifically to review whether safety training content remains current and whether new high-priority procedures have emerged, tends to prevent this natural drift better than assuming the initial collaborative energy will sustain itself indefinitely without deliberate structure supporting it.

Frequently Asked Questions

What should any team check first before adopting safety training video?

Whether it generates from existing procedures and stays accessible beyond the initial training session, since in-the-moment access is what actually prevents forgotten steps from causing incidents, more than any other single factor in the evaluation.

Why does this matter to both Learning and Development and IT and Cybersecurity?

Because safety training spans both general workforce training, owned primarily by Learning and Development, and compliance-relevant procedures requiring the precision and formal review that IT and Cybersecurity typically brings to regulated or security-adjacent content.

How should these two teams divide responsibility in practice?

Learning and Development typically owns the broader training program and general safety content, while IT and Cybersecurity takes lead on anything touching formal regulatory compliance, with both teams coordinating on shared standards for accuracy and update discipline.

Is a formal review step always necessary before publishing safety content?

For anything touching regulated activity or genuinely high-consequence procedures, yes, a review step is worth the added time. For lower-stakes, routine safety awareness content, a lighter review process may be sufficient without meaningfully increasing risk.

How do we know if our current safety training approach has a retention problem worth addressing?

Look for incidents or near-misses correlating with content that was technically already trained, informal gaps in what workers recall weeks after training, and whether safety-critical content is genuinely accessible outside the formal training calendar.

What’s a good first step for a team new to this joint approach?

Identify one procedure that’s both high-consequence and compliance-relevant, convert it collaboratively with input from both Learning and Development and IT and Cybersecurity, and use that shared experience to establish a repeatable process before expanding further.

Try Safety Training Video for Your Team

The fastest way to evaluate this is against your single highest-risk procedure. Convert it, check the analytics after a few weeks, and let what you learn about where people actually struggle guide the rest of the rollout.

Try Velo for free · See how it works

Related reading

• Safety training that is forgotten by the time it matters doesn’t have to be the norm. Here’s safety training video - what safety training video is and how teams use it
• Safety training videos tools compared: Who actually solves safety training that is forgotten by the time it matters - comparison page
• Still dealing with safety training that is forgotten by the time it matters? Here’s what’s actually wrong - the cost of the problem, by team
• Building a repeatable safety training videos process that ends safety training that is forgotten by the time it matters - the workflow playbook

---

About the author

Ritu Parakh is Growth Lead at Velo, the AI video messaging platform that turns a screen recording, a deck, or a URL into a polished, narrated video - and an editable written doc. She writes about video for demos, onboarding, training, and enablement. Connect on LinkedIn