LMS RFP guidance urges HR teams to compare vendors on evidence, not feature lists
A practical guide published by eLearning Industry on Nov. 19 sets out how employers can use a request for proposal to make Learning Management System purchases more comparable. Written by founder Christopher Pappas, it recommends defining learning and business outcomes first, then asking shortlisted vendors to respond to shared requirements, demonstrate real workflows and provide comparable cost details.
The guidance addresses a familiar procurement challenge for HR and Learning and Development teams: vendors may offer overlapping features, but those features do not necessarily solve an organization’s specific problems. A structured RFP can help connect platform selection to the needs of learners, administrators, IT, security, procurement and finance, while giving each vendor the same basis for a response. The objective, the guide says, is not to create the longest possible document, but to gather enough consistent evidence to support a sound decision.
Start with outcomes and requirements
Before drafting the RFP, organizations should identify the work the system must support. Examples in the guide include employee onboarding, compliance training, leadership development, reskilling, sales enablement, customer education and partner training. Teams should also establish relevant context, such as learner populations, administrator numbers, geographic reach, languages, expected growth, existing systems and reporting needs. A platform suited to a small internal audience may not fit an employer serving a much larger or geographically dispersed learner base.
The guide advises involving stakeholders across L&D, HR, IT, information security, privacy or legal, procurement, finance, business units, system administrators and representative learners. Their input can help distinguish learning needs from technical, operational and commercial constraints. Requirements should be grouped into functional and technical areas, with functional examples including course management, learning paths, assessments, certifications, mobile learning, reporting, accessibility and localization. Technical considerations can include APIs, single sign-on, HRIS or HCM connections, data exchange, scalability and support for standards such as SCORM and xAPI.
Rather than treating every capability as equally important, the guide recommends marking requirements by priority and separating pass-or-fail conditions from criteria that can be scored. A mandatory security standard or essential integration, for example, may be a gate for proceeding, while other capabilities can contribute to a comparative score. Vendors should also explain whether a requirement is available natively, requires configuration, depends on a third-party integration or calls for custom development. That distinction makes a simple yes less likely to conceal meaningful differences in delivery.
Make vendor responses comparable
The proposed RFP structure covers the organization and project background; objectives and use cases; functional and technical requirements; security, privacy, accessibility and governance; implementation and data migration; customer support; vendor experience and product direction; pricing; contract and exit terms; and proposal instructions. The guide also recommends asking about how learner and organizational data are used in AI-enabled capabilities, alongside broader questions about permissions, encryption, audit logs, backup and data residency where relevant to the employer.
Scenario-based questions can reveal more than a checklist of yes-or-no responses. Instead of asking whether a system supports reporting, an employer could ask a vendor to show how an administrator would create and distribute a recurring regional compliance report without vendor assistance. Other suggested questions cover internal resources needed for implementation, the limits of data exports, costs excluded from implementation estimates, pricing as learner numbers grow, platform limitations and how data can be retrieved when a contract ends. Scripted demonstrations can then let every finalist show the same learner and administrator workflows.
For evaluation, the guide offers an example scorecard assigning 20% each to functional fit and user experience, 15% each to technical fit and pricing, and 10% each to reporting and to security, privacy and accessibility. Implementation and support receive 5%, as does vendor strategy and innovation. These are illustrative weights, not a standard employers are expected to adopt. The guide says eLearning Industry’s 2026 buyer research found user experience, pricing and integrations ranked above AI in buyers’ LMS evaluations, underscoring that a prominent technology feature need not outrank core operational needs.
Assess the full cost and verify claims
A vendor score should be based on evidence as well as written claims. The guide suggests a common scoring scale, from not meeting a requirement to significantly exceeding it, and recommends checking important claims through demonstrations, technical documentation, customer references, security reviews or pilots as appropriate. Organizations should set weights before reviewing proposals to reduce the risk of shifting criteria in favor of a vendor they already prefer. After the initial review, a selection process can move through compliance checks, weighted scoring, demonstrations, technical and security review, references or a pilot, cost assessment and contract negotiation.
Price comparisons should use the same scenario and time horizon for every vendor, with a multi-year view such as three years. In addition to subscription fees, employers should ask about implementation, migration, integrations, configuration, premium modules, support, training, storage, professional services, usage charges, renewal increases and likely costs as the learner population expands. Contract duration, renewal terms, price increases, termination, data ownership, export formats and transition assistance also matter. For HR teams, the central takeaway is that an RFP works best as a decision framework linking learning goals, user experience, technology fit, service and total cost—not as a feature-counting exercise or a substitute for professional judgment.