# Rewrite the returns policy in plain English

> Use when your returns policy is legally fine but customers keep asking support what it means.

## Fill in before running

- `{{CURRENT_POLICY_TEXT}}`
- `{{JURISDICTION_AND_RIGHTS}}`
- `{{HOW_RETURNS_ACTUALLY_WORK}}`

## Prompt

```
Rewrite this returns policy so a customer can act on it without contacting support.

Current policy:
{{CURRENT_POLICY_TEXT}}

Jurisdiction and statutory rights that must be preserved: {{JURISDICTION_AND_RIGHTS}}
Actual operational process: {{HOW_RETURNS_ACTUALLY_WORK}}

Produce:
1. THE SHORT VERSION - 5 bullets a customer can read in 15 seconds: window, condition required, who pays postage, how the refund arrives, how long it takes.
2. HOW TO RETURN SOMETHING - numbered steps, one action each.
3. EXCEPTIONS TABLE - Item type | Can it be returned | Why not | What we do instead.
4. FULL POLICY - the complete rewritten text, plain language, headed sections.
5. CHANGE LOG - every place the meaning could have shifted from the original, listed for legal to check.

Rules:
- Do not remove or weaken any statutory right, deadline or obligation in the original.
- Do not add a rule that is not in the original or in the operational process. If the two disagree, list the conflict rather than resolving it.
- Replace passive constructions with who does what.
- Mark anything you are unsure of with [LEGAL CHECK].
- No em dashes.
```

## Getting a better result

- The change log is what gets this signed off. Without it legal rejects the rewrite unread.
- Feed in the real process, not the documented one - most confusion comes from the gap between them.
- Publish the short version above the fold and keep the full policy below it on the same page.

---

From the QuQi prompt library - https://www.quqi.io/prompts/returns-policy-plain-english