# Understand rubric judgments
Generated: 2026-11-13T08:01:28.224Z
Source build: local
Canonical docs: https://teammately.ai/docs
---
id: workflow.benchmark-evaluations.rubric-judgments
title: Understand rubric judgments
summary: Read the applicable criterion and observed behavior before interpreting a pass, failure, or score.
kind: task
product_area: benchmark_evaluations
status: stable
updated: 2026-11-11
canonical: /docs/benchmark-evaluations/rubric-judgments
---
# Understand rubric judgments
Read the applicable criterion and observed behavior before interpreting a pass, failure, or score.
## Prerequisites
A Run with recorded responses and available rubric judgments.
## Steps
1. Open the relevant Case from Results or the Run and read the response or captured trajectory.
2. Inspect the Policy, Rubric, applicability, and stated reason for the judgment.
3. Check completeness, mandatory requirements, and the Project’s scoring treatment before comparing aggregate results.
4. When a judgment needs correction, use the existing judgment-correction workflow and inspect the resulting history and recalculated result.
## Object and state changes
A rubric assessment, a human judgment correction, a changed standard, and a new Run retain distinct identities and histories.
## Success criteria
The team can explain the judgment from the actual behavior, applicable criterion, and scoring configuration.
## Common failure modes
Treating incomplete execution as a scored failure; changing a standard to hide a bad response; reading an aggregate without its applicability.
## Related reference pages
{% related-card-grid title="Continue this workflow" %}
- [Inspect outputs and recorded trajectories](/docs/benchmark-evaluations/inspect-results)
{% /related-card-grid %}
## Related troubleshooting pages
{% related-card-grid title="Resolve a problem" %}
- [Permissions troubleshooting](/docs/troubleshooting/permissions)
- [Benchmark run troubleshooting](/docs/troubleshooting/benchmark-runs)
{% /related-card-grid %}
---
id: benchmark-evaluations.inspect
title: Inspect outputs and recorded trajectories
summary: Trace scores to exact responses and rubric judgments, distinguish incomplete results, and record authorized corrections.
kind: task
product_area: benchmark_evaluations
status: stable
updated: 2026-11-11
canonical: /docs/benchmark-evaluations/inspect-results
---
# Inspect outputs and recorded trajectories
Start with identity and completeness, then explain the score from the response, captured actions, and applicable Rubrics.
## Prerequisites
- Access to the selected Benchmark Version and Run.
- Available responses or evaluation progress.
- Project-management permission if a judgment correction is needed.
## Steps
1. Open Runs and confirm the candidate, saved Harness Version where present, machine and planned Trials.
2. Identify whether this is the Run used for score or another independent execution.
3. Open Results and inspect the Case population, applicable criteria and incomplete count.
4. Read failed gates, earned positive points and triggered penalties separately.
5. Open the response and rubric detail. For a response criterion, inspect the answer and visible Case materials. Choose **Inspect recorded steps** for the selected Case or individual Trial judgment. Read recorded model turns, tool arguments and results, and delegated work where captured. The judgment's references identify cited steps. Check capture status to understand which behavior was recorded.
6. Inspect individual Trial outcomes when reading a repeated result.
7. Decide whether the responsible change belongs to candidate code, Case content, applicability, rubric wording or the observed judgment.
## Scores and missing results
An absent trajectory does not establish that an action did or did not happen.
Interpret a response or trajectory judgment using the recorded material its
criterion requires. Captured tool calls and execution steps remain distinct from
private model reasoning.
**Recorded observations used by the AI evaluation** identifies the saved AI evaluator view. A later manual correction retains that original AI assessment. **Recorded execution** identifies the associated execution when the judgment has no saved observation view. Keep these distinct when explaining an older result. A missing source record is reported separately from the availability of the judgment itself.
Point scores can be negative, including below -100% for mixed positive/penalty Cases. A completed mandatory-gate failure contributes zero to the benchmark score. Missing or incompatible judgments stay incomplete even when another gate has failed.
The full planned population remains the denominator. An incomplete evaluation cannot be made comparable by ignoring its difficult or failed executions.
## Correct a judgment
An authorized project manager can choose **Correct judgment** on the exact Trial's rubric result and supply the supported corrected judgment and rationale. The original AI judgment and manual change remain recorded. Reopen the refreshed result to interpret its resulting scores consistently.
Changing the judgment is different from editing the Rubric or the Case. Correct the owning artifact when its meaning is wrong.
## Object and state changes
Inspection and filtering do not mutate results. A judgment correction records an attributable authoritative change. Starting a Contribution or an improvement Session creates separate work and preserves the inspected Run.
## Success criteria
- The conclusion identifies its Run, Trial and Benchmark Version.
- Scores are explained by applicable criteria and the configured Regime.
- Missing telemetry and judgments remain unknown.
- Corrections retain original judgment provenance.
## Common failure modes
- Reporting a rank without completeness.
- Assuming all results are read-only.
- Treating a gate failure as permission to replace unavailable results with zero.
- Inferring hidden model reasoning from a captured trajectory.
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Evaluation Results](/docs/benchmark-evaluations/results)
- [Run Details and Metadata](/docs/benchmark-evaluations/run-details)
- [Rubric Points and Benchmark Scores](/docs/correctness-governance/scoring)
{% /related-card-grid %}
## Related troubleshooting pages
{% related-card-grid title="Related troubleshooting pages" %}
- [Benchmark Results Changed Unexpectedly](/docs/troubleshooting/benchmark-results-changed-unexpectedly)
- [Overlapping Rubrics](/docs/troubleshooting/overlapping-rubrics)
{% /related-card-grid %}
---
id: troubleshooting.permissions
title: Permissions troubleshooting
summary: Separate Project membership from Expert Contribution assignment and readiness when an expert has no tasks available.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-11-06
canonical: /docs/troubleshooting/permissions
---
# Permissions troubleshooting
Use this when project role, reviewer assignment, or approval ownership prevents someone from completing the intended work.
## Symptom
A user can access Teammately but cannot open the expected Project, or an expert reports **no tasks available** after opening their Contribution link. These symptoms belong to different owning surfaces.
## Likely causes
- The user lacks the required Project permission through a direct grant, workspace group, or workspace role.
- The Contribution was requested for a different recipient.
- The Contribution exists but its next Task or Checkpoint is not ready.
- The current IP is blocked before Project membership is evaluated.
## Diagnostic checks
- Check direct grants in **Project Settings → Project Members**, the user's workspace-group membership, and the group's permission for the intended Project. Absence from the direct member list alone does not establish lack of access. Inspect workspace status and role in **Admin → Directory → Members** as well.
- Open the Contribution from the sender-side Expert Contributions workspace and verify its recipient and status.
- Check whether the expert has an executable Task or Checkpoint, not merely whether the Contribution exists.
- If **Access Restricted** is visible, resolve the IP allowlist first.
## Fix
- Add the correct individual workspace user under **Project Settings → Project Members** when direct Project membership is missing.
- If access is intended through a workspace group, confirm both the user's membership in that group and its permission for the intended Project.
- Correct the Contribution recipient through the owning Contribution workflow when the request went to the wrong person.
- Resolve lifecycle or readiness problems in Expert Contributions when access succeeds but no Task can be entered.
- Do not infer a permission from a role label or edit governed artifacts merely to make a control appear.
## Prevention
- Separate reviewer access from approval authority in review setup.
- Check assignments before launching a review session.
- Use a small pilot Contribution before assigning a larger specialist cohort.
- Keep project membership changes visible to review owners.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)
- [Expert Contributions](/docs/expert-contributions)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Permissions](/docs/reference/permissions)
- [Roles and Permissions](/docs/governance/roles-and-permissions)
- [Expert Contributions](/docs/expert-contributions)
{% /related-card-grid %}
---
id: troubleshooting.benchmark-runs
title: Benchmark run troubleshooting
summary: Diagnose a Run that cannot start, has no usable outputs, or produces results that cannot be compared safely.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-11-06
canonical: /docs/troubleshooting/benchmark-runs
---
# Benchmark run troubleshooting
## Symptoms
- The evaluation surface has no Benchmark Version to run.
- Output import or mapping cannot identify a Case or output column.
- A Run is created but remains empty, incomplete, or failed.
- Results appear under the wrong candidate label or Harness Version.
- Two Runs show a score change but do not share a comparable snapshot boundary.
## Likely causes
- No immutable Snapshot exists for the intended evaluation set.
- Imported outputs are mapped to the wrong Case or column.
- The saved Harness Version or candidate metadata does not match the evaluated system.
- The Run is partial, failed, or being compared across different Benchmark Versions.
## Check the boundary before the failure
1. Confirm the URL and page identify the intended Project, Benchmark, and Benchmark Version.
2. Open the Version or Snapshot and verify it contains the expected Cases and evaluators. If it does not, repair coverage and create a new Snapshot; do not edit the historical Run.
3. For managed execution, confirm the saved Harness Version and recorded settings. For imported results, confirm that the external candidate context describes the system that produced the submitted responses.
4. If importing outputs, inspect the mapping preview. Match the Case identifier and candidate-output column deliberately; do not use a reference-output column as candidate behavior.
5. Open Run detail and inspect status, Case count, errors, metadata, and per-Case results before trusting aggregates.
## Fix
- **No runnable version:** finish Case selection and create a Snapshot first.
- **Missing imported outputs:** append only missing Cases to an uncompleted Trial using the exact manifest IDs. Correcting an accepted response or adding Cases after completion requires a new Trial in the external Run or a new Run. Preserve the original results.
- **Wrong Harness or metadata:** create a correctly configured Run. Do not relabel completed results to represent a different system.
- **Partial managed failure:** inspect and preserve the existing Run's recorded outcomes. For another independent execution under unchanged conditions, use **Run again**. **Run evaluation** reopens matching work, including failed work. Publish a new Harness Version when its code changes, or create a new Snapshot and Benchmark Version when Case content or criteria change.
- **Confusing comparison:** compare the Benchmark Version, Harness Version, candidate metadata, and evaluator boundary. Qualify or avoid the comparison when more than the intended variable changed.
## Prevention
Create a Snapshot before evaluation. For managed execution, save the exact Harness Version. For imported results, preserve external candidate context and preview the mapping on representative Cases. Before comparing, confirm that every difference between the two Runs is intentional and visible.
## Recovery check
Open the recovered Run and sample several Case results. Confirm the displayed input, candidate output, reference output where present, applicable Rubrics, and metadata all belong together. A completed status alone does not prove correct mapping.
{% example-demo title="Example: scores drop after output import" %}
A team imports a new candidate file and sees a sudden score collapse. Run detail shows that the column containing reference outputs was mapped as candidate output. The operator creates a new Run, maps the actual candidate column, preserves the mistaken Run as an identifiable failed attempt, and compares only the corrected Run with the prior candidate under the same Benchmark Version.
{% /example-demo %}
## Related task pages
{% related-card-grid title="Related workflows" %}
- [Run a Benchmark Evaluation](/docs/benchmark-evaluations/run-evaluation)
- [Import External Evaluation Outputs](/docs/benchmark-evaluations/output-mapping)
- [Inspect Evaluation Results](/docs/benchmark-evaluations/inspect-results)
- [Evaluation Results](/docs/benchmark-evaluations/results)
- [Run Details and Metadata](/docs/benchmark-evaluations/run-details)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference" %}
- [Benchmarks and versions](/docs/concepts/benchmarks-and-versions)
- [Benchmark snapshots](/docs/coverage-engineering/benchmark-snapshots)
- [Outputs](/docs/object-model/outputs)
{% /related-card-grid %}