LMS RFP Template: The Questions to Ask Every Vendor

Last updated July 2026.

An LMS RFP template should contain seven sections: company background and goals, functional requirements, technical and security requirements, implementation and migration, support and service levels, pricing and commercial terms, and vendor viability. Score responses with a weighted rubric rather than a yes/no checklist, weighting functional fit around 30 percent, technical fit 15, ease of use 15, pricing 15, implementation 10, support 10 and vendor stability 5. The section that saves the most money is pricing, because that is where the units are defined and where the add-ons hide.

Most LMS RFPs fail the same way. The buyer sends a 200-question feature checklist, every vendor answers "yes" to almost everything, and the decision ends up being made on the demo that happened to be scheduled last. A useful RFP does the opposite: it asks fewer questions, insists on evidence, and forces vendors to be specific about the two things they most want to keep vague, which are pricing units and implementation effort.

Before you write the RFP: define the job

Write two paragraphs describing what the LMS must do in your company, in plain language, before you write a single requirement. Something like: "Onboard 40 new hires a quarter across five roles, deliver six mandatory compliance courses a year to 600 employees, track OSHA and HIPAA certification expiry with automatic reminders, and produce a completion report an auditor will accept." That paragraph decides which requirements are must-haves and stops the RFP from turning into a wish list.

Then set the constraints: budget range, target go-live date, number of learners in year one and year three, integrations that must exist on day one, and who will administer the system. Vendors that cannot meet a hard constraint should be disqualified before they consume evaluation time. If you have not sized your budget yet, the published and quoted ranges on our corporate LMS pricing comparison are a reasonable place to anchor.

The seven sections of an LMS RFP template

1. Company background and goals

One page. Headcount, industry, locations, current system if any, learner count in year one and year three, the training programs you run, the go-live date, and the evaluation timeline with dates. Include the budget range unless you have a strong reason not to. Hiding the budget mostly guarantees you will receive three proposals that are all out of range.

2. Functional requirements

Group requirements into must-have, should-have and nice-to-have, and cap the must-haves at about fifteen. Ask each question so a "yes" costs the vendor something. Instead of "Do you support certification tracking?", ask "Describe how an administrator sets a certificate to expire 12 months after completion, who is notified 30 days before expiry, and what the auditor-facing report looks like. Include a screenshot."

The functional areas worth covering for most corporate buyers: course authoring and templates, SCORM and xAPI support, assignment by role, group and location, onboarding paths, mandatory training with due dates, certification expiry and renewal, assessments and question banks, reporting and export, learner notifications, mobile access, and multi-language if you operate outside the US. If your program is compliance-led, our page on compliance training software lists the specific capabilities auditors tend to ask about.

3. Technical and security requirements

Ask for the integration method, not just the integration name: native connector, API, SFTP file drop or middleware. Confirm SSO protocol support (SAML 2.0, OIDC), SCIM provisioning for automatic user creation and deactivation, HRIS sync direction and frequency, data residency, retention and deletion policy, current SOC 2 Type II or ISO 27001 status with report date, and WCAG 2.2 AA accessibility conformance with a VPAT.

One question that separates vendors quickly: "Which of these are included in the plan you are proposing, and which require a higher tier or an additional fee?" SSO in particular is often a tier upgrade.

4. Usability

Usability cannot be answered in a document, so use the RFP to set up the test. Require each finalist to run the same scripted scenario in a live environment: create a course from scratch, assign it to a group of 25, set a due date, trigger a reminder, and pull a completion report. Time it. Have the person who will actually administer the system do the clicking, not the L&D director.

5. Implementation and migration

Ask for a week-by-week implementation plan for a company your size, the total professional services cost, how many hours of your team's time it assumes, who migrates existing learner records and completion history, what formats they accept, and what happens to your data and content if you leave. Content portability and an exit path matter more than people expect, and they are cheapest to negotiate before you sign.

6. Support and service levels

Support hours in your time zone, guaranteed first-response times by severity, escalation path, whether you get a named customer success contact, whether support is included or a paid tier, and the uptime commitment with the remedy if it is missed. Ask for last year's actual uptime figures rather than the contractual number.

7. Pricing and commercial terms

This is where the money is. The questions that matter:

• How do you define a user: registered, active in the month, or seats purchased?
• Quote the three-year total for our year-one and year-three headcount, including every fee.
• What happens if we exceed the tier mid-contract, and at what rate?
• Is there a cap on annual price increases at renewal? What number?
• Which of these are extra: SSO, API access, additional portals, content library, premium support, extra admin seats?
• What is the minimum term, the notice period, and the renewal mechanism?
• What discount applies to a multi-year commitment, and what do we give up to get it?

Insist on a single three-year total-cost figure from every vendor, on the same headcount assumptions. It is the only number that compares cleanly across published-price and quote-based platforms. Once you have the winning proposal, it is worth having someone read the contract terms against the proposal before signature, because auto-renewal clauses and uncapped uplifts routinely survive into the final paper after being waved off on a call.

Scoring: use a weighted rubric

Score each section 0 to 5 against defined criteria, multiply by the section weight, and total. Define what each score means before you read any responses: 5 means demonstrated in a live environment, 3 means available today with configuration, 1 means possible with custom work, 0 means not available. A roadmap answer without a contractual date scores 0. That single rule removes most of the noise from an LMS evaluation.

Require evidence with the response: a demo clip, a screenshot, a report export, or a reference customer of similar size and industry available within 10 business days. Vendors who cannot produce a comparable reference are telling you something.

A realistic six-week evaluation timeline

Common questions about LMS RFPs

Do I need an RFP to buy an LMS?

Not always. If your budget is under roughly $15,000 a year and you have fewer than about 200 learners, a structured trial of three shortlisted platforms will get you a better answer faster than a formal RFP. A full RFP earns its overhead when procurement requires it, when spend crosses an approval threshold, or when migration of existing records makes switching costs high.

How many vendors should I include in an LMS RFP?

Five to seven. Fewer than four and you have no pricing leverage or comparison baseline. More than eight and scoring becomes a full-time job for two weeks, which is usually when evaluations stall. Shortlist by hard constraints first: budget range, must-have integrations, and whether they serve companies your size.

What questions should I ask an LMS vendor about pricing?

Ask how a user is defined, what the three-year total cost is at your projected headcount including all fees, what happens if you exceed your tier mid-contract, whether annual increases are capped and at what percentage, and which features sit behind a higher tier. Those five questions surface most of the difference between a headline rate and a real invoice.

What is the difference between an RFI and an RFP for an LMS?

An RFI is a short information request used to build a shortlist when you do not yet know the market: capabilities, rough pricing, customer profile. An RFP comes after, with detailed requirements and a formal scored response. For most corporate LMS purchases you can skip the RFI, since vendor websites and comparison research already cover what an RFI would tell you.

How long does an LMS implementation take?

It depends entirely on the platform class. Self-serve platforms are live in days, with your first course assigned the same week. Mid-market platforms typically run two to six weeks including data migration and SSO. Enterprise suites with HRIS integration, multiple portals and custom reporting commonly take three to six months. Ask for a week-by-week plan rather than a range.

Where CompanyLMS fits in your RFP

CompanyLMS is built for the buyer whose requirements are onboarding paths, mandatory compliance training with due dates, certification expiry tracking with reminders, and reporting an auditor will accept, without an implementation project in front of it. Pricing is published flat per seat, so the three-year total cost question answers itself. If you want to see how it scores against the platforms you are shortlisting, start with the best corporate LMS comparison, the TalentLMS vs Docebo breakdown, or run the scripted demo scenario yourself in the Course Studio above.