xAPI, SCORM, and video in one instructional design portfolio

One URL for mixed media

TrainingOS is designed so SCORM, video, and documents sit next to written case study sections—ideal for blended and multimodal programs.

Mixed media tells a fuller story: video for executive tone, SCORM for interaction fidelity, PDF for job aids or facilitator guides when permitted.

Think about the reviewer's experience: they open one URL and see a project page with a written case study, a playable SCORM module, a short video walkthrough, and a downloadable facilitator guide. That single surface answers four questions at once—what did you build, how does it feel, what does the learner see, and what does the facilitator get. Sending those as separate attachments in an email creates version confusion and forces the reviewer to assemble the story themselves. One URL with everything organized by section puts you in control of the narrative.

When you upload SCORM alongside video, label each artifact with its purpose: "Interactive scenario—SCORM 2004, 15 min" versus "Executive overview—MP4, 3 min." That labeling prevents a VP from launching the full SCORM when they only had three minutes, or a technical reviewer from watching a summary video when they wanted to click through branching logic. If you built in Storyline 360, export SCORM for the interactive piece and record a separate Loom or Camtasia walkthrough for the narrative layer—different audiences need different entry points.

PDFs often get overlooked in portfolio design, but they carry weight for blended programs. A facilitator guide shows you think beyond the screen. Upload it as a named artifact—"FacilitatorGuide_SalesOnboarding_v2.pdf"—and write a one-line note in the case study about how it fits the program: "Facilitators used this guide during the 90-minute live session that followed the e-learning module." That context turns a static PDF into proof of systems thinking. If you designed job aids, include those too: quick-reference cards, decision trees, or checklists that learners used on the floor after training.

If your project included both instructor-led and self-paced components, organize them chronologically in the case study so reviewers see the full learner journey: pre-work video, live session with facilitator guide, post-session SCORM practice, and follow-up job aid. That sequence shows you designed a program, not just a module. Buyers hiring for blended curriculum work specifically look for evidence that you can stitch modalities together into a coherent experience rather than treating each format as an isolated deliverable.

Discovery and SEO

Public project pages support structured metadata so your best work can be indexed and cited consistently.

When your portfolio pages include proper titles, descriptions, and structured headings, search engines can surface your work when hiring managers search for specific skills like "Storyline scenario compliance training" or "SCORM healthcare onboarding." That organic discovery supplements your outreach—you get found by people who were not in your network. Write project titles that include the tool, the industry, and the format: "Branching Compliance Scenario—Storyline 360, Healthcare" is more discoverable than "Project 3."

Each project page on TrainingOS generates its own URL with clean metadata. Use that URL in LinkedIn posts, conference speaker bios, and proposal appendices. When multiple sources link to the same stable URL, search engines treat it as more authoritative over time. Avoid creating duplicate pages for the same project on different platforms—pick one canonical home and link to it everywhere. If you guest-post on an ID blog or get quoted in an article, ask the author to link to your portfolio project page rather than your generic homepage.

Write your project descriptions with the words hiring managers actually search for. Skip internal jargon and use the terms that appear in job postings: "rapid e-learning development," "LMS administration," "scenario-based assessment," "SCORM packaging." Sprinkle these naturally into your case study text—not as keyword stuffing, but as accurate descriptions of what you did. If you built a module in Rise 360 for a retail client, say "Rise 360 retail onboarding module with knowledge checks and manager sign-off" rather than "a course I made for a store."

Consistency helps too: if every project page follows the same structure—challenge, process, solution, outcomes—search engines and readers both benefit from the predictability. Update old project pages when tools change names or when you have new metrics to add. A portfolio that looks abandoned signals you stopped caring; regular updates signal active practice. Even small edits like refreshing a tool version from "Storyline 3" to "Storyline 360" keep your pages accurate for people searching current terminology.

xAPI when you have it

If you instrumented experiences with xAPI, summarize what you tracked and why it mattered to stakeholders. You do not need to expose statements publicly to show sophistication.

Describe the xAPI implementation in plain language first, then add technical detail for readers who want it. Start with the business question: "Leadership wanted to know which practice scenarios correlated with fewer errors in the first 30 days." Then explain what you instrumented: "We sent xAPI statements for each scenario attempt, recording the path chosen, time spent, and whether the learner self-corrected before submitting." Finally, name the LRS and reporting layer: "Statements flowed to a Learning Locker instance; we built a dashboard in Power BI that mapped scenario performance to on-the-job error rates." That three-layer explanation works for executives, IDs, and technical reviewers simultaneously.

If you cannot share the actual xAPI data or LRS dashboard, create an architecture diagram that shows the flow: authoring tool sends statements to LRS, LRS stores and exposes data, reporting tool visualizes patterns. Use a simple flowchart in Miro, Lucidchart, or even a slide in PowerPoint—the visual proves you understand the pipeline even when the data is confidential. Annotate the diagram with the statement verbs you used (attempted, completed, scored, experienced) so technical reviewers see you went beyond default tracking.

Most freelancers do not have xAPI experience, so even a single project with xAPI instrumentation sets you apart. If you only did lightweight xAPI—like tracking video interactions or custom question responses beyond what SCORM reports—that still counts. Name what you tracked that SCORM could not: "SCORM reported pass/fail; xAPI captured which three decision points learners revisited most, which told us where the policy language was confusing." That sentence shows you chose xAPI for a reason, not as a buzzword.

When pitching xAPI in proposals, translate the value into stakeholder language. Instead of "we will implement xAPI statements with an LRS," say "you will see which practice scenarios your team struggles with most, broken down by role and region, updated in near-real-time on a dashboard your managers can access without opening the LMS." If the client uses Docebo, Cornerstone, or another LMS that supports xAPI natively, mention compatibility—it reduces perceived risk. If they need a standalone LRS like Learning Locker or Watershed, scope the setup cost separately so it does not surprise them in the final invoice.

Bandwidth and honesty

Large video files can frustrate mobile reviewers. Offer a short trailer and a deeper walkthrough. Label duration and prerequisites so hiring managers can budget time.

Compress video before upload: H.264 MP4 at 1080p with a moderate bitrate (around 5–8 Mbps for screencasts, lower for talking-head) keeps quality acceptable without punishing mobile connections. If your walkthrough is longer than five minutes, cut a 60-second highlight reel that opens the project page and put the full version behind a "Watch full walkthrough" link. Reviewers on a train or between meetings will watch 60 seconds; the ones who are seriously evaluating you will click through to the rest.

Label every media artifact with duration, format, and what the viewer will see: "3-min executive summary (MP4, no audio)" or "12-min narrated walkthrough with chapter markers (MP4, captioned)." That labeling respects the reviewer's time and prevents them from clicking a 12-minute video when they only had two minutes between calls. If your video has audio, always include captions—some reviewers watch on mute in open offices, and captioned video signals you think about accessibility in production, not just in proposals.

Be honest about what each artifact represents. 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 PDF facilitator guide was a draft that never got final approval, either update it or label it "draft—illustrative of facilitation approach." Small dishonestries—or even ambiguities—erode trust when a technical reviewer notices the SCORM completion screen says "Acme Corp" but your case study says the client was anonymous. Consistency across artifacts is a signal of professional rigor.

Test your portfolio page on a throttled connection before sharing. Chrome DevTools lets you simulate 3G or slow 4G—if your page takes 20 seconds to load because of uncompressed hero images and autoplay video, fix it before a hiring manager blames their hotel Wi-Fi. Move large assets behind click-to-load interactions so the page renders fast and the heavy content loads only when requested. That pattern mirrors good e-learning design: do not front-load bandwidth when the user might not need it.