Jobs move through their respective workflows in Pepper Flow through votes. All users selected to participate in a review task must review the document and cast a vote on what they think is the appropriate next step for the document.
Certification tasks are a type of review task that include additional information supporting the user’s approval vote, most commonly used to meet requirements of local regulations. Unlike standard review tasks, additional groups may not be added to participate in a Certification task.
Vote options
A reviewer may be able to select from 5 voting options when reviewing or certifying a document. The available voting options for each task are configured based on your organization’s SOPs.
Vote |
Definition |
Approve |
No changes are needed to the document. |
Amend and Progress |
Changes need to be made, but once those changes are made, the document can advance to the next task. |
Amend and Return |
Changes need to be made, and after those changes are made, the document needs to be reviewed again by all reviewers in this task, but can skip the task(s) before this one. |
Amend and Resubmit |
Changes need to be made, and after those changes are made, the document needs to be reviewed again by all reviewers in all tasks (i.e., start at the beginning of the review process). |
Reject |
Document will not be approved, regardless of changes made. |
Cast a vote
- Open up the document in the Viewer.
- Review the document and its properties. Instructions about how to review and vote will appear in the task panel.
- Once you are ready to vote, click Cast your vote in the task panel and select your vote.
- Click Vote.
- Depending on your organization’s configuration, you may be prompted to fill out a few additional fields in the vote modal. These may include:
- Providing additional vote rationale by selecting a vote reason from the list of options and/or adding comments in the free text field.
- Entering your PIN to confirm your vote.
- Providing additional vote rationale by selecting a vote reason from the list of options and/or adding comments in the free text field.
- Click confirm vote.
Please note, if you are completing a certification task, your job title and department will be displayed along with a certification reason when casting an “approve” vote. You may input your job title and department within the task modal and manage it in your user profile.
Change your vote
If you're participating in a parallel review, you can change your vote up until all other reviewers cast their votes.
- Click "Change vote" next to your vote status in the task panel.
- Update your vote selection from the dropdown.
- Click "Vote" and (if applicable) enter your vote reason (if configured) and PIN.
Final vote outcome
When all reviewers in a task have voted, Pepper Flow uses the most conservative vote as the final vote outcome for that task. For example, if two reviewers vote Approved but one votes Amend and Resubmit, the final vote will be recorded as Amend and Resubmit.
The jobs progresses according to the table below for each task outcome.
Final Vote |
Job Progression |
Approve |
Job progresses to the next task. If this is the final task, the job progresses to complete, and the document status changes to approved. |
Amend and Progress |
The document returns to the Initiator with a job status of Incorporating Feedback. When the changes are completed, the review process begins at the next task in the job. If there are no additional tasks, the job progresses to complete. |
Amend and Return |
The document returns to the Initiator with a job status of Incorporating Feedback. When the changes are completed, the review returns to the task the vote was cast from, bypassing previous tasks. |
Amend and Resubmit |
The document returns to the Initiator with a job status of Incorporating Feedback. When the changes are completed, the review process begins back at the first review task. This increments the job’s circulation. |
Reject |
Job ends and does not progress to the next task. The initiator must start a new job. |
Illustrated example
Comments
0 comments
Article is closed for comments.