A practical guide to fixing the accountability gap before it becomes a training gap
Ask five different people in a growing business who owns employee training and it's rare to get the same answer twice. HR usually assumes operations handles the day to day skills side. Operations assumes HR is tracking mandatory compliance. Managers focus on their own team and assume someone above them is watching the bigger picture. If there's an L&D function, everyone else quietly assumes training is entirely their job. Nobody's really wrong. They're each describing one genuine slice of it. The problem is that slices don't add up to ownership on their own.
This isn't actually a training problem. It's an accountability problem that shows up looking like a training problem. Onboarding drifts because nobody's explicitly responsible for how it goes, not just whether it happened. Compliance lapses go unnoticed until an audit forces the question. Standards vary team to team because informal coaching depends entirely on whoever's managing that team. None of it traces back to one obvious failure. It traces back to the fact that, on paper, nobody was ever quite in charge.
Why training ends up as everyone's job and nobody's job
Training touches almost every function in a business, which is exactly why it's so easy for ownership to blur. HR runs onboarding. Compliance sets what's mandatory. Operations knows what a role actually requires day to day. Managers do most of the real coaching, informally, on the floor. Each function reasonably assumes its own piece is under control. What nobody's assuming, because nobody's been asked to, is responsibility for the gaps between those pieces, the parts that don't obviously belong to any one department and so quietly belong to none of them.
What happens when nobody's actually accountable
The costs rarely show up as a single dramatic failure. They show up as drift. Two departments build near identical content without knowing the other one exists. A new starter's onboarding depends heavily on which manager happens to be running it that week. A compliance requirement that changed six months ago still hasn't been reflected in training, because updating it wasn't clearly anyone's job. None of this looks urgent from inside any single department. It only looks like a problem from outside, which is usually the view an auditor, a new hire, or a frustrated manager ends up getting first.
Ownership doesn't mean one department does everything
The instinct when this gets noticed is often to hand the whole thing to one function, usually HR or a newly created L&D role, and hope that fixes it. It rarely does, because training genuinely needs input from more than one place. Compliance knows the regulatory detail. Operations knows what the job actually requires. Managers know their own team's specific gaps. Centralising all of it under one department doesn't remove that need, it just adds a layer that has to keep going back to ask the people who actually know.
The fix isn't deciding which single department owns training. It's deciding, clearly, who owns each part of it.
A simple way to split it
There's a useful distinction between who does the work and who answers for whether it got done properly. They don't have to be the same person or department, and pretending they should be is part of why ownership gets muddled. Compliance can be the one who's answerable for what's legally required and whether it's current, while managers are the ones who actually get their team through it. HR can own the onboarding experience overall, while whoever builds the content, an L&D function if one exists, is responsible for keeping it accurate and current. Splitting the question this way turns “who owns training” from one unanswerable question into several specific, answerable ones.
Approval is a different question from ownership
Owning content answers who built or maintains it. Approval is a separate, easily overlooked question. Who has to sign off before it actually reaches employees? A compliance course written by L&D still needs compliance's sign-off before it goes live, not because L&D can't be trusted to write clearly, but because getting the legal detail right isn't their area of expertise. The same logic applies in reverse. Operations should have a say before a compliance team publishes something that describes a process they've never actually run.
Skipping that approval step to move faster is exactly how a confidently written, well-designed course ends up being confidently wrong. The fix isn't adding bureaucracy to every piece of content. It's being clear about which content genuinely needs a second set of eyes before publishing, and making sure that step can't quietly be skipped when someone's in a hurry.
What this looks like in practice
Giving each function control over its own piece, not everything
Ownership only works if it's actually possible to act on. Restricting who can view and be assigned specific documents and content by job role, department or branch means compliance material stays visible to the people who actually need it, rather than becoming something every other department has to sift through to find what's relevant to them, and the same holds true in reverse for process-specific content.
Reviews as the accountability checkpoint, not just a performance tool
Appraisals usually get framed as something for the individual being assessed. They're just as useful as a check on whether the system around that person is working. Reviews that score consistently and trigger automatically at set points give whoever's accountable for a role an actual, structured answer to “is this being covered properly”, rather than a general impression.
Reporting that shows whose gap it is, not just that one exists
A completion report that just says 40 percent of a course is outstanding doesn't tell anyone who's supposed to act on that. Reporting broken down by branch, department or role turns a vague gap into something specific enough for the right owner to actually pick up, rather than something everyone assumes someone else is already handling.
Automations that remove the “I thought someone else assigned that” excuse
A lot of ownership failures aren't really about accountability at all, they're about a manual step nobody remembered. Automatic enrolment based on role, branch or department means the right content reaches the right person the moment they're set up, without depending on whichever department happened to remember that day.
Career paths as the one place ownership comes together
Progression is where every function's contribution has to meet in one place, whether that's designed deliberately or not. A career path that brings together the operational skills, compliance requirements and milestones relevant to a role into a single visible route is what cross-functional ownership actually looks like once it's working, rather than staying an abstract idea about who's supposed to talk to whom.
What to look for if you're fixing this properly
A few questions are worth asking before assuming the current setup is working:
Can each function see and manage the training that's actually theirs, without needing access to everything or being locked out of everything?
Does reporting show gaps broken down by branch, department or role, or just a single overall completion number nobody feels personally responsible for?
Is there a genuine accountability checkpoint built in, not just content being delivered and hoped for?
Does the right content reach a new starter automatically, or does it depend on someone remembering to assign it?
Is there one place where different departments' contributions to a person's development actually come together, or do they stay separate forever?
Common questions
Should L&D own all employee training?
Not entirely, even where an L&D function exists. L&D is usually best placed to own content quality and consistency, but compliance still needs to own regulatory accuracy, and managers still need to own whether their own team is actually applying what they've learned. Handing everything to L&D tends to create a bottleneck rather than solve the ownership problem.
What's the actual difference between who's responsible and who's accountable?
Responsible means doing the work day to day, like a manager running a team through an induction. Accountable means answering for whether it happened properly, like compliance being able to say with confidence that every mandatory course is current and completed. The two roles can sit with different people, and usually should.
How should ownership be split between HR, operations and compliance?
As a rough starting point, HR tends to own the overall onboarding and development experience, operations owns the accuracy of role-specific process content and compliance owns anything with a legal or regulatory requirement attached. Managers sit underneath all three, responsible for making sure their own team actually completes and applies what's relevant to them.
What happens if the business doesn't have a dedicated L&D role?
Ownership still needs to be assigned, it just gets distributed across existing functions rather than centralised in one. Someone still needs to own content quality even if that's a part-time responsibility sitting with HR or an operations lead, rather than a dedicated job title. The absence of an L&D role is a reason to be more deliberate about assigning ownership, not a reason to leave it undefined.
Who should approve training content before it goes live?
Whoever has the relevant expertise the content depends on, not necessarily whoever built it. Compliance content needs compliance sign-off. Process content benefits from operational sign-off, even if L&D or HR did the actual writing. The person approving something doesn't need to be the same person who created it, and for anything with legal or safety weight, it's usually better if they aren't.
How Expert LMS supports this
This is the structural gap Expert LMS is built to close. Content, documents and checklists can be restricted and assigned by job role, department or branch, so each function genuinely owns its own piece rather than sharing one undifferentiated pile. Automated enrolment removes the manual handoff where ownership usually gets lost, and reviews give whoever's accountable for a role a consistent, scored way to check it's actually working.
Reporting broken down by branch, department and role means a gap is immediately traceable to whoever should be closing it, instead of sitting in a single overall number nobody feels is theirs to fix. Career paths bring every function's contribution together in one visible route, which is what genuine cross-functional ownership looks like once it's actually built, not just discussed.
Helena Raymonde, Learning and Development Manager at San Carlo, summed up our partnership simply: “Working with the Expert LMS team has been a dream.”
See how it fits your business. Book a demo or start a free trial with Expert LMS today.
