The Decision451 Board is where you can build and modify your decision-making process. In conjunction with Decision451 Groups and Permissions, you can further determine precise process movements and designations. Before starting, be sure you have a thorough understanding of your institution's evaluation process. See an example of a Decision Board here:

In this article, we will be discussing Decision Stages/Steps and Statuses. The Stages/Steps correspond to the blocks you see set out above, including "Ready for Review" and "1st Read." Think about what these steps might be in your Decision process. Statuses provide more information about the application, and might be something like "In Review," "Document Collection Phase," "Admitted," or "Denied." The only default status that cannot be edited in the Status tab of the Decision module is the "Submitted" one, which any application that migrates to the Decision module will have. The only default Step is "Ready for Review."

To add a new step to your board, click on the blue plus sign in the bottom right, give the stage a name, and assign a status to it. You can change the name of that step later on by simply clicking into the header and editing it. You can then drag and drop the stage to the correct location within your board to make it visually accurate. To modify the statuses available to each step, hover over them and click the pencil icon. Finally, you can determine to which steps an applicant can Transition from that stage by either checking "All Stage" or de-selecting and zeroing in on one or more.  

Keep in mind that both the stage transitions and the statuses must be in alignment for an application to move between stages. Additionally, ensuring an Element451 user has the proper permissions to do so will be critical--so be sure to go back and check your Decision451 Groups and Permissions before going live with your Decision Board!

Note: The different pieces of the Decision module all work together to streamline your Decision process. Be sure to check each piece against each other (Groups and Permissions, Board, Statuses, Cohorts, and Intelligent Admissions). For example, if you have Intelligent Admissions rules set up to migrate students to a certain Stage based on whether they meet the conditions of a segment, be sure that rule won't be unintentionally forcing students back to an earlier stage.

Did this answer your question?