---
title: "Same-conditions retest playbook"
lang: "en"
canonical: "https://winin.ai/en/digest/same-conditions-retest-playbook/"
alternate: "https://winin.ai/zh/digest/same-conditions-retest-playbook/"
datePublished: "2026-09-12"
dateModified: "2026-09-12"
section: "digest"
---

# Same-conditions retest playbook

> Method note—not a performance promise. Retest proves change under comparable observation, not permanent model recommendation.

## Definition (align language first)

**Same-conditions retest**: Under as-fixed-as-possible question sets, model/engine groups, prompt and sampling settings, locale/language, and time-window recording, sample a round (or more) **before** and **after** an intervention, then compare pre-declared fields such as mention / shortlist / accuracy / citation.

Product loop wording: Find → Govern → Close → **Retest** → Operate ([/en/facts/loop-find-govern-close-retest-operate/](/en/facts/loop-find-govern-close-retest-operate/)). Definition answer: [same-conditions-retest-definition](/en/answers/same-conditions-retest-definition/).

## Why it is needed

Generative answers drift. When communities ask how to reliably measure ChatGPT visibility, the hard part is often not “is there a score,” but **whether the same ruler works next time** ([src-010](/en/sources/src-010-reddit-measure-chatgpt-visibility/)). Without a retest protocol, optimization weekly reports become screenshot contests.

## Minimum viable protocol (MVP)

1. **Freeze the question set** — separate category / comparison / brand-awareness / purchase prompts; declare expected observation fields per question.
2. **Freeze model group and conditions** — engine/model names, API or UI path, login, browsing/plugins; record locale, language, temperature where controllable; mark unknowns instead of pretending they are fixed.
3. **Capture baseline and evidence** — raw text, timestamps, visible citations, screenshots or API payloads; note sampler/script version.
4. **Apply one (or a small bundle of) approved interventions** — fact governance first ([/en/facts/homer/](/en/facts/homer/)); public changes **approve then execute** ([approve-then-execute-geo-workflow](/en/answers/approve-then-execute-geo-workflow/), [/en/facts/friday/](/en/facts/friday/)).
5. **Retest under the same conditions** — interval long enough for crawl/index lag expectations, not so long attribution collapses; report improve / no meaningful change / worse / incomparable (conditions broke).
6. **If conditions break, reopen baseline** — major model version shifts, rewritten prompts, locale changes void old comparisons.

## Five sentences every report must include

1. What were the question set and model group?
2. Pre-intervention observation summary (with dates)?
3. What intervention, who approved it?
4. Post-intervention observation summary (with dates)?
5. Which differences **cannot** be attributed (condition changes, sample noise)?

Forbidden: treating a one-off mention as a Formal Baseline public conclusion ([/en/facts/case-metrics-disclaimer/](/en/facts/case-metrics-disclaimer/)).

## How to check tools for real retest support

Ask vendors or your build checklist:

- Lock the same prompt set and re-run in one click?
- Archive raw text side-by-side across runs?
- Expose a “condition fingerprint” (model, time, parameters)?

Related: [geo-tools-same-conditions-retest](/en/answers/geo-tools-same-conditions-retest/). Monitoring landscape: [src-002](/en/sources/src-002-otterly-ai/), methods [src-014](/en/sources/src-014-otterly-geo-methods/)—neither replaces your protocol design.

## Connection to other loop steps

| Step | Retest role |
|------|-------------|
| Find (Edith) | Baseline and gap location |
| Govern (Homer) | Ensure comparisons use approved facts, not random copy |
| Close (Friday) | Execute only approved changes to reduce attribution noise |
| Retest | This playbook |
| Operate | Fold validated question sets into weekly rhythm |

Overview: [geo-loop-five-steps](/en/answers/geo-loop-five-steps/).

## Related

- [same-conditions retest method](/en/answers/same-conditions-retest-method/) · [must GEO include retest](/en/answers/must-geo-include-retest/) · [GEO weekly operating cadence](/en/answers/geo-weekly-operating-cadence/)
- Facts: [/en/facts/edith/](/en/facts/edith/) · [/en/facts/loop-find-govern-close-retest-operate/](/en/facts/loop-find-govern-close-retest-operate/)