Rise 360 Review Workflow

When working in Rise 360 with an external reviewer using Review 360, edits made in Rise are not automatically visible to reviewers. A new version must be explicitly published and a fresh review must be requested each time. Skipping either step means the reviewer sees a stale version of the course.

This workflow was formalized during the ^[1] SOAR project after a reviewer could not see updated videos because a new version had not been published.

The Workflow

1. Edit in Rise 360

Make all desired changes directly in the Rise 360 course editor. Changes save automatically within the editor but are not reflected in any previously published review link.

2. Publish a New Version

Once edits are complete and ready for review:

1. In Rise 360, click Review in the top navigation.
2. Select Publish New Version.

This overwrites the previous published version in Review 360 and updates the review link to reflect the current state of the course.

Note: Do not use the browser back arrow while inside Review 360 — it will break navigation.

3. Re-Request Review

Publishing alone does not notify the reviewer. After publishing:

1. Open Review 360.
2. Click into the course.
3. Select Re-request Review.

The reviewer will receive a new email with a link to the updated version.

Managing Feedback Comments

• Who resolves comments: The designer (Asymmetric side) resolves comments in Review 360 once the feedback has been addressed. The reviewer (client side) leaves comments but does not resolve them.
• Why this matters: Unresolved comments persist across versions. If comments are not resolved, the reviewer cannot distinguish between open issues and addressed ones.
• Audit trail: Resolved comments disappear from the active view, providing a clean signal of remaining work.

Locating Where a Comment Was Made

When a reviewer adds a comment in Review 360, a screenshot of their screen at the time of the comment is captured. Clicking the thumbnail in the comments panel navigates to the relevant section of the course — useful when comments lack explicit location context.

Notifications and Email

Review 360 sends email notifications when:
- A review is requested or re-requested (reviewer receives this)
- A comment is added (designer receives this)

Because designers may be working from an external client environment (e.g., an Agility Recovery email/SharePoint login), the client may double-send notifications to both the client-domain email and the designer's primary email to ensure nothing is missed. This is expected behavior, not redundancy for its own sake.

Common Mistakes

Related

• ^[1]
• ^[2]