Applications

Applications are how prospective students apply to programmes in Full Fabric. Staff build an application template: the form, the dates it is open, who may apply, and the extra steps it asks for (programme choices, an application fee, references, a digital signature). Applicants start an application from that template, fill it in over as many sessions as they need, and submit it. Staff then review the submission, evaluate it, and move the applicant towards an offer.

Key Concepts

Term Definition
Application template The form staff build, with its dates, availability rules and settings. Every application is started from a template.
Application One applicant's copy of a template, holding their answers, choices, payment and references.
Tab A page of the application form. Each template starts with a personal details tab, an application tab and a payment tab.
Primary choice The programme (class) or course the applicant applies to. Choosing it creates the applicant's journey in that class.
Secondary choice An optional second choice field, with its own association rules.
Reference template A group of references the applicant must collect, with a minimum and maximum number of referees.
Reference request One referee the applicant names. The referee receives an email with a link to submit the reference.
Application fee A fee the applicant pays before submitting. It can depend on the programme chosen.
Update request A request from staff asking the applicant to correct specific fields of a submitted application.
Template group Templates that share a tag. An applicant can submit only one application within a group.

Where Staff Work With Applications

  • Application templates are under Settings > Templates & documents > Application templates. Each template belongs either to the whole institution or to one class.
  • Individual applications open inside the applicant's profile, with tabs for the form, Evaluations, Subjects, Payment plan and Advanced actions. Opening an application from anywhere else as staff redirects to this view.
  • Lists of applications are reached from Applications in the sidebar (view all applications) or a template's list. Stats cards (Started, Pending Payment, Submitted) filter the list, and columns include Application state, Completion, References, Fee, Score and Agent Score. Export applications exports the list.

Application Lifecycle at a Glance

An application moves through four states:

State Shown as Meaning
not_started The application exists but has not been started.
started Started The applicant is filling in the form.
pending_payment Pending Payment The form is complete and the applicant is paying the application fee.
submitted Submitted The application has been submitted.

Submitting also moves the applicant's journey in the chosen class from prospect::started_application to applicant::submitted. See Application States for every transition and its side effects.

In This Section

Page What it covers
Application Templates Creating a template, its context, dates, availability and form tabs
Template Settings Confirmation page, redirects, notifications, PDF, signatures, experience and groups
Applying and Submitting How applicants start, save, pay for and submit an application, and what staff can do on their behalf
Application States The state machine, what each transition triggers, and unsubmitting
Programme Choices Primary and secondary choices, journeys, capacity and closed classes
Fees and Payment Application fees, fees per programme, payment plans and discount codes
References Reference templates, referees, deadlines, reminders and staff actions
Review and Update Requests Reviewing a submission and asking the applicant for corrections
Evaluations and Offers How submitted applications feed evaluations, scores and offers
Permissions The features that control what staff can do with applications

Note: Registration forms use the same template engine with a different kind. This section covers application templates. Course registration is covered in Registration.