---
id: workflow.fieldloop.benchmark-coverage
title: Connect observed behavior to benchmark coverage
summary: Use investigated application behavior to decide which situations need coverage or expert follow-up.
kind: task
product_area: fieldloop
status: stable
updated: 2026-11-11
canonical: /docs/fieldloop/benchmark-coverage
---

# Connect observed behavior to benchmark coverage

Use investigated application behavior to decide which situations need coverage or expert follow-up.

## Prerequisites

An accessible Fieldloop Thread with captured sources and an identified coverage question.

## Steps

1. Read the report, original records, contrary examples, and relevant project objects.
2. Distinguish an input-coverage discovery from a correctness claim or an unsupported report paragraph.
3. Inspect supported coverage findings in Coverage Design Inbox. Review the situation and requested preparation before accepting follow-up.
4. Inspect prepared Cases and adopt dataset changes through the normal review path. Request expert judgment separately when expected behavior is unresolved.

## Object and state changes

Reading a Thread changes no dataset. A coverage discovery, accepted preparation, reviewed Case, and dataset adoption retain separate states.

## Success criteria

The resulting benchmark change has a traceable coverage reason and an explicit adoption decision.

## Common failure modes

Treating recent traffic as the full target population; treating report prose as an approved standard or automatic dataset mutation.

## Related reference pages

{% related-card-grid title="Continue this workflow" %}
- [Inspect Logs and Threads](/docs/fieldloop/threads)
{% /related-card-grid %}

## Related troubleshooting pages

{% related-card-grid title="Resolve a problem" %}
- [Fieldloop Intake and Processing](/docs/troubleshooting/fieldloop)
- [Unbalanced Coverage](/docs/troubleshooting/unbalanced-coverage)
{% /related-card-grid %}