Application States
Every application has a state that records how far the applicant has got. The state changes only through defined transitions, each of which records who made it and when, and publishes an automation event that workflows, inbox cards and the profile timeline listen to.
State Machine
| State | Shown to staff as | Meaning |
|---|---|---|
not_started |
The application exists but has not been started yet. | |
started |
Started | The applicant is filling in the form. Answers are saved as they go. |
pending_payment |
Pending Payment | The form is complete and the applicant has moved on to pay the application fee. |
submitted |
Submitted | The application has been submitted and is locked for the applicant. |
On the applications list these appear as stats cards that also filter the list. On a submitted application with update requests, the badge reads Submitted · followed by the review status.
Transitions
Start
not_started → started. Happens when an applicant opens a template's start link, or when staff use Start application on someone's profile. Full Fabric records who started it and when.
Start Payment
started → pending_payment. Only allowed when the template has payment enabled and every part of the form except the payment is valid. If the template uses payment plan fees, the applicant's payment plan is saved at this point.
Restart
pending_payment → started. Takes the applicant back from the payment step to the form so they can change answers. Any payment plan choices already made are cleared.
Submit
started or pending_payment → submitted. Only allowed when the application passes every check: the template is open (or the applicant has an extended deadline), every required field is answered, the choices are valid, references are in order, the fee is paid or waived, and any signature is complete. See Applying and Submitting for the full list.
Unsubmit
submitted → started. Staff use Unsubmit this application on the application's Advanced tab to reopen it for the applicant, and confirm with I understand the consequences, unsubmit this application. Full Fabric records who unsubmitted it and when.
Note: Only staff with the
applics.applications_unsubmitfeature can unsubmit. Applicants cannot unsubmit their own application.
What Each Transition Triggers
| Transition | Automation event | Default effects |
|---|---|---|
| Start | Application started | Journey moves to prospect::started_application; inbox card; timeline entry |
| Start payment | Application pending payment | Inbox card; timeline entry |
| Submit | Application submitted | See On Submit below |
| Unsubmit | Application unsubmitted | Timeline entry |
On Submit
When an application is submitted, Full Fabric:
- Copies mapped answers onto the applicant's profile (fields whose answers map to profile fields).
- Sends any reference requests that have not been sent yet, if the template sends them automatically on submission.
- Starts the review cycle, if the template uses update requests.
- Moves the applicant's journey to
applicant::submittedin the template's class and every class the application is associated with. - Emails the applicant a confirmation, unless the template disables it or a staff member submitted the application.
- Emails the profile owner of each related class, where the applicant has an owner.
- Saves and, if the template is set to, publishes the applicant's payment plan.
- Starts an AI evaluation, if the template has one configured. See Evaluations and Offers.
On Unsubmit
When an application is unsubmitted, Full Fabric:
- Clears any digital signature, because the answers can now change. The applicant has to sign again before resubmitting.
- Cancels any open update request and clears the review status.
- Leaves the applicant's journey state unchanged. Move it back by hand if needed.
Journey States
Applications drive the applicant's journey through the default lifecycle transitions:
| Lifecycle transition | From | To |
|---|---|---|
start_application |
prospect::cold, prospect::engaged, prospect::qualified |
prospect::started_application |
submit_application |
prospect::started_application |
applicant::submitted |
These moves are made by the default automation Transition applicant role. If an institution has changed its lifecycle and the transition does not exist from the applicant's current state, the journey stays where it is. See Lifecycle & Journeys.
Late Applications
On the application's Advanced tab, under Deadline, staff can tick Allow late application and set a date for that one applicant. While the date is today or in the future, the applicant can still submit after the template has closed, and a closed class choice is not rejected.
Timestamps Staff Can See
| Field | Set when |
|---|---|
| Started at / by | The application is started |
| Started payment at / by | The applicant moves to the payment step |
| Submitted at / by | The application is submitted |
| Unsubmitted at / by | Staff unsubmit the application |
| Last updated at | Any of the above, or the applicant saves answers |