How Moodle competencies work: building frameworks, learning plans, competency-based progression, mapping to roles and a skills matrix, and real reporting.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A step-by-step guide to building a competency framework, with a reusable template and how to run it on a platform you own.
A skills matrix shows who can safely do what at each location, and an owned platform ties it to training and HRIS in one place.
How digital badges and verifiable credentials prove real skills, tie to recertification, and stay yours when you own the platform.
Course completions tell you someone finished a course. They do not tell you whether that person is competent to do a job. Moodle competencies close that gap. They let you define what "capable" actually means for each role, attach evidence to prove it, and report on capability instead of just attendance. For HR and L&D leaders who need to answer "is this person qualified?" rather than "did they click through the module?", this is the feature that changes the question you can answer. This guide walks through how Moodle competencies work and how to model your real organization on a platform you own outright.
Moodle competencies are structured, reusable descriptions of what a learner should know or be able to do. They live in competency frameworks — collections of competencies you build once and reuse across the organization.
A framework is more than a flat list. It supports a hierarchy, so a broad competency like "Site Safety" can contain child competencies like "Lockout/Tagout" and "Confined Space Entry." Each competency carries a rating scale that defines the levels of achievement — the default is a simple "Not yet competent / Competent," but you can define scales with more gradations when a role needs them.
The key idea is separation. Competencies describe capability; courses deliver learning. A single competency can be met by more than one course, and a single course can contribute to more than one competency. That decoupling is what lets you model your organization honestly instead of pretending every skill maps to exactly one training module.
A learning plan is where competencies meet an individual. You bundle the competencies a person needs into a plan — either directly or from a reusable learning plan template — and assign it to a user or a cohort.
This is the mechanism that scales. Build one template for "Warehouse Supervisor," populate it with the competencies that role requires, and assign it to every warehouse supervisor across every site. Each person then has a visible, personal view of what they need to achieve and where they stand. New hires into that role inherit the same plan automatically when you assign the template to their cohort.
For a multi-site firm, this matters because the requirement travels with the role, not the location. The supervisor in one facility and the supervisor in another are held to the same defined standard, and you can see both at a glance.
Competencies can do more than sit alongside courses — they can gate them. Moodle lets you tie course completion to competency attainment, so finishing a course can automatically mark a linked competency as complete. You can also use competencies as part of activity completion and access rules, building learning paths where later content unlocks only after a learner has demonstrated an earlier competency.
The result is progression based on demonstrated capability rather than pure sequence. Instead of "you watched three videos, so you may proceed," the logic becomes "you have demonstrated this competency, so you are ready for the next." For skills-based programs, apprenticeships, and role certifications, that is a far more defensible model.
The real payoff comes when your competency frameworks mirror your actual job architecture.
The pattern looks like this:
That last step turns Moodle competency data into a live picture of organizational capability. You can see coverage, gaps, and single points of failure — where only one person holds a critical competency. The broader discipline of designing this structure is covered in competency framework, and the reporting view it feeds is exactly what a skills matrix software is meant to surface. Modeled well, Moodle gives you both without a separate tool.
A claim of competence is only as good as what backs it.
Moodle competencies support evidence of prior learning and manual rating, so competence is recorded deliberately, not just inferred from a click.
For regulated or high-consequence work, the manual-rating-with-evidence path is what gives a record its weight. It answers not just "is this marked complete?" but "who assessed it, against what standard, with what proof?" You can also pair attainment with a credential — see digital badges and credentials in an LMS for issuing verifiable badges when a competency or plan is achieved.
This is where competencies justify the setup effort. Standard course reporting answers "who finished the course." Competency reporting answers questions that actually map to risk and readiness:
Because competency data is structured and role-aware, it feeds dashboards and custom reports that speak to leadership in terms they care about — capability and coverage — rather than raw completion counts. For an L&D team, that shift from "training delivered" to "capability built" is often what earns the program its budget.
Your role and skills architecture is a genuine asset. It encodes how your organization defines competence, and it should not live inside a platform you merely rent. On an owned Moodle platform — bespoke or Moodle Workplace, owned outright — your frameworks, plans, rating scales, and evidence are yours to model, extend, and export without asking a vendor's permission or paying per learner as you grow.
That ownership is what lets the model keep pace with your organization. Roles change, new competencies emerge, standards get revised — and because you own the platform, you adapt the structure on your timeline. Moodle competencies give you the mechanism; owning the platform gives you the freedom to make it match reality for years, not just for the length of a subscription.