An Assignment asks participants to do something and submit, confirm, or reflect on the result. Assignments work well when someone needs to review or follow up on the work — and they're the only activity type where a manager can be required to approve a submission before it counts as completed.
When to use it
Use this feature when it supports the goal of the learning journey and helps participants understand, practise, answer, meet, or reflect in a clearer way.
What to decide before launch
Check the instructions, audience, timing, and any notifications before you publish. If managers are involved, also check what they should see or do.
Preview before participants receive it
Preview the activity as a participant before launch. A preview helps you catch unclear instructions, missing resources, and wording that does not match the rest of the journey.
When "submitted" isn't the same as "completed"
Assignments can finish in two ways, depending on how the author has set them up:
No manager approval required. The participant submits and the assignment is marked as completed straight away.
Manager approval required. The participant submits, and the assignment shows Submitted, awaiting manager approval. It stays in that state until a manager opens the submission and clicks Approve — only then does the activity count as completed. The manager can also request a new version, which sends the assignment back to the participant.
Authors turn this on in the assignment with Require managers to approve participants' submissions, and pick a review mode: Only approval or Approve and comment.
If a participant tells you they can't complete an assignment, check whether it requires approval and whether a manager has reviewed the submission yet. That's the most common reason a submitted assignment isn't yet completed.
Your organization may call the manager role coach, mentor, leader, or something else. The approval flow works the same regardless of the label.