An assignment will be set-up to handle a submission in different ways based on the type of assessment it'll receive - continuous, periodic or one-off feedback.
Modify until deadline
For continuous assessment when a learner completes work over a period of time. The asset submitted remains synchronised with the learner's version until the assignment's modify or deadline date is reached.
Learner can:
- submit a blank or unfinished asset to an assignment,
- make changes to the asset up until the modify deadline,
- continue to modify their asset after the modify deadline, without the changes synchronising to ATLAS.
Assessor can:
- assess the submission with the learner's latest changes,
- see the date of submission,
- rewind to see the submission 'as was' at a previous date in time.
Read more on late submissions and giving an extension.
Copy on submission
For periodic or one-off assessment. A learner completes work and shares with ATLAS when ready. The asset submitted is a duplicate copy of the learner's version.
Learner can:
- continue to modify their asset after submission, without the changes synchronising to ATLAS,
- see the assessor view to compare versions,
- remove the current submission and resubmit an updated version (if permitted).
- submit the same asset to a different assignment.
Assessor can:
- assess the submission without the learner making further changes,
- see the date of submission.
If an activity log and collection is part of a submission, these will continue to be connected to the learner's version and update in ATLAS if modified.
Lock on submission
For a hard deadline and one-off assessment. A learner completes work and shares with ATLAS when ready. The asset submitted locks the learner's version.
Learner can:
- view their asset, but cannot make further changes,
- remove the current submission to unlock asset (if permitted),
- resubmit an updated version (if permitted).
Assessor can:
- assess the submission without the learner making further changes,
- see the date of submission.