How to choose an LMS: a 9-step scorecard method with a free template

To choose an LMS, start with the business outcome, not the feature list. Define who will learn and why, turn that into weighted requirements, set a three-year budget, pick a deployment model, then score a shortlist of three to five platforms on the same scorecard and prove the winner in a short pilot with your own users and content. That is the whole method in one sentence, and the nine steps below make it repeatable.

Most "how to choose an LMS" guides are written by LMS vendors, so their checklists quietly favour the features they sell. This guide is vendor-neutral. It is written for HR, L&D, training and IT leads who are starting an LMS search, whether you are replacing a legacy system, moving off spreadsheets or buying a first platform for customers or partners.

You get a free, copy-ready scorecard template with suggested weights, a worked scoring example, a table of selection criteria by organisation type and the mistakes we see most often when teams choose in a hurry.

The 9-step LMS scorecard method at a glance

Each step produces something concrete that feeds the next one. If a step produces nothing you can write down, it has not been done yet.

Steps 1 to 3: define outcomes, requirements and budget

Step 1: Define the outcome and the audiences

Write down the problem in one or two sentences. "We need an LMS" is not a problem statement. "New hires take six weeks to become productive and we cannot prove who completed safety training" is. The outcome decides almost everything that follows: onboarding speed, compliance evidence, customer adoption, partner certification and course revenue each point to different platforms.

Then list every audience, because audience mix is the single biggest filter on the market:

• Employees: usually need SSO, HR system sync, manager reporting and mandatory training with due dates.
• Customers: need a branded, low-friction sign-up, often e-commerce or CRM links, and analytics on product adoption.
• Partners, resellers or client organisations: need separate portals or tenants, delegated administrators and per-organisation reporting.
• Students or exam candidates: need assessment depth, question banks, proctoring and certificates.
• Members of an association: need continuing education credits, renewals and membership system links.

Record rough numbers too: registered users, how many are active in a typical month, and how that might change over three years. Pricing models depend heavily on these figures.

Step 2: Turn use cases into requirements

Interview the people who will run the platform every day, not only the sponsor. Ask administrators, instructors, managers and a few learners to describe the tasks they do today and what goes wrong. Write each requirement as a testable statement, for example "a manager can see overdue compliance training for their team without exporting a spreadsheet".

Then prioritise with a simple MoSCoW split:

• Must have: without it the project fails. Keep this list short, ideally under fifteen items.
• Should have: important, but a workaround exists for the first year.
• Could have: nice extras that break ties.
• Won't have (now): explicitly out of scope, which stops scope creep during demos.

A long must-have list is a warning sign. When everything is mandatory, every vendor fails on something and the decision falls back to gut feel.

Group the requirements under the same headings as the scorecard in this guide (use cases, learner experience, admin effort, content, assessment, integrations, reporting, cost, vendor and deployment). That way every requirement maps to a scoring row, and nobody has to translate between two documents during demos. If you plan to issue a formal request for proposal, this grouped list becomes its core.

Step 3: Set the budget and the cost model

Estimate total cost over three years, not the first-year licence. LMS pricing usually follows one of these models:

Add the costs that rarely appear on a pricing page: implementation and configuration, content migration or rebuilding, integrations, SSO set-up, admin training, and the internal time of the people who will run it. For a first estimate of build, customisation or integration effort, our LMS cost calculator gives an indicative range you can refine with vendors.

Steps 4 to 6: deployment, content standards and integrations

Step 4: Choose a deployment model

Deciding the deployment model early removes most of the market and makes demos faster. The four common options are:

• SaaS (cloud) LMS: fastest to launch and the vendor runs upgrades and hosting. You trade away some control over data location, customisation and pricing at scale.
• Commercial self-hosted LMS: you run the software on your own servers or cloud account. Good for data control and predictable costs at volume, but your team or a partner owns operations.
• Open source LMS: platforms such as Moodle, Open edX or Canvas's open source edition. No licence fee, maximum flexibility, but you need hosting, upgrades and security discipline.
• WordPress with an LMS plugin: a strong fit when your website already runs on WordPress and you want to sell courses, less so for complex enterprise compliance.

