This is likely a permissions issue. To check:

Updating permissions should allow the missing decisions to appear.

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.

To grant view-only access to documents, include permissions like View Profiles and Access Decisions. Avoid adding Administer Documents, as that permission provides full control rather than just view-only access.

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.

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.

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.

Rules that rely on Application (All Properties) filters can sometimes misfire because those filters are evaluated before the full application data finishes syncing. This timing mismatch can cause your rule to skip or trigger incorrectly.

To avoid this, use Decision conditions or Decision segment filters instead. These re-evaluate after the application sync completes, ensuring your logic runs on the most accurate and complete data—like updated GPA, transcript details, or evaluation results.

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.

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.