These two articles provide information regarding best practices for creating Decision Codes and Reasons in Slate for application review. Reasons work essentially like a “subcode” or an explanation for the Decision Code. These codes can “stack” as the student continues through the application process.
Often interactions, activities, statuses, decisions reasons, and actual decisions are combined into decision codes. This is an opportunity to consolidate and organize decision codes to be more sustainable by adopting the Slate standard decision names and codes. Adopting these standards from the start will make the rest of the decision process cleaner and easier to understand.
Adding a decision reason can be an effective way to further define the decision and quickly isolate particular records. For example, a person may be admitted by the dean of admissions. This student might have a decision code of Admit and a decision reason of Dean Admit.