Skip to main content
Scope of this page. This page covers how metric results translate into evaluation success or failure — pass/fail thresholds, AND/OR rules across multiple metrics, and which metrics affect call success. For building individual metric definitions, see Building High-Fidelity Metrics. For the data shape each metric type returns (Boolean, Rating, Numeric, Enum), see Output Types of Metric.

​
What is Rubric Configuration?

Rubric Configuration allows you to define exactly when an evaluation should be marked as successful or failed. Instead of using default logic, you can create custom rules based on multiple metrics, set specific thresholds, and combine conditions with AND/OR logic.

​
Why Use Rubric Configuration?

  • Define success criteria tailored to your use case
  • Combine multiple metrics to determine overall success
  • Set specific thresholds for different metric types
  • Automatically pass/fail evaluations based on your rules

​
Which Metrics Affect Call Success

A metric affects evaluation success only when it has an active rule in the Rubric. Adding a rule for a metric makes it part of the pass/fail outcome: if the metric’s score does not meet the configured threshold, the evaluation is marked as a failure. Metrics without a Rubric rule are still evaluated and their scores are visible in results, but they do not affect whether the evaluation passes or fails. To make a metric affect call success, navigate to the Rubric and add a rule for that metric with an appropriate operator and threshold value (see Configuring Your Rubric below). To configure a rubric for your project:
  1. Click on the Rubric tab
Rubric Configuration Navigation

​
Configuring Your Rubric

The rubric configuration page allows you to define rules for each metric in your project. Rubric Configuration Interface

​
Components

Each rule consists of:
  • Metric: Select which metric to evaluate
  • Operator: The comparison operator (e.g., greater than or equal, less than or equal, equals, in)
  • Value: The threshold or expected value

​
Common Examples

​
Example 1: All Boolean Metrics Must Pass

For evaluations to succeed, all binary metrics must have a score of 5 (success):
  • Rule 1: Workflow Adherence score greater than or equal to 5
  • Rule 2: Task Completion score greater than or equal to 5

​
Example 2: Acceptable Latency Threshold

Require low latency in addition to workflow adherence:
  • Rule 1: Workflow Adherence score greater than or equal to 5
  • Rule 2: Latency score less than or equal to 2000

​
Auto-Added Metrics

​
Projects

For Projects, all default predefined metrics are automatically added to your rubric with appropriate success conditions. This gives you a ready-to-use rubric configuration from day one.

​
New Boolean Metrics

When you create new boolean metrics (Binary Qualitative or Binary Workflow Adherence), they are automatically added to your rubric with a default success condition:
  • Operator: greater than or equal
  • Value: 5
This ensures new critical metrics are immediately included in your success evaluation.

​
Tips

Start Simple: Begin with basic rules (e.g., all boolean metrics greater than or equal to 5) and add complexity as needed.
Test Your Rubric: After configuring, run evaluations and check if pass/fail results match your expectations.
Use Meaningful Thresholds: Base thresholds on real requirements, not arbitrary numbers. For example, if 2000ms is your SLA, use that value.
Match the operator direction to the metric’s interpretation: For “lower is better” metrics (such as Unnecessary Repetition Count or Latency), use “less than or equal to” so the evaluation passes when the value is low and fails when it is too high. Using “greater than or equal to” on a “lower is better” metric will cause failures even when the score is 0 — the best possible result. For “higher is better” metrics (such as boolean pass/fail scores), use “greater than or equal to”. See the Interpretation field on each metric in Pre-defined Metrics for guidance, and this FAQ entry for a worked example of the mismatch symptom.

​
Metric Skipping

The rubric automatically skips certain metrics:
  • Metrics with null/empty values
  • Metrics marked as irrelevant
When all rules are skipped, the evaluation defaults to success.

​
Next Steps

Metrics Overview

Learn about different metric types

Test Profile

Configure test identities