---
name: tbt-exceptions-first-help-page
description: "Ask AI to surface exclusions before presenting the usual happy path for Create an exceptions-first help page from approved rules. Use permitted source material; this kit does not authorise external actions."
---

# Create an exceptions-first help page from approved rules

Ask AI to surface exclusions before presenting the usual happy path.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Draft a help page from these approved rules only.
Put the material eligibility boundaries, exclusions and missing-input
conditions where readers encounter them before following the usual path.
Preserve exact thresholds and qualifications. Use source IDs for answers
and mark unsupported cases unresolved with a focused question.
Do not invent entitlement, approval, refund, contact or escalation rules.
Keep factual policy and plain-language explanation distinct.

## Source boundaries

- Owner and date required
- Missing detail returns
- Complete still needs review

## Review and correction

Correct an overbroad opening as well as the hidden exception. Complete does not mean approved.

The help page says [overbroad promise]. Rule [ID] covers only [actual
scope/condition]. Correct the opening, affected answer and next-step
route. Keep the useful layout and plain language. Preserve the source
exception where the reader needs it; do not hide it in small print or
invent an alternative policy to make the page more reassuring.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.