What Is a Learning Management System (LMS)? Types and Features

A learning management system (LMS) is software that delivers, tracks and reports on employee training. It stores your courses, assigns them to the right people, records who finished what and when, and gives you proof of completion for audits. If your organization runs required training of any kind, an LMS is the system of record for it.

This guide explains what an LMS does, how it differs from a learning experience platform and the training module inside your HRIS, which technical standards matter, and how to pick one without regretting it a year later.

Key takeaways

• An LMS assigns, delivers, tracks and reports on training, and it is the main record you show auditors and regulators.
• An LXP focuses on discovery and self-directed learning, while an HRIS training module usually only logs completions.
• SCORM and xAPI decide whether your content will play and report correctly, so ask about both before you buy.
• Accessibility is not optional: plan for WCAG conformance, and Section 508 if you serve or sell to federal agencies.
• Choose based on your compliance obligations, integrations and learner experience, not on the length of the feature list.

What is a learning management system and what does it do?

An LMS is a platform that manages the full training cycle: content, enrollment, delivery, tracking and reporting. Think of it as the training equivalent of a payroll system, where the output is a reliable record instead of a paycheck.

Most LMS platforms handle four jobs:

• Administration: creating courses, building learning paths (a set sequence of courses for a role), and enrolling people manually or by rule.
• Delivery: playing e-learning modules, videos and quizzes, and scheduling instructor-led or virtual classroom sessions.
• Tracking: recording attempts, scores, time spent, completions and certificate expiry dates.
• Reporting: showing who is overdue, which departments are behind, and producing audit-ready completion records.

An LMS sits alongside your core HR systems rather than replacing them. If you are mapping where it fits, our overview of the systems an HR team needs in its tech stack shows how learning connects to recruiting, payroll and the employee record.

What core features should an LMS have?

At minimum, an LMS should support rule-based assignment, standards-based content playback, automated reminders, certification tracking and exportable reports.

Look for these core capabilities:

• Rule-based enrollment: assign courses automatically by job title, location, department or hire date, so a new forklift operator gets the right training without anyone remembering to add it.
• Recertification: set training to expire and reassign itself on a schedule (for example, every 12 months).
• Notifications and escalation: remind learners before deadlines and alert managers when someone is overdue.
• Blended learning: combine online modules with in-person sessions, attendance sign-off and skills checks observed by a supervisor.
• Assessments: quizzes, passing scores and retake limits.
• Reporting and audit trail: a time-stamped history of every assignment, attempt and completion that cannot be quietly edited.
• Integrations: a data feed from your HRIS for new hires, transfers and terminations, plus single sign-on (SSO, one login shared across systems).
• Mobile access: frontline and field staff often have no desk, so courses must work on a phone or shared tablet.

If you already record some training in your HR platform, read how to track training and development in your HRMS before deciding whether you need a separate tool at all.

How is an LMS different from an LXP or an HRIS training module?

An LMS is built for assigned, tracked and reportable training. An LXP (learning experience platform) is built for discovery and self-directed learning, and an HRIS training module is usually a simple log of completed courses tied to the employee record.

Many organizations end up with more than one. The table shows where each one is strongest.

Factor	LMS	LXP	HRIS training module
Main purpose	Assign, deliver and prove completion of training	Help employees find and choose learning content	Record training history on the employee file
Who drives learning	Administrators and managers	Employees, guided by recommendations	HR administrators
Compliance tracking	Strong: deadlines, expiry, audit trail	Usually limited	Basic: dates and course names
Content playback (SCORM, xAPI)	Standard	Often supported, sometimes via an LMS	Rarely supported
Content sources	Your own courses plus purchased libraries	Curated articles, videos, courses, internal content	Usually none; it logs external training
Best fit	Required, regulated or role-based training	Upskilling and career growth	Small teams with light training needs

The HRIS remains the source of truth for who works where. If you need a refresher on that system, see what an HRIS is and who owns its data. Your LMS should pull employee details from the HRIS rather than keeping its own copy that drifts out of date.

Should you choose a cloud or on-premise LMS?

Most organizations now choose a cloud LMS because it removes server maintenance and updates automatically. On-premise still makes sense when strict data residency rules, an air-gapped network or deep custom development rule out a hosted service.

The NIST definition of cloud computing describes cloud as on-demand network access to a shared pool of computing resources that can be provisioned and released with minimal management effort. For an LMS, that usually means software as a service (SaaS): the provider hosts and maintains the system and you pay a subscription.

• Cloud strengths: faster setup, automatic updates, easier mobile access for remote and frontline staff, and no hardware to manage.
• Cloud trade-offs: less control over upgrade timing, reliance on the provider's security practices, and data stored outside your own network.
• On-premise strengths: full control of data location and configuration, which some regulated or classified environments require.
• On-premise trade-offs: your IT team owns servers, patches, backups and upgrades, and remote access takes more work.

Whichever you choose, ask where data is stored, how it is encrypted, how access is controlled by role, and how you get your records back if you leave.

What are SCORM and xAPI, and why do they matter?

SCORM and xAPI are technical standards that let training content talk to a learning system. They decide whether a course you buy or build will play correctly and send completion data back to your LMS.

SCORM (Sharable Content Object Reference Model) was created by the Advanced Distributed Learning (ADL) Initiative. It defines how content is packaged into a transferable ZIP file and a common data model and API for communication between course content and the LMS. The most recent release is SCORM 2004 4th Edition. SCORM tracks the basics well: completion, pass or fail, score and time.

