Skip to main content
All CollectionsDecisions
๐Ÿ“Œ Decisions: Frequently Asked Questions
๐Ÿ“Œ Decisions: Frequently Asked Questions

This article answers commonly asked questions about Decisions, providing quick solutions and key insights.

Michael Stephenson avatar
Written by Michael Stephenson
Updated over 3 weeks ago
Pardon our progress as we actively develop this article.

General

Why are some decisions missing from All Decisions? I submitted a test application, but it's not visible in Decisions.

This is likely a permissions issue. To check:

  1. Navigate to Applications > Decisions > Decision Settings.

  2. Open the Groups + Permissions tab.

  3. Locate the permission group for yourself or the affected user.

  4. Ensure the group has access to all relevant permissions.

Updating permissions should allow the missing decisions to appear.

Is it possible to export notes from the Decision module?

Decision notes cannot be exported from the Decision module. As a workaround, you can add the decision notes to the contact record notes, which are exportable. For added organization, consider creating a custom note type (e.g., "Application" or "Decision") so you can easily categorize these notes when adding them to the contact record.


Cohorts, Stages, and Statuses

I updated the conditions for my cohort, but it is not updating.

Cohorts are recalculated only when the conditions defining them are changed. Changing the segment that a cohort references does not automatically trigger a re-evaluation of the cohort. This can lead to inconsistencies if updates to segments are expected to influence existing cohorts. To manually trigger a cohort re-evaluation, toggle the cohort's active state to inactive and then back to active.

I added a new cohort, stage, or status, but I can't see it.

It is likely that you are missing permission to see it. By default, when you add new cohorts, stages, and statuses, they are not automatically assigned to any permission groups. This means they are not visible to you or other internal users. You need to adjust your permissions. Click here for a step-by-step guide to adjusting permission groups.


Checklists

How can I customize checklist requests for different applicant types?

You can customize checklist visibility in Decision Settings > Checklist by adjusting the โ€˜Visible Toโ€™ setting. This allows you to restrict checklist items based on user segment or segment reference, ensuring only relevant applicants see specific requests.

Additionally, checklist items can have conditions to further refine visibility. For example, you can hide the transcript request for international applicants while keeping it visible for domestic students.

For step-by-step guidance, visit our help article: Decisions Checklists.


Packages

Can I use the same custom field tokens in a Package letter that I use in Campaigns?

The Tokens feature within Decisions operates differently than tokens in other platform modules. If you wish to insert custom data, you first must create token placeholders and then assign those tokens a value at the application decision level.


Reviewing + Scoring

Why Didnโ€™t the Last Reviewer Field Update?

The Last Reviewer field updates only in specific scenarios, such as when the applicationโ€™s status or stage is changed. However, actions like updating a checklist item do not trigger changes to the Last Reviewer field. For more details, check out the Anatomy of the Application Overview section within this help article.


The Decisions Module is included with the Element Engage package.

Did this answer your question?