Independent review of your SCORM build
A senior pair of eyes on the SCORM package, the authoring-tool output, or the in-house code your team wrote. We tell you what is wrong, what is risky, and what to do about it — in a written report you can hand to leadership or to the vendor.
$200/hr · 2-hour minimum · Written report (5-10 pages) · 3-5 business days
When a code review pays for itself
A few common moments where an independent technical voice saves a lot of money.
A vendor delivered SCORM and you do not trust it
They say it is done. You want a second technical opinion before you sign the acceptance certificate or release the final payment.
You inherited a SCORM catalog from another team
Hundreds of courses, no documentation, and an LMS migration on the horizon. A review tells you what is safe to migrate vs. what needs rebuilding.
Tracking is silently wrong and you cannot reproduce it
Some learners complete. Some do not. Reports look right in the authoring tool and wrong in the LMS. We trace the cmi.* calls and find the gap.
Your team is new to SCORM and learning the hard way
A review doubles as a teaching exercise. The written report explains the "why" so your in-house developers can avoid the same mistakes on the next course.
What we cover
A structured pass across the technical surface of your course or build.
Manifest & packaging
imsmanifest.xml structure, resource declarations, dependencies, organization hierarchy, schema version conformance.
SCORM API calls
cmi.* and SCORM 2004 API usage, suspend_data handling, completion/success status, score reporting, exit / unload behaviour.
Accessibility (WCAG 2.1)
Keyboard navigation, screen-reader compatibility, contrast, focus management, captioning, ARIA usage in interactive elements.
LMS compatibility
Behaviour in SCORM Cloud and your target LMS (Moodle, Cornerstone, TalentLMS, Canvas, Docebo, SuccessFactors, Totara, and others).
Cross-device & cross-browser
Chrome / Firefox / Safari / Edge on desktop, iOS Safari and Chrome Android on mobile. Touch interactions, viewport behaviour, audio playback.
Performance & payload
Initial load time, asset weight, audio/video encoding, JS bundle size, animation jank, and the cost of authoring-tool runtimes.
Content security
Inline credentials, exposed API keys, mixed-content warnings, CDN dependencies, third-party tracking scripts inside the SCORM package.
Code quality (when you own the source)
Framework choice, build tooling, test coverage, dependency hygiene, opportunities to consolidate or simplify the codebase.
Localisation readiness
How the course handles RTL, multibyte characters, swapped audio tracks, and locale-specific assets — even if you only ship one language today.
What lands in your inbox
One PDF report, written in plain English, that a non-developer can hand to a developer.
Executive summary
One page, plain English. Three numbers: how many critical issues, how many should-fix, and how many nice-to-have. A non-developer can hand this to leadership.
Prioritised fix list
Every finding is rated by severity and rough effort to fix. The list is sorted so the cheapest, highest-impact fixes are at the top.
Annotated screenshots & log excerpts
When the bug is visible we show you the screenshot. When it is in the SCORM API trace we show you the relevant lines. No hand-waving.
Recommendations your team can action
For each finding: what to change, in which file, with a one-paragraph explanation of why. Written so a developer who has never seen the code can follow it.
Pricing
Targeted look at one specific problem (broken tracking, manifest errors, a single failing interaction). Short written summary.
Full pass across one course or build. Manifest, API calls, accessibility, LMS compatibility, performance. Written report with prioritised fixes.
Reviewing a vendor's full catalog, an in-house authoring framework, or an LMS integration layer. Quoted after a free 30-minute scoping call.
All reviews billed at $200/hour. Estimate confirmed in writing before work starts. See full pricing.
How it runs
No drawn-out sales cycle. Send us the package, get the report.
Send the package
SCORM zip, repo access, or authoring source. NDA on request.
Scoping call (30 min)
We agree what is in scope, target LMS, and the deadline.
Review (3-5 days)
We run the course, read the code, and write the report.
Handover
PDF report by email + 30-min walkthrough call included.
Get an independent answer in a week
Send the SCORM package or the repo. We will scope it, quote it, and have the report in your inbox in 3-5 business days. NDA-friendly by default.