eLearning course QA checklist: what to check before launch (and how to run it in zipBoard)

A course QA pass catches the problems learners would otherwise report: broken links, wrong answers, typos, narration that doesn't match the screen, and screens that break on a phone. Use the checklist below for every course, whether it was hand-built or generated with AI. The second half shows how to run the QA pass in zipBoard so every issue has an owner and a status.

The checklist

Content

• Facts, figures, names and policy references are correct and current
• Learning objectives are covered, and nothing from the source material is missing
• Spelling, grammar, terminology and brand style are consistent

Assessments

• The correct answer is marked correct, and the feedback text matches the answer
• The passing score and number of attempts are set as intended

Media

• Audio and narration match the on-screen text; captions are present and accurate
• Videos play, and images are clear and have alt text

Navigation and functionality

• Buttons, links, menus and branching all go where they should
• The course resumes where the learner left off and reports completion as expected

Devices and accessibility

• Layout works at desktop, tablet and mobile sizes
• Keyboard navigation works, contrast is sufficient, and the reading order is logical

LMS readiness

• The SCORM version matches what your LMS expects, and the package has index.html (or its start file) at the top level

Running the QA pass in zipBoard

1. Upload the course as a SCORM or HTML ZIP. See Review a SCORM course without an LMS.
2. Create task types for the checklist areas (Content, Assessment, Media, Navigation, Accessibility) so each issue is filed in the right bucket. See Statuses and task types.
3. Assign QA reviewers and a due date. See Mandatory reviewers.
4. Log issues on the screen where they happen. Each comment becomes a task with an assignee and priority.
5. Fix and re-upload as a new version, then compare versions to verify the fixes. See Compare SCORM versions.
6. Export the issue list to CSV as your QA sign-off record. See Exporting data.

If a package won't load, see I cannot play my SCORM file.