OneSpace’s rework functionality allows contributors to redo submitted tasks that do not follow the assignment’s instructions. When rework is enabled on an assignment, contributors get a chance to fix an incorrect submission instead of having their work rejected.
How It Works
Rework is available on the Create step of a workflow. Enabling this setting gives the creator the ability to rework their tasks.
—
Create > Review Workflows
In two-step workflows that consist of Create and Review steps, the reviewer has the ability to send a task directly back to the creator for rework. If a reviewer chooses to do so, they are required to provide feedback to the creator that explains what they need to do in order to make the task acceptable.
—
Create > Edit > Review Workflows
In three-step workflows that consist of Create, Edit and Review steps, the editor has the ability to suggest rework on a task. If an editor suggests rework, they are required to provide feedback to the creator that explains what they need to do in order to make the task acceptable.
The editor’s rework suggestion and corresponding feedback is then surfaced to the reviewer in the Review step. The reviewer decides whether or not the editor’s rework suggestion is valid.
If the reviewer agrees with the editor’s rework suggestion, the task (and the editor’s feedback) is sent back to the creator to redo.
If the reviewer disagrees with the editor’s rework suggestion, the editor’s work is rejected, and the task is sent back to another editor to re-evaluate from scratch.
—
Contributor Experience
When a task is sent back to a contributor for rework, they automatically receive an email notification with a link to the task in WorkStation. This task shows their original submission along with the feedback from the editor or reviewer that states what needs to be fixed.
If the contributor does not begin working on the task within the designated Time Allowed to Claim Revision, their task is automatically rejected without pay and is sent back to a new creator to redo from scratch.
Similarly, if the contributor starts working on the task but does not submit it within the designated Time Limit per Task, their task is automatically rejected without pay and is sent back to a new creator to redo from scratch.
If the contributor successfully accepts and submits the task within the designated timeframes, the reworked version automatically goes to the next step(s) of the workflow. The editor and/or reviewer in the next step(s) will only be able to see the contributor’s reworked version of the task. They will not be able to compare it to the original version or see the original feedback.
Note: A creator does not receive additional pay for reworking a task, as rework is seen as an opportunity to fix a task that is considered unacceptable. However, if you send a task back to a creator for rework, you will have to pay at least one additional editor and/or reviewer to review the reworked version of that task.
Enabling Rework
You can enable rework at any time in the Evaluation Settings section of the Assignment Settings.
If you enable rework on an assignment, you’ll need to define the number of revision attempts allowed along with the time allowed to claim the revision.
Revision Attempts Allowed: This is the number of times a contributor is allowed to rework and resubmit a task before their work is rejected. We recommend allowing no more than two attempts per task depending on the difficulty level.
Time Allowed to Claim Revision: This is the amount of time a contributor has to start working on a task that has been sent back to them for rework. If a contributor does not start working on their rework task within the timeframe specified here, their work will be automatically rejected without pay. We recommend allowing between one and three days to claim a revision.