Most eLearning projects that go over budget or produce the wrong output can trace the problem back to the RFP. Vague briefs produce vague proposals. When vendors cannot scope accurately, they either pad costs to protect themselves or underprice to win — both outcomes create problems before the project starts. This guide covers every section of an eLearning RFP, what information each section needs to contain, and how to evaluate what comes back.
Why the RFP Is the Most Important Document in Your Project
The RFP defines the project before any vendor is involved. It forces internal clarity on what you need, how you will evaluate options, and what success looks like. Organisations that skip or rush the RFP almost always pay for it later in scope disputes, missed deadlines, and rework costs. The time you invest in writing a clear RFP is returned many times over during vendor selection and project delivery.
The three outputs of a good eLearning RFP
- Comparable proposals — vendors respond to the same brief, so you can evaluate like-for-like
- Accurate pricing — scoped requirements produce defensible cost estimates, not guesses
- A project baseline — the approved RFP becomes the reference document for scope management throughout the project
The Six Sections Every eLearning RFP Needs
Organisation and project background
What to include
- Brief description of your organisation, industry, and size
- The business problem or opportunity driving this project
- Who the learners are: role, geography, language, technical access level
- Any relevant history: existing eLearning, previous vendor experience, LMS in use
Why it matters: Vendors need context to scope the right solution. Without understanding your audience and constraints, they are guessing.
Project scope and deliverables
What to include
- Number of modules or courses required
- Estimated finished learning hours per module (be realistic — compress for eLearning)
- Interactivity level: click-through / standard interactive / simulation-based
- Media requirements: voiceover, animation, custom video, illustrations
- Languages and localisation requirements
- Accessibility standard required (WCAG 2.1 AA is standard)
Why it matters: This is the core of the RFP. Every line here directly affects cost and timeline. Vagueness here is expensive.
Technical requirements
What to include
- LMS and SCORM/xAPI version requirement (e.g. SCORM 1.2, xAPI)
- Device and browser support requirements
- Any integration requirements (HR system, user data, assessment platform)
- Hosting and file delivery preferences
- Source file format and ownership requirements
Why it matters: Technical mismatches discovered post-delivery are expensive and sometimes unfixable. Specify requirements upfront.
Project constraints and commercial terms
What to include
- Project timeline and key milestone dates
- Budget range (include this — see note below)
- Review and approval process: who signs off, how many rounds, timeline per round
- IP and content ownership expectations
- Confidentiality requirements for source materials
Why it matters: Constraints help vendors propose realistic solutions. Hidden budget and opaque approval processes are the two most common causes of project overruns.
Evaluation criteria and vendor requirements
What to include
- How proposals will be scored (e.g. 40% technical approach, 30% experience, 20% price, 10% team)
- Required evidence: portfolio samples, case studies, referee contacts
- Team requirements: instructional designer, project manager, QA process
- Any mandatory vendor qualifications or certifications
Why it matters: Transparent evaluation criteria attract serious vendors and reduce the time you spend on proposals that do not meet minimum requirements.
Submission instructions and timeline
What to include
- Submission deadline and format (PDF, email, portal)
- Clarification question deadline and process
- Estimated shortlisting and decision dates
- Contact person for all RFP correspondence
Why it matters: Clear process details signal that you are an organised client — which attracts better-quality vendor responses.
Should You Include a Budget in the RFP?
Yes. Including a budget range consistently produces better proposals. Without a budget, vendors face a binary choice: overscope to be thorough, or underscope to be competitive. Neither serves you well.
A budget range (e.g. "$80,000–$120,000 for the full programme") allows vendors to propose the best solution within your parameters. Proposals become directly comparable because they are built to the same financial framework. Vendors who cannot deliver quality at your stated range will self-select out — saving everyone time.
If procurement rules prevent disclosing a budget, ask vendors to propose at two price points: a "core scope" and a "full scope" — it achieves a similar result.
How to Score eLearning Proposals
A structured scoring matrix removes subjectivity from vendor selection. The four evaluation dimensions and suggested weights for a typical eLearning project:
| Dimension | Weight | What to assess |
|---|---|---|
| Technical approach and solution design | 35% | Does the vendor understand your learning objectives? Is their proposed instructional approach sound? Do portfolio samples match the quality and interactivity level you need? |
| Relevant experience and case studies | 25% | Have they delivered comparable projects — similar content type, industry, audience size, language requirements? Verified references from past clients in your sector carry significant weight. |
| Team, process, and project management | 25% | Who specifically will work on your project? What is their review and revision process? How do they manage scope change? What does their QA process look like? |
| Commercial and timeline | 15% | Is the pricing transparent and itemised? Does the timeline match your requirements? What are the payment milestones? What is included in maintenance and post-delivery support? |
Common RFP Mistakes That Cost You Later
Specifying the tool, not the outcome
Saying "must be built in Articulate Storyline" limits vendors unnecessarily. Specify the output requirements (SCORM 1.2, responsive, accessible to WCAG 2.1 AA) and let vendors propose their preferred tool — unless you have a genuine operational reason for a specific platform.
Underestimating content volume
L&D teams consistently underestimate how much content they have. Before finalising the RFP, list every ILT session, document, and SME interview that constitutes source material. Vendors scope based on the source material volume, not the finished module length.
Not specifying the review process
Unlimited review rounds and slow stakeholder approval are the most common causes of eLearning project overruns. Specify in the RFP: number of review rounds, who has approval authority, and the expected turnaround time for each review.
Sending to too many vendors
Open RFPs attract low-quality responses. Quality eLearning studios evaluate RFPs before responding — they will decline if the list is too long. Pre-qualify with a brief questionnaire, then send the full RFP to three to five shortlisted vendors.
Template
eLearning RFP Template
A complete eLearning RFP template with all six sections pre-structured, guidance notes for each field, a vendor evaluation scoring matrix, and a proposal comparison sheet. Edit for your project and send directly to vendors. Want us to manage the vendor evaluation for you? Book an EQUIP Strategy Session.
Frequently Asked Questions
How long should an eLearning RFP be?
An effective eLearning RFP is typically 8–15 pages. Long enough to give vendors the information they need to scope accurately, short enough to read in under 30 minutes. The most common mistake is a 30+ page document full of procurement boilerplate — this discourages quality vendors and does not improve proposal quality.
Should I include a budget in my eLearning RFP?
Yes — a budget range produces better proposals. Without one, vendors either overscope or underscope. A budget range allows vendors to propose the best solution within your constraints, making proposals directly comparable. If procurement rules prevent it, ask vendors to propose at a "core" and "full" price point.
How many vendors should I invite?
Three to five is the standard recommendation. Fewer limits comparison; more than five creates disproportionate evaluation effort and discourages serious vendors. Pre-qualify with a capability questionnaire before sending the full RFP to your shortlist.
What are the most important things to evaluate in a proposal?
The four most predictive factors: (1) Portfolio samples matching your content type and interactivity level. (2) Instructional design capability — do they employ qualified instructional designers? (3) Project management process — how do they handle scope changes and review cycles? (4) Post-delivery support. Price matters but rarely predicts project success better than these four.
Key Takeaways
A well-structured eLearning RFP protects your project from the start. It produces comparable proposals, surfaces vendor quality, prevents scope disputes, and gives you a project baseline to manage against throughout delivery. The investment in a thorough RFP is the cheapest risk management available at the start of any eLearning project.
Use the eLearning RFP Template to structure your brief — all six sections are pre-built with guidance notes, and the vendor evaluation scoring matrix is included.