Picture the classic generic safety video. A narrator with a radio voice explains the rules with total confidence. They're perfectly good rules, too. They just belong to someone else.
That was the problem facing a public utility in the Pacific Northwest. Its safety training came from a big generic content library, and the library kept citing federal OSHA standards. The utility trains to state safety rules that are stricter than federal OSHA, plus its own company policies that go further still.
The usual fix for bad training sounds simple: get a better platform. Then someone says the words "LMS migration," and the room goes quiet.
An LMS migration is a big headache. We get it. So this utility didn't do one. They kept the LMS they had and added AI agents that build courses from their own rules. No new LMS, no migration, and no more paying for training nobody uses.
Their story is the proof that your organization can think this way too: don't migrate, add.
The problem, part one: the wrong rulebook
Their safety lead walked us through how training works there. Most of it is required every year:
"We deliver a lot of our required training through our monthly safety meetings."
Crews get it in person. Anyone who misses the meeting gets a video, and other staff just get the video.
For years, much of that content came from a subscription to a generic training-content vendor. The trouble was the rules it cited. As the safety lead told us, their state is "very strict compared to a lot of states," and the old content "would reference OSHA standards and they're different here."
That's not a typo you can fix with a sticky note. When training quotes the wrong standard, the people who know the real rules stop trusting it, and everyone else learns the wrong thing.
The problem, part two: paying a fortune for content nobody watched
Then there was the bill. When they looked closely, the numbers weren't flattering:
"We had been using much less of their content than I originally thought, but we were paying for 40 plus thousand a year."
Some of the content was outdated, too. In safety training, outdated isn't just a style problem.
So about a year and a half ago, they changed course. In the safety lead's words, "we decided that we wanted to shift to something that's a little bit more specific to what we do." They started working with a local video vendor: "We supply a lot of the pictures and the video, and then we kind of work collaboratively with them to create an output."
That's the right direction, and it's slow. Every course is a production.
The catch: another team runs the LMS
This is where most training upgrades stall.
The utility already has an LMS, and a separate learning and development team runs it. The safety team is responsible for the safety content. A department admin has rights to create and upload courses. As the safety lead put it: "we make our content and we put it in their system, but they gotta run the system."
The safety team is also the LMS's heaviest user. They're "probably the super users of it just because we create a lot of stuff."
So "switch platforms" was never a real option. An LMS migration means exporting every user, mapping every course, re-uploading every record, filing SSO tickets, and running "both systems in parallel for just one quarter" (which is never just one quarter). It also means asking another department to tear out a system it runs and relies on. That's a big ask for a team that only wants better safety courses.
We said as much on the call: a migration can be a big thing. You don't need one to fix this. Start small, on the department's own budget, and add to what's already there.
The fix: keep the LMS, let AI agents build the courses
The setup is simple:
- Keep the LMS. No migration, no re-uploading users, no rip-and-replace. The L&D team keeps running the system.
- Build the courses with AI agents. The safety team starts with a Creator plan in Learn Or Teach, an add-on to the stack, not a replacement for it.
- Export as SCORM and upload. SCORM is a standard file format for courses. A SCORM file uploads to almost any LMS, the same way a PDF opens on almost any computer. The safety team builds the course in Learn Or Teach and uploads the file to the LMS they already have, and it runs like any other course.
What sold the safety lead on our site was being able to upload "safety plans or procedures or standards that they could pull information out of and incorporate that into training." That fixes the wrong-rulebook problem at the source. The training is built from their own policies, procedures, and safety standards, so it cites their rules, including the state rules and the places where the company goes beyond them.
What it looked like live
On the call, the safety lead dropped in one of their own internal PowerPoints, an office-safety and ergonomics deck. The AI agent asked the questions an instructional designer would ask: Who's the audience? Is this compliance training or operational training? What tone? What mix of text, images, and video? How long? He picked 15 to 20 minutes, with a quiz.
The agent storyboarded the course, then built it: lessons, narrated slide lessons, flashcards, and a quiz. What used to take a string of meetings with an instructional designer happened in about three minutes.
His reactions, in order:
- When the course came together: "Okay, that's pretty damn cool."
- When he refined the course by chatting with the AI after it was built: "That's pretty slick."
- When he saw he could swap in his own video blocks and images: "So you could customize the crap out of this stuff."
- On getting a 90% draft to tweak instead of starting from scratch: "Yeah, that's huge."
One more thing safety teams will like. The AI doesn't only build courses from documents like policies, procedures, safety plans, PDFs, and PowerPoints. Hand it raw video footage from your own sites and it can turn that into a course too. That's how the training ends up looking like their sites and their crews.
Why it worked
- The training cites the right rules. Courses come from their own policies and procedures, so state requirements and company standards are built in rather than bolted on.
- Nobody had to touch the LMS. The L&D team keeps the system, and the safety team keeps making content, just faster.
- They stopped paying for shelf-ware. They now pay for the ability to build the courses they actually need, from the material they actually have.
- Unlimited courses make the volume realistic. Their annual subscription covers an unlimited number of AI-built courses. Monthly safety-meeting topics, catch-up versions for people who missed the meeting, and courses for every policy update all become realistic.
- It's easy to pick up. After demoing several safety management systems, the safety lead's verdict was: "you guys have the cleanest looking UI I've seen yet."
What's next
Their internal content creator is next in line for onboarding. The safety lead also mentioned that, as a public utility, "we're a little bit slow to adopt things", and they're now rolling out iPads to field crews. Signing off toolbox talks on a tablet is on their wish list, so watch this space.
We'll share how the rebuild goes, with their permission.
The lesson: don't migrate, add
An LMS migration is a big headache, and we get it. It's months of exports, mappings, SSO tickets, and "parallel runs" that outlive the people who planned them. For most teams, the real problem was never the LMS. It's the courses inside it.
So don't migrate. Add.
This utility is proof, not an exception. If your organization has:
- an LMS that works fine (or that another team owns and isn't giving up),
- training that's generic, out of date, or citing somebody else's rules,
- and policies and procedures sitting in documents,
then you can do exactly what they did. Upload your own procedures or raw video footage, let an AI agent build the course, export SCORM, and upload it to the LMS you already run. Your LMS team's whole part in the project is clicking "upload."
Low commitment, high value, and it adds to your existing system without requiring a big change.
Start with a Creator plan
The Creator plan is $1,500 a year, which includes unlimited AI credits, unlimited exports, and 5 users from any department. It plugs into your existing LMS via SCORM, so nothing you already run has to change.
For a team that used to pay 40 plus thousand a year for generic content it barely used, the math does itself.
Start free at learnorteach.com
— Clever
