New job, new LMS login, and a catalogue of 240 courses. Some have names like "Module 3 NEW (use this one)", and some were last edited before half your team was hired. Nobody can tell you which ones still matter, and somebody is going to ask. An e-learning course audit is how you stop guessing. How do you audit an old course library without spending a year on it?

Record the same dozen facts for every course, test that each one still launches, score each on value and condition, and sort them into keep, fix, convert or retire. The audit is a spreadsheet and a set of decision rules, not a research project. Pull usage data from the LMS first, so you can skip deep review of courses nobody takes. Spend your review time on the courses that are required, popular or broken. Then put the results in front of the people who own the content and the records before anything gets switched off.

Why Run an E-Learning Course Audit at All?

Because an untended library keeps costing you money and credibility in ways nobody tracks. Learners get assigned courses with old policy, old screenshots and old phone numbers. Some modules no longer launch on current browsers, and the help desk quietly absorbs the tickets. Two departments maintain near-identical courses on the same topic and neither knows.

How to Audit an Old E-Learning Course Library – A Practical Triage for Courses Nobody Has Touched in Years - 3D Animation

A course library audit turns that mess into a list. It tells you what you have, what state it is in and what to do next, in an order you can defend. It also gives you something solid to show a manager who asks why the migration budget looks the way it does.

Fair warning: you will find at least one course that everyone assumed someone else owned. That is normal, so write it down and keep going.

What Should You Record for Each Course?

Record enough to make a decision, and not a column more. A spreadsheet with one row per course works fine. These columns have earned their place:

  1. Course ID and title, exactly as they appear in the LMS.
  2. Business owner, a person or team who can approve changes.
  3. Audience and whether the course is required by a policy or regulation.
  4. Last content update, from the files or the LMS, not from memory.
  5. Enrolments and completions over the last 12 months.
  6. Format and technology: HTML5, Flash, Authorware, video, SCORM 1.2 or 2004.
  7. Source files: available, partial or missing, and where they live.
  8. Launch test result on a current browser: works, partly works, fails.
  9. Content accuracy flag from the owner: current, needs updates, wrong.
  10. Accessibility quick check: captions present, keyboard usable, obvious contrast problems.
  11. Overlap: other courses covering the same topic.
  12. Value score and condition score (see below), plus the decision.

For the usage columns, most LMS platforms can export a course activity or enrolment report covering a date range. Export twelve months, paste it into a second tab, and match it to your list by course ID rather than by title, because titles drift and IDs usually do not. Courses that appear in the LMS but not in the report have had no activity at all, which is useful information in itself.

Fill columns one to seven from LMS reports and the file share before you open a single course. That part is clerical and fast, while columns eight to ten are where the real hours go, so you want them only for courses that justify the effort.

The accessibility check here is a quick screen, not an evaluation. If your team needs to build that skill, the free Section508.gov training and tools are a reasonable place to start, even outside US federal work.

How Do You Spot Courses That Depend on Dead Technology?

You spot them by launching each course and then looking inside the package. A launch test on a current browser catches the obvious failures in seconds. A quick look inside the package catches the ones that only fail on certain screens.

The usual suspects:

  • SWF files anywhere in the package. Flash-based courses have not played in mainstream browsers since Flash Player support ended, and a single SWF interaction can blank out one screen of an otherwise healthy course.
  • Packaged Authorware pieces, or the files that went with its web player.
  • Other retired plugins: Shockwave, Java applets, Silverlight, QuickTime embeds.
  • Hard-coded links to servers, shares or intranet pages that no longer exist.
  • Fixed small screen sizes, built for a 4:3 monitor, that turn unreadable on a laptop and useless on a phone.
  • Tracking aimed at an LMS or reporting tool your organization retired.

Do not trust the "works" result from a single machine. Test on a standard work laptop with a standard browser, signed in as an ordinary learner, because that is what your learners have. Your developer machine with three old runtimes installed is not a fair test.

Which Courses Should You Keep, Fix, Convert or Retire?

Score each course twice, once for value and once for condition, and let the pair decide the bucket. Two simple 0 to 3 scales are plenty.

  • Value: 0 nobody needs it, 1 nice to have, 2 used and wanted, 3 required or business critical.
  • Condition: 0 does not launch, 1 launches but outdated or partly broken, 2 minor fixes needed, 3 current and working.
ValueConditionDecision
0 to 1AnyRetire (or merge into another course)
2 to 33Keep
2 to 32Fix in place
2 to 30 to 1Convert or rebuild, required courses first

Here is a made-up example of how that plays out. Say the audit of 240 courses finds 90 with no completions in a year and no policy requirement. Those score 0 or 1 on value and go straight to retire, without any further review.

Of the remaining 150, say 70 are in good shape (keep), 45 need small fixes (fix), and 35 fail to launch or are badly out of date (convert or rebuild). Your detailed work is now 80 courses, not 240, and any required courses among the 35 broken ones come first.

Expect a few arguments over scores, and treat that as a good sign. A content owner who insists a value-1 course is really a 3 usually has a reason, such as an upcoming audit or a contract requirement, and that reason belongs in the notes column next to the score.

Two rules keep the sorting honest. A course that is required stays required, so a broken one jumps the queue no matter how dull it is. And duplicates get merged before anyone fixes them, because fixing two versions of the same course is a special kind of waste.

The retire bucket is the one people flinch at. Retiring outdated training content is not deleting it. You archive the package, the source files and the records, and you stop assigning it.

Who Should Review the Audit Results?

Everyone who can say no later should see the results before anything changes. It is far better to hear objections in one review meeting than one by one after a course disappears.

  • Content owners confirm the value scores and the accuracy flags for their courses.
  • Compliance or HR check that nothing required lands in the retire bucket, and decide what happens to historical completion records.
  • The LMS administrator confirms how retiring or replacing a course affects existing records and assignments.
  • IT weighs in on courses that depend on old plugins or old machines.
  • Whoever holds the budget sees the convert and rebuild list with rough effort attached.

Send the spreadsheet a week before the meeting, sorted by decision, with the retire list on its own tab. People engage faster with a short list labelled "we plan to retire these" than with a 240-row sheet. Record every change of decision, with the reason, in a notes column.

How long to keep old training records is a question for your records team or legal counsel. The audit's job is to make sure the question gets asked before anything is removed.

How Often Should You Repeat the Audit?

Repeat the full audit every year or two, with a lighter check in between. The full version is the one described above. The light version takes an hour a quarter: pull usage reports, look for courses with zero completions, and re-run launch tests on anything required.

Some events should trigger a fresh look regardless of the calendar:

  • A policy, regulation or product change that touches course content.
  • An LMS migration or major LMS upgrade.
  • A rebrand, which makes every old logo and colour scheme an instant eyesore.
  • A browser or operating system change rolled out across the organization.

The cheapest way to make the next audit easier is to keep two columns alive after this one: owner and last reviewed date. Put them in the LMS course description if your system allows it. A library where every course has a named owner and a date stays manageable almost by itself.

A Course Audit Turns an Inherited Mess Into a Work Plan

An e-learning course audit is not glamorous, since it is a spreadsheet, a launch test and two small scores per course. But it replaces "we have a lot of old stuff" with a sorted list that says what to keep, what to fix, what to convert and what to retire, and in what order.

Start with the LMS reports, because they let you dismiss the dead weight quickly. Spend your real effort on required and popular courses. Get the owners in a room before anything goes. And when it is done, keep the owner and review date columns current, so whoever inherits the library after you gets a list instead of a mystery.