⏱️ The Essentials in 3 Minutes |
🧠 Understand the Importance of Reviewing Training Content
A quality training course requires content validation before distribution. Having your projects reviewed allows you to:
Ensure content accuracy: a subject matter expert can spot errors or inaccuracies the author no longer notices.
Improve pedagogical clarity: a fresh perspective identifies ambiguous wording or poorly structured sequences.
Secure the distribution: formal validation reduces the risk of correcting content that learners have already seen.
📌 Example: for a compliance training, have the project reviewed by your compliance manager via the .docx export before any distribution. This avoids them needing a Didask account and lets you collect feedback in Word using track changes.
🔀 Choose the Right Method for Your Situation
Situation | Recommended method |
Author with a Didask account and access to the project | Review comment |
Internal reviewer with a Didask account, you want to protect the original | Duplication |
Reviewer in another Didask space | Duplication to a target space |
External reviewer without a Didask account |
|
💬 Option 1: Add Review Comments to the Project
The fastest way to annotate a project without creating a copy. Ideal for team review directly on the source content.
In each granule, a speech bubble icon on the right lets you add a comment and optionally assign it to a author for follow-up.
How to do it:
Open the granule you want to comment on.
Click the speech bubble icon on the right.
Write your comment and assign it to a author if needed.
💡 This method is ideal for targeted feedback on a specific granule. The assigned author receives a notification and can address the comment directly in the project.
📋 Option 2: Duplicate the Project for Internal Review
Ideal if your reviewer has a Didask account and you want to protect your original version.
The reviewer works on an independent copy: they can annotate, modify, and test without affecting your source project.
How to do it:
Open your project.
Click the three dots (...) in the top right.
Select Duplicate.
⚠️ Changes made to the copy do not sync with the original. You will need to apply corrections manually once the review is complete.
🤝 Option 3: Duplicate to Another Space for Targeted Collaboration
If you manage multiple training spaces, you can send a copy of the project to the space where your collaborators or clients are located.
This enables review by admins or authors in a given space, without exposing all your content.
How to do it:
Open your project.
Click the three dots (...) in the top right.
Select the target space and click Duplicate.
⚠️ Author access on the copy is full edit access, not read-only. Make sure the person knows they are working on a copy.
📄 Option 4: Export as .docx for External Reviewers
The ideal method for anyone without a Didask account or who prefers working in Word.
You export the entire project as a .docx file. The reviewer can use Word's track changes feature to annotate the document directly.
How to do it:
In your project, open the ⚙️ Settings tab.
Go to the Export section.
Click Export as .docx.
💡 This is the simplest method for validation with clients or external subject matter experts outside your organization.
👀 Anticipate the Reviewer's Experience
Depending on the method chosen, the reviewer's experience is very different:
Duplication: the reviewer navigates the Didask interface granule by granule, and can leave review comments directly in the copied project (not the original).
.docxexport: the reviewer reads a linear Word document. They see the text content but not the interactions or the final visual rendering.
💡 For reviewers less comfortable with digital tools, the Word export remains the most universal and least intimidating format.
Keywords: review, validation, comment, external users, partners, collaboration.