Review and Update Requests
Once an application is submitted it is locked for the applicant. Staff can still edit any answer, but to have the applicant correct something, staff send an update request: a message, a reply-by date, and the list of fields to reopen. The applicant corrects those fields only and sends the application back. When staff are satisfied, they mark the application as reviewed.
Turning It On
Update requests are a template setting. They only take effect when both of these hold:
- The template's Can staff request updates after submission? is set to Yes, staff can reopen specific fields (on the Details tab).
- The institution uses the new application experience for applicants, because applicants answer update requests there.
While either is off, submitted applications have no review status and staff use unsubmit to reopen a whole application instead.
Review Status
Each submitted application on such a template carries a review status, separate from its state:
| Status | Shown as | Meaning |
|---|---|---|
pending_review |
Pending review | Submitted and not yet reviewed. Set on every new submission, which also clears any earlier approval. |
awaiting_updates |
Awaiting updates | An update request is open and the applicant has not sent it back yet. |
updates_in |
Updates in | The applicant sent back the requested corrections. Staff have not reviewed them yet. |
reviewed |
Reviewed | A staff member approved the application. Full Fabric records who and when. |
On the applications list, the Submitted card breaks down into these statuses, with a count of overdue requests. The Review status filter (with values including Update overdue) is available only on templates that use update requests.
Cancelling an open request returns the application to the status it had before: reviewed if it had been approved, updates_in if earlier corrections were waiting, otherwise pending_review. Unsubmitting the application cancels any open request and clears the review status.
Requesting Updates
In the application's Review panel, a staff member clicks Request updates, marks the fields to reopen on the form, then clicks Continue to open the request:
| Field | Required | Description |
|---|---|---|
| Fields being reopened | Yes | The fields marked on the form. |
| Message to the applicant | No | Explanation for the applicant, included in the email. |
| Reply by (required) | Yes | The date the applicant should answer by. A request still open after this date counts as overdue. |
| State | No | Moves the applicant's journey in the application's class to the chosen state at the same time, for example back to an applicant substate that means "incomplete". Only journey states (prospect, applicant, student, alumnus) can be chosen. |
Send update request sends it.
Rules that apply:
- Only one request can be open at a time. Cancel the open one before sending another.
- Fields that depend on a reopened field (fields it can reveal or make required) are reopened with it, so the applicant can complete them.
- Some fields can never be reopened: first name, last name, email, fields mapped onto those, primary and secondary choice fields, system fields, instruction fields and sequential IDs. Fields the applicant cannot see on their own form cannot be reopened either.
When the request is sent, the applicant receives an email from the default automation and the application moves to awaiting_updates.
How the Applicant Answers
The applicant opens their application and sees only the reopened fields as editable. Each field counts as corrected once a valid value is saved. A required field saved blank stays outstanding.
The applicant can send the application back only when every field staff asked for that is still on their form has been saved, and every reopened field is valid. Sending it back:
- Copies mapped answers onto the applicant's profile again.
- Marks the request completed and moves the application to
updates_in. - Publishes an automation event that workflows can use to notify staff.
The application stays submitted throughout. Deadlines are not checked again, because only the reopened fields changed.
Tip: Staff who correct a reopened field on the applicant's behalf also count towards completing the request. A staff member or the organisation contact who started the application can send it back for the applicant with the
applics.applications_resubmitfeature.
Approving and Cancelling
Approve sets the status to reviewed and records the reviewer and the time. Approving publishes an automation event. An application with an open update request cannot be approved as is: the panel offers Cancel request and approve to do both.
Cancel request closes the open request without waiting for the applicant.
What Staff See
The Review panel shows Update request sent with the open request's details. Once the applicant sends it back, the fields they changed in that round are marked Updated, until a new request is opened or the application is unsubmitted.
Permissions
| Action | Feature |
|---|---|
| Request updates, cancel a request, approve | applics.applications_review_change |
| Send corrections back on the applicant's behalf | applics.applications_resubmit |
| Edit answers on a submitted application | applics.applications_change |
See Permissions for the full list.