Workflow Checklist

Allow External Users To Transition is set appropriately. (Including on post-Decision Type steps)

Set Submitted Date function is always done before creating a CoR

All the transitions from a step are in the most intuitive order you can think of. If the same transitions (or set of transitions) exist on another workflow, then use the same order. This may mean reordering the transitions when adding new ones. Always check the order in an actual activity so you see what the menu looks like.

Add a transition description if needed. If staff may be confused by when/why to choose the transition or need to know what will happen, then add a description. As Brief As Possible. They clutter up the menu, so they should be reserved for necessary information.

Is the step assigned to anyone?
Either on the step itself or on transitions ending on the step. As a general rule the activity should be “owned” by someone. There are exceptions. End state activities should NOT be assigned to anyone. Activities that are “Active” are generally not assigned. If someone needs to perform work when the activity is in that state, then it needs an assignee.

All steps should have a description for the intended EXTERNAL stakeholder.
--Grammar and Spellcheck
--Communicates what is happening (status may be enough) AND what is expected of them.
--Is similar in tone, language, and layout to existing workflows (plagiarize with abandon). Use an HTML Editor Free Online HTML Editor and Cleaner - http://HTML-Online.com

Remember that the functions are going to run every single time the workflow is transitioned into that step. If you don’t want that to happen, then the functions need to be moved to upstream transitions.

Advanced Properties - Checkbox Data Prompt with the acknowledgement of submission order is 1

Advanced Properties - Checkbox Data Prompt with the PIN request order is 2