Ask one blunt question: who will patch this platform at 7 pm on a Friday when a security release lands? If the honest answer is "nobody", favour SaaS or a managed hosting contract.

Self-hosting starts to make sense when data must stay in a particular country or on your own infrastructure, when per-user SaaS fees become expensive at your learner volume, or when you need custom workflows a SaaS vendor will not build. Hybrid choices exist too: some commercial platforms offer the same product as SaaS or self-hosted, and open source platforms can be run for you by a specialist hosting partner.

Step 5: Check content, authoring and e-learning standards

List the content you already have and the content you plan to build. Then check the standards each platform actually supports, not only what the sales deck says:

• SCORM 1.2 and SCORM 2004: still the most common package formats from authoring tools. Test both if you own older content.
• xAPI: records learning experiences as statements in a learning record store (LRS). It is now published as IEEE standard 9274.1.1-2023.
• cmi5: an xAPI profile that defines how an LMS launches and tracks content, useful if you want xAPI data with LMS-style completion rules.
• LTI 1.3: the 1EdTech standard for securely launching external tools, or for launching your courses from another platform such as a university LMS.

Our SCORM vs xAPI vs cmi5 comparison explains which standard fits which situation. Also check built-in authoring (can subject experts build a quiz without an authoring tool?), video hosting, assessment types, certificates and whether content can be exported if you leave.

Step 6: Map integrations, identity and data flows

Draw a simple diagram of how users, courses and results move between systems. Typical flows are:

• Identity: single sign-on through SAML 2.0 or OpenID Connect, and automatic user provisioning, often through SCIM.
• HR system: new starters, leavers, departments and managers synchronised into the LMS.
• CRM and e-commerce: customer accounts, course purchases and entitlements.
• Collaboration tools: notifications in Slack or Microsoft Teams, and video conferencing for live sessions.
• Reporting: exports or APIs that feed your BI tool or data warehouse.

For each flow, ask whether it is a native connector, a paid add-on, a documented API you must build against, or a manual CSV. Our guide to LMS integrations with HRIS, CRM and payments covers the common patterns and where they break.

A practical test during the trial is to take one real flow end to end. Create a test employee in your identity provider, confirm the account appears in the LMS with the right role and group, assign a course, complete it, and check the result lands wherever your reporting lives. If any hop needs a manual step, note who will do it every week and add that time to your cost estimate.

Steps 7 to 9: risk checks, scoring and the pilot

Step 7: Set security, privacy and accessibility gates

Some requirements are not scored; they are pass or fail. Decide them before demos so a charming presentation cannot talk you out of them:

• Security: SSO and multi-factor authentication for administrators, role-based access, audit logs, encryption in transit and at rest, a documented vulnerability management process and, where relevant, independent attestations. Use our LMS security checklist as the question set.
• Privacy: where data is stored, how long it is kept, and how the platform handles access and deletion requests. If you train people in the EU, the GDPR applies; in India, check your obligations under the Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 published by MeitY. Take legal advice for your own situation.
• Accessibility: ask vendors which WCAG 2.2 level the learner interface meets and request their accessibility conformance report.
• Exit terms: confirm you can export users, completions, certificates and SCORM or xAPI results in a usable format.

Step 8: Score the shortlist with scripted demos

Cut the long list to three to five platforms using your must-haves and gates, then send each vendor the same demo script built from your real use cases. A script stops vendors from showing only their strongest screens. For example: "Show a manager assigning a compliance course to a new team member, the reminder the learner receives, and the report the manager sees when it is overdue."

Keep demos to the same length for every vendor, invite the same scorers to all of them and ask vendors to use a trial site with your own sample content where possible. If a vendor cannot show a scripted task live, score it as not demonstrated rather than taking a promise on trust.

Score every vendor on the scorecard below straight after each demo, with at least three people scoring independently. Average the scores and discuss the big disagreements, because they usually reveal a requirement that was unclear.

Step 9: Run a pilot, check references and negotiate

Take the top two platforms into a short pilot, typically two to four weeks, with real content and 10 to 30 real users across your audiences. Measure what matters to you: time for an admin to build and assign a course, learner completion without help, report accuracy and support response times. Ask each vendor for reference customers of a similar size and industry and talk to their administrators, not only their sponsors.