xAPI (Experience API) is the newer standard. It is now published as IEEE standard 9274.1.1, which describes a JSON data model and a web service API for tracking learning and human performance data, covering more than course completions, test scores or pages viewed. Each record is a "statement" with an actor, a verb and an object (for example, "a learner completed lockout training"). Statements are stored in a learning record store (LRS), a server that receives, validates and returns xAPI records.

In practice:

• Your LMS should play SCORM 1.2 and SCORM 2004 packages, since most off-the-shelf libraries still ship in those formats.
• Ask whether xAPI is supported and whether the vendor includes an LRS or connects to an external one.
• If you want to track simulations, mobile apps or on-the-job observations, xAPI is the better fit.
• Ask about cmi5, a profile that uses xAPI inside an LMS launch model. ADL now points new acquisitions toward xAPI and cmi5.

How do you track compliance training in an LMS?

You track compliance training by mapping each legal or policy requirement to a course, assigning it automatically to the roles it covers, setting expiry dates, and keeping a tamper-evident completion record. Then you review overdue reports on a fixed schedule.

Safety training is a clear example. OSHA's booklet Training Requirements in OSHA Standards explains that many OSHA standards include explicit safety and health training requirements, and it advises that it is a good idea to keep a record of all safety and health training. Some standards go further. The powered platforms standard, for example, requires the employer to certify that employees have been trained, with the trainee's identity, the trainer's or employer's signature and the completion date.

To make your LMS audit-ready:

• Keep a requirement register that lists each rule, the roles it applies to, the course that satisfies it and the refresh interval.
• Capture who delivered instructor-led sessions and how competence was checked, not just that a video played.
• Store certificates and sign-off forms with the completion record.
• Retain records for terminated employees according to your retention policy.

Onboarding is where most compliance gaps begin. Our guide to onboarding and offboarding automation covers how to trigger day-one training as soon as a hire is entered.

How do WCAG and Section 508 apply to an LMS?

Your LMS and its courses must be usable by employees with disabilities. WCAG is the main technical benchmark, and Section 508 makes WCAG-based accessibility mandatory for federal agencies and the technology they buy.

WCAG (Web Content Accessibility Guidelines) is published by the W3C. Version 2.2 is the latest and has 13 guidelines with testable success criteria at three levels: A, AA and AAA. Content must be perceivable, operable and understandable, and it must work reliably with assistive technologies such as screen readers.

For federal work, Section508.gov states that the Revised 508 Standards incorporate by reference the WCAG 2.0 Level AA success criteria. If you are a federal agency or a contractor delivering training to one, ask vendors for an accessibility conformance report.

Check both the platform and the content: keyboard navigation, captions and transcripts for video, screen reader labels, color contrast and adjustable time limits on quizzes. For a broader view, see how to make HR services accessible to every employee.

How do you choose the right LMS?

Start with your training obligations and your learners, then test a short list of systems against real scenarios. A scripted demo built around your own use cases tells you far more than a feature checklist.

1. List your requirements. Record every mandatory course, who needs it, how often, and what proof an auditor expects.
2. Profile your learners. Note how many are desk-based, frontline, remote, multilingual or using assistive technology.
3. Map integrations. Decide what the LMS needs from your HRIS (hires, job changes, managers, exits) and what it sends back.
4. Set technical must-haves. SCORM and xAPI support, SSO, mobile access, data export and WCAG conformance.
5. Run scripted demos. Ask each vendor to show a new hire auto-enrolling, a certification expiring and an overdue report going to a manager.
6. Pilot with real users. Test with one department, including frontline staff, before a full rollout.
7. Review total cost. Include licenses, content, implementation, integration and admin time over three to five years.
8. Plan the go-live. Migrate historical records, assign owners and train administrators before launch.

The same discipline applies to any HR platform. Our HRIS requirements checklist is a useful template, and our HRMS implementation best practices carry over well to an LMS rollout.

Common mistakes when buying an LMS

• Buying for features, not workflows. A long feature list hides weak basics like assignment rules and reporting.
• Skipping the HRIS integration. Manual uploads mean new hires miss required training and former employees stay enrolled.
• Ignoring accessibility. Retrofitting captions and keyboard support after launch costs more than requiring them up front.
• Not testing content. Upload your own SCORM packages during the trial to confirm they play and report correctly.
• Forgetting historical records. Plan how to migrate past completions so you can still prove compliance for earlier years.
• No owner after launch. Someone must maintain rules, retire old courses and review overdue reports.

FAQ

Is an LMS the same as e-learning software?

No. E-learning authoring software creates courses, while an LMS delivers them, tracks progress and stores records. Many teams use an authoring tool to build SCORM or xAPI packages and then upload them to the LMS.

Do small businesses need an LMS?

Not always. If you have a few required courses and a small team, your HRIS training log may be enough. An LMS becomes worth it when you have recurring certifications, multiple locations or regular audits.

Can an LMS track in-person training?

Yes. Most LMS platforms let you schedule classroom sessions, record attendance, upload sign-in sheets and log practical skills checks alongside online courses.

What is a learning record store?

A learning record store (LRS) is a server that receives, validates and stores xAPI statements. It can be built into an LMS or run separately and feed data to several systems.

What to do next

Start by listing every training requirement you must prove, the roles it applies to and how often it renews. Then confirm how employee data will flow from your HRIS, and write SCORM, xAPI and WCAG support into your requirements before you contact vendors.

Sources

• IEEE 9274.1.1: Experience API (xAPI) standard
• W3C: WCAG 2 Overview
• Section508.gov: Applicability and Conformance Requirements
• OSHA: Training Requirements in OSHA Standards (OSHA 2254)
• NIST SP 800-145: The NIST Definition of Cloud Computing

Last reviewed: November 2026.