Decide what must survive outside the authoring tool
Write the destination before choosing a format: a printed handout, an LMS assignment, or a browser lesson. For the room-booking exercise, a handout can carry the rule and cases but cannot behave like a scored online question. An LMS package is useful only if the receiving system can launch it and interpret the required result. A direct lesson link may be simpler when no LMS assignment is needed.
Do not select SCORM merely because it sounds more portable. Ask who will own the learner record and what should happen when the authoring subscription, network connection or source lesson changes. Those are separate questions from whether a file downloads.
Use the documented export route, then inspect the result
The export help describes Share → Export to PDF, followed by a download when generation finishes. It also lists Export to SCORM with SCORM 1.2 or 2004 third edition. The article warns that PDF can omit media or interactions and that SCORM runs online. These are documented capabilities, not exports we have tested.
For a PDF exercise, move any essential video-only instruction into readable text before export. Put an answer key on a separate clearly marked page if the file is meant for practice. Inspect the downloaded file itself: a correct authoring preview does not prove that a table, accented character or page break survived.
Resolve the plan-name conflict before paying for an export
As checked on 2 October 2026, the current pricing page lists PDF in Creator Plus and dynamic SCORM in Creator Pro; the December 2025 export article instead names Pro and Elite. Do not combine those labels into a new entitlement claim. Treat the current plan comparison as the buying reference, but confirm the exact export in the intended account before a purchase that depends on it.
Importing an existing SCORM activity into a course is not the same feature as exporting a new SCORM package. Write “export” in your requirement so an import check cannot accidentally pass it. See the cost guide for other plan limits.
A concrete acceptance sheet for the receiving system
- Content: the rule, exception and answer explanation are present and in the right order.
- Presentation: long choices, time intervals and tables remain readable at the destination, not just in the editor.
- Interaction: the learner can select and submit the intended response; the shown explanation matches that response.
- Records: the LMS owner can explain which completion or score it stored. A successful launch alone is not this check.
- Revision: record the source version, exported filename, export date and receiving course. Keep the prior package recoverably until the replacement is accepted.
- Connectivity: confirm the expected network requirement and provide an alternative reference when connectivity is unavailable.
Use a permitted test learner and invented answers in your own system. Do not distribute actual employee results with a sample package. This checklist is a proposed acceptance procedure, not a claim of LMS compatibility.
Keep a simpler fallback
If the destination cannot preserve the required interaction, use an accessible text exercise with a facilitator or choose a delivery tool suited to the requirement. A static reference is an honest fallback; a broken interactive file labelled “complete training” is not. Link the handout back to the current authoritative procedure and identify who replaces obsolete copies.
Sources and evidence limits
Documentation checked 2 October 2026. Product instructions are documentation-led, not a hands-on account test. Worked examples are fictional.
- Mini Course Generator: PDF and SCORM export — Merchant-controlled documentation · checked 2026-10-02
- Mini Course Generator pricing — Merchant-controlled documentation · checked 2026-10-02