xAPI, SCORM, and video in one instructional design portfolio.

A hiring manager opens your email on a phone, between two interviews. Inside are four attachments: a SCORM .zip that won’t play, an .mp4 that buffers on hotel Wi-Fi, a 9MB facilitator .pdf, and a Loom link. They have ninety seconds. They close all of it and move on. The work was good. The packaging lost the job.

Blended programs are the strongest thing a freelance ID can show — and the easiest to show badly. The fix isn’t a flashier deliverable. It’s one URL where SCORM, video, PDFs, and a written case study sit in sections you control, so the reviewer reads the story you meant to tell instead of assembling it from a download folder.

/01Why one URL beats five attachments.

A single project page answers four questions at once: what did you build (the case study), how does it feel (a playable SCORM module), what does the learner see (a short video), and what does the facilitator get (a downloadable guide). Email attachments answer those questions in random order, force the reviewer to stitch them together, and introduce version confusion the moment you send a v2 of anything.

One canonical surface puts you in control of the narrative. Sequence the artifacts the way the learner actually experienced the program — pre-work video, live session with the facilitator guide, post-session SCORM practice, follow-up job aid — and the reviewer sees that you designed a program, not an isolated module. Buyers hiring for blended curriculum work screen specifically for that: can this person stitch modalities into one coherent experience?

A Training OS project page is built for this layout: hosted SCORM plays in the browser next to your written case study (one structured STAR case study on Free, unlimited on Pro), and the same project can carry a video — a YouTube or Vimeo link, or an uploaded MP4 — and a PDF. Training OS doesn’t add captions or chapter markers to video, so caption the file before you upload it or use your video host’s caption tools. If you’ve only ever sent zips, the portfolio examples are the fastest way to see the shape before you build your own.

/02Label every artifact by job.

The single highest-leverage edit on a mixed-media page is naming each piece by what it’s for and how long it takes. “Interactive scenario — SCORM 2004, 15 min” versus “Executive overview — MP4, 3 min” tells a VP and a technical reviewer which door is theirs. Skip the labels and a VP launches the full 15-minute SCORM with three minutes to spare, or a senior ID watches a summary video when they wanted to click branching logic.

Same rule for files. A facilitator guide uploaded as FacilitatorGuide_SalesOnboarding_v2.pdf with a one-line note — “Facilitators used this during the 90-minute live session that followed the e-learning module” — turns a static PDF into proof of systems thinking. Job aids count too: the quick-reference card or decision tree learners actually used on the floor says more than another polished slide.

If you built the interactive piece in Storyline 360, export SCORM for the module and record a separate Loom or Camtasia narrative layer. Different audiences need different entry points; one artifact rarely serves the executive and the practitioner at the same time.

/03Which format proves which thing.

Each format does one job better than the others. Pick deliberately instead of dumping everything you have — here’s how I rank them for a portfolio page.

/04Show xAPI without exposing the data.

Most freelance IDs have never instrumented anything with xAPI, so even one project that did sets you apart. The instinct is to dump a dashboard screenshot — don’t. Lead with the business question, then the instrumentation, then the stack, in plain language a non-technical buyer can follow.

That three-layer explanation reads like this: “Leadership wanted to know which practice scenarios correlated with fewer errors in a learner’s first 30 days. We sent an xAPI statement for each scenario attempt — the path chosen, time spent, whether the learner self-corrected before submitting. Statements flowed to a Learning Locker instance, and a Power BI dashboard mapped scenario performance against on-the-job error rates.” Executives, IDs, and technical reviewers all get something from the same paragraph.

Name the thing xAPI captured that SCORM physically couldn’t. “SCORM reported pass/fail; xAPI showed which three decision points learners revisited most — which told us where the policy language was confusing.” That one sentence proves you chose the standard for a reason, not as a buzzword. If you only did lightweight xAPI — tracking video interactions or custom responses beyond the SCORM envelope — that still counts. Say so precisely.

On Training OS the xAPI story lives in words and diagrams for now: the platform plays SCORM 1.2 and 2004 today, and xAPI support is planned — coming with Allure Connect, the runtime Training OS already plays SCORM through.

If you’re still fuzzy on where xAPI statements actually live — and why a self-hosted course so often records nothing — the xAPI hosting primer walks through the LRS, CORS, and the empty-completion-report trap in detail.

/05Bandwidth, captions, and honesty.

A page that takes twenty seconds to load gets blamed on your craft, not the reviewer’s Wi-Fi. Compress media before upload, move heavy assets behind click-to-load so the page renders fast and the big files arrive only when requested, and test on a throttled connection. Chrome DevTools will simulate slow 4G in two clicks — that pattern mirrors good e-learning design: don’t front-load bandwidth the user might not need.

Caption every video. Some reviewers watch on mute in an open office, and captioned video signals you think about accessibility in production, not just in proposals. Pair captions with the labels from section two — “3-min executive summary (MP4, captioned)” — and you respect the reviewer’s time twice over.

Then be honest about what each artifact is. If the SCORM is a redacted replica, say so. If the video shows v1.2 but the client shipped v1.4, note the delta. If the facilitator guide was a draft that never got final sign-off, label it “draft — illustrative of facilitation approach.” The trust killer isn’t imperfection; it’s a technical reviewer noticing the SCORM completion screen says “Acme Corp” while your case study claims the client was anonymous. Consistency across artifacts is the signal of professional rigor.

/06TL;DR — the assembly order.

Lead with the playable SCORM. The interaction is the craft; let reviewers click it. Host it somewhere that runs the runtime, not a file server.

Open with a 60-second video. Captioned, compressed, with the full walkthrough one click away for the people who are serious.

Add PDFs only for blended work. A named facilitator guide or job aid with one line of context proves systems thinking; out of context it’s clutter.

Describe xAPI in three layers — business question, what you tracked, the stack — and use a diagram when the data is confidential.

Then label everything, caption the video, and tell the truth about each artifact. When you’re ready to write the words around the media, the STAR case-study template gives you the structure reviewers expect.

/07Frequently asked questions.