You can now export any Story from We Are Learning as a SCORM package and use it in your LMS with built-in tracking. We support both SCORM 1.2 and SCORM 2004, with tracking for:
Story start and completion
Response node choices (which option the learner picked)
Quiz scores
Bookmarking so learners can continue where they left off
đĄ SCORM packages from We Are follow the standard SCORM structure with an imsmanifest.xml and a launch file for your Story.
Who can use SCORM export?
SCORM export is available for Enterprise plan customers only. Read more.
Here is how you do it:
Click Share and then Publish and share.
2. Toggle on Publish Story, click SCORM
From here you can pick which SCORM version to use and configure the export options.
SCORM 1.2: Best if your LMS is older or only supports SCORM 1.2.
SCORM 2004: Recommended if your LMS supports it and your organisation prefers SCORM 2004 for consistency.
If youâre unsure which to use, your LMS admin or vendor will usually recommend a âdefaultâ SCORM version for all content.
Once chosen which version, click Download.
Once that is done you can go ahead and upload the SCORM file to your LMS.
In your LMS:
Create a new SCORM course/activity.
Upload the ZIP file you just exported.
Configure attempts, grading and visibility as you normally do for SCORM content.
Enrol learners and let them start the Story from within the LMS. If you later update the Story in We Are, the SCORM activity in the LMS will automatically use the updated content.
What gets tracked in your LMS?
1. Started & completion tracking
We send start and completion data so your LMS can show:
That the learner started the Story.
That the learner completed the Story (based on the completion rules you set in We Are).
Depending on your LMS, this might appear as:
Not started / In progress / Completed, or
Incomplete / Complete / Passed / Failed
The exact wording is decided by your LMS, not We Are.
2. Response node tracking (coming soon)
For interactive Stories where learners choose between options, We Are:
Tracks which response node the learner selected.
Sends this information to your LMS as part of the SCORM tracking data.
How this appears depends on your LMS, but typically youâll see:
The question or interaction identifier.
The option the learner chose (and sometimes whether it was marked correct/incorrect, depending on the interaction type).
This is useful for reviewing choices in branching scenarios or decision-based training.
3. Quiz score tracking (coming soon)
If your Story includes quizzes or scored interactions, We Are:
Calculates the learnerâs score in the Story.
Sends this score to the LMS as the SCORM quiz score.
Your LMS will typically show:
A percentage score (e.g. 85%)
Optionally raw score and max score
Overall status (e.g. Completed / Passed / Failed)
The exact grading and pass/fail rules in the LMS are configured on the LMS side, but we provide the data needed.
4. Bookmarking & resume
We Are supports bookmarking for both SCORM 1.2 and SCORM 2004:
The Story remembers the state and position where the learner stopped.
The next time they open the same SCORM activity in the LMS, We Are can restore that state.
đĄ Important details:
Bookmarking works as long as the Story has not changed since the learnerâs last attempt.
If the structure of the Story changes significantly (nodes added/removed/re-ordered), we canât safely guarantee an identical resume point.
Learner choice: restart or continue
When a learner comes back to a Story theyâve already started, theyâll see a choice:
Continue where I left off
Resumes from the last saved state and position.
Start from the beginning
Starts a fresh run-through of the Story.
This gives learners control, while still allowing you to keep tracking consistent in the LMS.
Dynamic SCORM packages
A key advantage of We Areâs SCORM export is that the package is dynamic:
Once youâve exported and uploaded the SCORM package to your LMS, any later edits you make to the Story in We Are are automatically reflected the next time learners launch the SCORM activity. In other words, you do not need to re-export or re-upload the package every time you tweak content.
This is especially useful when:
You correct typos or update minor details.
You iterate on scenarios and quizzes over time.
You need to adjust content quickly after feedback.
đĄ Note: Some LMSs or browsers may cache content. If learners donât see changes immediately, ask them to refresh or clear cache, or check if the LMS has a ârebuildâ or âclear cacheâ option for SCORM activities.
FAQs
Do I need to re-export a new SCORM package after editing my Story?
No. SCORM exports from We Are are dynamic. As long as youâre using the same export, edits to the Story will automatically be reflected the next time learners launch it.
Will bookmarking still work if I change the Story?
Bookmarking is reliable as long as the Story structure stays the same. If you make large structural changes, existing bookmarks may no longer point to the exact same place, and learners may be prompted to restart.
Which SCORM version should I pick?
Use whatever your LMS and organisation recommend. If there is no preference:
Choose SCORM 1.2 for maximum compatibility with older LMSs.
Choose SCORM 2004 if your LMS supports it and you want to align with more modern SCORM implementations.
If you need help deciding which SCORM version to use, or want someone to double-check your LMS reporting setup, reach out to us and include:
The name/version of your LMS
Which SCORM version youâre using
A screenshot of how the tracking appears in the LMS reports
Weâre happy to take a look and help you get things working smoothly.