Playback + packaging evidence
SCORM and xAPI conformance evidence
Declared versions, completion and score behaviour, sample-package test plan, and how Studio/Convert packages play in Evolve — screenshots are not conformance.
SCORM and xAPI conformance evidence is a stated list of supported versions, suspend/resume and score rollup behaviour, and a test against the buyer’s packages in the target LMS. Innovito Studio and Convert produce standards-based packages; Evolve plays SCORM 1.2 and 2004 and records xAPI statements where configured. Require a sample Arabic package in UAT.
Export this pack · No gate. No nurture sequence. Downloads are generated in your browser.
SCORM 1.2 playback
Published hereEvolve plays SCORM 1.2 packages commonly used across MENA enterprises. Suspend/resume and lesson_status/score behaviour are verified in UAT against the buyer’s sample, not a vendor demo package only.
SCORM 2004 playback
Published hereSCORM 2004 packages (including 3rd/4th edition as used in the buyer’s catalogue) are in the playback class. Rollup and sequencing quirks are documented during the sample test — editions differ.
xAPI (Tin Can) statements
Published herexAPI statements can be recorded where the programme is configured for richer analytics. Actor/verb/object mapping is agreed in implementation; an LRS destination is a scoped lot, not an unspoken SaaS assumption.
cmi5
Not claimedNot claimed as a default Evolve lot on this page. If your catalogue is cmi5-first, say so in the RFP so we can scope playback versus SCORM/xAPI.
LTI (campus / SIS tools)
Evaluator file — no formLTI is evaluated when the buyer is a campus or ministry SIS scenario. It is not assumed for a corporate academy. Ask for the current connector inventory in the evaluator pack.
Studio packaging
Published hereInnovito Studio produces standards-based packages (SCORM export as used in production lots) with Arabic/English narration options. Packaging evidence is a sample export played in the target LMS — Evolve or another.
Convert production packages
Published hereConvert delivers custom modules as SCORM/HTML5 lots agreed in the statement of work, including Arabic QA when that track is bought.
Sample package test plan
01
Provide a buyer package
One Arabic SCORM 1.2 or 2004 module you already run, plus one English control if bilingual.
02
Launch, suspend, resume
Close the player mid-module and reopen. Bookmark/suspend data must restore. Failure here is a scored defect.
03
Score and completion rollup
Complete pass and fail paths. Admin report must show status and score matching the package rules you documented.
04
Certificate / evidence export
Issue a bilingual certificate (if in lot) and export a completion file a CHRO could file.
Are screenshots SCORM conformance?
No. Conformance evidence is a declared version list plus a sample-package test on the target LMS with suspend/resume and score rollup.
Must the sample package be in Arabic?
If Arabic is a MUST in your SOW, yes. English-only SCORM tests miss RTL truncation and font embedding issues.
Educational and evidentiary material for procurement and IT evaluators. Adapt with your legal, privacy, and information-security counsel. Commercial terms, SLAs, and certificate serials are confirmed in the bid — not invented on this page. · Instructional technology evaluators