---
title: Move to next stage
description: >-
  Change an applicant's application status from Submitted through Under Review
  and a decision to Enrolled, one at a time or in bulk, including the rules for
  enrolling.
sidebar:
  order: 5
---

**Moving to the next stage** means changing an applicant's **application status** in **Campus Management → Applications**, either in the **Status** column of the list or with the status selector on the submission page. The status is the stage: from **Submitted** through **Under Review** and your decision to **Enrolled**.

Fuxam Apply does not use a separate configurable stage engine. The pipeline is **status-driven**: each status value is both the stage label and the control point for notifications, applicant portal display, and downstream enrollment. Understanding this pipeline is essential for coordinating [review](/docs/fuxam-web/apply/applicants/review-an-application), [decisions](/docs/fuxam-web/apply/applicants/approve-or-reject), and handoff to [user management](/docs/fuxam-web/base/user-management) and [cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts).

## Why it matters

Admissions is a sequence of accountable transitions. Status updates tell applicants where they stand, trigger [review emails](/docs/fuxam-web/apply/apply-portal-settings/email-notifications) at the right moments, and signal to colleagues which files need attention. Without consistent stage movement, teams duplicate work, applicants receive conflicting messages, and enrollment staff cannot tell which offers are ready for cohort assignment.

Stage discipline also supports reporting: filtering the [Applicants](/docs/fuxam-web/apply/applicants) table by **Application status** only works when staff update status as work progresses.

## Status pipeline overview

The status selector offers these values (your institution may skip some):

| Status | Meaning |
|---|---|
| **Draft** | Applicant started but has not submitted. Submitting changes it to **Submitted**. |
| **Pending** | Not submitted yet. Pending applications without a submission date also appear on the **In progress** tab. |
| **Submitted** | Application received, not yet under review |
| **Under Review** | Admissions team is evaluating the submission |
| **Needs Update** | Applicant must correct or supplement answers. Set automatically when you mark a field for changes or use **Request Changes**. |
| **Conditionally Accepted** | Offer made with open conditions; you can set deadlines for single fields |
| **Accepted** | Offer made. The only status from which you can enroll. Listed on the **Accepted** tab. |
| **Enrolled** | Applicant is formally enrolled. The submission leaves the Application Management lists and can't be changed anymore. |
| **Rejected** | Application declined |
| **Withdrawn** | Applicant withdrew; staff record it with this status |

Not every submission visits every stage. Conditional acceptance and enrollment may trigger additional workflows (study contracts, health insurance, user account provisioning).

## How to move a single applicant

1. Go to **Campus Management → Applications** and find the applicant on the **Pending** (or **Accepted**) tab.

2. Click the status in the applicant's row, or click the applicant's name and use the status selector at the top right of the submission page.

3. Choose the new status. **Draft**, **Pending**, **Submitted**, **Under Review**, **Needs Update**, **Rejected** and **Withdrawn** are saved right away.

4. For **Accepted** or **Conditionally Accepted**, the **Preview Study Contract** dialog opens. Check it and click **Continue**. In the list (and in the detail sheet) you then confirm the study program and cohort (**Confirm and continue**) or answer **Add Study Programs or Cohorts?**.

5. On the submission page, **Needs Update** and **Conditionally Accepted** ask **Send Request Changes Email?**. Click **Send** to notify the applicant, or **Don't Send** to change only the status.

