# Rechecks

A recheck is how Shruwd answers the only question that matters after you make a change:
did it work?

Access findings do not need one. Their fix shows up in your own logs, robots.txt or page,
and Shruwd resolves them when it does — see [How findings work](https://shruwd.io/docs/findings/how-findings-work.md).

## What happens after you mark a fix applied

1. **Your current numbers are captured as a baseline** — the metric values, their
   intervals, the sample size and the timestamp. This is the "before" the recheck compares
   against.
2. **Shruwd waits 14 days.** AI answer surfaces re-crawl and re-index on their own
   schedule. Rechecking on day two measures nothing and would report a false *did not
   move*.
3. **A recheck cycle runs** on the prompts the finding affects, at **nine repetitions**
   instead of the usual three. A small prompt subset needs the extra sampling for the
   result to be conclusive either way, and because the subset is small it is cheap.
4. **The verdict appears** in the finding's **Closed** tab.

> **Warning**
>
> Mark the fix applied only once the change is live. The baseline is captured at that
> moment, so marking it early compares your change against itself.

## Reading the verdict

| Verdict | Meaning |
|---|---|
| **resolved** | The numbers moved, and the movement passed both gates |
| **did not move** | The recheck ran and the change was not big enough or not distinguishable from noise |

The prompts are compared together and one by one. Together is the fix's own claim — it was
made for those prompts — and it is the comparison a recheck can usually decide: one prompt
alone rarely has enough answers to show anything but a very large change. A fix aimed at one
prompt still counts if that prompt moves on its own.

*Did not move* is a real result, not a failure of the product. Most single-page changes do
not shift a prompt-set-wide number by five percentage points, and saying so is the whole
reason for measuring.

A finding marked *did not move* **re-opens after 30 days** if the condition still holds,
noting that the previous fix did not work.

## Why a fix that looks like it worked is not called movement

The verdict uses the same rule as everything else in Shruwd: the intervals before and
after must not overlap, **and** the change must be at least five percentage points, after
correcting for the fact that many prompts are being checked at once.

See [When a number has moved](https://shruwd.io/docs/metrics/when-a-number-has-moved.md) for the full rule.

If the provider changed its underlying models between the baseline and the recheck, the
comparison is marked **model changed** — the difference may be the new model rather than
your fix.

## Recheck limits

Rechecks are capped per month by plan.

| Plan | Rechecks per month |
|---|---|
| Crawl | None |
| Starter | 1 |
| Pro | 6 |

If you are out, the finding waits until next month and says so on the fix panel. Spend
them on findings where you actually changed something substantial.

## Next steps

- [How findings work](https://shruwd.io/docs/findings/how-findings-work.md) — the full finding lifecycle
- [When a number has moved](https://shruwd.io/docs/metrics/when-a-number-has-moved.md) — the movement rule
- [Plans and limits](https://shruwd.io/docs/account/plans-and-limits.md) — what your plan includes