Decision Code Settings
  • 21 Nov 2023
  • 2 minute read
  • Dark
  • PDF

Decision Code Settings

  • Dark
  • PDF

Article Summary

Decision Codes




Inactivate decision codes that are no longer used.  This preserves the decision history on the record, but inactive decisions cannot be accidentally assigned to applications administratively.


Give the decision a descriptive name.  This name is visible administratively only.


Each decision must be assigned a unique code.  It is typically helpful to use short alpha codes, such as AT for admit codes.  This simply makes reading SQL easier to understand, as numeric codes like 42 do not typically hold meaning.  If your SIS is looking for a numeric code, consider entering this code as the Export Value.

Export Value

Configure up to 3 export values for a decision code.  Export values can be used in exports to external systems, including your SIS.

Decision Label (optional)

Optionally add a decision label that will appear for applicants when viewing decision letters online.  This is often helpful for applicants who have multiple released decisions with letters, as they are able to more easily view a specific decision letter again.

Priority (optional)

If you release multiple decisions at exactly the same time, you may set a priority order in which the decision will appear.  Decisions that are not released at exactly the same time will display in order of the release date.


This setting allows you to prevent certain decision codes from being batch released if a prerequisite decision has not yet been released for that application.  For example, an Admit/Decline decision should not be released if the application does not have a released Admit decision yet.  Configure up to three prerequisite decisions for a particular decision.  If more than one prerequisite is specified, this decision can be batch released if an application has at least one of the prerequisite released decisions. 

Opt Out

This setting will automatically set the Opt Out tag when the decision is released.  This is typically used for Deny decisions, where institutions want to prevent denied applicants from continuing to receive marketing communications.


Most decisions should have the type of Decision.  Decision codes that are used for other types of items, such as Financial Aid or Scholarship letters, should typically be set to Correspondence/Letter.  Correspondence/Letter decisions are not ranked, so it will prevent these decisions from being considered the most recent or first decision for an application, which will prevent their inclusion in decision exports that rely on the decision rank or filters that are specific to the most recent decision or first decision.

Admitted Student SSO

Enable this setting if you are using Slate as a CAS provider to authenticate users into another on-campus system and would like to require certain decisions for access.  This setting can also be used to enable access to an admitted student portal.


This setting is used for Decision Letter exports, including the Query Output option Decision Letter Export to Word.  Only printable decisions will be included in the file.

Hide Checklist

Hide checklist when released will hide material and financial aid checklist items on the status page.  The Forms checklist items will still appear (see the Hide Forms option below).  Once an applicant has a released decision that is configured to hide the checklist when released, these checklist items will not appear on the status page, even if a new decision is released that is not configured to hide the checklist.

Hide Forms

Hide forms if not yet viewed will hide just the forms section of the checklist until the applicant has viewed the decision letter online.  This setting is particularly useful for Admit decisions, where you do not want the applicant to see the form Reply to Offer of Admission on the checklist before reading the decision letter that tells them that they have been admitted.

Was this article helpful?