# Test offer clarity with a five-second message check

**trustWF workflow pack** · Marketing

## Outcome
A test script, response-coding sheet, clarity findings, and a revised message draft.

## Who this is for
A marketer refining a short offer, headline, or promotional message before launch

## What to provide
Required: exact message, intended audience, desired customer action, and approved product facts. Optional: alternative versions and any brand or accessibility rules. Do not provide personal respondent data.

## Steps
1. Define the single message comprehension question and recruit a small set of suitable reviewers.
2. Collect unaided responses before explaining the offer; record words faithfully and anonymously.
3. Code confusion, recall, perceived benefit, and action clarity without treating the sample as representative.
4. Revise the message and list what should be retested.

## Copy-ready instructions
STAGE 1 — 1. Prepare a neutral test
When to use: Use before showing the message to reviewers.
Prompt: Help me prepare a small qualitative clarity check. Exact message to test: [paste]. Intended audience: [description]. Desired action: [action]. Approved facts and required wording: [list]. Generate a neutral test script that shows the message briefly and then asks no more than four non-leading questions about what the person remembers, what they think is being offered, who it is for, and what they would do next. Add a simple anonymous response sheet. Do not suggest the “right” answer to participants.
Expected return: A short facilitator script and response sheet.
User check: Check that questions do not reveal the answer or promise benefits absent from the message.

STAGE 2 — 2. Analyze collected responses
When to use: Use after you have real, anonymized responses.
Prompt: Here are anonymized responses from [number] people: [paste, one per ID]. Do not add or rewrite participant statements. For each response, code: offer understood, audience understood, benefit recalled, action clear, confusion or misinterpretation. Use Yes/Partial/No and quote only short phrases supplied. Then summarize recurring confusion and disagreements, stating the sample size.
Expected return: A response coding table and a concise pattern summary.
User check: Verify every quote against the submitted response and distinguish one-off feedback from repeated patterns.

STAGE 3 — 3. Revise and define retest
When to use: Use after checking the coding.
Prompt: Based on the response table and approved facts, propose up to three clearer message versions. For each, state what wording changed and which confusion it addresses. Do not add claims or urgency not supplied. Recommend one version for a second small comprehension check, plus the exact question that would show whether the main confusion improved. State that this check does not measure actual sales or conversion.
Expected return: Three labeled copy options, a recommended retest question, and a limitation note.
User check: Have the brand or product owner approve claims and check accessibility before external use.

## Review before using
A five-second check is a quick qualitative signal, not proof of conversion or market preference. Do not fabricate participant responses or expose identities.

---
Use the result as a draft. Review it for accuracy, context and any required approvals.