Rise 360 Review Feature & Feedback Workflow
Overview
When clients review Rise 360 courses and submit feedback outside of the built-in Review feature — via email, chat, or verbal notes — the feedback typically lacks context. Without knowing which screen or block a comment refers to, the instructional designer must spend time reconciling vague notes against the course, which slows revision cycles and increases the risk of misapplied changes.
The Rise 360 Review feature solves this by automatically attaching a screenshot of the exact course screen to each comment a reviewer submits. This creates a shared, contextual record of all feedback tied directly to the content.
This workflow was formalized during the [1] engagement after early feedback rounds created alignment issues between the client (Gus Donelson) and the instructional designer (Isalia Ramirez).
The Problem with Ad-Hoc Feedback
Without using the Review feature:
- Client comments arrive without visual context (e.g., "the second screen feels off")
- The designer cannot reliably identify which block, lesson, or module is being referenced
- Feedback threads in email or chat become disconnected from the course state at the time of review
- Revisions may be applied to the wrong location or missed entirely
Recommended Workflow
1. Publish a Review Version
After completing a revision cycle, publish the course to a Review link rather than (or in addition to) a preview link. In Rise 360:
- Open the course → Share → Review
- Generate and copy the review link
- Send the link to the client with clear instructions
2. Instruct the Client to Use the Review Link
Ask the client to open the review link and submit all feedback directly within the interface. Each comment they add will automatically capture:
- A screenshot of the current screen
- The lesson and block location within the course
- A timestamp
This eliminates ambiguity about what the comment refers to.
3. Designer Reviews Comments in Rise
The designer accesses submitted comments from within the Rise 360 authoring environment. Comments appear inline alongside the relevant content, making it straightforward to action each piece of feedback in context.
4. Resolve or Reply to Each Comment
As revisions are made, mark comments as resolved. If a comment needs clarification before actioning, reply directly in the thread so the client receives a notification and can respond.
5. Repeat Per Revision Cycle
For each new revision cycle, publish a new review version. Do not reuse old review links — a fresh link ensures comments are tied to the current state of the course.
Key Benefits
| Without Review Feature | With Review Feature |
|---|---|
| Vague, context-free feedback | Comments anchored to specific screens |
| Designer must interpret location | Location captured automatically via screenshot |
| Feedback scattered across email/chat | All feedback centralized in Rise |
| Easy to miss or misapply changes | Clear resolution tracking per comment |
Notes & Caveats
- Client training may be needed. Some clients default to emailing feedback even after being given a review link. A brief explanation of why the Review feature produces better outcomes can help reinforce the behavior.
- Version discipline matters. If the designer continues editing the course after publishing a review link, the client's screenshots may not match the current state. Coordinate timing so the client reviews a stable version.
- Rise Review is separate from LMS publishing. Publishing a review link does not push the course to the LMS. These are independent actions.
Related
- [2]
- [3]