---
id: coverage-management.case-review
title: Review Prepared Cases
summary: Inspect generated inputs and materials against their captured coverage purpose before relying on benchmark membership.
kind: task
product_area: coverage_management
status: stable
updated: 2026-10-30
canonical: /docs/coverage-design/case-review
---

# Review Prepared Cases

Review prepared Cases for the input situation they actually demonstrate. Preparation success, current inclusion and sufficient coverage are separate conclusions.

## Prerequisites

- Prepared candidates and their captured coverage context.
- Permission to manage benchmark membership.
- The Project Input Schema and required materials used for preparation.

## Inspect candidates

Read the canonical input, source relationship, facet assignments and stated fit to the tuple or requirement. Check required files and values rather than assuming a completed generation produced usable materials.

Remove a candidate that is redundant, unsupported or misplaced through the available controls. Inclusion should reflect a deliberate decision about the current editable dataset. It does not change an older Snapshot.

For a tuple that still lacks suitable Cases, generation can append candidates and regeneration can replace the preparation proposal according to its displayed source mode. Preserve whether material was retrieved, reused or synthesized.

## Materials and compatibility

Project Input Schema owns material keys, accepted families and extensions. A required material must be present and usable. Accepted extensions are alternatives, not a demand to generate every listed format.

Generated-material status and Case status may settle at different times. A partial or failed attachment is not a complete Case. Use the reported failure to correct the owning source or contract rather than silently dropping the required material.

## Object and state changes

Review changes candidate inclusion or editable membership through the owning operation. Additional preparation records another captured request. A Snapshot freezes the selected Cases only when explicitly created.

Cases staged by an Inbox generation have a separate adoption decision in Inbox. Completing generation alone does not add those Cases or resolve the source observation.

## Success criteria

- The input demonstrates its intended situation without invented assumptions.
- Required materials are inspectable and conform to the captured contract.
- Current membership matches the review decision.
- Repeated or generated Cases retain their source relationship.

## Common failure modes

- Accepting a candidate because its card exists.
- Using count completion as proof of distinct coverage.
- Confusing generated material with approved correctness.
- Treating a Case correction as a mutation of historical Runs.
## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Coverage Design](/docs/coverage-design)
- [Input Coverage Inbox](/docs/coverage-design/inbox)
- [Case Foundry](/docs/coverage-design/case-foundry)
- [Project Input Schema](/docs/project-settings/input-schema)
{% /related-card-grid %}

## Related troubleshooting pages

{% related-card-grid title="Related troubleshooting pages" %}
- [Unclear Cases](/docs/troubleshooting/unclear-cases)
- [Synthetic Cases That Feel Unrealistic](/docs/troubleshooting/unrealistic-synthetic-cases)
{% /related-card-grid %}