Write the pilot success criteria before it starts, for example "90% of pilot learners complete the onboarding path without contacting support" or "an admin can produce the monthly compliance report in under ten minutes". Agreeing the bar in advance stops the pilot from turning into a second round of opinions.

Then negotiate with the pilot results in hand. Clarify how users are counted, renewal price caps, what support is included, implementation scope, data export on exit and any minimum contract term.

Free LMS selection scorecard template

Copy this table into a spreadsheet. Adjust the weights so they total 100, keeping your must-haves as pass/fail gates rather than weighted rows. Score each vendor from 1 (poor) to 5 (excellent), multiply by the weight and divide by 5. The maximum total is 100.

Keep a separate list of pass/fail gates from step 7, such as SSO, data residency or accessibility conformance. A vendor that fails a gate is removed, whatever its weighted score.

Worked example: scoring three shortlisted platforms

Here is a hypothetical example to show the arithmetic. A 400-employee company with two factories wants onboarding, safety compliance with renewals and a small customer academy. After gates, three anonymised vendors remain. The team adjusts the weights to put more emphasis on admin effort and compliance.

The arithmetic is simple. Vendor A's total is 16 + 10 + 9 + 4 + 9 + 8 + 6 + 8 + 5 = 75, because each row is the weight multiplied by the score and divided by 5 (for fit to use cases, 20 x 4 / 5 = 16). Vendor B scores 83 and Vendor C scores 76.

In this example Vendor B leads because it handles compliance renewals well, even though Vendor C is cheaper. The team would take B and C into a pilot, because a seven-point gap is small enough that real users could change the result. The point of the scorecard is not the final number; it is that everyone can see why a platform won and what the trade-off was.

LMS selection criteria by organisation type

People often ask "what is the best LMS?" There is no single answer, because the best platform for a 40-person agency is rarely the best one for a 4,000-person bank or a test-prep academy. The same scorecard works for everyone, but the weights shift. Use this table as a starting point for your own weighting.

Questions to ask LMS vendors before you sign

Scripted demos show what a platform does. These questions show how the vendor behaves once you are a customer. Ask them in writing so the answers can be attached to the contract.

Pricing and contract

• How exactly is a billable user counted, and what happens if we exceed our band mid-term?
• Which features in the demo are add-ons, and what do they cost?
• What is the minimum contract length, and is there a cap on renewal price increases?
• What is included in implementation, and what is billed as extra services?

Product and roadmap

• Which of our must-have requirements are delivered by configuration, which need customisation, and which are on the roadmap?
• How often do you release updates, and can we test them before they reach learners?
• Which standards do you support today (SCORM 1.2, SCORM 2004, xAPI, cmi5, LTI 1.3), and can we upload our own test package during the trial?

Data, security and exit

• Where is our data stored, who can access it, and how are backups tested?
• Can you share your security documentation and accessibility conformance report?
• If we leave, what data do we get back, in what format, and how quickly?

Support and service

• What are your support hours and response targets, and do they differ by plan?
• Will we have a named contact after go-live?
• Can we speak to two administrators at customers similar to us?

Vague answers are a signal in themselves. A vendor that cannot explain its own user counting before you sign will not become clearer at renewal time.

Common LMS selection mistakes to avoid

• Buying the demo, not the daily work. Unscripted demos show the best screens. Script them around your admin tasks.
• Ignoring admin effort. Learners use the LMS for minutes a week; administrators live in it. A platform that saves them an hour a day often beats a prettier one.
• Underestimating migration. Historical completions, certificates and SCORM results are the hardest data to move. Ask each vendor exactly what their migration service covers and test a sample export early.
• Comparing first-year prices only. Renewal uplifts, add-on modules and user growth change the picture by year three.
• Skipping the pilot. A two-week pilot with real users is cheaper than a three-year contract with the wrong platform.
• Letting one stakeholder decide alone. IT, L&D, finance and at least one manager should score independently.

How we can help

If you want an independent second opinion, our engineers run vendor-neutral LMS selections: requirements workshops, demo scripts, scorecards and pilots, and we can estimate integration and migration effort before you sign. See our LMS consulting service, or talk to an LMS engineer about your shortlist.