# AI Project Brief Template / Шаблон брифа на AI-проект

Use this file before discovery, vendor review or first estimate. Score each row from 0 to 3.

| Section | Question | Current answer | Evidence / source | Owner | Score 0-3 | Next action | Decision |
| --- | --- | --- | --- | --- | ---: | --- | --- |
| Business outcome | What business result should change? |  |  |  |  |  |  |
| Current workflow | What trigger, user, tool, decision and output exist today? |  |  |  |  |  |  |
| Users and roles | Who requests, reviews, approves and owns changes? |  |  |  |  |  |  |
| Data sources | Which documents, records, fields or messages can be used? |  |  |  |  |  |  |
| Privacy boundary | What must not be sent to an AI model or external service? |  |  |  |  |  |  |
| Integrations | Which systems are read-only and which systems can be written to? |  |  |  |  |  |  |
| AI behavior | Should AI draft, classify, retrieve, summarize, route or act? |  |  |  |  |  |  |
| Evaluation | What good and bad examples should be tested? |  |  |  |  |  |  |
| Approval gates | Which outputs require human review before action? |  |  |  |  |  |  |
| Risk and fallback | What happens if AI is wrong, slow or uncertain? |  |  |  |  |  |  |
| Rollout path | What is audit, prototype, pilot and production scope? |  |  |  |  |  |  |
| Ownership | Who owns repo, docs, logs, support and changes after launch? |  |  |  |  |  |  |

## Readiness scale

| Score | Meaning | Use |
| --- | --- | --- |
| 0 | Unknown | Stop production estimate and clarify |
| 1 | Draft | Validate in discovery |
| 2 | Reviewable | Contractor can check assumption |
| 3 | Ready | Scope can move to technical review |

## Routing rule

- Any 0 in data, permissions, write actions, approval or rollback: run audit first.
- Many 1 scores in workflow or users: run discovery workshop.
- Weak evaluation: build evaluation set before implementation.
- Weak ownership: define logs, support owner and change process.
- Mostly 2 and 3: request audit, prototype or controlled pilot proposal.