Evaluations

Evaluations let staff and committee members review applications with structured forms. Each evaluation is one review of one application, made from an evaluation template: an evaluator fills in the form next to the application, the answers can produce a score, and the evaluator submits it when done. The scores of an application's evaluations roll up to the application, where they help admissions staff decide what happens next.

Evaluations can also be completed by an AI agent, which reads the application, applies criteria written by staff, and records a score with an explanation for reviewers to weigh.

Key Concepts

Term Definition
Evaluation template Defines one kind of review: the form, who can work on its evaluations, what the evaluator sees, and its automations. See Evaluation Templates.
Evaluation One review of one application, made from a template. It is Started or Submitted. See Evaluation States.
Evaluator The staff member an evaluation is assigned to.
Individual evaluation An evaluation only its evaluator (or an administrator) can work on. It always has an evaluator.
Team evaluation An evaluation any staff member who can open it can work on. It may be left unassigned.
Agent evaluation An evaluation completed and submitted by an AI agent. See AI Agent Evaluations.
Product choice The programme choice of the application an evaluation is for: primary, secondary, or none (generic).
Evaluation score The sum of the scored matrices in an evaluation's form.
Score (of an application) The average of the scores of the application's evaluations.
Agent score The average score the AI agent evaluations gave an application, from 0 to 100.

How It Fits Together

  • Applications. Every evaluation belongs to an application, and each application template chooses which evaluation templates its applications can use. Deleting an application deletes its evaluations.
  • Profiles. Evaluation fields can be pre-filled from the applicant's profile and application, and can write results back to the profile on submission.
  • Lifecycle. From an evaluation list, staff can move the applicants behind the evaluations to a lifecycle state, such as a decision state.
  • Offers. Evaluations inform admissions decisions but do not create or change offers. See Offers.
  • Inbox and automations. Evaluators get an inbox card when an evaluation is assigned to them; the staff following the applicant get one when it is submitted. Each template can run automations on both events.
  • Segments. Evaluation rules (has an evaluation, has a started or submitted evaluation, has an evaluation assigned to someone) can filter profiles. See Segments.

In This Section

Page Covers
Evaluation Templates Creating templates, individual and team types, the form, field mappings, connecting templates to application templates
Starting and Assigning Evaluations Starting evaluations one at a time or in bulk, product choices, assigning, duplicating to another application
Working with Evaluations The evaluation lists, bulk actions, exports, and the evaluation page
Evaluation States Started and Submitted, submitting, unsubmitting, the audit log, deleting, inbox cards and automations
Scoring and Decisions How matrices are scored, the evaluation and application scores, moving applicants on after evaluation
AI Agent Evaluations Setting up an agent template, when agents run, and what they produce
Permissions and Settings Features, which evaluations each staff member sees, and institution settings