Discovery
How will you confirm requirements before launch?
Requirements map, integration inventory, success criteria, data boundaries
Implementation and quality assurance
Review the work, evidence, owners, and approval points for discovery, migration, integrations, accessibility, testing, training, and launch support.
Agree on acceptance before expanding the rollout
Start with a representative content sample and the actual destination system. Assign an owner to each check so your team can identify what is ready and what still needs work.
- Define the source formats, question types, and required metadata.
- Review imported content and resolve the warnings.
- Verify the learner experience in the intended destination.
- Check access, accommodations, results, and exports.
- Record unresolved limitations and approve the next scope.
The sequence below is a planning framework. Dates, responsibilities, support, and pricing belong in the agreed project scope.
Plan your evaluation →Move from discovery to launch
Each phase has a question and a deliverable. Administrators, information technology teams, accessibility reviewers, and assessment teams can review the results.
Migration proof
Can you move our content and keep its fidelity?
Sample import, fidelity report, transformation notes, preserved source package
Integration proof
Will LMS, roster, SSO, and export flows work in our environment?
LTI launch test, Deep Linking sample, AGS passback proof, NRPS membership read, OneRoster import report, result export sample
Accessibility review
How will the team verify accommodations and accessibility?
Support matrix, test plan, AT rotation, VPAT/ACR status, remediation log
Pilot
How will we reduce risk before a high-stakes window?
Pilot form, test roster, submit receipts, recovery drills, signoff notes
Launch
What happens during the live assessment window?
Launch checklist, monitoring plan, escalation contacts, receipt and recovery workflow
Quality assurance evidence
| QA area | Evidence to include | Status |
|---|---|---|
| Requirements traceability | Each RFP requirement maps to a product capability, test, artifact, or hold note. | Evidence in progress |
| Unit and route checks | Authoring, delivery, form, and worker routes have smoke checks before release. | Planned evidence |
| Migration validation | Import sample set includes fidelity counts, warnings, preserved source, and reviewer signoff. | Ready |
| Integration testing | The team tests LTI launch, Deep Linking, AGS, NRPS, OneRoster, exports, and role maps in the customer environment. | Ready |
| Accessibility testing | The team tracks automated checks, assistive technology tests, user sessions, and ACR updates. | Evidence in progress |
| Load and recovery testing | The delivery test plan covers launch, submit, reconnect, old tab, and queue recovery scenarios. | Evidence in progress |
| UAT and training | Administrators, instructors, accessibility reviewers, and support teams get role-specific scenarios. | Evidence in progress |
Launch packet
Request the implementation plan
The implementation packet includes a milestone plan, QA matrix, user acceptance test checklist, accessibility test plan, training outline, and launch support model.