The LMS Is Not the Training

The request usually comes up in a trustee meeting. For a year, the training director has watched apprentices fall behind on related instruction hours, instructors email PDFs from personal accounts, and the coordinator rebuild the same attendance spreadsheet every semester. Someone finally says it out loud: “We need an LMS.” Nobody disagrees. The motion carries.

A year and a half later, the system is live. Courses are loaded. Apprentices log in. The same second-year apprentices still show up to the lab unprepared. Contractors still say new journeyworkers are missing the same skills. And the coordinator now maintains the spreadsheet and the LMS.

That outcome is not a software failure. The software did what it was built to do: it delivered content. The problem is that nobody decided, before the purchase, what the content was supposed to produce. The learning management system gets treated as the answer to a training problem, when it is really a delivery tool for a training strategy. The LMS is not the training. The training is the training.

Every LMS purchase starts with a real problem

None of this means the original request was wrong. Apprenticeship programs are running more cohorts across more locations, often with part-time instructors who work the tools all day and teach at night. Apprentices expect to do some coursework on a phone at 9:00 PM, not only in a classroom on Tuesday. Related instruction has to be documented well enough to hold up in an audit.

So the diagnosis (we have outgrown our tools) is usually correct. What goes wrong is the prescription. The program buys a system to solve a delivery problem and expects it to solve a design problem too.

A platform moves content. It does not decide what matters.

Every LMS does roughly the same core jobs. It hosts courses, tracks completion, records hours, issues certificates, and sends reminders. Those are useful jobs. None of them answers the harder questions, like which skills a third-year apprentice needs to demonstrate before moving on, or what a signatory contractor needs from a new journeyworker on day one.

Those are training decisions. They belong to the training director, the instructors, and the joint apprenticeship committee. When a program skips them, the LMS fills the gap with its defaults: a course catalog, a completion bar, a dashboard of logins. The program ends up measuring what the software can count instead of what the trade needs.

Start with the journeyworker you are trying to produce

The programs that get the most out of a training platform work backward. They start with a picture of the finished journeyworker: what that member can do on a job site, safely and without supervision, in the first week after turnout. Then they ask what an apprentice needs to show at each stage to get there. Only then do they ask which pieces should be delivered online, which in the lab, and which on the job.

That sounds obvious. In practice, most LMS rollouts run in the opposite direction: pick the platform, migrate the existing material, then try to figure out what the data means.

Content built for compliance teaches compliance

Registered apprenticeship programs live with real requirements. Federal regulations recommend a minimum of 144 hours of related instruction for each year of apprenticeship (29 CFR 29.5), and many program standards hold apprentices to that number or more. Those requirements matter. A program that cannot document its hours has a serious problem.

But hours are an input. A program designed around hitting 144 hours is a program designed to produce 144 hours. It will get there. Whether its apprentices can troubleshoot a panel, read a set of prints, or lead a small crew is a separate question the hour count cannot answer.

The risk with an LMS is that it makes compliance easier to track than learning. Hours, logins, and completions show up cleanly on a dashboard. Competence does not, unless someone decided in advance how to capture it. When a program lets the easy numbers stand in for the hard ones, the platform quietly turns the training into a compliance exercise.

Programs that do capture competence get something an hour count never could: a view of where apprentices get stuck, across every cohort and location. When apprentices keep stalling at the same evaluation, or one section keeps sending them back for rework, that is a friction point in the program, not a problem with one apprentice. It might be a gap in the online material, a lab that needs more time, or an instructor who needs support. A training director can see it while the cohort is still in the room, not a year later in the grade report.

Instructors are the training, and the tool has to serve them

In most programs, the instructor is still the most important part of the training. Often a working journeyworker. Often teaching after a full shift. Often the person an apprentice will call years later when a job goes sideways. Nothing a platform does replaces that relationship.

That makes instructors the real test of any training tool. If the system adds work (duplicate grade entry, clumsy course editing, one more password), instructors will route around it. They will go back to their own spreadsheets and printed handouts, and the program will end up with two sets of records and no reliable tie between them. We have watched that happen more than once.

A good training tool takes administrative weight off instructors and coordinators. It gives an instructor a clear view of the cohort in front of them. It records what the instructor sees at the bench, not just what the apprentice clicked. It flags the apprentice who has missed two sessions before it becomes six. A tool that is not doing those things is competing with the program’s own instructors for attention.

Five questions to settle before you pick a platform

If your program is weighing an LMS, or already has one that is not delivering, these five questions are worth answering first. None of them require software.

1. What should an apprentice be able to do at the end of each year, stated as skills a contractor would recognize?
2. Which of those skills can be learned online, which need hands-on time with an instructor, and how will the instructor confirm the apprentice has them?
3. How will you know an apprentice is struggling, and who needs to know first?
4. Beyond hours and completion, what outcomes will the joint apprenticeship committee review each year?
5. What administrative work are instructors and the coordinator doing today that a tool should take off their plate?

A program with clear answers to those questions can evaluate any platform in an afternoon. A program without them will struggle no matter which one it buys.

Forge Learn works best when the program knows what it is chasing

Mosaic Learning built Forge Learn, the training side of Forge, around that sequence. It handles the delivery jobs every program needs: coursework, hybrid instruction, hours tracking, and records that hold up. Because it sits inside the same platform as member communications and events, training records connect to the rest of the member’s relationship with the union.

Where it goes further is the hands-on work most platforms leave out. Skills checks are built into a course as evaluations scored against a rubric. The instructor watches the task, scores the attempt, and adds a note or a photo. Every attempt stays on the record, and access gates hold the next section until an instructor confirms the apprentice is ready.

It also follows the principle behind the rest of Forge: who are you, and what do you need to see? An apprentice sees where they stand and what comes next. An instructor sees who is waiting on them and who has fallen off pace. A training director sees the program and where it is losing people. The coordinator stops rebuilding the attendance sheet.

What Forge Learn will not do is decide what your program should produce. It can record a rubric score. It cannot write the rubric. No platform can. It works best in programs that walk in knowing what outcomes they are chasing, and part of how Mosaic works with training directors is getting those answers on paper before anything is configured. If a vendor tells you their system will fix your training program on its own, that is the moment to be skeptical.

The training is the training

The LMS is not the training. The training is the training. The outcomes you set, the instructors you support, and the way you sequence skills from first year to turnout are what produce a journeyworker. A platform can make that work easier to deliver and easier to see. It cannot do the work for you.

This week, before anyone opens a vendor demo, get your instructors and coordinator in a room for an hour. Write down what a finished journeyworker from your program should be able to do. Start there.