Evaluation States
An evaluation has two states: Started while the evaluator is working on it, and Submitted once they have finished. Submitting records who submitted and when, makes the evaluation count as complete in lists and filters, and can trigger notifications and automations. A submitted evaluation can be taken back to Started.
| State | Meaning |
|---|---|
| Started | The evaluation exists and can be filled in. Every new evaluation starts here, whether or not anyone has opened it yet. |
| Submitted | The evaluator has finished. Full Fabric records who submitted it and when. |
The state shows as a badge next to the evaluation's name, in the Evaluation state column of the evaluation lists, and in the Started and Submitted counters above them.
Note: AI agent evaluations are submitted as soon as they are created, and have no Submit evaluation button. See AI Agent Evaluations.
Who Can Work on an Evaluation
Filling in, submitting and unsubmitting an evaluation need the permission to start, submit and edit evaluations, and one of the following:
| Evaluation type | Who can work on it |
|---|---|
| Individual | The evaluator it is assigned to. |
| Team | Any staff member who can open it. |
| Any type | An administrator. |
Anyone else who can open the evaluation sees it read-only; a change they attempt is refused with "You cannot edit this Evaluation". See Starting and Assigning Evaluations for individual and team evaluations, and Permissions and Settings for who can open which evaluation.
Submitting
Answers are saved as the evaluator fills in each field, so there is no separate save step. When the evaluation is complete, select Submit evaluation and then Confirm, submit evaluation.
Submitting checks the form first: every required field must be answered and every answer must be valid. If anything is missing or invalid, the evaluation stays Started and Full Fabric reports the fields to fix.
When the submission succeeds:
- The state changes to Submitted, with the submitter and the submission date recorded. The button now reads Submitted and is disabled.
- The staff who follow the applicant get an inbox card (see below).
- Automations set on the template for evaluation is submitted run.
- Fields mapped to profile fields copy their values to the applicant's profile. See Evaluation Templates.
If an evaluation is already submitted, submitting it again changes nothing. When someone other than the original submitter tries, it is refused with "Already submitted by someone else".
Unsubmitting
Choose Unsubmit evaluation from the evaluation's menu and confirm with I understand, unsubmit this evaluation. The evaluation returns to Started, so the evaluator can change their answers and submit again. Full Fabric records who unsubmitted it and when. The previous submission date is kept until the next submission replaces it.
The Audit Log
Choose Audit log from the evaluation's menu, or from its row in the application's evaluations list. The log has one row per event, with the User, Action, Date and Changes:
- Each time someone opens the evaluation (a view).
- Each change to the evaluation, with the old and new values.
- Each submission and unsubmission.
The audit log needs the permission to access audit logs.
Deleting an Evaluation
Choose Delete evaluation from the evaluation's menu and confirm with I understand, delete this evaluation. The evaluation and its answers are removed permanently. Full Fabric then:
- Takes it off any inbox card about it, and deletes a card left with no evaluations.
- Recalculates the application's score without it. See Scoring and Decisions.
Evaluations are also deleted when their application is deleted, and when their evaluation template is deleted.
Warning: Deleting cannot be undone. Unsubmit an evaluation instead when it only needs changes.
Notifications and Automations
Inbox Cards
Full Fabric creates inbox cards for evaluations on its own, without any setup. They appear under Evaluations in the inbox, with a View evaluation (or View evaluations) button.
| Event | Who gets a card |
|---|---|
| Assigned | The evaluator ("assigned you the evaluation of" the applicant). Assignments of the same template made within an hour are gathered on one card ("assigned you N evaluations"), so a bulk assignment is a single alert. |
| Submitted | The owners of the applicant's journeys, the staff following the applicant's profile, and whoever assigned the evaluation (or created it, when nobody did). The card says the applicant "was evaluated by" the submitter. One card per evaluation. |
The staff member who acted never gets a card about their own action, and nobody gets a card about an evaluation they cannot open. No cards are created for AI agent evaluations. Reassigning or unassigning an evaluation, or deleting it, takes it off the previous evaluator's card.
Automations on a Template
Each evaluation template has an Automation tab in its settings, with two triggers:
| Trigger | Fires when |
|---|---|
| evaluation is assigned | An evaluation of the template is started with an evaluator, or assigned to a new one. |
| evaluation is submitted | An evaluation of the template is submitted. |
Besides the general actions (Send email to profile, Send email to staff, Add tag to profile, Wait), these automations offer Send email to assigned evaluator: an email to the evaluator from a shared email template, with the Sender email, Sender name and Subject you set.
Emails sent from these automations can use the evaluation merge fields Evaluation link, Evaluation template, Assignee's first name, Assignee's last name and Assignee's email.
Besides all actions have been completed, a workflow on an evaluation template can exit when the evaluation is submitted or reassigned, the evaluation is submitted, or the evaluation is reassigned. An exit applies only to the evaluation that started the workflow: for example, a reminder workflow started when an evaluation is assigned stops once that evaluation is submitted. See Automation.