Scoring and Decisions
Evaluation forms can calculate a score from the answers evaluators give. Each evaluation gets its own score, and the scores of an application's evaluations are averaged into the application's score. Staff use these scores, together with the evaluation lists, to decide what happens to each applicant.
How a Matrix Is Scored
Scores come from matrix fields: a grid of rows (the criteria) and columns (for example, one column per evaluator rating). Three settings on a matrix field decide its score:
| Setting | Where | Effect |
|---|---|---|
| Calculate average | On a column | Only columns with this setting count towards the score. |
| Weight | On a row | A percentage. Each cell is multiplied by its row's weight divided by 100. |
| Total score | On the field | Counts this matrix's score towards the evaluation score. |
Only matrices whose cells are text or drop-down produce a score. Each cell is read as a number, and a cell that is empty or not a number counts as 0.
For each column with Calculate average, Full Fabric adds up every cell multiplied by its row weight. The matrix score is the average of those column results, rounded to two decimal places.
Note: With row weights that add up to 100, each column result is a weighted average of its cells, on the same scale as the cells. Weights that add up to more or less than 100 scale the result up or down.
Example. A matrix has three criteria weighted 50, 30 and 20, and one averaged column. An evaluator rates them 8, 6 and 10. The column result is 8 × 0.5 + 6 × 0.3 + 10 × 0.2 = 7.8, so the matrix score is 7.8.
The Evaluation Score
The evaluation score is the sum of the scores of every matrix flagged Total score, across all the documents of the template. A flagged matrix that the evaluator has not answered yet does not count. While none of them is answered, the evaluation has no score.
A matrix that calculates an average but is not flagged Total score still has its own score, which evaluation lists can show as a column, but it does not add to the evaluation score.
Note: Templates built before the Total score flag existed may take their score from a field named
scoreinstead. This only applies when no matrix in the template is flagged.
Scores are recalculated each time an evaluation is saved, whether it is started or submitted.
On the evaluation page, a Total score table under the form shows the score of each flagged matrix and the total, recalculated as the evaluator answers. See Working with Evaluations.
Changing How a Template Scores
Changing anything that affects a matrix score in the template's form builder (the Total score flag, Calculate average on a column, row weights, the cell type or the drop-down options) recalculates the scores of every evaluation of that template in the background, then the scores of their applications. The answers are not touched, so the recalculation does not change an evaluation's last updated date or its audit log. Adding a matrix that neither averages nor counts towards the total does not trigger a recalculation.
The Application Score
Every application carries two scores built from its evaluations:
| Score | How it is calculated |
|---|---|
| Score | The average of the scores of all the application's evaluations that have one. Evaluations without a score are left out. With none, the score is 0. |
| Agent score | The average of the Agent Score of the application's AI agent evaluations, from 0 to 100. With none, it is 0. See AI Agent Evaluations. |
The application score is updated every time one of its evaluations is saved or deleted.
Warning: The application score includes evaluations that are still in progress, not only submitted ones. An evaluator's partial answers move the average until the evaluation is submitted.
From Evaluations to a Decision
Evaluations inform a decision; they do not make one. Submitting an evaluation does not change the application's state, the applicant's lifecycle state, or any offer. Staff act on the results in the following ways.
Move Applicants to a Lifecycle State
From an evaluation list, staff can select evaluations and move the people behind them to a lifecycle state in one action, for example to the state that marks an admissions decision. Each person moves in the class their evaluation is for, so one run can update journeys in several classes.
Full Fabric picks the journey to move in this order:
- The class of the evaluation's programme choice.
- The application's own programme or class, then the other contexts the application is linked to.
- If none of those matches, the person's only journey, when they have exactly one.
Journeys in a class or course are preferred over a journey held at institution level. Before the run starts, a preview shows how many people can move and how many will be skipped, and why (the preview checks the first 200 selected). The run itself happens in the background. People are skipped when their profile is anonymised, when they have no journey, or when they have journeys in several classes and none matches the application.
Note: This action needs the permission to bulk change profile states. See Permissions and Settings.
Copy Results to the Profile
Fields in an evaluation template can be mapped to profile fields. When an evaluation is submitted, the values of its mapped fields are written to the applicant's profile, where the rest of the platform (segments, lists, automations) can use them. See Evaluation Templates.
React with Automations
Assigning and submitting an evaluation are automation triggers, set per evaluation template. An automation can, for example, email the evaluator when an evaluation is assigned, or start a workflow when one is submitted. See Evaluation States.
Offers
Evaluations have no direct link to offers: no evaluation setting creates, changes or sends an offer. Staff decide on the strength of the evaluations, then handle offers in the Offers module. See Offers.
Scores in Exports
Evaluation exports include an Evaluation score column with two decimals, blank while the evaluation has no score. Application exports include the application score. See Permissions and Settings for who can export.