Measure. Optimize. Pass.

Automated QA for eLearning. Reduce errors. Ship with confidence.

Upload SCORM packages, run automated QA checks, enforce showstopper rules, and export audit-ready reports.

120+
Automated checks on every course
Readiness score across versions Re-scan to track it
Illustrative • Animates on load
~3s
Typical scan of a full course

The problem with manual QA

Manual QA is slow, inconsistent, and often takes as long as development. Failures cause launch delays, audit risk, and poor learner experience. In regulated industries, QA failure is operational risk.

Slow & repetitive

Manual checks across slides, interactions, and media consume hours per course.

Inconsistent outcomes

Different testers catch different issues — results vary from release to release.

Audit exposure

No clean evidence trail means higher risk during audits, compliance reviews, or incident investigations.

Platform features

FULLPASS reads the published slide model your authoring tool produces — every object, trigger, timeline and layer — so it can test how a course behaves, not just how it reads.

Functionality

Next buttons disabled and never re-enabled, or locked until the timeline ends, with the exact wait in seconds. Buttons that reload their own slide. Instructions naming a button that isn't there. A copied trigger that fires with the one it was copied from. Learners left with no way on.

Simulation steps

Screen recordings checked against themselves: a recorded click that misses its highlight, a callout pointing somewhere else, a patch that has lost its text, a stray box laid over the recording.

Layout & formatting

Text cut off by the slide edge, or running past the bar it sits on. Text printing over other text while both are on screen. Pictures covering words. Headings that jump between slides. Elements almost — but not quite — centred, and shapes left in Storyline's default blue.

Consistency & storyboard

The course measured against itself — a project name that reads differently on one slide, Step 07 missing from Steps 01 to 08 — and, if you upload them, against its storyboard and brand palette: screens missing or out of order, wording changed from the script, colours off-brand.

Copy & proofing

Spelling in British and American English, commonly confused words, missing words, double spaces, repeated words, leftover placeholder text, Word-paste corruption, and the same term spelled two ways.

Audio & video

Voiceovers that play over each other, narration missing from a slide, and captions. Inside a video: an empty screen while the voice carries on, text too faint to read or cut short, a label that flickers, a "click here" nobody can click, and spelling mistakes burnt into the picture.

SCORM & LMS tracking

Manifest validity and dangling references. Whether the course ever records completion, saves its data and closes the session. A "slides viewed" target no learner can reach, a course that reports "Passed" with no test, or a player that won't scale to the LMS window.

Media & accessibility

Oversized and oversampled images, broken asset references, missing alt text, text contrast measured against the shape behind it, and http:// links that browsers silently block inside an LMS.

Sign-off & audit

Showstoppers block sign-off. Dismiss a false positive with a reason and it is kept in the audit trail, not deleted. Excel and PDF export, and a version history showing whether quality is improving.

How it works

A simple workflow designed for speed, accuracy, and sign-off control.

1
Upload a SCORM package or a video — with its storyboard and brand colours if you have them
2
System analyses course structure
3
More than 120 checks run against every slide, asset and trigger
4
Review findings by slide number, dismissing anything that is not a real problem
5
Export to Excel or PDF, and sign off — blocked while any showstopper remains

Why FULLPASS?

A quick, honest comparison: FULLPASS vs manual QA.

Using FULLPASS

✔Automated checks catch issues early (navigation, simulations, spelling, links, media, SCORM)
✔Consistent enforcement: showstoppers block sign-off
✔Audit-ready evidence & attribution reduce compliance risk
✔Clear severity categories (Critical / Major / Minor) speed up fixes
✔Exportable reports for stakeholders and LMS readiness

Manual QA

✖Time-consuming, repetitive slide-by-slide checking
✖Inconsistent results (depends on who tests)
✖Errors slip through: broken interactions, missed links, UI drift
✖No reliable audit trail or standard sign-off enforcement
✖Higher risk of launch delays and poor learner experience

Pricing

Start free with three courses. No card until you are sure it earns its place.

Monthly Yearly 2 months free
Billed monthly. Cancel any time.

Free trial

Free
• 3 courses in total
• 14 days from sign-up
• Every automated check
• PDF and Excel export
• No card required · one per person

Solo

$29 / mo
• 12 courses per month
• One user
• Every automated check
• PDF and Excel export
• Course history and trend

Studio

$59 / mo
• 40 courses per month
• Up to 3 people
• Every automated check
• PDF and Excel export
• Shared course history

Team

$99 / mo
• 150 courses per month
• Up to 10 people
• 2 managers handle billing and the team
• Shared course history
• Dismissal audit trail
• Priority support

Need more than 150 courses a month, or more than 10 people? Email info@fullpass.ai and we will sort something out.

Demo scan

No backend needed — this simulates upload, scanning, and a results dashboard.

Ready to scan course
QA Score
--%
Final QA score
Status
--
Certification / readiness
LMS Readiness
--
SCORM + gating result
Critical Issues
0
Showstoppers
Major Issues
0
Must fix
Minor Issues
0
Nice to fix
Top findings
—

Help and support

A small team that answers its own email. No ticket queue, no chatbot — you get one of the people who built it.

What can I upload?

SCORM 1.2 and SCORM 2004 packages, courses authored in Articulate Storyline or Rise 360, and standalone video files. Up to 2 GB. Alongside a course you can add its storyboard (.pptx, .docx or PDF) and your brand colours to check it against.

Is my course stored?

No. A package is held in memory while the scan runs and discarded when it finishes. It is never written to our disks, never backed up, and never sent to anyone else. Only the report is kept.

Does it replace manual QA?

No, and we will not pretend otherwise. FULLPASS reads the published files — it does not open your course in a browser and click through it. A clean report means the mechanical faults are gone, not that the course is good.

Can I cancel?

Any time, from the billing portal. Cancellation takes effect at the end of the period you have paid for, and you are not charged again. The refund policy has the detail.

Built for real QA

Built by experienced eLearning QA practitioners, designed inside a high-pressure global airline learning environment, created to handle audits, compliance, and delivery at scale.