Fuxam sends a review email and an in-app notification for every status change except **Draft** and **Pending** (and except when you click **Don't Send**).

## How to enroll an accepted applicant

1. Check that the applicant's status is **Accepted**. A **Conditionally Accepted** applicant has to be set to **Accepted** first; otherwise Fuxam refuses the change.

2. Choose **Enrolled** in the status selector. If the applicant's study contract still waits for a signature, Fuxam stops with **Contract signature required**.

3. The **Enroll student** dialog explains that enrolling creates the institution membership, assigns the default role, generates a matriculation number, adds the user to their cohort and creates their study plan when applicable. If health insurance is enabled on the form, a checkbox (on by default) reports the immatriculation date to the applicant's health insurance provider. Click **Enroll**.

4. Complete the **Preview Study Contract** dialog (and, in the list, the study program / cohort dialogs) as for acceptance.

If the applicant has no user account yet, Fuxam sends them an invitation to your institution (valid for 7 days) and marks the submission **Enrolled**; enrollment is completed once they accept the invitation. Enrolled submissions disappear from the **Pending**, **In progress** and **Accepted** tabs. Find enrolled students in [user management](/docs/fuxam-web/base/user-management) and their [cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts).

## Recommended flow

A common administrative sequence:

1. **Submitted** → **Under Review** when an evaluator picks up the file.
2. **Under Review** → **Needs Update** if corrections are required (this happens automatically when you mark a field for changes), or → **Accepted**, **Conditionally Accepted** or **Rejected** for a decision.
3. **Needs Update**: after the applicant resubmits, the status stays **Needs Update** and a "changes addressed" marker appears next to it. Review the changed fields, then decide.
4. **Conditionally Accepted** → **Accepted** once the conditions are met.
5. **Accepted** → **Enrolled** after the contract is signed and onboarding steps are complete.

Use the **Pending requirements** area (when visible in your Campus Management navigation) to track conditional items with deadlines and send reminders.

This sequence aligns with handbook task guides: [Review an application](/docs/fuxam-web/apply/applicants/review-an-application) during **Under Review**, [Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject) at decision points, then **Enrolled** when ready for [add users to cohort](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts/add-users-to-cohort) workflows.

## Bulk stage changes

To move multiple applicants to the same stage, select rows and use the bulk status control. See [Bulk process applications](/docs/fuxam-web/apply/applicants/bulk-process-applications).

:::warning
Enrolled submissions no longer appear in the Application Management lists, so you can't select them for bulk changes. Their status can't be changed anymore (**Cannot change enrolled submissions**).
:::

## Stage transition reference

| From | Common next stages | Notes |
|---|---|---|
| **Draft** / **Pending** | **Submitted** (applicant action) | Staff rarely set these except for data correction. |
| **Submitted** | **Under Review** | Signals evaluation has started. |
| **Under Review** | **Needs Update**, **Accepted**, **Rejected**, **Conditionally Accepted** | Decision or correction branch. |
| **Needs Update** | Your decision after re-review | Stays **Needs Update** when the applicant resubmits. |
| **Conditionally Accepted** | **Accepted** | Conditions met → advance. **Enrolled** is not possible directly. |
| **Accepted** | **Enrolled** | Signed contract required when one is pending; **Enroll student** confirmation. |
| Any active stage | **Withdrawn** | Recorded by staff per policy. |
| **Enrolled** | — | Can't be changed. |

## Best practices

- **Advance status when work starts** — Move to **Under Review** when assigned, not only when the decision is ready.
- **Do not skip conditional steps** — Use **Conditionally Accepted** when contract or document collection remains; avoids premature **Enrolled**.
- **Watch deadlines** — [Configure program settings](/docs/fuxam-web/apply/application-programs/configure-program-settings) submission deadlines affect whether late applications should progress.
- **Coordinate enrollment** — Before setting **Enrolled**, confirm study contract and [user management](/docs/fuxam-web/base/user-management) prerequisites your institution requires.

## Common pitfalls

| Pitfall | What happens | What to do |
|---|---|---|
| Enrolling a **Conditionally Accepted** applicant | Fuxam refuses: the applicant must be accepted first | Set **Accepted**, then **Enrolled** |
| Enrolling before the contract is signed | **Contract signature required** — the status doesn't change | Wait for the applicant's signature, then enroll |
| Enrolling too early | Enrollment creates the membership, matriculation number and cohort placement, and the submission can't be changed afterwards | Confirm contracts and conditions first (see [Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject)) |
| Leaving files at **Submitted** | Reporting and the applicant's view look stale | Bulk-move to **Under Review** to show active processing |
| Expecting email for every status | No review email for **Draft** or **Pending** | Use [Communicate with an applicant](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant) if you need to tell them something |

## FAQ

**Can we define custom stage names?**

The pipeline uses fixed application status values. Your process maps to these statuses; you cannot add arbitrary stage names beyond the supported set.

**Where do accepted applicants appear in the table?**

The **Accepted** tab shows only submissions with status **Accepted**. **Conditionally Accepted** submissions stay on **Pending**. **Enrolled** submissions leave the Application Management lists; find those students in user management and their cohorts.

**What happens at Enrolled?**

Enrolling creates the institution membership, assigns the default role, generates a matriculation number, adds the user to their cohort and creates their study plan when applicable. Applicants without a user account first get an invitation; enrollment completes when they accept it.

## Related pages

**[Review an application](/docs/fuxam-web/apply/applicants/review-an-application)**

Evaluate answers before advancing status.

**[Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject)**

Decision emails and enrollment guards.

**[Configure program settings](/docs/fuxam-web/apply/application-programs/configure-program-settings)**

Submission deadlines that affect open applications.

**[Study programs and cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts)**

Downstream enrollment and cohort structure.

