# AI answer and handoff review notes

Original fictional review pack from Derrick.dk, 20 October 2026.
The pack does not call a model, establish a pass rate or prove a production system's accuracy.

## Agree the response choices

- Answer when allowed evidence supports the relevant claim.
- Ask a clarifying question when a specific ambiguity blocks the answer.
- Explain missing information when no adequate source or authorised account record is available.
- Use a human handoff only when that route actually exists. Distinguish a draft message, an attempted send and confirmed delivery.

## Run and review

Use controlled data and the actual source permissions. Keep the response, supporting passage, source version, implementation version and reviewer judgement. Check correct answers as well as missing, conflicting and inaccessible information. A link or an apology alone does not establish a good result.

## Revisit when things change

Rerun relevant cases after changes to sources, retrieval, prompts, models, permissions or connected tools. A removed policy should not survive as an apparently current answer. A newly supplied answer should reduce the need for the missing-source response in that case.

## Own the unresolved question

Name who reviews repeated gaps and whether the response needs better help content, a human decision or a real account capability. Use the product's appropriate data handling rules when retaining questions. Do not create an unattended second support inbox.