> ## Documentation Index
> Fetch the complete documentation index at: https://docs.attensira.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Before and after: re-reads

> How Attensira checks whether a shipped change moved anything: three re-reads at +7, +14 and +30 days, each comparing a week before the change with a week around the re-read date, only once the change is live.

A change shipping is not the same as a change working. After something ships, Attensira reads the same tracked prompts again and compares them with how they read before. That comparison is the only place the product uses movement words.

## What starts the re-reads

Re-reads start when a change reaches the world:

* a pull request Attensira opened is **merged**;
* a rewrite, an article or a copy item is **marked shipped** with its live URL;
* an article is **published through a connector** such as [Notion](/agent/notion);
* an [off-site placement](/agent/off-site#how-a-placement-is-verified) is **verified**.

The re-reads cover the tracked prompts attached to the change (for a pull request, the `prompt_ids` given to `propose_fix`). A shipped change with no tracked prompts attached is not re-read.

## Three re-reads: +7, +14 and +30 days

Each change is re-read three times, at **+7**, **+14** and **+30** days after it shipped.

Each re-read compares two windows of the prompt's daily reading slots:

* **Before:** the 7 slot days before the change.
* **After:** 7 slot days centred on the +N date.

A re-read is read, and its verdict sent, only once its after-window has fully happened: about 4 days after the +N date, so around **day 11, day 18 and day 34**. Both windows always end on or before the day it is read.

Every verdict states its sample size (`n`), and none is a day-over-day comparison.

## Is the change live?

Before measuring, the re-read checks that the change is on the live page:

* For a **rewrite** or **copy**, the exact new text must appear on the page.
* For a **new article**, the page must load with content.

If the change is not live, that re-read is recorded as **Not live yet**, with the reason in terms of what happened ("merged, but the new text is not on the page yet"), and nothing is measured.

## The verdicts

| Verdict               | Meaning                                                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Moved**             | Named more often after the change, on X of N prompt and engine pairs, across M answers, past the significance test |
| **Fell**              | Named less often, past the same test                                                                               |
| **No change**         | The before and after windows do not differ past the test                                                           |
| **Too close to call** | A difference inside the noise                                                                                      |
| **Too few answers**   | Not enough readings from before the change to compare against                                                      |
| **Not live**          | The change was not found on the live page, so nothing was measured                                                 |
| **Re-read booked**    | Not read yet; the date shown is the day it will be read                                                            |

Every result is a single dated reading. A **Moved** verdict is what lets the [morning brief](/agent/morning-brief), the [receipt](/account/receipt) and the [win plan](/measure/win-this-answer) use movement wording at all.

## How a verdict reads

Each verdict, in its email and in the action log, opens with the windows it compared:

> Re-read at +14 days, read on 2026-10-06: 2026-09-15 to 2026-09-21 before the change, against 2026-09-26 to 2026-10-02 after it.

## Where you see them

* **Work → Shipped**: each shipped item shows its latest re-read result, or **Re-read booked** with its date. See [Work](/agent/inbox#shipped).
* **The prompt page**: **Before and after** lists this prompt's re-reads with their samples, windows and outcome. See [Prompts](/tracking/prompts#the-prompt-page).
* **The morning brief**: **What we read again, and when**, at most five prompts, soonest first.
* **The win plan**: `rereads_at` is the day the next booked re-read for that prompt is actually read.
* **Client reports**: the re-read verdicts are the only place a [client report](/agencies/client-reports) uses movement language.