Overview

What is this?	A signoff flow specifies who signs off on feedback and which of those signatures are required. Your organization will create Signoff Flows by designating certain people who will be approving or “signing off” on Feedback Reports. There may be several levels of people who will be signing off on each Feedback Report. Some of these various levels will be required to sign off. Each signor on a level can be marked as required (they must sign off before that sign-off engine will mark that level as complete).
Why am I learning this?	Signoff Flows automates the documentation of the review and acknowledgement Feedback Reports, Training Observations, Task Lists, and Phase Enrollments.
What will I learn?	By the end of this training, you will be able to… Build a Signoff Flow Turn ON (set as default) a Signoff Flow Edit a Signoff Flow Add Levels to a Signoff Flow

Definitions

Feedback Report	Feedback Report with Events with Feedback is authored and completed by an evaluator. Evaluator Signs Off and submits Subject reviews Report's comments/summary and feedback on attached events. They can sign-or refute feedback on the report If Refuted, it is routed back to the evaluator who can review subjects comments and edit and resubmit or not edit and resubmit
Author	Writes the Feedback
Evaluator	Signs off on Feedback Submits Feedback
Subject	Reviews Report's comments/summary and feedback on attached events. They can signoff or return feedback on the report
Signoff Flows	The QA signoff allows for an automated signoff workflow by enabling specific users or groups to view, comment, return, and acknowledge feedback reports.
TOR - Training Observation Report	Training Observation Report. Also referred to as DOR (Daily Observation Report). Each day a trainee is in training, the trainer must complete a form that tracks the trainee's performance in 'core competency' areas of the trainee's job.
Signatory	Some signatories can sign off but are not required to do so.
Returned	If Refuted, the Feedback Report is routed back to the evaluator who can review subjects comments and edit and resubmit or not edit and resubmit.
Custom User	Specifying a User by name/email [email protected]
Context User	Specifying a User/Signatory by role. Examples: Supervisor Agency Chief Training Manager QA Manager
Sender	If someone other than the original author *sends* the shared draft, that person becomes the Author as well as "Sender". It is always the Sender who is signing off for the sign-off engine.
Pending Request for Me	A quick filter button at the top of the Signature Requests tab list view, enabling one click access to records.
Notification of signoff	Notification is sent where there is… Completion of a signoff flow level is completed (all required sign offs) Completion of all levels – all users at all levels are notified

Video Demonstration

This video provides a walkthrough of how to build a new sign-off flow.

Play Video

Build a Signoff Flow Toolkit

text
Start at *Home* and select *Settings*
Select *Workflow*
Select Add Sign-off Flow
*Fill:* *Name* *Description* *Type*
Select Type *QA/Training Feedback Report* Training Observation Task List Phase Enrollment
Select Add Level
Select *Add Context User* Reminder: *Context User* - Specifying a Signatory by their job Subject Author Supervisor
Specify who the *Context User* will be: *Author* (the person writing the feedback)
What does *Allow Return* mean? *Allow Return Toggle* This allows this user, the Shift Supervisor to Return (or reject) the Feedback *Reviewer Only* users will not Allow Return
On the same *Level 1, let’s add another Context User: Subject* Reminder: *Context User* - Specifying a Signatory by role Subject Author Supervisor
Fill *Context User: Subject* Specify what this Context User: Subject can do. Required Allow Return
Add *Custom User* Click the Add Custom User button. Reminder: *Custom User* - Specifying a User by name/email examples: Adam the Training Lead Sally the QA Lead
Fill *Custom User:* Adam (our Training Lead) Specify what this Custom User: Adam can do. *Reviewer only* *Save*
Signoff flow now shows in the list. Click the *Edit Pencil* to make changes
Let’s edit our Signoff flow and add Trish’s supervisor. This will be a Context User. Select *Add Context User*
Choose *Shift Supervisor* from the dropdown list of Context Users
*Save*
After saving, your new signoff flow will show in your list.
*View existing Signoff Flows*

Application:	Example Scenarios
Scenario A - Shift Supervisor User/Subject
Scenario B - Shift Supervisor Subject QA Lead
Scenario C Shift Supervisor Subject Trainer Agency Head

Build a Signoff Flow

Overview

Definitions

Video Demonstration

Build a Signoff Flow Toolkit

text