SCORM Consultant who reads the API calls
Hire an independent, UK-based SCORM consultant for tracking failures, LMS migrations, compliance audits and SCORM 1.2 / 2004 / xAPI decisions. Hands-on diagnosis, honest scoping, fixed quotes.
SCORM since 2019 · Web development since 2008 · Based in London, UK
What a SCORM consultant actually does
A SCORM consultant is a specialist who solves technical problems at the point where e-learning content meets the Learning Management System. That means diagnosing tracking failures, fixing compliance issues, advising on SCORM version selection, de-risking LMS migrations, and making sure courses behave reliably across platforms.
Nobody searches for a consultant for fun. The search usually starts with "why isn't this course tracking completion?" or "we switched LMS and nothing works". I've been that person since 2019 — the one training teams call when e-learning breaks in ways they can't diagnose, or when they want a straight answer before committing budget.
New to the standard? Start with my plain English guide to SCORM.
Courses that don't track
Learner finishes, LMS says Incomplete. Scores stuck at 0%. Resume restarts from slide one. Usually a mismatch between the course's SCORM API calls and what the LMS expects — I read the calls and find it.
LMS migrations gone wrong
Every LMS implements SCORM slightly differently — API timing, status handling, commit behaviour. A package that was fine in Moodle can fail in Cornerstone. I test your critical courses before go-live, not after 500 learners complain.
SCORM compliance audits
Regulated sectors need to prove a specific learner completed a specific course on a specific date. I check whether your completion records are actually reliable — or driven by a timer nobody noticed.
SCORM 1.2 vs 2004 vs xAPI
The right choice depends on your LMS, your reporting needs and your content — not on a headline. I give you a straight recommendation for your situation and explain the trade-offs.
Content & conversion strategy
PowerPoints, PDFs, recorded webinars — all convertible, but the approach matters. I help you pick tooling and scope that produce packages people will actually sit through.
RFP & vendor reviews
Sanity-check a SCORM development RFP or a vendor's proposal before you sign: realistic pricing, sensible technical specs, deliverables you can actually test.
- 01
Completion isn't recording and you've tried the obvious
Publish settings checked, different browser tried, attempt data cleared — still broken. The problem is now in the SCORM API communication layer, and that needs someone who can read the calls.
- 02
You're migrating to a new LMS
Courses that leaned on quirks in the old platform lose them on migration day. Testing your critical packages beforehand is far cheaper than discovering issues one angry learner at a time.
- 03
Your training is compliance-critical
If a failed completion means a failed audit or legal exposure, "it seems to work" isn't good enough. You need the course, LMS configuration, data model and reporting chain validated end to end.
- 04
You're deciding between SCORM 1.2, SCORM 2004 and xAPI
This choice shapes your content library, LMS requirements and reporting for years. Get a recommendation from someone who has shipped against all three, not from whichever is newest.
- 05
Nobody in-house owns the technical plumbing
Most L&D teams are excellent at instructional design and don't have a SCORM specialist — that's normal. A consultant fills the gap on demand without a full-time hire.
SCORM consultant vs SCORM developer
A developer builds courses. A consultant diagnoses and advises. Most real problems need a bit of both — so I do both, and you only pay for the part you need.
Diagnoses and advises
- Works out why tracking, scoring or resume is failing
- Recommends SCORM 1.2 vs 2004 vs xAPI for your situation
- Audits existing packages and LMS configuration
- Plans LMS migrations and vendor evaluations
You're on the right page. Engagement options are below.
Builds the thing
- Custom SCORM 1.2 / 2004 courses from your content
- PowerPoint and document conversion into trackable packages
- Fixes to the course code once the diagnosis is done
- Testing against your LMS and SCORM Cloud before launch
Need building, not diagnosing? See SCORM development or PowerPoint conversion.
Ways to work with me
Pick the shape that matches your problem. Anything with a defined scope gets a fixed quote up front — you'll never get a surprise invoice.
Diagnose & fix
A focused engagement on one problem: why completion isn't tracking, why scores are wrong, why resume fails. Root cause, fix, and a written explanation.
Best for: one broken course
Advisory session
Strategy calls, technical and code reviews, RFP checks. Booked in 1–3 hour blocks with written notes afterwards — never an open-ended meter.
Best for: decisions & reviews
On-site or remote day
Migration testing, multi-course audits, or training your internal team on SCORM fundamentals and LMS testing. Half-days available.
Best for: audits & team training
Retainer
A SCORM specialist on call for your L&D team: priority response, ongoing package reviews, and someone to escalate tracking tickets to.
Best for: teams shipping monthly
Every engagement includes
- Written findings — what was wrong, why, and how to avoid it next time
- Testing in SCORM Cloud plus your actual LMS where access is provided
- Plain-English explanations your non-technical stakeholders can follow
- Follow-up email support after delivery
- NDA signed on request — your standard agreement is fine
- A direct line to me, not a ticket queue
Rates exclude VAT. Payment by BACS, Stripe link or invoice. If I can't solve the problem I set out to solve, you don't pay for the diagnostic — see the FAQ below.
How a consulting engagement runs
Free discovery call
30 minutesThirty minutes to understand the problem: your LMS, authoring tool, SCORM version, what you've tried. If the answer is quick, you get it on the call and we're done — no charge.
Scope and fixed quote
24 hoursWithin one working day you get a written scope, the engagement shape that fits, and a fixed price. No open-ended estimates.
Diagnosis
Usually hours, not daysSend the package ZIP and, ideally, a test LMS account. I isolate whether the fault is in the course or the platform using SCORM Cloud, then trace the API calls in your real LMS.
Recommendation or fix
Varies by scopeEither a written recommendation (what to do, why, how) or a direct fix — modified package, LMS configuration change, or both — with every change explained.
Handover
IncludedYou get the files, the documentation, and follow-up support by email so your team can handle the same issue themselves next time.
One specialist, not an agency
I'm Larry Ioannidis, trading as LOST END FOUND LTD in London. I've been building e-learning since 2019 on top of a web-development background that goes back to 2008 — so when a course fails I'm reading the SCORM API traffic, not guessing from a screenshot.
When you hire me, you get me. No account manager, no hand-off to a junior, and no incentive to rebuild everything in a particular authoring tool.
E-learning since 2019
Custom SCORM 1.2 and 2004 courses, conversions and fixes for training teams.
Web developer since 2008
JavaScript, HTML5 and LMS API work — the layer SCORM problems actually live in.
Cross-LMS experience
Moodle, Cornerstone, TalentLMS, Canvas, SAP SuccessFactors, Totara, Docebo and more.
Builds the tools, too
SCORM Lab, ppt-to-scorm and SCORMBridge grew out of consulting problems I kept solving.
How to choose a SCORM consultant
Not all SCORM expertise is equal. Use this to vet anyone you're considering — including me.
Look for
- Hands-on technical depth — Can they explain what cmi.core.lesson_status does, and have they actually debugged a SCORM API failure — not just managed a project where someone else did?
- LMS breadth — A consultant who has only ever worked in one LMS won't spot the cross-platform issues that matter during a migration.
- Honest scoping — A good consultant tells you when your problem is simpler than you feared, and won't pad a one-hour fix into a three-day engagement.
- Clear communication — SCORM is technical. The explanation of what's wrong and how to fix it shouldn't be.
Watch out for
- Full-service agencies — SCORM becomes one line item in a larger engagement, and you pay enterprise rates for something a specialist solves in an afternoon.
- Tool-specific consultants — Whose default answer is to rebuild everything in their preferred authoring tool, even when the existing package is fixable.
- Vague on the versions — Anyone who can't explain the practical difference between SCORM 1.2 and SCORM 2004 can't advise you on which to use.
- No written output — If the engagement ends with a call and no document, your team can't repeat the fix — and you'll be paying again next time.
Tell me what's broken (or what you're deciding)
Send a description of the problem, your LMS, and the SCORM version. I'll come back within one working day with an honest read on whether you need a consultant — and a fixed quote if you do.