An authoring tool RFP is a structured request that asks eLearning authoring vendors to answer the same requirements and questions, so you can score them side by side. For a training company, that means testing what a corporate buyer rarely needs: inherited client courses, many brands, and LMSs you do not control.
As of October 2026, searching the phrase mostly returns software for answering RFPs, plus LMS and custom-development templates. The authoring tool checklists we found were short, dated or gated. This post adds a weighted scoring table and a vendor question list to copy.
Disclosure: SimpliAuthor is made by the company that publishes this site. It is one possible candidate, and the checklist below is vendor-neutral.
Key takeaways
- Group requirements into ten categories, and mark four as pass or fail gates before scoring anything.
- Agree the weights in writing before any demo, so a polished presentation cannot move them.
- Run a proof of concept with your worst real package, not the vendor’s demo course.
What should an authoring tool RFP include?
An authoring tool RFP for a training company should include six parts: your business context and use cases, requirements grouped by category, a vendor questionnaire, a weighted scoring method, proof-of-concept instructions, and commercial terms with a timeline. Each vendor receives identical documents so the answers compare line by line.
A Miyens guide to eLearning RFPs (April 2026) lays out six sections of its own, but it is written for hiring a custom development vendor, not for buying a tool. It advises sending the full RFP to three to five pre-qualified vendors.
A small team can skip the full document and run a three-tool shortlist with a proof of concept. Use a full RFP when procurement or several approvers demand a paper trail. To build the shortlist, start with our iSpring alternatives for training providers comparison of seven tools.
How should an authoring tool RFP test SCORM, xAPI and cmi5 output?
A training company should test SCORM, xAPI and cmi5 output by naming the exact LMS behaviors required, then checking them in the LMSs clients actually use. A bare claim of support proves little, so specify package versions, reported data and where it is sent.
According to xapi.com’s guidance on xAPI and your RFP, “You need to be specific about how xAPI will be used.” That page is written for LMS buyers and was last modified in December 2018, so use the principle, not its sample list. The xapi.com cmi5 page defines cmi5 as “an xAPI Profile that bridges the SCORM and xAPI divide by defining interoperability rules,” released in 2016, with adoption that has lagged.
Write each standard as a behavior you can test:
- SCORM 1.2 and SCORM 2004: the package launches, reports completion and score, and resumes in your clients’ LMSs.
- xAPI: the tool sends statements to a named learning record store, and the vendor lists the data each statement carries.
- cmi5: the tool exports a package your LMS can launch, or the vendor says plainly that it does not.
Pro tip: Ask for the Statements, Not the Checkbox. Ask each vendor to send the raw xAPI statements or SCORM runtime values that a short test course produces. Compare them with what your clients’ reports need.
How do you check accessibility, AI and security claims?
Checking accessibility, AI and security claims means asking for written evidence on each, then testing a sample. Accessibility needs a conformance report and a look at real output, AI needs written data terms, and security needs hosting and access details that match your client contracts.
Accessibility. The W3C’s ATAG 2.0, a W3C Recommendation since 24 September 2015, has two parts: “Make the authoring tool user interface accessible” and “Support the production of accessible content.” The Information Technology Industry Council says a VPAT completed for a specific product is an Accessibility Conformance Report, that vendors declare their own degree of conformance, and that it does not review or approve VPATs. Treat the report as a claim and test a sample course yourself. Our post on accessible eLearning for corporate clients covers what buyers ask.
AI. Ask whether your content trains any model, where it is processed and stored, whether AI can be switched off per project, and who pays for usage. Some tools accept your own AI provider key. As of October 2026, SimpliAuthor’s AI authoring page says it does.
Security and hosting. Ask for the hosting region, encryption, single sign-on, role-based access and certifications held, then compare them with your client contracts. We did not test any vendor’s security.
How do you score vendors in an authoring tool RFP?
To score vendors in an authoring tool RFP, give each requirement category a weight so the weights total 100, rate each vendor from 0 to 5 per category, and multiply. Set a few categories as pass or fail gates first. Agree the weights before any demo, so a polished presentation cannot shift them.
These weights are our starting point, not an industry standard. Copy the table into a spreadsheet and add a score column per vendor.
| Category | Weight | What earns a 5 out of 5 | Gate? |
|---|---|---|---|
| Output standards and tracking | 12 | Exports every package format your clients’ LMSs accept; xAPI or cmi5 behavior is documented and passes your test | Yes |
| Editing inherited and published courses | 12 | You can change a package you did not build, with or without source files, and re-export it | No |
| Multi-client branding and reuse | 12 | One course becomes several branded versions without a rebuild; templates and media are shared | No |
| Collaboration and review | 8 | Reviewers comment without a paid seat; version history shows who changed what | No |
| Accessibility documentation | 12 | Current conformance report for the tool and its output, plus a process for fixing issues | Yes |
| AI features and data handling | 8 | AI is optional; written terms cover training use, storage and processing location | If clients restrict AI |
| Security and hosting | 10 | Hosting region, encryption, access control and sign-on match your client contracts | Yes |
| Licensing and total cost | 12 | Three-year cost is clear, including reviewer seats, add-ons, renewals and price caps | No |
| Support and training | 6 | Written response times, team onboarding, current documentation | No |
| Exit and lock-in | 8 | Source and published files export in formats another tool or LMS can open; exit terms in writing | Yes |
A vendor scoring 4 out of 5 on a category weighted 12 earns 9.6 points. Add the ten results for a total out of 100, and drop any vendor that fails a gate.
Adjust the weights to how you earn money: raise editing if you mostly inherit client courses, and raise reuse if you sell branded variants. The Miyens guide shows a four-row weighted table but does not explain its weights, so write down yours and why.
Which questions should the vendor questionnaire ask?
The vendor questionnaire for an authoring tool RFP should ask two direct questions per category and request a document or demo as proof for each. Avoid questions a bare yes can answer. The table is a starter set to paste into a spreadsheet, with one answer column per vendor.
| Category | Questions to send | Evidence to request |
|---|---|---|
| Output standards | Which SCORM, xAPI and cmi5 outputs do you export? What does each report, and where does it go? | Sample packages and raw tracking data |
| Inherited courses | Can we edit a published package without its source files? What breaks on re-export? | Live demo on our file |
| Branding and reuse | How do we make ten branded versions of one course? Where do themes and media live? | Demo with two client brands |
| Collaboration | Can reviewers comment without a paid seat? How are approvals recorded? | Trial with an outside reviewer |
| Accessibility | Do you publish a conformance report for the current version, covering the tool and its output? How are issues fixed? | Dated, versioned report |
| AI and data | Is our content used to train models? Where is it processed? Can we turn AI off or use our own key? | Written data terms |
| Security | Where is data hosted? Which access controls, sign-on and certifications apply? | Security documentation |
| Licensing | What is the three-year cost for our author and reviewer counts? What are renewal caps and add-on fees? | Itemized quote |
| Support | What are your response times? What onboarding do you provide? | Support terms |
| Exit | If we leave, what can we export, in which format, and how fast? | Export test and contract clause |
For the cost row, insist on a quote built from your real seat counts. Our Articulate 360 pricing breakdown for training companies shows what that comparison looks like for one vendor.
How do you run a proof of concept with your worst real package?
A proof of concept for an authoring tool uses your worst real package, not the vendor’s demo course. Give every shortlisted vendor the same old, messy, client-branded course and the same tasks, then time the results. Using one file for everyone means differences come from the tool, not the sample.
Run it in this order:
- Pick your most awkward package: the oldest, largest or oddest-tracking one. Get client permission and remove confidential content.
- Give each vendor the same three tasks: change body text and a quiz pass mark, rebrand the course for a second client, and re-export it.
- Launch each export in two LMSs you actually use. Check completion, score and resume.
- Ask an SME and a client-style reviewer to leave feedback in the tool without vendor help.
- Run a keyboard-only pass and a screen reader pass on the output, then compare them with the vendor’s conformance report.
Task two reflects the work in our guide to white-label eLearning for corporate clients. If the package has no source files, our walkthrough on how to edit a SCORM file without the source files explains the options for task one.
Pro tip: Score Straight After Each Task. Fill in the scoring sheet the moment a task ends, with minutes spent and defects found. Scores written a week later drift toward the most polished demo.
What red flags show up in vendor answers?
Red flags in vendor answers are replies that sound complete but cannot be checked: a bare yes, a missing document, or a refusal to run your file. Strong products can usually be shown, so score a vague reply as zero until the vendor supplies evidence.
Watch for these patterns:
- “Yes, we support xAPI” with no statements, no learning record store and no list of data sent.
- An accessibility statement that covers the vendor’s website but not the tool or its output.
- No way to export a course in a form another tool or LMS can open.
How long should an authoring tool RFP take?
A focused authoring tool RFP can run about six weeks from kickoff to decision, though your procurement rules may change that. This timeline is our suggested plan, not an industry benchmark, and most of it goes to the proof of concept and scoring.
- Week 1: agree stakeholders, gates, weights and the proof-of-concept package.
- Week 2: send the questionnaire to three to five pre-qualified vendors.
- Week 3: score the answers and cut to two or three vendors.
- Weeks 4 and 5: run the proof of concept.
- Week 6: hold the scoring session, check references and negotiate terms.
What should you do next?
Your next step this month is to write the gates and weights with your delivery team, then send the questionnaire to three to five vendors. Agree the proof-of-concept package at the same time, and let the scores decide rather than the most impressive demo.
SimpliTrain, which is made by the same company that publishes this site, offers a free LMS RFP template and questionnaire, a DOCX and an XLSX behind a short form as of October 2026. It is for LMS selection, not authoring tool selection.
If SimpliAuthor makes your shortlist, read its AI course authoring page first. As of October 2026 it describes AI authoring, a Bring Your Own AI key and a paid Visual SCORM Editor for compiled packages. It does not state SCORM versions, xAPI, cmi5 or WCAG conformance, so send it the same questionnaire.
Frequently asked questions
What is an authoring tool RFP?
An authoring tool RFP is a written request that asks eLearning authoring vendors to answer the same requirements and questions, so a training company can compare them fairly. It is for buying the tool, not for hiring a course developer.
How many vendors should receive an authoring tool RFP?
Three to five is a workable range. A Miyens guide on eLearning RFPs, written for hiring custom development vendors, advises pre-qualifying and then sending the full RFP to three to five. Each extra vendor adds a proof of concept to run and score.
Should an authoring tool RFP require xAPI or cmi5?
Only if a client or report needs them. The xapi.com guidance says to be specific about how xAPI will be used rather than listing it as a checkbox. Make SCORM export a gate, and treat xAPI and cmi5 as scored items unless your clients’ LMSs and reports depend on them.
Do I need a VPAT from an authoring tool vendor?
Ask for one, but treat it as the vendor’s own claim. The Information Technology Industry Council says vendors declare their degree of conformance and that it does not review or approve VPATs. Request the current report, then test a sample course.
Can I use an LMS RFP template for an authoring tool?
Only partly. LMS templates are written around running learners and courses, not building them. Reuse the commercial, legal and submission sections, then replace the functional requirements with the ten categories in this post. Check each borrowed requirement for features, such as learner management, that authoring tools lack.



