# Team-confirmed answer record

Keep the answer, its evidence and the people who checked it together. Use one record per question in your existing team tools.

**Status: draft / confirmed / needs review**

Record ID: [internal reference] | Version: [version] | Owner: [name] | Updated: [YYYY-MM-DD]

## 1. Question and context

Exact question, client/project, period and applicable contract or policy version.

[Complete here]

## 2. Answer and limits

Established facts, conditions and unresolved points. Do not mark a draft as confirmed.

[Complete here]

## 3. Sources

For each fact: source link or reference, section/message/record, version and date checked. Keep restricted evidence in its authorized location.

[Complete here]

## 4. Confirmations

Name, role, specific fact checked, source reference and confirmation date for each person.

[Complete here]

## 5. Access

Who may read/reuse this answer? List restricted evidence and the authorized owner to contact.

[Complete here]

## 6. Review triggers

What changes require another check? Name the owner and record the next check, if useful.

[Complete here]

## Before reuse

- [ ] The question and conditions still match.
- [ ] The evidence is still applicable and available.
- [ ] The reader is authorized to receive the answer.
- [ ] No unresolved change affects the confirmations.

If a check fails or is uncertain, mark the answer for review. A confirmation never widens source permissions.

Change log: [date] | [what changed] | [new evidence] | [who checked it]

Free to copy and adapt for your team, including commercial work. Cite QAIZEN if sharing the template publicly; attribution is appreciated, not required. No signup required.

QAIZEN: https://qaizen.io/blog/reuse-confirmed-answers