Scenario
As an admin or content owner, you want to set an expiration date for content assignments so that they can be reassigned via an automated rule when no longer considered valid. This is especially useful for compliance content that needs to be completed every year, for example.
Solution
Go to the content item you want to set an expiration date for.
Open the context menu (button with three dots) and select Edit.
Go to Completion.
For tracks, the Completion settings are on the Details & Settings page.
โ
โTurn on Time to expiration and set the number of days until expiration.
Save your changes.
When you assign the content to someone, the expiration date is automatically set based on the number of days you defined. You can change the expiration date during the assignment process or you can override the expiration date after assignment.
Go deeper
Due date v. expiration date
Completion settings include a Time to complete (which determines the default due date) and a Time to expiration (which determines how long an assignment is considered valid). Due dates apply to when someone should complete a content assignment and expiration dates are when content can be reassigned.
You can always manually reassign content to someone who has dropped, completed, or been exempted from an assignment, but rules can only reassign content automatically once its assignments reach their expiration date.
Please note when viewing expired user assignments that you will not see expired assignments for expired assignments by default and will want to filter explicitly by adding one or both of these filters depending on your use case:
Expires at is the date after which the assignment is no longer valid. It is set at assignment time if the content item has the "Time to Expiration" checkbox set. Yes the date can be in the future.
Remember that you cannot reassign content, such as a Course, to a user if their status is not equal to Completed as this would create a double active assignment which is not possible in the platform. You'd have to first perform one of these three actions: Mark as Exempted, Mark as Completed, or Drop
Using the Time to Expiration model, let's consider a useful scenario where you want to reassign an onboarding compliance track and all its child items to returning interns after 8 months who are now FTEs.
Here are the steps you'll follow:
Set the Time to Expire (TTE) appropriately for the main track and ALL child items individually, as the track's time to expire (or time to complete) doesn't filter down
For events, in the event series, set the TTE/TTC appropriately (Time to complete which determines the default due date)
As you cannot re/assign users to any content with an active status (AKA In Progress or Not Started) set the Time to Complete (TTC) to assign users with incomplete/active assignments or manually mark them inactive - see this new article for more details on this which also shows how to utilize the Bulk action to not have to tediously mark each active user individually.
Here you can see the active status per an excerpt from this article - Assignment and Re/assignment Management Best Practice:
So, you can reuse a track every 12, 3, 1 months (or by whatever cycle you need) by ensuring:
Changing the TTE/TTC manually to a newer date every 12 months (or whatever date necessary) would allow for reuse of the same track and child items.
For compliance reporting you'll be relieved to know
each instance of a user completing the track is preserved separately, maintaining accurate reporting for compliance purposes.
There's no limit to the number of reporting instances per user, so historical progress and completion status are maintained regardless of how many times a user takes an expired track.
Bulk Mark as Expired
A new feature just added early November 2024 is the ability to Mark As Expired those users who've failed to finish the assignment per the time to complete date.
This is very useful on relevant content items when there's more than a few users to expire for reassignment.
Good News!
What's exciting is what is future plans coming up for Tracks where most of the manual processes mentioned above are removed with a new upcoming feature: Tracks are special" which will go through all the active assignments, set them to expired, then reassigns to the track to guarantee new assignments to the track and all it's child content items.