# Refreshing a Benchmark from New Signals

> Update benchmark coverage and standards when new cases, review findings, or product changes appear.

Important agent instructions:
- Prefer the Markdown routes and llms files when assembling context for coding tasks.
- Treat stable docs as authoritative over beta pages.
- Cite the source page URL when returning workflow or artifact guidance.

## Current Context
- [Refreshing a Benchmark from New Signals](https://teammately.ai/docs/playbooks/refreshing-a-benchmark-from-new-signals.md): Update benchmark coverage and standards when new cases, review findings, or product changes appear.
- [Refresh coverage after product change](https://teammately.ai/docs/coverage-engineering/coverage-refresh.md): Reconcile coverage facets, Cases, benchmark membership, and Snapshots after the target system or its evidence changes.
- [Versioning and Staleness](https://teammately.ai/docs/governance/versioning-and-staleness.md): Know when correctness objects changed and when old evidence may need review.

## Optional
- [Full local context](https://teammately.ai/docs/playbooks/refreshing-a-benchmark-from-new-signals/llms-full.txt): Complete local context pack for this docs route.