58 lines
2.9 KiB
Markdown
58 lines
2.9 KiB
Markdown
# Making Decisions
|
|
|
|
The **Decisions** tab provides a ranked view of applicants and tools to record accept, waitlist, or decline decisions. It appears when the cohort reaches the `decide` stage.
|
|
|
|
## Prerequisites
|
|
|
|
You need cohort admin or higher access. The cohort must be in `decide`, `onboard`, `active`, or `closed` status.
|
|
|
|
## The Decision Dashboard
|
|
|
|
The **Decisions** tab shows:
|
|
|
|
- **Statistics cards** -- Total applications, accepted count, waitlisted count, and declined count.
|
|
- **Ranked Applicants table** -- All applications with review scores, sorted by average score (highest first). Each row shows rank, studio name, contact name, email, average score percentage, review count, and current decision status.
|
|
|
|
Applications appear here once they have review scores or are already in a terminal status (`accepted`, `waitlist`, `declined`).
|
|
|
|
## Making a Decision
|
|
|
|
### Single Application
|
|
|
|
Click the dropdown menu (three dots) on any row. Choose **Accept**, **Waitlist**, or **Decline**. The decision is recorded immediately and the application status updates.
|
|
|
|
You can also click **View Reviews** to open the application detail page and review scores before deciding.
|
|
|
|
### Bulk Decisions
|
|
|
|
1. Select applications using the checkboxes in the leftmost column. Use the header checkbox to select all.
|
|
2. Click **Accept**, **Waitlist**, or **Decline** in the header buttons. The count of selected applications is shown on each button.
|
|
3. Decisions are applied to all selected applications. If some applications cannot transition to the chosen status (e.g., already decided), those are skipped and you receive a partial update notification.
|
|
|
|
## Decision Records
|
|
|
|
Each decision creates a record in the Decision model with:
|
|
|
|
- **Decision** -- `accepted`, `waitlist`, or `declined`.
|
|
- **Decided at** -- Timestamp of the decision.
|
|
- **Rationale** -- Optional text explaining the reasoning.
|
|
- **Rationale code** -- Optional code for categorizing the reason.
|
|
- **Committee notes** -- Optional notes from committee discussion.
|
|
|
|
:::info
|
|
Decisions enforce valid status transitions. You cannot re-decide a `declined` application to `accepted` without first changing its status. Waitlisted applications can transition to `accepted` or `declined`.
|
|
:::
|
|
|
|
## Workflow
|
|
|
|
The typical decision workflow is:
|
|
|
|
1. Lock all reviews for the relevant stage (see Locking Reviews & Consensus).
|
|
2. Review consensus data and scores on the **Decisions** tab.
|
|
3. Hold a committee discussion if needed.
|
|
4. Record decisions individually or in bulk.
|
|
5. Move the cohort to `onboard` status when all decisions are finalized. If all decisions are made through the bulk decision endpoint, the cohort may automatically transition to `onboard`.
|
|
|
|
## After Decisions
|
|
|
|
Once decisions are recorded, the **Email Tasks** tab shows which applicants need to be notified. Accepted applicants will appear on the **Onboarding** tab when the cohort reaches `onboard` status.
|