A Rise 360 course is responsive by design, but publishing it correctly determines whether learners can launch it, resume where they stopped, and receive completion credit. Knowing how to publish responsive Rise 360 courses means choosing the destination first, then matching the export settings to that destination. A web package, an LMS package, and a Review 360 version serve different purposes.
Choose The Correct Publish Destination
Before you export, answer one question: where will learners open the course?
Choose Web when your organization will place the course on a web server, intranet, or learning portal that does not require LMS tracking. Rise creates a folder containing the files needed to run the course in a browser. Learners can complete the content, but their progress and completion status will not be reported to an LMS.
Choose LMS when learners must receive completion credit, scores, or progress tracking through a learning management system. Rise packages the course as a ZIP file that you upload directly to the LMS. Do not unzip that file before uploading it unless your LMS administrator specifically requires it.
Choose Review 360 when stakeholders need to test the course and leave comments. Review 360 is not a replacement for an LMS launch. It is the right place to gather feedback, test navigation, and confirm that content looks correct across devices before the production upload.
Prepare The Rise 360 Course Before Publishing
Open the course and select Settings. Confirm the course title, description, and cover image. These details may display in your LMS catalog or in the browser tab, depending on the publishing destination.
Next, review the course navigation. If you want learners to move through lessons in any order, use free navigation. If learners must complete content in sequence, use restricted navigation. Restricted navigation can prevent learners from opening later lessons before completing earlier content, but it can also create support issues when a required interaction has not been completed correctly. Test it carefully.
Then verify your completion requirement. In Rise 360, completion can be based on the number of lessons viewed or on a quiz result. A lesson-based requirement is usually appropriate for informational content. Choose a quiz-based requirement when your LMS needs a passing score.
If your course includes a quiz, open the quiz settings and confirm the passing score, attempt limit, and feedback. Also verify that the quiz is included in the course completion criteria. A quiz that looks correct but is not connected to completion settings will not report the result you expect.
Publish A Responsive Rise Course To Review 360
Use Review 360 before sending an LMS package to stakeholders or learners. From the course dashboard, select Share or Publish, then choose Review 360. The exact button label can vary slightly as Rise 360 is updated.
Enter a version title that makes the review cycle clear, such as “Safety Orientation – SME Review 2.” Avoid generic labels such as “final” or “new version.” Those names become confusing as revisions accumulate.
Publish the course, then open the Review 360 item yourself. Test the course in a desktop browser first. Check the course menu, continue buttons, knowledge checks, embedded media, and quiz. Then use a phone or narrow the browser window to confirm that images, labeled graphics, and text-heavy blocks remain readable.
Responsive layout does not fix every content decision. A wide screenshot with tiny text may technically resize for a phone but still be unusable. Replace it with a larger image, split it into steps, or provide the information as HTML text.
Publish To An LMS
To create an LMS package, select Export or Publish, then choose LMS. Select the standard required by your LMS administrator. If no standard is specified, ask before publishing. The correct choice depends on the reporting your organization needs and what the LMS supports.
SCORM 1.2 remains common and is often the safest choice for basic completion and score reporting. SCORM 2004 can support more detailed status reporting, but LMS support varies by edition. xAPI and cmi5 are appropriate when your organization has specifically implemented those standards. Do not choose a newer standard simply because it sounds more capable. An incompatible package creates preventable launch problems.
Set the reporting option to match your completion requirement. For a course completed by viewing lessons, report completion status. For a scored quiz, report both completion and success status when your LMS supports it. This distinction matters: a learner can finish every lesson yet fail a required assessment.
Download the exported ZIP file and keep the original file name meaningful. Include the course name and version, such as `Cybersecurity_Basics_v3.zip`. Upload that ZIP file to a test location in the LMS before replacing an active course. This protects learners from encountering a broken package during a revision.
Publish To A Web Server
When the course does not need LMS tracking, choose Web during export. Rise 360 downloads a ZIP file containing the published course files.
Unzip the package on your computer. You should see an `index.html` file and supporting folders. Upload the contents of the package to the same folder on the web server. Do not upload only the `index.html` file, and do not separate it from its supporting folders. The course relies on those files for assets, scripts, and navigation.
After upload, open the URL that points to `index.html`. If the course displays a blank page, shows missing media, or fails to load, ask the web administrator whether the server permits the required file types and supports HTTPS. Also confirm that every file and folder was uploaded without changing the package structure.
Test Completion And Resume Behavior
A course that opens successfully is not necessarily published successfully. In your LMS test environment, launch the course as a learner. Complete enough content to trigger the intended completion rule, then exit and reopen it. Confirm that the course resumes at the expected location.
Finish the course and check the learner record in the LMS. Verify the completion status, success status, score, and date recorded. If the course reports incomplete, first compare the Rise completion settings with the LMS reporting option. Most reporting failures come from a mismatch between those two settings, not from responsiveness.
Test at least one desktop browser and one mobile device. Check that video controls work, button labels are not obscured, and any custom content opens correctly. If your course contains a Storyline block, test that block especially carefully because its behavior and tracking can affect the learner experience inside Rise.
Keep A Publish Record
For each release, record the course version, publish date, completion method, LMS standard, reporting option, and test result. This takes only a few minutes and makes future updates far easier to manage. When someone asks why version 4 reports completion differently from version 3, you will have an answer instead of a guessing session.
Publish to Review 360 for feedback, validate the LMS package in a test environment, and release only after completion reporting works as intended. That disciplined final check is what turns a responsive Rise 360 course into a dependable learner experience.