Your LMS Has Too Many Courses. Now What?

A growing course catalogue can look like a sign of a healthy learning environment. Until people can no longer find what they need.

Most LMSs do not become cluttered overnight. A new course is added. An updated version is published but the old one remains. Another team creates similar training because they did not know something already existed. A policy changes, but nobody is quite sure who owns the related course.

Over time, the platform accumulates content faster than the organisation reviews it. The result is not simply an administration problem. It affects learner trust, search, reporting and the overall usefulness of the LMS.

Why LMS course catalogues become difficult to manage

Content creation usually has a clear beginning: there is a request, an audience and a reason to publish. Content retirement is often less defined.

If courses do not have an owner, review date or clear purpose, administrators are understandably reluctant to remove them. The safest option appears to be keeping everything.

That approach creates a different risk. Learners see several versions of similar content, search results become less useful, and administrators spend more time maintaining material that may no longer serve a business need.

This is one reason a capable platform can still become difficult to use. As explored in Why a Good LMS Still Fails, the operating model around the LMS matters as much as the technology itself.

A practical LMS content-audit framework

You do not need to start by deleting courses. Start by understanding what is there and why it exists.

1. Inventory: What do we actually have?

Create a reliable view of the active course catalogue. Capture the course name, audience, owner where known, last update, enrolment or usage information, and any learning path or programme it supports.

The purpose of the inventory is not to build another permanent spreadsheet. It is to make the current state visible enough to make informed decisions.

2. Ownership: Who is responsible for it?

Every important course should have someone who can answer whether the content is still accurate and required.

If nobody can identify an owner, that is useful information. It does not automatically mean the course should be removed, but it signals that the organisation needs to confirm its purpose before continuing to maintain it.

3. Relevance: Does the audience still need it?

Ask what task, capability, requirement or business outcome the course supports today.

A course may still be technically accurate while no longer being useful. Roles change, systems are replaced and processes evolve. Content should evolve with them.

4. Accuracy: Is the information current?

Review courses for outdated screenshots, policies, links, terminology, system steps and organisational information.

High-risk or compliance-related learning may need a more formal review cycle. Other content may only need a lightweight periodic check.

5. Usage: Is anyone actually using it?

Usage data should inform the review, but it should not make the decision on its own.

A low-use course may be unnecessary, difficult to find, intended for a small specialist audience or required only occasionally. The important question is why usage looks the way it does.

6. Placement: Does this belong in the LMS?

Not every useful piece of information needs to be a course.

If employees need to look something up while doing their work, a knowledge base or performance-support resource may be more appropriate. The article LMS, Knowledge Base or Chat? provides a simple model for deciding where employee information should live.

7. Action: Keep, update, consolidate, archive or remove

Once the previous questions have been answered, assign each course a clear action:

• Keep — current, useful and correctly placed.
• Update — still needed, but information or design needs attention.
• Consolidate — overlaps with other learning and can be combined.
• Archive — no longer active but should be retained outside the learner-facing catalogue.
• Remove — no longer needed and has no retention requirement.

The problem may be bigger than the course catalogue

A content audit often reveals structural issues that are difficult to see when reviewing courses one at a time.

You may discover that learners are being shown too much content because audiences and groups are too broad. Courses that should form a guided journey may be sitting separately in the catalogue. Similar content may exist because different teams are publishing without shared ownership rules.

In those situations, deleting courses will only solve part of the problem. The LMS structure, learning paths, assignment rules or governance may also need attention.

What a cleaner LMS should achieve

The objective is not to have the smallest possible course catalogue.

A well-managed LMS should make it easier for learners to understand what matters, easier for administrators to maintain the platform and easier for the business to trust the learning being delivered.

That means keeping the content that has a clear purpose and creating a simple lifecycle for what happens after content is published.

Where to start

Choose one audience, business area or section of the catalogue rather than trying to clean up the entire LMS at once.

Run the seven checks above, agree the actions with the relevant owners and use what you learn to define a repeatable content-review process.

The first cleanup improves the catalogue. The review process helps prevent the same problem from returning.